partitionmanager - rev 1342 Linux-3.8.1 amd-x64 bad detection of partitions on startup it shows: Devices: /dev/sda5 unknown 20.47 GiB /dev/sdb7 unknown 19.99 GiB Partitions are listed as: /dev/sda5p1 type: loop (read only) /dev/sdb7p1 type: loop (read only) In fact there are multiple partitions on both sda and sdb # fdisk -l Disk /dev/sda: 120.0 GB, 120034123776 bytes, 234441648 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 identifier: 0x000e6f1e Device Boot Start End Blocks Id System /dev/sda1 * 2048 41945087 20971520 83 Linux /dev/sda2 41945088 62916607 10485760 83 Linux /dev/sda3 62916608 234309631 85696512 5 Extended /dev/sda5 62918656 105844735 21463040 83 Linux /dev/sda6 217663488 226050047 4193280 83 Linux /dev/sda7 105846784 189732863 41943040 83 Linux /dev/sda8 204240896 217661439 6710272 83 Linux /dev/sda9 226052096 234309631 4128768 82 Linux swap / Solaris /dev/sda10 189734912 191832063 1048576 7 HPFS/NTFS/exFAT Partition table entries are not in disk order Disk /dev/sdb: 400.1 GB, 400087375360 bytes, 781420655 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 identifier: 0x0003fb05 Device Boot Start End Blocks Id System /dev/sdb1 63 37736447 18868192+ 7 HPFS/NTFS/exFAT /dev/sdb2 37736448 781418495 371841024 5 Extended /dev/sdb5 * 79682463 121628114 20972826 83 Linux /dev/sdb6 592670043 773031734 90180846 83 Linux /dev/sdb7 205518848 247461887 20971520 7 HPFS/NTFS/exFAT Partition table entries are not in disk order # blkid /dev/sda1: LABEL="root64" UUID="942e1eb7-f30e-4d8d-990e-56a5e670a022" TYPE="ext4" PTTYPE="dos" /dev/sda2: LABEL="root32" UUID="345f4fb0-3939-41f2-aac9-565690ba19b2" TYPE="ext4" PTTYPE="dos" /dev/sda5: LABEL="home" UUID="d107362a-1abf-49e6-8ce6-69e707c0bf7c" TYPE="ext4" /dev/sda6: LABEL="spool" UUID="a0d9ac3a-38aa-440d-ac19-e14db7c96ec1" TYPE="ext4" /dev/sda7: LABEL="git" UUID="8773a123-7dd9-4489-8f93-b3fbd5174b52" TYPE="ext4" /dev/sda8: LABEL="cache" UUID="e11bc26b-50cb-4ad7-940a-61898b9246f8" TYPE="ext4" /dev/sda9: LABEL="swap" UUID="afebff8b-7baf-4c48-9524-1cecb9b42ac9" TYPE="swap" /dev/sda10: LABEL="wine" UUID="0561BD2F5ECC3EC3" TYPE="ntfs" /dev/sdb1: LABEL="winxp" UUID="E6D0DD01D0DCD8BF" TYPE="ntfs" /dev/sdb5: LABEL="rescue64" UUID="b05da783-edbe-4b1b-ac89-a9aaaf721b16" TYPE="ext4" PTTYPE="dos" /dev/sdb6: LABEL="video" UUID="29da0bad-21ef-4ba0-9349-d6d86a9fbd2f" TYPE="ext4" /dev/sdb7: LABEL="win-dat" UUID="7898A40098A3BB50" TYPE="ntfs" # dmesg [ 0.591740] ahci 0000:00:11.0: version 3.0 [ 0.591781] ahci 0000:00:11.0: irq 42 for MSI/MSI-X [ 0.591844] ahci 0000:00:11.0: AHCI 0001.0300 32 slots 4 ports 6 Gbps 0xf impl SATA mode [ 0.591879] ahci 0000:00:11.0: flags: 64bit ncq sntf ilck pm led clo pmp pio sxs [ 0.592198] scsi0 : ahci [ 0.592279] scsi1 : ahci [ 0.592343] scsi2 : ahci [ 0.592408] scsi3 : ahci [ 0.592459] ata1: SATA max UDMA/133 abar m2048@0xfeb51000 port 0xfeb51100 irq 42 [ 0.592492] ata2: SATA max UDMA/133 abar m2048@0xfeb51000 port 0xfeb51180 irq 42 [ 0.592524] ata3: SATA max UDMA/133 abar m2048@0xfeb51000 port 0xfeb51200 irq 42 [ 0.592557] ata4: SATA max UDMA/133 abar m2048@0xfeb51000 port 0xfeb51280 irq 42 [ 0.910005] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 0.910066] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 0.910124] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 0.910173] ata3: SATA link down (SStatus 0 SControl 300) [ 0.910860] ata1.00: ATA-9: Samsung SSD 840 Series, DXT06B0Q, max UDMA/133 [ 0.910895] ata1.00: 234441648 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [ 0.910968] ata1.00: failed to get Identify Device Data, Emask 0x1 [ 0.911235] ata1.00: failed to get Identify Device Data, Emask 0x1 [ 0.911239] ata1.00: configured for UDMA/133 [ 0.911371] scsi 0:0:0:0: Direct-Access ATA Samsung SSD 840 DXT0 PQ: 0 ANSI: 5 [ 0.911564] sd 0:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/111 GiB) [ 0.911580] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 0.911564] sd 0:0:0:0: [sda] 234441648 512-byte logical blocks: (120 GB/111 GiB) [ 0.911580] sd 0:0:0:0: Attached scsi generic sg0 type 0 [ 0.911696] sd 0:0:0:0: [sda] Write Protect is off [ 0.911728] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [ 0.911747] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 0.914228] ata2.00: HPA detected: current 781420655, native 781422768 [ 0.914327] ata2.00: ATA-7: SAMSUNG HD400LJ, ZZ100-15, max UDMA7 [ 0.914358] ata2.00: 781420655 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [ 0.916849] sda: sda1 sda2 sda3 < sda5 sda6 sda7 sda8 sda9 sda10 > [ 0.917288] sd 0:0:0:0: [sda] Attached SCSI disk [ 0.918595] ata2.00: configured for UDMA/133 [ 0.918707] scsi 1:0:0:0: Direct-Access ATA SAMSUNG HD400LJ ZZ10 PQ: 0 ANSI: 5 [ 0.918882] sd 1:0:0:0: [sdb] 781420655 512-byte logical blocks: (400 GB/372 GiB) [ 0.918921] sd 1:0:0:0: Attached scsi generic sg1 type 0 [ 0.919003] sd 1:0:0:0: [sdb] Write Protect is off [ 0.919041] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 [ 0.919063] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 0.943068] ata4.00: ATAPI: TSSTcorpCD/DVDW SH-W163A, TS01, max UDMA/33 [ 0.943102] ata4.00: applying bridge limits [ 0.977045] ata4.00: configured for UDMA/33 [ 0.978760] scsi 3:0:0:0: CD-ROM TSSTcorp CD/DVDW SH-W163A TS01 PQ: 0 ANSI: 5 [ 0.978949] scsi 3:0:0:0: Attached scsi generic sg2 type 5 [ 0.983256] sdb: sdb1 sdb2 < sdb5 sdb6 sdb7 > [ 0.983591] sd 1:0:0:0: [sdb] Attached SCSI disk [ 0.983833] EXT3-fs (sda1): error: couldn't mount because of unsupported optional features (40) [ 0.984953] EXT2-fs (sda1): error: couldn't mount because of unsupported optional features (40) [ 0.988673] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 0.988716] VFS: Mounted root (ext4 filesystem) readonly on device 8:1.
Same here on my X200s. After this happened with partitionmanager-1.0.3 I tried out partitionmanager.git which produced slightly different output (e.g. 'sda3p1' instead of 'sda11') but still basically fails to detect anything fine. The initial thought was incompatibility with GPT system disk, but it also failed to detect the partition table of another regular MBR disk. At the same time, gparted runs perfectly fine. # gdisk -l /dev/sda GPT fdisk (gdisk) version 0.8.6 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Disk /dev/sda: 1000215216 sectors, 476.9 GiB Logical sector size: 512 bytes Disk identifier (GUID): 4E089492-B1EB-475F-AA62-FEA462B17344 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 1000215182 Partitions will be aligned on 2048-sector boundaries Total free space is 3038 sectors (1.5 MiB) Number Start (sector) End (sector) Size Code Name 1 2048 206847 100.0 MiB 0700 Linux filesystem 2 206848 207871 512.0 KiB EF02 BIOS boot partition 3 208896 1000215182 476.8 GiB 0700 Linux filesystem
Probably a duplicate of bug #311408: https://bugs.kde.org/show_bug.cgi?id=311408
*** This bug has been marked as a duplicate of bug 311408 ***