Thanks! I'm sure I can wipe out the card clean and start over, and if 
everything fails, get a new one.

My concern is that exactly following the instructions on 
elinux.org/Beagleboard yields a result that is (a) contrary to expectations 
and (b) potentially damaging to hardware. Moreover, it is insisted that 
this expansion step be followed.

On Friday, June 10, 2016 at 11:08:48 AM UTC-7, William Hermans wrote:
>
> There are a couple options here. 
>
> First, you can use dd to wipe out the first 1M or more, to get rid of both 
> partitions. But I'd use this as a last resort.
>
> Second, you can use fdisk to delete that partition, and start over again.
>
> If that is a 4G card, and showing a 7.1G partition. Thats definitely 
> wrong, and needs to be dealt with. I've had it happen to me once or twice, 
> manipulating partitions manually. Not sure how exactly, but in each case it 
> was fixable. 
>
> On Fri, Jun 10, 2016 at 11:02 AM, Vladimir Gusiatnikov <
> [email protected] <javascript:>> wrote:
>
>> On the Ubuntu machine:
>>
>> $ lsblk /dev/sdb
>> lsblk: /dev/sdb: not a block device
>> $ lsblk /dev/sdb1
>> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
>> sdb1   8:17   1  96M  0 part /media/vladimir/BEAGLEBONE
>> $ lsblk /dev/sdb2
>> NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
>> sdb2   8:18   1  7.1G  0 part /media/vladimir/rootfs
>>
>> On Friday, June 10, 2016 at 10:57:06 AM UTC-7, William Hermans wrote:
>>
>>> What does lsblk report for that scard ?
>>>
>>> On Fri, Jun 10, 2016 at 10:43 AM, Vladimir Gusiatnikov <
>>> [email protected]> wrote:
>>>
>>>> So I attempted to expand the partition on my 4 GB SD card (yes these 
>>>> still exist) according to 
>>>> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Expanding_File_System_Partition_On_A_microSD
>>>>  
>>>> <http://www.google.com/url?q=http%3A%2F%2Felinux.org%2FBeagleboard%3ABeagleBoneBlack_Debian%23Expanding_File_System_Partition_On_A_microSD&sa=D&sntz=1&usg=AFQjCNEeDwVst0WLU-HSqW-sghhCHyV0sg>,
>>>>  
>>>> and got the following results. I didn't capture the output and the 
>>>> operation seems to have been irreversible, so sorry about the inexact 
>>>> report. This was while running Linux beaglebone 3.8.13-bone79 #1 SMP Tue 
>>>> Oct 13 20:44:55 UTC 2015 armv7l GNU/Linux from the eMMC.
>>>>
>>>> Git pull didn't work because the board is not directly connected to the 
>>>> Internet because I am in a corporate setting and to get a hobbyist board 
>>>> wired to the corporate network would require multiple levels of slow 
>>>> approval. 
>>>>
>>>> The grow_partition.sh script reported that it wrote a new partition, 
>>>> but failed to verify it, or something similar. Again, sorry for the lack 
>>>> of 
>>>> captured output.
>>>>
>>>> After grow_partition.sh ran, Beaglebone's df reported a 7.2 GB drive 
>>>> with 1.9 GB used and 5.0 GB free. On this 4 GB card. Yes, I rubbed my eyes.
>>>>
>>>> When I then inserted this card into an Ubuntu laptop, I got the same 
>>>> report out of df: 7281280 1K blocks total, 1934304 used, 4999784 available 
>>>> on the rootfs partition.
>>>>
>>>> When I attempt to dd another image to this SD card, dd fails after 780 
>>>> MB is written. When I try to erase the partitions with cfdisk and create a 
>>>> new one, cfdisk offers a maximum of 780 MB.
>>>>
>>>> To my untrained eye it looks like grow_partition.sh has rendered this 
>>>> SD card partly inoperable.
>>>>
>>>> On Thursday, June 9, 2016 at 4:42:45 PM UTC-7, William Hermans wrote:
>>>>
>>>>>
>>>>>> *I didn't expand the partition since it seemed that wouldn't 
>>>>>> accomplish anything; the image was a 4 GB image obtained from 
>>>>>> https://debian.beagleboard.org/images/bone-debian-8.4-lxqt-4gb-armhf-2016-05-13-4gb.img.xz
>>>>>>  
>>>>>> <https://debian.beagleboard.org/images/bone-debian-8.4-lxqt-4gb-armhf-2016-05-13-4gb.img.xz>
>>>>>>  
>>>>>> that was actually about 3.6 GB in uncompressed size. The partition on 
>>>>>> the 4 
>>>>>> GB SD card was slightly bigger than that. Would expanding the partition 
>>>>>> have materially changed anything?*
>>>>>
>>>>>
>>>>> If your sdcard was larger than 4G of course it would have.
>>>>>
>>>>>
>>>>> On Thu, Jun 9, 2016 at 3:53 PM, Vladimir Gusiatnikov <
>>>>> [email protected]> wrote:
>>>>>
>>>>>> I didn't expand the partition since it seemed that wouldn't 
>>>>>> accomplish anything; the image was a 4 GB image obtained from 
>>>>>> https://debian.beagleboard.org/images/bone-debian-8.4-lxqt-4gb-armhf-2016-05-13-4gb.img.xz
>>>>>>  
>>>>>> that was actually about 3.6 GB in uncompressed size. The partition on 
>>>>>> the 4 
>>>>>> GB SD card was slightly bigger than that. Would expanding the partition 
>>>>>> have materially changed anything?
>>>>>>
>>>>>> On Thursday, June 9, 2016 at 1:39:06 PM UTC-7, RobertCNelson wrote:
>>>>>>>
>>>>>>> On Thu, Jun 9, 2016 at 3:17 PM, Vladimir Gusiatnikov 
>>>>>>> <[email protected]> wrote: 
>>>>>>> > Seems that I figured it out, for others' reference. The SD card 
>>>>>>> with the 
>>>>>>> > Jessie image that I was running off was 4 GB and filled up quickly 
>>>>>>> (with 
>>>>>>> > what? logfiles? errorlogs?), so the disk indeed became full. 
>>>>>>>
>>>>>>> Did you expand the image after booting? 
>>>>>>>
>>>>>>>
>>>>>>> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Expanding_File_System_Partition_On_A_microSD
>>>>>>>  
>>>>>>> <http://www.google.com/url?q=http%3A%2F%2Felinux.org%2FBeagleboard%3ABeagleBoneBlack_Debian%23Expanding_File_System_Partition_On_A_microSD&sa=D&sntz=1&usg=AFQjCNEeDwVst0WLU-HSqW-sghhCHyV0sg>
>>>>>>>  
>>>>>>>
>>>>>>> Regards, 
>>>>>>>
>>>>>>> -- 
>>>>>>> Robert Nelson 
>>>>>>> https://rcn-ee.com/ 
>>>>>>>
>>>>>> -- 
>>>>>> For more options, visit http://beagleboard.org/discuss
>>>>>> --- 
>>>>>> You received this message because you are subscribed to the Google 
>>>>>> Groups "BeagleBoard" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it, 
>>>>>> send an email to [email protected].
>>>>>> To view this discussion on the web visit 
>>>>>> https://groups.google.com/d/msgid/beagleboard/b892e9cc-1c9a-4589-b653-ba1f408aeb6c%40googlegroups.com
>>>>>>  
>>>>>> <https://groups.google.com/d/msgid/beagleboard/b892e9cc-1c9a-4589-b653-ba1f408aeb6c%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>> .
>>>>>>
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>>
>>>>> -- 
>>>> For more options, visit http://beagleboard.org/discuss
>>>> --- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "BeagleBoard" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to [email protected].
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/beagleboard/8bb1eadf-e1db-4288-9f70-2c7b4cc7ea3c%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/beagleboard/8bb1eadf-e1db-4288-9f70-2c7b4cc7ea3c%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> -- 
>> For more options, visit http://beagleboard.org/discuss
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/5afdd7b8-2435-4ad3-bff5-29bdd9e8f802%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/beagleboard/5afdd7b8-2435-4ad3-bff5-29bdd9e8f802%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/6a55a0e7-1621-4bf8-bd2c-75d3c1996425%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to