On Mon, Sep 15, 2014 at 3:36 PM, RT Mistler <[email protected]> wrote:
> I haven't had any success here. I created my microSD from the IMG file, > bone-debian-7.5-2014-05-14-2gb.img. > > I used an 8 Gig microSD card. > > It shows I'm at 100% disk usage right off the bat. I used this process > and it appeared to work, but complained of errors at the end. After > reboot, my file system size was still incorrect: > > debian@beaglebone:~$ df -h > Filesystem Size Used Avail Use% Mounted on > rootfs 1.6G 1.5G 2.6M 100% / > udev 10M 0 10M 0% /dev > tmpfs 100M 500K 99M 1% /run > /dev/mmcblk0p2 1.6G 1.5G 2.6M 100% / > tmpfs 249M 0 249M 0% /dev/shm > tmpfs 249M 0 249M 0% /sys/fs/cgroup > tmpfs 100M 0 100M 0% /run/user > tmpfs 5.0M 0 5.0M 0% /run/lock > /dev/mmcblk0p1 96M 70M 27M 73% /boot/uboot > debian@beaglebone:~$ cd /opt/scripts/tools/ > debian@beaglebone:/opt/scripts/tools$ sudo git pull > remote: Counting objects: 780, done. > remote: Compressing objects: 100% (221/221), done. > remote: Total 780 (delta 575), reused 758 (delta 553) > Receiving objects: 100% (780/780), 102.38 KiB, done. > Resolving deltas: 100% (575/575), completed with 13 local objects. > From https://github.com/RobertCNelson/boot-scripts > 8690159..c0429c4 master -> origin/master > Updating 8690159..c0429c4 > Fast-forward > 3rdparty/xinput_calibrator_pointercal.sh | 65 +- > boot/am335x_evm.sh | 52 +- > boot/omap3_beagle.sh | 32 +- > boot/omap5_uevm.sh | 54 + > device/bone/capes/BB-BEAGLELOGIC/beaglelogic-pru0 | Bin 0 -> 11160 > bytes > device/bone/capes/BB-BEAGLELOGIC/beaglelogic-pru1 | Bin 0 -> 12648 > bytes > device/bone/capes/BBB_Audio_Cape_RevB/asound.state | 1311 > ++++++++++++++++++++ > device/bone/tester/eeprom-u-boot.sh | 277 +++++ > tools/beaglebone-black-eMMC-flasher.sh | 161 ++- > tools/developers/apt-proxy.sh | 2 +- > tools/developers/nfs-rsync.sh | 16 + > tools/eMMC/bbb-eMMC-flasher-eewiki-12mb.sh | 316 +++++ > ...glebone-black-make-microSD-flasher-from-eMMC.sh | 445 ++++--- > tools/eMMC/generic-eMMC-flasher-12mb.sh | 210 ++++ > tools/eMMC/init-eMMC-flasher-v2.sh | 335 +++++ > tools/eMMC/init-eMMC-flasher-v3.sh | 415 +++++++ > tools/graphics/ti-omapdrm.sh | 122 +- > tools/grow_partition.sh | 74 +- > tools/init-eMMC-flasher.sh | 391 ++++++ > tools/update_bootloader.sh | 27 +- > tools/update_kernel.sh | 184 ++- > tools/wm/efl.sh | 170 +++ > tools/wm/lxqt.sh | 1 + > tools/wm/maynard.sh | 114 ++ > tools/wm/weston-drm.sh | 7 + > tools/wm/weston-fbdev.sh | 8 + > tools/wm/weston.sh | 12 + > 27 files changed, 4354 insertions(+), 447 deletions(-) > create mode 100755 boot/omap5_uevm.sh > create mode 100644 device/bone/capes/BB-BEAGLELOGIC/beaglelogic-pru0 > create mode 100644 device/bone/capes/BB-BEAGLELOGIC/beaglelogic-pru1 > create mode 100644 device/bone/capes/BBB_Audio_Cape_RevB/asound.state > create mode 100755 device/bone/tester/eeprom-u-boot.sh > create mode 100755 tools/developers/nfs-rsync.sh > create mode 100755 tools/eMMC/bbb-eMMC-flasher-eewiki-12mb.sh > create mode 100755 tools/eMMC/generic-eMMC-flasher-12mb.sh > create mode 100755 tools/eMMC/init-eMMC-flasher-v2.sh > create mode 100755 tools/eMMC/init-eMMC-flasher-v3.sh > create mode 100755 tools/init-eMMC-flasher.sh > create mode 100755 tools/wm/efl.sh > create mode 100755 tools/wm/maynard.sh > create mode 100755 tools/wm/weston-drm.sh > create mode 100755 tools/wm/weston-fbdev.sh > create mode 100755 tools/wm/weston.sh > debian@beaglebone:/opt/scripts/tools$ sudo ./grow_partition.sh > Media: [/dev/mmcblk0] > > Disk /dev/mmcblk0: 238720 cylinders, 4 heads, 16 sectors/track > Old situation: > Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from 0 > > Device Boot Start End MiB #blocks Id System > /dev/mmcblk0p1 * 1 96 96 98304 e W95 FAT16 (LBA) > start: (c,h,s) expected (32,0,1) found (0,32,33) > end: (c,h,s) expected (1023,3,16) found (12,93,17) > /dev/mmcblk0p2 97 1699 1603 1641472 83 Linux > start: (c,h,s) expected (1023,3,16) found (12,93,18) > end: (c,h,s) expected (1023,3,16) found (216,183,31) > /dev/mmcblk0p3 0 - 0 0 0 Empty > /dev/mmcblk0p4 0 - 0 0 0 Empty > New situation: > Units = mebibytes of 1048576 bytes, blocks of 1024 bytes, counting from 0 > > Device Boot Start End MiB #blocks Id System > /dev/mmcblk0p1 * 1 96 96 98304 e W95 FAT16 (LBA) > /dev/mmcblk0p2 97 7459 7363 7539712 83 Linux > /dev/mmcblk0p3 0 - 0 0 0 Empty > /dev/mmcblk0p4 0 - 0 0 0 Empty > Successfully wrote the new partition table > > Re-reading the partition table ... > BLKRRPART: Device or resource busy > The command to re-read the partition table failed. > Run partprobe(8), kpartx(8) or reboot your system now, > before using mkfs > 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).) > debian@beaglebone:/opt/scripts/tools$ sudo reboot > > # Reboot logs omitted > debian@beaglebone:~$ df -h > Filesystem Size Used Avail Use% Mounted on > rootfs 1.6G 1.5G 904K 100% / > udev 10M 0 10M 0% /dev > tmpfs 100M 528K 99M 1% /run > /dev/mmcblk0p2 1.6G 1.5G 904K 100% / > tmpfs 249M 0 249M 0% /dev/shm > tmpfs 249M 0 249M 0% /sys/fs/cgroup > tmpfs 5.0M 0 5.0M 0% /run/lock > tmpfs 100M 0 100M 0% /run/user > /dev/mmcblk0p1 96M 70M 27M 73% /boot/uboot > debian@beaglebone:~$ > > If I take that card and plug it into a development system, use gparted to > look at it, it shows that the filesystems are about 96M for boot and a > little over 7.2G for the ext4 partition. So I do not understand why the > BBB is not seeing this same information. > > Any suggestions? For what it's worth, I re-imaged my microSD card over > and retried without having done any other actions. > > My next step may be to re-image the microSD card, then look at it via > gparted and adjust the partition size before I ever even boot it on the BBB. > Instead of starting over just run: sudo resize2fs /dev/mmcblk0p2 sfdisk already resized it. Regards, -- Robert Nelson http://www.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]. For more options, visit https://groups.google.com/d/optout.
