Red Hat Bugzilla – Bug 1288091
parted cannot find any partition on my disk
Last modified: 2015-12-03 13:24:11 EST
Created attachment 1101803 [details]
The first 62 sectors of my disk
Description of problem:
parted thinks my disk doesn't have a partition table. This crashes blivet and Fedora installer.
Version-Release number of selected component (if applicable):
Always on my machine
Steps to Reproduce:
1. Run 'parted /dev/sdb print' on my machine
Model: ATA Hitachi HDP72505 (scsi)
Disk /dev/sdb: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 500GB 500GB fat16
It should be able to find a partition table. Fedora installer should not crash. fdisk output:
Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 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: 0xa5b43cc2
Device Boot Start End Sectors Size Id Type
/dev/sdb1 63 4192964 4192902 2G 6 FAT16
/dev/sdb2 4192965 8385929 4192965 2G 16 Hidden FAT16
/dev/sdb3 * 8385930 113258249 104872320 50G 17 Hidden HPFS/NTFS
/dev/sdb4 113258250 976773167 863514918 411.8G 5 Extended
/dev/sdb5 113258313 742404095 629145783 300G 7 HPFS/NTFS/exFAT
/dev/sdb6 742406144 847268099 104861956 50G a5 FreeBSD
/dev/sdb7 847268163 976773119 129504957 61.8G 8e Linux LVM
This bug was reported to blivet:
The first 62 sectors of my disk is attached.
Parted supports reading loop mounted devices with the raw filesystem. It appears that at one time your disk had a FAT16 filesystem written to the start of it and it wasn't completely wiped when you repartitioned things.
What happens is that parted probes for msdos disklabel, but aborts because the disk looks like a FAT16 fs, and falls through into the loop probe code which detects it as a FAT16 loop device.
I don't think there's anything that can be done here other than using a different disk (or wiping this one using wipefs).