Activity log for bug #324987

Date Who What changed Old value New value Message
2009-02-03 19:08:35 TJ bug added bug
2009-02-03 19:08:35 TJ bug added attachment 'syslog' (syslog)
2009-02-03 19:09:19 TJ bug added attachment 'partman' (partman)
2009-02-05 13:23:27 TJ bug added attachment 'syslog' (syslog for daily 0203.1)
2009-02-05 13:24:02 TJ bug added attachment 'partman' (partman for daily 0203.1)
2009-02-05 13:39:51 TJ description Binary package hint: ubiquity The description of this bug report might also read "Ubiquity causes kernel to *lose* the /dev/sda5 partition". The installer fails because one of the partitions it is trying to prepare *disappears* as a result of one of the many scan/file-system detection operations that ubiquity/partman perform. I've been unable to pin-point the culprit so far. Checking /proc/partitions shows that sda5 has gone missing. Before: major minor #blocks name 7 0 690828 loop0 8 0 390711384 sda 8 1 9764864 sda1 8 2 28738560 sda2 8 3 4194304 sda3 8 4 1 sda4 8 5 122880 sda5 8 6 347889719 sda6 8 16 2000880 sdb 8 17 2000061 sdb1 252 0 19529728 dm-0 252 1 9764864 dm-1 252 2 4882432 dm-2 252 3 9764864 dm-3 252 4 3903488 dm-4 252 5 9763836 dm-5 252 6 3902460 dm-6 252 7 19528700 dm-7 After: major minor #blocks name 7 0 690828 loop0 8 0 390711384 sda 8 1 9764864 sda1 8 2 28738560 sda2 8 3 4194304 sda3 8 4 1 sda4 8 6 347889719 sda6 8 16 2000880 sdb 8 17 2000061 sdb1 252 0 19529728 dm-0 252 1 9764864 dm-1 252 2 4882432 dm-2 252 3 9764864 dm-3 252 4 3903488 dm-4 252 5 9763836 dm-5 252 6 3902460 dm-6 252 7 19528700 dm-7 Although I'm testing Jaunty amd64 alpha 3 LiveCD, this bug also occurs using the Intrepid amd64 LiveCD. The Sony Vaio (laptop) has a single new SATA 400GB. It has been organised thus: /dev/sda1 Windows Recovery ntfs ~9GB /dev/sda2 Windows Vista ntfs ~28GB /dev/sda3 Linux swap ~4GB /dev/sda4 extended /dev/sda5 Linux ext3 ~125MB /dev/sda6 Linux LVM Once the LiveCD environment starts I install LVM and cryptsetup, 'mount' the LVM volumes and unlock them (each is secured using LUKS and a key-file. VG = Ubuntu LVs (in /dev/Ubuntu/) = Jaunty, Jaunty_var, home encrypted (in /dev/mapper) = root (ext4), var ext4), home (ext3) sda3 is for swap sda5 is for /boot/ (ext3) Binary package hint: ubiquity Affects: Jaunty Live-CD alpha-3 (and daily 0203.1) amd64 The description of this bug report might also read "Separate /boot/ partition fails". The installer fails because a partition it is trying to prepare *disappears* as a result of one of the many scan/file-system detection operations that ubiquity/partman perform. I've been unable to pin-point the culprit so far. Note: this affects installations that don't attempt to use LVM/encryption as described in the initial description - see later comments for 'simpler' scenarios that still fail. Checking /proc/partitions shows that sda5 has gone missing. Before: major minor #blocks name 7 0 690828 loop0 8 0 390711384 sda 8 1 9764864 sda1 8 2 28738560 sda2 8 3 4194304 sda3 8 4 1 sda4 8 5 122880 sda5 8 6 347889719 sda6 8 16 2000880 sdb 8 17 2000061 sdb1 252 0 19529728 dm-0 252 1 9764864 dm-1 252 2 4882432 dm-2 252 3 9764864 dm-3 252 4 3903488 dm-4 252 5 9763836 dm-5 252 6 3902460 dm-6 252 7 19528700 dm-7 After: major minor #blocks name 7 0 690828 loop0 8 0 390711384 sda 8 1 9764864 sda1 8 2 28738560 sda2 8 3 4194304 sda3 8 4 1 sda4 8 6 347889719 sda6 8 16 2000880 sdb 8 17 2000061 sdb1 252 0 19529728 dm-0 252 1 9764864 dm-1 252 2 4882432 dm-2 252 3 9764864 dm-3 252 4 3903488 dm-4 252 5 9763836 dm-5 252 6 3902460 dm-6 252 7 19528700 dm-7 Although I'm testing Jaunty amd64 alpha-3 live-CD, this bug also occurs using the Intrepid amd64 live-CD. The Sony Vaio VGN-FE41Z (laptop) has a single new SATA 400GB disk-drive (replacing the original 200GB drive to gain more space). It has been organised thus: /dev/sda1 Windows Recovery ntfs ~9GB /dev/sda2 Windows Vista ntfs ~28GB /dev/sda3 Linux swap ~4GB /dev/sda4 extended /dev/sda5 Linux ext3 ~125MB /dev/sda6 Linux LVM Once the live-CD environment starts I install LVM and cryptsetup, 'mount' the LVM volumes and unlock them (each is secured using LUKS and a key-file. VG = Ubuntu LVs (in /dev/Ubuntu/) = Jaunty, Jaunty_var, home encrypted (in /dev/mapper) = root (ext4), var ext4), home (ext3) sda3 is for swap sda5 is for /boot/ (ext3)
2009-02-05 13:39:51 TJ title Separate /boot/ partition fails Kernel *loses* partitions at partitioning stage; installer fails
2009-02-05 20:37:28 TJ description Binary package hint: ubiquity Affects: Jaunty Live-CD alpha-3 (and daily 0203.1) amd64 The description of this bug report might also read "Separate /boot/ partition fails". The installer fails because a partition it is trying to prepare *disappears* as a result of one of the many scan/file-system detection operations that ubiquity/partman perform. I've been unable to pin-point the culprit so far. Note: this affects installations that don't attempt to use LVM/encryption as described in the initial description - see later comments for 'simpler' scenarios that still fail. Checking /proc/partitions shows that sda5 has gone missing. Before: major minor #blocks name 7 0 690828 loop0 8 0 390711384 sda 8 1 9764864 sda1 8 2 28738560 sda2 8 3 4194304 sda3 8 4 1 sda4 8 5 122880 sda5 8 6 347889719 sda6 8 16 2000880 sdb 8 17 2000061 sdb1 252 0 19529728 dm-0 252 1 9764864 dm-1 252 2 4882432 dm-2 252 3 9764864 dm-3 252 4 3903488 dm-4 252 5 9763836 dm-5 252 6 3902460 dm-6 252 7 19528700 dm-7 After: major minor #blocks name 7 0 690828 loop0 8 0 390711384 sda 8 1 9764864 sda1 8 2 28738560 sda2 8 3 4194304 sda3 8 4 1 sda4 8 6 347889719 sda6 8 16 2000880 sdb 8 17 2000061 sdb1 252 0 19529728 dm-0 252 1 9764864 dm-1 252 2 4882432 dm-2 252 3 9764864 dm-3 252 4 3903488 dm-4 252 5 9763836 dm-5 252 6 3902460 dm-6 252 7 19528700 dm-7 Although I'm testing Jaunty amd64 alpha-3 live-CD, this bug also occurs using the Intrepid amd64 live-CD. The Sony Vaio VGN-FE41Z (laptop) has a single new SATA 400GB disk-drive (replacing the original 200GB drive to gain more space). It has been organised thus: /dev/sda1 Windows Recovery ntfs ~9GB /dev/sda2 Windows Vista ntfs ~28GB /dev/sda3 Linux swap ~4GB /dev/sda4 extended /dev/sda5 Linux ext3 ~125MB /dev/sda6 Linux LVM Once the live-CD environment starts I install LVM and cryptsetup, 'mount' the LVM volumes and unlock them (each is secured using LUKS and a key-file. VG = Ubuntu LVs (in /dev/Ubuntu/) = Jaunty, Jaunty_var, home encrypted (in /dev/mapper) = root (ext4), var ext4), home (ext3) sda3 is for swap sda5 is for /boot/ (ext3) Binary package hint: ubiquity Affects: Jaunty live-CD alpha-4, alpha-3 and daily 0203.1 (amd64) The description of this bug report might also read "Separate /boot/ partition fails". The installer fails because a partition it is trying to prepare *disappears* as a result of one of the many scan/file-system detection operations that ubiquity/partman perform. I've been unable to pin-point the culprit so far. Note: this affects installations that don't attempt to use LVM/encryption as described in the initial description - see later comments for 'simpler' scenarios that still fail. Checking /proc/partitions shows that sda5 has gone missing. Before: major minor #blocks name 7 0 690828 loop0 8 0 390711384 sda 8 1 9764864 sda1 8 2 28738560 sda2 8 3 4194304 sda3 8 4 1 sda4 8 5 122880 sda5 8 6 347889719 sda6 8 16 2000880 sdb 8 17 2000061 sdb1 252 0 19529728 dm-0 252 1 9764864 dm-1 252 2 4882432 dm-2 252 3 9764864 dm-3 252 4 3903488 dm-4 252 5 9763836 dm-5 252 6 3902460 dm-6 252 7 19528700 dm-7 After: major minor #blocks name 7 0 690828 loop0 8 0 390711384 sda 8 1 9764864 sda1 8 2 28738560 sda2 8 3 4194304 sda3 8 4 1 sda4 8 6 347889719 sda6 8 16 2000880 sdb 8 17 2000061 sdb1 252 0 19529728 dm-0 252 1 9764864 dm-1 252 2 4882432 dm-2 252 3 9764864 dm-3 252 4 3903488 dm-4 252 5 9763836 dm-5 252 6 3902460 dm-6 252 7 19528700 dm-7 Although I'm testing Jaunty amd64 alpha-3 live-CD, this bug also occurs using the Intrepid amd64 live-CD. The Sony Vaio VGN-FE41Z (laptop) has a single new SATA 400GB disk-drive (replacing the original 200GB drive to gain more space). It has been organised thus: /dev/sda1 Windows Recovery ntfs ~9GB /dev/sda2 Windows Vista ntfs ~28GB /dev/sda3 Linux swap ~4GB /dev/sda4 extended /dev/sda5 Linux ext3 ~125MB /dev/sda6 Linux LVM Once the live-CD environment starts I install LVM and cryptsetup, 'mount' the LVM volumes and unlock them (each is secured using LUKS and a key-file. VG = Ubuntu LVs (in /dev/Ubuntu/) = Jaunty, Jaunty_var, home encrypted (in /dev/mapper) = root (ext4), var ext4), home (ext3) sda3 is for swap sda5 is for /boot/ (ext3)
2009-02-06 23:13:52 TJ ubiquity: status New Invalid
2009-02-06 23:13:52 TJ ubiquity: statusexplanation
2009-02-08 17:18:51 Colin Watson ubiquity: status Invalid Confirmed
2009-02-08 17:18:51 Colin Watson ubiquity: bugtargetdisplayname ubiquity (Ubuntu) parted (Ubuntu)
2009-02-08 17:18:51 Colin Watson ubiquity: bugtargetname ubiquity (Ubuntu) parted (Ubuntu)
2009-02-08 17:18:51 Colin Watson ubiquity: statusexplanation 17:16 <IntuitiveNipple> cjwatson: I found it easy to recreate the issue: create the partition table with fdisk -u and start each partition on the next availabe sector number... in 'cyclinder' mode the end and next-start will be in the same cylinder... and that was the root cause
2009-02-08 17:18:51 Colin Watson ubiquity: title Bug #324987 in ubiquity (Ubuntu): "Kernel *loses* partitions at partitioning stage; installer fails" Bug #324987 in parted (Ubuntu): "Kernel *loses* partitions at partitioning stage; installer fails"
2009-02-12 14:41:12 Colin Watson parted: assignee kamion
2012-05-17 14:06:53 Colin Watson parted (Ubuntu): assignee Colin Watson (cjwatson)
2012-05-17 18:17:07 Phillip Susi parted (Ubuntu): importance Undecided Low
2012-05-17 18:17:07 Phillip Susi parted (Ubuntu): status Confirmed Triaged
2012-05-17 18:17:07 Phillip Susi parted (Ubuntu): assignee Phillip Susi (psusi)
2012-05-17 18:18:23 Phillip Susi summary Kernel *loses* partitions at partitioning stage; installer fails parted doesn't handle extended partitions that don't leave at least a 2 sector gap
2012-05-17 18:20:52 Phillip Susi description Binary package hint: ubiquity Affects: Jaunty live-CD alpha-4, alpha-3 and daily 0203.1 (amd64) The description of this bug report might also read "Separate /boot/ partition fails". The installer fails because a partition it is trying to prepare *disappears* as a result of one of the many scan/file-system detection operations that ubiquity/partman perform. I've been unable to pin-point the culprit so far. Note: this affects installations that don't attempt to use LVM/encryption as described in the initial description - see later comments for 'simpler' scenarios that still fail. Checking /proc/partitions shows that sda5 has gone missing. Before: major minor #blocks name 7 0 690828 loop0 8 0 390711384 sda 8 1 9764864 sda1 8 2 28738560 sda2 8 3 4194304 sda3 8 4 1 sda4 8 5 122880 sda5 8 6 347889719 sda6 8 16 2000880 sdb 8 17 2000061 sdb1 252 0 19529728 dm-0 252 1 9764864 dm-1 252 2 4882432 dm-2 252 3 9764864 dm-3 252 4 3903488 dm-4 252 5 9763836 dm-5 252 6 3902460 dm-6 252 7 19528700 dm-7 After: major minor #blocks name 7 0 690828 loop0 8 0 390711384 sda 8 1 9764864 sda1 8 2 28738560 sda2 8 3 4194304 sda3 8 4 1 sda4 8 6 347889719 sda6 8 16 2000880 sdb 8 17 2000061 sdb1 252 0 19529728 dm-0 252 1 9764864 dm-1 252 2 4882432 dm-2 252 3 9764864 dm-3 252 4 3903488 dm-4 252 5 9763836 dm-5 252 6 3902460 dm-6 252 7 19528700 dm-7 Although I'm testing Jaunty amd64 alpha-3 live-CD, this bug also occurs using the Intrepid amd64 live-CD. The Sony Vaio VGN-FE41Z (laptop) has a single new SATA 400GB disk-drive (replacing the original 200GB drive to gain more space). It has been organised thus: /dev/sda1 Windows Recovery ntfs ~9GB /dev/sda2 Windows Vista ntfs ~28GB /dev/sda3 Linux swap ~4GB /dev/sda4 extended /dev/sda5 Linux ext3 ~125MB /dev/sda6 Linux LVM Once the live-CD environment starts I install LVM and cryptsetup, 'mount' the LVM volumes and unlock them (each is secured using LUKS and a key-file. VG = Ubuntu LVs (in /dev/Ubuntu/) = Jaunty, Jaunty_var, home encrypted (in /dev/mapper) = root (ext4), var ext4), home (ext3) sda3 is for swap sda5 is for /boot/ (ext3) Parted fails to update the kernel partition table when an extended partition starts on the sector immediately following the EBR instead of leaving two sectors for LILO. This can cause otherwise apparently fine partitions to get "lost" during installation when parted deletes the kernel partition table and tries to recreate it and fails.