Re: [beagleboard] Re: Expanding Root Partition - Bad magic number in super-block while trying to open /dev/mmcblk0p2

[Louis Whitcomb]

To build ROS Kinetic from source on the Beaglebone, in addition booting 
from the SD card (for extra flash space) you need to create and enable a 
swap file. A 1GB swap file seems to wrok fine.  Without a swap file the 
build of ROS Kinetic failed due to lack memory.   Instructions here:  
https://sheldondwill.wordpress.com/2013/12/14/beaglebone-black-ubuntu-adding-a-swapfile

On Wednesday, November 22, 2017 at 3:40:30 AM UTC, RobertCNelson wrote:
>
> On Tue, Nov 21, 2017 at 9:02 PM, Dariush Keivan 
>  wrote: 
> > I erased it. Now just 2 LEDS light up and I can not even connect to the 
> > beaglebone through SSH. 
> > What should I do now? 
>
> Now stick your flashed microSD and it'll boot from it.. 
>
> If it doesn't, let's start back with this image: 
>
>
> https://rcn-ee.com/rootfs/2017-10-12/microsd/bone-ubuntu-16.04.3-console-armhf-2017-10-12-2gb.img.xz
>  
>
> Use etcher.io to write teh *.img.xz directly to the microSD card.. 
>
> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/f5efce16-453c-427f-a231-693c20357cdc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Expanding Root Partition - Bad magic number in super-block while trying to open /dev/mmcblk0p2

[Robert Nelson]

On Tue, Nov 21, 2017 at 9:02 PM, Dariush Keivan
 wrote:
> I erased it. Now just 2 LEDS light up and I can not even connect to the
> beaglebone through SSH.
> What should I do now?

Now stick your flashed microSD and it'll boot from it..

If it doesn't, let's start back with this image:

https://rcn-ee.com/rootfs/2017-10-12/microsd/bone-ubuntu-16.04.3-console-armhf-2017-10-12-2gb.img.xz

Use etcher.io to write teh *.img.xz directly to the microSD card..

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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYiLwhUyWQc%3DPWewKRVGmphaDXxzouZPkWhQ5htnd%2BuD5A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Expanding Root Partition - Bad magic number in super-block while trying to open /dev/mmcblk0p2

[Dariush Keivan]

I erased it. Now just 2 LEDS light up and I can not even connect to the 
beaglebone through SSH.
What should I do now?

On Tuesday, November 21, 2017 at 8:48:09 PM UTC-6, RobertCNelson wrote:
>
> On Tue, Nov 21, 2017 at 8:44 PM, Dariush Keivan 
>  wrote: 
> > How can I erase eMMC? 
>
> sudo dd if=/dev/zero of=/dev/mmcblk1 
>
> after 2-3 minutes just hit ctrl-c, the "former" data on the partition 
> including the boot partition will be mostly zeros.. 
>
> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/980e4263-227e-4fb0-9ba2-c3f00169eb03%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Expanding Root Partition - Bad magic number in super-block while trying to open /dev/mmcblk0p2

[Robert Nelson]

On Tue, Nov 21, 2017 at 8:44 PM, Dariush Keivan
 wrote:
> How can I erase eMMC?

sudo dd if=/dev/zero of=/dev/mmcblk1

after 2-3 minutes just hit ctrl-c, the "former" data on the partition
including the boot partition will be mostly zeros..

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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYhBwb%3DNbcq%3DFDZ2Vksf3EBka53efn98iytN8iz6s9S4gQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Expanding Root Partition - Bad magic number in super-block while trying to open /dev/mmcblk0p2

[Dariush Keivan]

How can I erase eMMC?

On Tuesday, November 21, 2017 at 8:26:59 PM UTC-6, RobertCNelson wrote:
>
>
>
> On Nov 21, 2017 8:20 PM, "Dariush Keivan"  > wrote:
>
> It shows :
>
> root@beaglebone:~# sudo /opt/scripts/tools/version.sh 
> git:/opt/scripts/:[23650994e41b16bcf78253cde7d35a93664beeef]
> eeprom:[A335BNLT00C03615BBBK1DA3]
> model:[TI_AM335x_BeagleBone_Black]
> dogtag:[BeagleBoard.org Debian Image 2017-03-19]
> bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2017.03-dirty]
> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
> 2017.03-2-gd12b1519b4]
>
>
>
> There's the issue...
>
> Either hold down the boot button before you power the board, or erase the 
> eMMC.. (bootloader is to old for what we do now by default)
>
> Regards,
>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/f5eacfcc-9f25-49de-b607-0c48908a9799%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Expanding Root Partition - Bad magic number in super-block while trying to open /dev/mmcblk0p2

[Robert Nelson]

On Nov 21, 2017 8:20 PM, "Dariush Keivan"  wrote:

It shows :

root@beaglebone:~# sudo /opt/scripts/tools/version.sh
git:/opt/scripts/:[23650994e41b16bcf78253cde7d35a93664beeef]
eeprom:[A335BNLT00C03615BBBK1DA3]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Image 2017-03-19]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2017.03-dirty]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
2017.03-2-gd12b1519b4]



There's the issue...

Either hold down the boot button before you power the board, or erase the
eMMC.. (bootloader is to old for what we do now by default)

Regards,

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYiUs87wKZCe_0WCiUBKijsDLYA0dhnL1yBD2hGetBc9OA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Expanding Root Partition - Bad magic number in super-block while trying to open /dev/mmcblk0p2

[Dariush Keivan]

It shows :

root@beaglebone:~# sudo /opt/scripts/tools/version.sh 
git:/opt/scripts/:[23650994e41b16bcf78253cde7d35a93664beeef]
eeprom:[A335BNLT00C03615BBBK1DA3]
model:[TI_AM335x_BeagleBone_Black]
dogtag:[BeagleBoard.org Debian Image 2017-03-19]
bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2017.03-dirty]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
2017.03-2-gd12b1519b4]
kernel:[4.4.68-ti-r111]
nodejs:[v4.8.3]
pkg:[bb-cape-overlays]:[4.4.20170614.0-0rcnee0~jessie+20170614]
pkg:[bb-wl18xx-firmware]:[1.20170612-0rcnee0~jessie+20170612]
WARNING:pkg:[firmware-ti-connectivity]:[NOT_INSTALLED]

Any idea?


On Tuesday, November 21, 2017 at 7:39:47 PM UTC-6, RobertCNelson wrote:
>
> On Tue, Nov 21, 2017 at 5:46 PM, Dariush Keivan 
>  wrote: 
> > The problem is that the beaglebone does not recognize my SD card and it 
> says 
> > that there is not enough space. 
> > I used the same link for installation of ROS. I think the problem is 
> that my 
> > SD card is not shown under "df -h". 
> > Do you have any suggestion? 
>
> No that doesn't make any sense.. 
>
> run: 
>
> sudo /opt/scripts/tools/version.sh 
>
> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/0314f3f9-f93a-4615-af3c-0eba89c36491%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Expanding Root Partition - Bad magic number in super-block while trying to open /dev/mmcblk0p2

[Dariush Keivan]

The problem is that the beaglebone does not recognize my SD card and it 
says that there is not enough space.
I used the same link for installation of ROS. I think the problem is that 
my SD card is not shown under "df -h".
Do you have any suggestion?

On Tuesday, November 21, 2017 at 5:10:40 PM UTC-6, RobertCNelson wrote:
>
> On Tue, Nov 21, 2017 at 5:06 PM, Dariush Keivan 
>  wrote: 
> > I wanted to install Ros from source (since Ros Kinetic is not working on 
> > debian Jessie on beaglebone black), However, in the middle of the 
> > installation, it said that there is not enough space. 
> > Should I get another SD card (Like 32 GB)? 
>
> ROS: 
>
> Using your 64GB microSD, just follow: 
>
> https://dscl.lcsr.jhu.edu/home/courses/EduMIP_ROS 
>
> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/00358f67-3fca-4864-889d-9a4dd1ce894c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Expanding Root Partition - Bad magic number in super-block while trying to open /dev/mmcblk0p2

[Robert Nelson]

On Tue, Nov 21, 2017 at 5:06 PM, Dariush Keivan
 wrote:
> I wanted to install Ros from source (since Ros Kinetic is not working on
> debian Jessie on beaglebone black), However, in the middle of the
> installation, it said that there is not enough space.
> Should I get another SD card (Like 32 GB)?

ROS:

Using your 64GB microSD, just follow:

https://dscl.lcsr.jhu.edu/home/courses/EduMIP_ROS

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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYiYWLzahAWKnkfiykPDShx22XaHGv40i2aaKGy7HoDsQQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Expanding Root Partition - Bad magic number in super-block while trying to open /dev/mmcblk0p2

[Dariush Keivan]

I wanted to install Ros from source (since Ros Kinetic is not working on 
debian Jessie on beaglebone black), However, in the middle of the 
installation, it said that there is not enough space. 
Should I get another SD card (Like 32 GB)?


On Tuesday, November 21, 2017 at 5:00:15 PM UTC-6, RobertCNelson wrote:
>
> On Tue, Nov 21, 2017 at 4:56 PM, Dariush Keivan 
>  wrote: 
> > Hi Robert, 
> > 
> > Thanks for the prompt response. 
> > "lsblk" shows: 
> > 
> > root@beaglebone:~# lsblk 
> > NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT 
> > mmcblk1boot0 179:16   01M  1 disk 
> > mmcblk1boot1 179:24   01M  1 disk 
> > mmcblk0  179:00 59.5G  0 disk 
> > └─mmcblk0p1  179:10 59.5G  0 part 
> > mmcblk1  179:80  3.7G  0 disk 
> > └─mmcblk1p1  179:90  3.7G  0 part / 
> > 
> > The brand of "64GB SD card" is SDXC. You think the problem comes from 
> the 
> > "SDXC" ? 
> > What should I do now? 
>
> Not sure, what you "should" do, as it's right there.. 
>
> > mmcblk0  179:00 59.5G  0 disk 
> > └─mmcblk0p1  179:10 59.5G  0 part 
>
> aka the 64GB card.. 
>
> So what do you want to do with the 64GB card again? 
>
> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/69230521-3f87-40ec-863d-bddae4f9e83d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Expanding Root Partition - Bad magic number in super-block while trying to open /dev/mmcblk0p2

[Robert Nelson]

On Tue, Nov 21, 2017 at 4:56 PM, Dariush Keivan
 wrote:
> Hi Robert,
>
> Thanks for the prompt response.
> "lsblk" shows:
>
> root@beaglebone:~# lsblk
> NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
> mmcblk1boot0 179:16   01M  1 disk
> mmcblk1boot1 179:24   01M  1 disk
> mmcblk0  179:00 59.5G  0 disk
> └─mmcblk0p1  179:10 59.5G  0 part
> mmcblk1  179:80  3.7G  0 disk
> └─mmcblk1p1  179:90  3.7G  0 part /
>
> The brand of "64GB SD card" is SDXC. You think the problem comes from the
> "SDXC" ?
> What should I do now?

Not sure, what you "should" do, as it's right there..

> mmcblk0  179:00 59.5G  0 disk
> └─mmcblk0p1  179:10 59.5G  0 part

aka the 64GB card..

So what do you want to do with the 64GB card again?

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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYhTQt2ySzhBFwmKt8EEHmhKbDXt3wi%3Dz2kj8HM9R7n1cA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Expanding Root Partition - Bad magic number in super-block while trying to open /dev/mmcblk0p2

[Dariush Keivan]

Hi Robert,

Thanks for the prompt response.
"lsblk" shows:

root@beaglebone:~# lsblk
NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk1boot0 179:16   01M  1 disk 
mmcblk1boot1 179:24   01M  1 disk 
mmcblk0  179:00 59.5G  0 disk 
└─mmcblk0p1  179:10 59.5G  0 part 
mmcblk1  179:80  3.7G  0 disk 
└─mmcblk1p1  179:90  3.7G  0 part /

The brand of "64GB SD card" is SDXC. You think the problem comes from the 
"SDXC" ?
What should I do now?




On Tuesday, November 21, 2017 at 4:45:14 PM UTC-6, RobertCNelson wrote:
>
> On Tue, Nov 21, 2017 at 4:29 PM,   
> wrote: 
> > Hello all, 
> > 
> > I have 64GB SD card but it is not shown under filesystems (df -h): 
> > 
> > Filesystem  Size  Used Avail Use% Mounted on 
> > udev 10M 0   10M   0% /dev 
> > tmpfs98M  6.5M   92M   7% /run 
> > /dev/mmcblk1p1  3.6G  3.5G 0 100% / 
> > tmpfs   244M 0  244M   0% /dev/shm 
> > tmpfs   5.0M  4.0K  5.0M   1% /run/lock 
> > tmpfs   244M 0  244M   0% /sys/fs/cgroup 
> > 
> > I created one partition that uses all the available space. 
>
> what does "lsblk" show? 
>
> What "brand" 64GB SD? (64GB are SDXC cards) 
>
> The am335x ip only "supports" SDHC cards.. (which is spec'd up to 32GB) 
>
> While some "SDXC" cards do work, there is no guarantee! 
>
> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/d88b9ed8-7241-4050-9ce1-255bc56cff05%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Expanding Root Partition - Bad magic number in super-block while trying to open /dev/mmcblk0p2

[Robert Nelson]

On Tue, Nov 21, 2017 at 4:29 PM,   wrote:
> Hello all,
>
> I have 64GB SD card but it is not shown under filesystems (df -h):
>
> Filesystem  Size  Used Avail Use% Mounted on
> udev 10M 0   10M   0% /dev
> tmpfs98M  6.5M   92M   7% /run
> /dev/mmcblk1p1  3.6G  3.5G 0 100% /
> tmpfs   244M 0  244M   0% /dev/shm
> tmpfs   5.0M  4.0K  5.0M   1% /run/lock
> tmpfs   244M 0  244M   0% /sys/fs/cgroup
>
> I created one partition that uses all the available space.

what does "lsblk" show?

What "brand" 64GB SD? (64GB are SDXC cards)

The am335x ip only "supports" SDHC cards.. (which is spec'd up to 32GB)

While some "SDXC" cards do work, there is no guarantee!

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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYhCOy70efX2ndW1fjGkhs_3ALj5hZeGTz7Cf9nf_4T8xQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Expanding Root Partition - Bad magic number in super-block while trying to open /dev/mmcblk0p2

[dariush . keivan]

Hello all,

I have 64GB SD card but it is not shown under filesystems (df -h):

Filesystem  Size  Used Avail Use% Mounted on
udev 10M 0   10M   0% /dev
tmpfs98M  6.5M   92M   7% /run
/dev/mmcblk1p1  3.6G  3.5G 0 100% /
tmpfs   244M 0  244M   0% /dev/shm
tmpfs   5.0M  4.0K  5.0M   1% /run/lock
tmpfs   244M 0  244M   0% /sys/fs/cgroup

I created one partition that uses all the available space.

root@beaglebone:~# fdisk -l

Disk /dev/mmcblk0: 59.5 GiB, 63864569856 bytes, 124735488 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x6a65dc0d

Device Boot Start   End   Sectors  Size Id Type
/dev/mmcblk0p1 * 8192 124735487 124727296 59.5G 83 Linux

Disk /dev/mmcblk1: 3.7 GiB, 3925868544 bytes, 7667712 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x

Device Boot Start End Sectors  Size Id Type
/dev/mmcblk1p1 * 8192 7667711 7659520  3.7G 83 Linux

Disk /dev/mmcblk1boot1: 1 MiB, 1048576 bytes, 2048 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/mmcblk1boot0: 1 MiB, 1048576 bytes, 2048 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

But when I run resize2fs /dev/mmcblk0p1, I got the following error:

root@beaglebone:/# resize2fs /dev/mmcblk0p1 
resize2fs 1.43 (17-May-2016)
resize2fs: Bad magic number in super-block while trying to open 
/dev/mmcblk0p1
Couldn't find valid filesystem superblock.

I also used Robert new method but I got following error:

root@beaglebone:/# cd /opt/scripts/tools/
root@beaglebone:/opt/scripts/tools# git pull || true 
Already up-to-date.
root@beaglebone:/opt/scripts/tools# sudo ./grow_partition.sh 
Media: [/dev/mmcblk1]

Disk /dev/mmcblk1: 119808 cylinders, 4 heads, 16 sectors/track
Old situation:
Units: 1MiB = 1024*1024 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start   EndMiB#blocks   Id  System
/dev/mmcblk1p1   * 4   3743   37403829760   83  Linux
/dev/mmcblk1p2 0  -  0  00  Empty
/dev/mmcblk1p3 0  -  0  00  Empty
/dev/mmcblk1p4 0  -  0  00  Empty
New situation:
Units: 1MiB = 1024*1024 bytes, blocks of 1024 bytes, counting from 0

   Device Boot Start   EndMiB#blocks   Id  System
/dev/mmcblk1p1   * 4   3743   37403829760   83  Linux
/dev/mmcblk1p2 0  -  0  00  Empty
/dev/mmcblk1p3 0  -  0  00  Empty
/dev/mmcblk1p4 0  -  0  00  Empty
Successfully wrote the new partition table

Re-reading the partition table ...
sfdisk: BLKRRPART: Device or resource busy
sfdisk: The command to re-read the partition table failed.
Run partprobe(8), kpartx(8) or reboot your system now,
before using mkfs
sfdisk: If you created or changed a DOS partition, /dev/foo7, say, then use 
dd(1)
to zero the first 512 bytes:  dd if=/dev/zero of=/dev/foo7 bs=512 count=1
(See fdisk(8).)

I figured out that my beaglebone black is booted from EMMC but not the SD 
card. I don't know how to boot from the SD card but what I need now is more 
space so I can Install other things on my beaglebone black.
Sorry for the long message, I'm kinda new to LInux and beaglebone black. 
I'll appreciate if anybody can help me.

Best,
Darioush


On Sunday, February 19, 2017 at 9:52:04 PM UTC-6, RobertCNelson wrote:
>
> On Sun, Feb 19, 2017 at 9:46 PM, James Hice  > wrote: 
> > I first found the instructions at 
> > 
> http://elinux.org/Beagleboard:Expanding_File_System_Partition_On_A_microSD 
> > which are a bit outdated. there was only 1 partition on the Debian Jesse 
> > image 
> > I still came across this issue though as my partition started on a 
> different 
> > sector so I thought it would be a good to add to this thread when I came 
> > across it while searching for instructions. 
> > 
> > in cases where the only partition has a different start sector, the new 
> > partition should also start on the same sector 
> > 
> > for my case the partition started on 8192 
> > as found from fdisk /dev/mmcblk0 
> > Device Boot Start   End   Sectors  Size Id Type 
> > /dev/mmcblk0p1   8192 124735487 124727296 59.5G 83 Linux 
> > 
> > when creating the new partition, the number under start should be used. 
> > (8192 in my case) instead of using the default of 2048 
> > after I did this I was able to resize the file system without issue 
>
> There's a built-in script: 
>
>
> 

Re: [beagleboard] Re: Expanding Root Partition - Bad magic number in super-block while trying to open /dev/mmcblk0p2

[James Hice]

Ah thank you I'll use that next time :)

On Feb 19, 2017 10:51 PM, "Robert Nelson"  wrote:

> On Sun, Feb 19, 2017 at 9:46 PM, James Hice  wrote:
> > I first found the instructions at
> > http://elinux.org/Beagleboard:Expanding_File_System_
> Partition_On_A_microSD
> > which are a bit outdated. there was only 1 partition on the Debian Jesse
> > image
> > I still came across this issue though as my partition started on a
> different
> > sector so I thought it would be a good to add to this thread when I came
> > across it while searching for instructions.
> >
> > in cases where the only partition has a different start sector, the new
> > partition should also start on the same sector
> >
> > for my case the partition started on 8192
> > as found from fdisk /dev/mmcblk0
> > Device Boot Start   End   Sectors  Size Id Type
> > /dev/mmcblk0p1   8192 124735487 124727296 59.5G 83 Linux
> >
> > when creating the new partition, the number under start should be used.
> > (8192 in my case) instead of using the default of 2048
> > after I did this I was able to resize the file system without issue
>
> There's a built-in script:
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#
> Expanding_File_System_Partition_On_A_microSD
>
> We moved the start of the partition from 1MB -> 4MB as the default
> u-boot has gotten big enough to break thru the 1MB hole boundary..
>
> 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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CA%2BmNLdTjrv_kV05VukggyNSSu50xdQOfaRXNw0RzMC%2B9y61dMQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Expanding Root Partition - Bad magic number in super-block while trying to open /dev/mmcblk0p2

[Robert Nelson]

On Sun, Feb 19, 2017 at 9:46 PM, James Hice  wrote:
> I first found the instructions at
> http://elinux.org/Beagleboard:Expanding_File_System_Partition_On_A_microSD
> which are a bit outdated. there was only 1 partition on the Debian Jesse
> image
> I still came across this issue though as my partition started on a different
> sector so I thought it would be a good to add to this thread when I came
> across it while searching for instructions.
>
> in cases where the only partition has a different start sector, the new
> partition should also start on the same sector
>
> for my case the partition started on 8192
> as found from fdisk /dev/mmcblk0
> Device Boot Start   End   Sectors  Size Id Type
> /dev/mmcblk0p1   8192 124735487 124727296 59.5G 83 Linux
>
> when creating the new partition, the number under start should be used.
> (8192 in my case) instead of using the default of 2048
> after I did this I was able to resize the file system without issue

There's a built-in script:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Expanding_File_System_Partition_On_A_microSD

We moved the start of the partition from 1MB -> 4MB as the default
u-boot has gotten big enough to break thru the 1MB hole boundary..

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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYgWtnbaMg1SXDd1doUax8sFdJwe1PNNG3gCGu0xLATDqg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Expanding Root Partition - Bad magic number in super-block while trying to open /dev/mmcblk0p2

[James Hice]

I first found the instructions at 
http://elinux.org/Beagleboard:Expanding_File_System_Partition_On_A_microSD 
which are a bit outdated. there was only 1 partition on the Debian Jesse 
image 
I still came across this issue though as my partition started on a 
different sector so I thought it would be a good to add to this thread when 
I came across it while searching for instructions.

in cases where the only partition has a different start sector, the new 
partition should also start on the same sector

for my case the partition started on 8192 
as found from fdisk /dev/mmcblk0
Device Boot Start   End   Sectors  Size Id Type
/dev/mmcblk0p1   8192 124735487 124727296 59.5G 83 Linux

when creating the new partition, the number under start should be used. 
(8192 in my case) instead of using the default of 2048 
after I did this I was able to resize the file system without issue

On Thursday, September 8, 2016 at 2:36:56 PM UTC-4, i.la...@gmail.com wrote:
>
> This worked for me as well on BBB Jessie. The thought of deleting the one 
> and only partition freaked me out at first but apparently fdisk works like 
> that. 
>
> On Monday, July 4, 2016 at 1:54:05 PM UTC-7, mailbot...@gmail.com wrote:
>>
>> I had the same issue as you. So, what I did is to remove all partitions (
>> /dev/mmcblk0p*) and create a new partition that uses all the available 
>> space. Write the changes and reboot BBB. Run resize2fs on the only 
>> partition. Do a "df -h" to confirm.
>>
>>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/66d200b2-5c75-428b-ae3f-86a1f46beccc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Expanding Root Partition - Bad magic number in super-block while trying to open /dev/mmcblk0p2

[i . law . yu]

This worked for me as well on BBB Jessie. The thought of deleting the one 
and only partition freaked me out at first but apparently fdisk works like 
that. 

On Monday, July 4, 2016 at 1:54:05 PM UTC-7, mailbot...@gmail.com wrote:
>
> I had the same issue as you. So, what I did is to remove all partitions (/
> dev/mmcblk0p*) and create a new partition that uses all the available 
> space. Write the changes and reboot BBB. Run resize2fs on the only 
> partition. Do a "df -h" to confirm.
>
>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/44711d11-82a4-4c3d-8780-3947be9ea042%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Expanding Root Partition - Bad magic number in super-block while trying to open /dev/mmcblk0p2

[gfast2]

Yeh, It works pretty well on a Beaglebone Black running Jessie. It seems 
like all Documentation about expand storage on Beaglebone are a little bit 
out of date.

在 2016年7月4日星期一 UTC+2下午10:54:05，mailbot...@gmail.com写道：
>
> I had the same issue as you. So, what I did is to remove all partitions (/
> dev/mmcblk0p*) and create a new partition that uses all the available 
> space. Write the changes and reboot BBB. Run resize2fs on the only 
> partition. Do a "df -h" to confirm.
>
>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/ea2d60ba-a1f1-4f5c-991e-623a11950dad%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Expanding Root Partition - Bad magic number in super-block while trying to open /dev/mmcblk0p2

[mailbot . netserv]

I had the same issue as you. So, what I did is to remove all partitions (/
dev/mmcblk0p*) and create a new partition that uses all the available 
space. Write the changes and reboot BBB. Run resize2fs on the only 
partition. Do a "df -h" to confirm.

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/a19e4d43-5da9-41b8-a1e2-2ddc5a728235%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.