Strange reading from fdisk...
~# fdisk -l /dev/sdd1
Disk /dev/sdd1: 29.2 GiB, 31378272256 bytes, 61285688 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: 0x69737369
Device Boot Start End Sectors Size Id Type
/dev/sdd1p1 ? 1869771365 2038460886 168689522 80.4G 69 unknown
/dev/sdd1p2 ? 1701519481 3571400945 1869881465 891.6G 73 unknown
/dev/sdd1p3 ? 2573 2573 0 0B 74 unknown
/dev/sdd1p4 2885681152 2885733566 52415 25.6M 0 Empty
Partition table entries are not in disk order.
Its not the first time I have seen spurious readings from fdisk.
Can anyone suggest a way of looking at the drive data on the sdd1p1 etc listed partitions? I find it hard to believe that my humble 32GiB flash drive is over a Terra byte in size. When I try to access one of them I get an error message that states cannot access /dev/sdd1p1: No such file or directory
So... is fdisk stuffed (got a bug) or a library thats not working right? Need some guidance on how to fix this.
What I need to do is resize the partition /dev/sdd1p4
, using gParted, it has any option to change the partition size greyed out.
Again, is this a gParted bug?