Problems with partitioning

Bug #2067 reported by X-Bert
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
partman-base (Ubuntu)
Expired
Medium
Unassigned

Bug Description

The partitioner in the installer does not recognize partition tables of the following structure:

1 primary
2 extended
  5 logical
  6 logical
  7 logical
  ...
3 primary

Furthermore, when deleting and recreating a partition, the numbering of all following partitions will change and cannot be restored.

This partitioner is really dangerous!

Revision history for this message
Colin Watson (cjwatson) wrote :

I need to see /var/log/partman from the installer after attempting to do this. Thanks.

Changed in debian-installer:
assignee: nobody → kamion
Revision history for this message
X-Bert (x-bert-0sg) wrote :

Sorry, but as I wrote, the partitioner does not recognize the partition table in this case. It suggests to create a new partition table and hence destroy all data. That's why I think that this partitioner is dangerous. If one does refuse, there will be no new installation and no log file, and if one accepts, there will be another partition table, which should be easily to handle by the partitioner, but might not be what the user wanted or expected ...

Revision history for this message
Colin Watson (cjwatson) wrote :

The log file is available by going back to the installer's main menu and selecting "Save debug logs"; you don't have to complete the installation.

Changed in partman-base:
status: Unconfirmed → Needs Info
Revision history for this message
kycho (kycho) wrote :

I have similar problem: partitioner is not able to read my partition table. I have 3 primary partitions + 1 extended with 6 logical partitions more.

During installation process 'Partitioner' does not see any of my partitions, GParted (not surprising) does not see it as well, but Disk Management tool (or something like that) has no problems with it and shows all my partitions.

I used 'fdisk' to partition my harddisk for the particular installation successfully. Unfortunately, the installer says: "No root file systems" after assigning partitions to mount points (e.g. "/" root and swap).

I used 'desktop' and 'alternate' installers with the same effect - I cannot install Ubuntu on ma PC.
It looks like the most stable version of Ubuntu still needs some work. Of course, if you want to wipe all your data from your harddisk (surprise! ;), it will go smoothly ...

Colin Watson (cjwatson)
Changed in partman-base:
assignee: kamion → nobody
Revision history for this message
jacubo (jacubo) wrote :
Download full text (7.3 KiB)

Hi,

Ubuntu Feisty the same problem as described. My partition table is:

Disk /dev/hda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot Start End Blocks Id System
/dev/hda1 * 1 2550 20482843+ c W95 FAT32 (LBA)
/dev/hda2 * 2551 4940 19197675 83 Linux
/dev/hda3 4941 9728 38459610 f W95 Ext'd (LBA)
/dev/hda4 5047 9728 37608133+ 7 HPFS/NTFS
/dev/hda5 4941 5046 851382 82 Linux swap / Solaris

Installator doesn't see my partition layout.

Here is what dmesg shows:

[ 102.070108] NET: Registered protocol family 10
[ 102.070221] lo: Disabled Privacy Extensions
[ 108.002062] input: Power Button (FF) as /class/input/input4
[ 108.029135] ACPI: Power Button (FF) [PWRF]
[ 108.092549] input: Power Button (CM) as /class/input/input5
[ 108.119743] ACPI: Power Button (CM) [PWRB]
[ 108.162020] No dock devices found.
[ 108.184348] Using specific hotkey driver
[ 108.238786] ibm_acpi: ec object not found
[ 108.425088] pcc_acpi: loading...
[ 112.807861] eth0: no IPv6 routers present
[ 123.168331] lp0: using parport0 (interrupt-driven).
[ 123.238220] ppdev: user-space parallel port driver
[ 133.957343] apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16ac)
[ 133.957350] apm: overridden by ACPI.
[ 134.582121] eth0: no IPv6 routers present
[ 137.304656] Bluetooth: Core ver 2.11
[ 137.304732] NET: Registered protocol family 31
[ 137.304734] Bluetooth: HCI device and connection manager initialized
[ 137.304738] Bluetooth: HCI socket layer initialized
[ 137.533342] Bluetooth: L2CAP ver 2.8
[ 137.533347] Bluetooth: L2CAP socket layer initialized
[ 137.738930] Bluetooth: RFCOMM socket layer initialized
[ 137.738946] Bluetooth: RFCOMM TTY layer initialized
[ 137.738949] Bluetooth: RFCOMM ver 1.8
[ 250.866026] kjournald starting. Commit interval 5 seconds
[ 250.866372] EXT3 FS on hda2, internal journal
[ 250.866445] EXT3-fs: mounted filesystem with ordered data mode.
[ 470.900610] NTFS driver 2.1.28 [Flags: R/O MODULE].
[ 471.081416] JFS: nTxBlock = 8192, nTxLock = 65536
[ 471.315287] SGI XFS with ACLs, security attributes, realtime, large block numbers, no debug enabled
[ 471.315784] SGI XFS Quota Management subsystem
[ 531.108908] hda: hda1 hda3 < hda5 > hda4
[ 533.119987] hda: hda1 hda3 < hda5 > hda4
[ 722.203990] QNX4 filesystem 0.2.3 registered.
[ 722.280212] cramfs: wrong magic
[ 722.505816] cramfs: wrong magic
[ 722.510466] FAT: bogus number of reserved sectors
[ 722.510474] VFS: Can't find a valid FAT filesystem on dev hda3.
[ 722.515966] attempt to access beyond end of device
[ 722.515974] hda3: rw=0, want=4, limit=2
[ 722.516325] EXT3-fs: unable to read superblock
[ 722.521507] attempt to access beyond end of device
[ 722.521514] hda3: rw=0, want=66, limit=2
[ 722.521853] isofs_fill_super: bread failed, dev=hda3, iso_blknum=16, block=32
[ 722.526507] SQUASHFS error: Can't find a SQUASHFS superblock on hda3
[ 722.543057] attempt to access beyond end of device
[ 722.543066] hda3: rw=0...

Read more...

Jim Qode (jimqode)
Changed in partman-base:
status: Incomplete → Confirmed
Revision history for this message
zorpox (nononinono) wrote :

I have to report similar problems:

Partman failed recognize my partitions and just presented me with the option to create new ones. The partition-structure was roughly similar to the one mentioned in the bug report.

Unfortunately, my partition table was partially (!) corrupted anyway, so I'm not sure whether this occurred because of the damage or because of the distinct structure #1 mentioned. Yet, parted and fdisk were able to read (and restore) it without problems so the problem seems to be with partman.

Revision history for this message
rusivi2 (rusivi2-deactivatedaccount) wrote :

Thank you for posting this bug.

Does this occur in Lucid?

Changed in partman-base (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for partman-base (Ubuntu) because there has been no activity for 60 days.]

Changed in partman-base (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.