I have a BBB Rev C (4 gig) but fdisk only shows that the eMMC has 1.8 gigs.

33 views
Skip to first unread message

Brian Wiegand

unread,
Oct 8, 2017, 8:15:37 AM10/8/17
to BeagleBoard
I'm not even sure where to begin with this one. Fdisk really shouldn't be showing wrong disk sizes and I've checked file-systems, deleted and rewrote the partition tables, deleted and created partitions.

Has anyone else had this strange problem before? Any more information I can provide.

Fdisk output.

root@beaglebone:/# fdisk -l
Disk /
dev/mmcblk0: 14.7 GiB, 15719727104 bytes, 30702592 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: 0xad20d647


Device         Boot Start      End  Sectors  Size Id Type
/dev/mmcblk0p1 *     8192 30702591 30694400 14.7G 83 Linux




Disk /dev/mmcblk1: 1.8 GiB, 1920991232 bytes, 3751936 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: 0xe9000d91


Device         Boot Start     End Sectors  Size Id Type
/dev/mmcblk1p1       2048 3751935 3749888  1.8G 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

Version script.

root@beaglebone:/opt/scripts/tools# ./version.sh
git
:/opt/scripts/:[9e4538c8313aae2d2ff50b07ec5e0ee7685a840c]
eeprom
:[A335BNLT0A5C3313BBBK3434]
dogtag
:[BeagleBoard.org Debian Image 2017-09-21]
bootloader
:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2017.09-00003-g11d92ba68a]
bootloader
:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2017.09-rc2-00002-g7c9353]
kernel
:[4.4.88-ti-r125]
nodejs
:[v6.11.3]
uboot_overlay_options
:[enable_uboot_overlays=1]
uboot_overlay_options
:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo]
uboot_overlay_options
:[enable_uboot_cape_universal=1]
pkg
:[bb-cape-overlays]:[4.4.20170921.0-0rcnee1~stretch+20170921]
pkg
:[bb-wl18xx-firmware]:[1.20170829-0rcnee1~stretch+20170829]
pkg
:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830]


Alan Corey

unread,
Oct 8, 2017, 10:25:58 AM10/8/17
to BeagleBoard
Is there any option in your fdisk to edit the disk geometry?  Hard drives grew rapidly so numbers of heads, tracks, etc quickly outgrew the number of bits set aside to store them and the solution was to divide one number by 2 and multiply a different one by 2.  Anyway the geometry is usually flexible.

Robert Nelson

unread,
Oct 8, 2017, 10:33:21 AM10/8/17
to Beagle Board, baw...@gmail.com
On Sun, Oct 8, 2017 at 1:07 AM, Brian Wiegand <baw...@gmail.com> wrote:
>> I'm not even sure where to begin with this one. Fdisk really shouldn't be
>> showing wrong disk sizes and I've checked file-systems, deleted and rewrote
>> the partition tables, deleted and created partitions.
>
>
> Has anyone else had this strange problem before? Any more information I can
> provide.

> eeprom:[A335BNLT0A5C3313BBBK3434]

0A5C is not a rev "C", it's rev "A" with only 2GB eMMC..

Regards,

--
Robert Nelson
https://rcn-ee.com/

Brian Wiegand

unread,
Oct 8, 2017, 8:18:52 PM10/8/17
to Robert Nelson, Beagle Board
That is interesting. So Adafruit must have sent me a SUPER old version 
So I wasn't sold the Rev C. Adafruit has some explaining to do. Thanks for the insight Robert.. 
Reply all
Reply to author
Forward
0 new messages