KDE Partition Manager claims no valid partition scheme is on my drive!

[Tynach]

Full details are here (I don't want to re-type all that).

Since I run KDE as well as Gnome, and the KDE partition manager is having the same problem as GParted, I figured I'd post my issue here as well.

[verndog]

Re: KDE Partition Manager claims no valid partition scheme is on my drive!

What's the output of fdisk:

sudo fdisk -l

[dibl]

Re: KDE Partition Manager claims no valid partition scheme is on my drive!

the KDE partition manager is having the same problem as GParted

There's your clue that there's a real problem with the hard drive setup, and not just some software bug.

Yes, as verndog says, we need to see the output of

sudo fdisk -lu

and I would be taking great care to copy off all important data files from that particular drive.

[Tynach]

Re: KDE Partition Manager claims no valid partition scheme is on my drive!

The KDE partition manager and GParted both use the same backend, so it could still be a software bug.

But RedHat Disk Utility still won't let me do anything.

I'm going to try with a LiveCD.

Output of that command:

$ sudo fdisk -l
[sudo] password for tynach: 
omitting empty partition (9)

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xb2b4cc50

  Device Boot   Start     End   Blocks  Id System
/dev/sda1  *      1     13   102400  7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2       13    47225  379230208  7 HPFS/NTFS
/dev/sda3      47225    60801  109041664+  f W95 Ext'd (LBA)
/dev/sda5      47225    47748   4193280  82 Linux swap / Solaris
/dev/sda6      47748    50358  20971520  83 Linux
/dev/sda7      50359    52969  20971520  83 Linux
/dev/sda8      55581    58191  20971520  83 Linux

Disk /dev/sdb: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x4e38e6e9

  Device Boot   Start     End   Blocks  Id System
/dev/sdb1  *      1    14448  116053528+  7 HPFS/NTFS
/dev/sdb2      28805    30401  12824576  7 HPFS/NTFS
/dev/sdb3      14449    28804  115314570  5 Extended
/dev/sdb5      14449    28215  110583396  83 Linux
/dev/sdb6      28216    28804   4731111  82 Linux swap / Solaris

Partition table entries are not in disk order

Disk /dev/sdc: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000029b2

  Device Boot   Start     End   Blocks  Id System
/dev/sdc1  *      1    23330  187395072  83 Linux
/dev/sdc2      23330    24322   7963648+  5 Extended
/dev/sdc5      23330    24322   7963648  82 Linux swap / Solaris

[verndog]

Re: KDE Partition Manager claims no valid partition scheme is on my drive!

Edit: for get that, your swap is inside the extended sda3.

I'm not sure what to make of sda extended sda3:
dev/sda3 47225 60801 109041664+ f W95 Ext'd (LBA)

The extended on sdb3 looks correct:


/dev/sdb3 14449 28804 115314570 5 Extended


Here's some info on ID:f

0f WIN95: Extended partition, LBA-mapped
Windows 95 uses 0e and 0f as the extended-INT13 equivalents of 06 and 05. For the problems this causes, see Possible data loss with LBA and INT13 extensions. (Especially when going back and forth between MSDOS and Windows 95, strange things may happen with a type 0e or 0f partition.) Windows NT does not recognize the four W95 types 0b, 0c, 0e, 0f ( Win95 Partition Types Not Recognized by Windows NT). DRDOS 7.03 does not support this type (but DRDOS 7.04 does).

[Tynach]

Re: KDE Partition Manager claims no valid partition scheme is on my drive!

Please ignore sdb. That whole drive is just my laptop hard drive, and is plugged into my computer at the moment. It is not the issue, and should be ignored as if it did not exist.