[arm-allstar] Partition resize issue

Wed Aug 27 22:07:03 EST 2014

Joel,

 Was the beginning default the same as the old partitions beginning? It has to be. Before you delete the old partition make note of that and make sure it is the same when you make the new one. Deleting and creating a partition does not mess with the data that is there but the new one has to start at exactly the same point as the old one.

I made note of this on the web page but I believe it is a fallacy that using the entire SD card helps with wear leveling. The the wear leveling is at a whole different level on the card. In other words the data is being wear leveled across the card regardless of the upper level partitioning. That is if there really is wear leveling on these cards at all! There is on solid state hard drives but it really isn't clear what is done on these cards. The bottom line though is that they are very reliable. I have had cards in use for a long time with no issues. Writes to the card are minimized as much as possible. 
73 Doug
WA3DSP
http://www.crompton.com/hamradio

Date: Wed, 27 Aug 2014 19:08:39 -0500
From: w0kgw3 at gmail.com
To: arm-allstar at hamvoip.org
Subject: Re: [arm-allstar] Partition resize issue

I just accepted the defaults for both start and end. It's more for allowing the OS to use the whole card for wear leveling and such.

On Wed, Aug 27, 2014 at 6:42 PM, Doug Crompton <doug at crompton.com> wrote:

Joel,

 Did you make the new larger partition start sector exactly the same as the one you deleted? Deleting a partition does not touch the data but the new partition has to start at exactly the same start sector. All you are doing when you create the new one is increasing the end sector. The filesystem still resides in its same size within the partition until you resize it after the reboot.

I am curious why you want to do this? It is really not necessary unless you need the space. You could also leave the current partition alone and create another new one starting one sector after it to the end of the SD card or whatever size you want less than that.

73 Doug
WA3DSP
http://www.crompton.com/hamradio

Date: Wed, 27 Aug 2014 17:50:42 -0500
From: w0kgw3 at gmail.com
To: arm-allstar at hamvoip.org

Subject: [arm-allstar] Partition resize issue

I'm following the guide which directed me to http://elinux.org/Beagleboard:Expanding_File_System_Partition_On_A_microSD to resize my partition.

It's erroring out, and I'm looking for any advise in case someone has run into this issue already. Card is a SanDisk Ultra, class 10, 8gb microSD card, attempted this twice with the same results. I restore from my backup image, and it's working fine but only at 4gb size.

I go through the steps, reboot immediately after writing in fdisk, and get the following on reboot on the serial console:

U-Boot SPL 2014.04-00015-gb4422bd (Apr 22 2014 - 13:24:29)
reading args
spl_load_image_fat_os: error reading image args, err - -1

reading u-boot.img
reading u-boot.img

U-Boot 2014.04-00015-gb4422bd (Apr 22 2014 - 13:24:29)

I2C:   ready
DRAM:  512 MiB
NAND:  0 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
*** Warning - readenv() failed, using default environment

Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw, usb_ether
Hit any key to stop autoboot:  0
gpio: pin 53 (gpio 53) value is 1
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1

SD/MMC found on device 0
reading uEnv.txt
574 bytes read in 5 ms (111.3 KiB/s)
gpio: pin 55 (gpio 55) value is 1
Loaded environment from uEnv.txt
Importing environment from mmc ...
Checking if uenvcmd is set ...

gpio: pin 56 (gpio 56) value is 1
Running uenvcmd ...
mmc0 is current device
jdm booting SD card!!!
Failed to mount ext2 filesystem...
** Unrecognized filesystem type **
Failed to mount ext2 filesystem...

** Unrecognized filesystem type **
Booting from mmc ...
Bad Linux ARM zImage magic!

uenvcmd was not defined in uEnv.txt ...
gpio: pin 56 (gpio 56) value is 0
gpio: pin 55 (gpio 55) value is 0
gpio: pin 54 (gpio 54) value is 0

Booting from mmc ...
Bad Linux ARM zImage magic!
Booting from nand ...

no devices available

no devices available
Bad Linux ARM zImage magic!
U-Boot#

_______________________________________________

arm-allstar mailing list
arm-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar

Visit the BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/ 		 	   		  

_______________________________________________

arm-allstar mailing list

arm-allstar at hamvoip.org

http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar

Visit the BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/

_______________________________________________

arm-allstar mailing list
arm-allstar at hamvoip.org
http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar

Visit the BBB web page - http://www.crompton.com/hamradio/BeagleBoneBlackAllstar/ 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20140827/c2435e7b/attachment.html>