/boot destroyed during install even when formatting disabled (alternate installer)
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| partman-md (Ubuntu) |
Fix Released
|
High
|
Colin Watson | ||
| Lucid |
Fix Released
|
High
|
Colin Watson | ||
Bug Description
Although at first blush this seems to be bug #527401, I don't think it's related to grub2. It's also a regression from alpha3; whereas #527401 also applies to lucid alpha3, this bug does not. I am using the alternate installer.
I have an existing server running Hardy with LVM on MD, with several disks partitioned with /dev/sdX1 as 256M and /dev/sdX2 as the rest, with /dev/md0 as raid1 using /dev/sd?1, and /dev/md1 as raid5 using /dev/sd?2.
/dev/md0 is formatted with ext4 and is /boot. /dev/md1 is the only PV for volume group vg0, and vg0 has LVs swap (2G), root (50G), lucid (50G), data.
The existing root LV contains Hardy, and my intent is to install Lucid fresh onto the new lucid LV, and share /boot between both installs, allowing me to easily reboot into Hardy if things go badly. Therefore, during the install, I specifically do not format /boot.
I'm obviously going to wait for 10.04 final before installing it on the actual server. For now I am staging it under a VM. This problem is consistently repeatable with beta1, and consistently absent with alpha3.
During the install, I select manual partitioning, and then:
- Select 'lucid' LV: use as: ext4; mount point: /
- Select 'swap' LV: use as swap
- Select RAID1 device #0: use as: ext3; format: no, keeping existing data; mount point: /boot
It is worth noting that in the partitioner, several partitions and LVs in the list show an "unusable" portion, e.g.:
RAID1 device #0 - 263.1MB Software RAID device
#1 262.1MB K ext3 /boot
917.5kB unusable
Lucid Alpha3 did not show these unusable lines. (Could be irrelevant, but thought I'd mention it.)
At this point, if I drop to another terminal, I am able to mount /dev/md0, so it's valid, and everything looks fine. I unmount before proceeding.
After selecting "Finish partitioning and write changes to disk" it warns me that "/dev/md0 assigned to /boot has not been marked for formatting." Alpha3 did this as well. I proceed.
It then says the partition tables of the following devices are changed:
LVM VG vg0, LV lucid
LVM VG vg0, LV swap
RAID1 device #0 <---- NOT LISTED IN ALPHA3
The following partitions are going to be formatted:
LVM VG vg0, LV lucid as ext4
LVM VG vg0, LV swap as swap
If I proceed to write changes to disk, it formats /, and then says:
"The attempt to mount a file system with type ext3 in RAID1 device #0 at /boot failed."
Now if I drop to a shell and try to mount /dev/md0, it fails:
~ # mount -t ext3 /dev/md0 /mnt
mount: mounting /dev/md0 on /mnt failed: Invalid argument.
| Jason Tackaberry (tack) wrote | #1 |
| Ben Scholzen 'DASPRiD' (dasprid) wrote | #2 |
| Philip Muškovac (yofel) wrote | #3 |
| affects: | ubuntu → debian-installer (Ubuntu) |
| tags: | added: lucid |
| Ben Scholzen 'DASPRiD' (dasprid) wrote | #4 |
| Ben Scholzen 'DASPRiD' (dasprid) wrote | #5 |
| Ben Scholzen 'DASPRiD' (dasprid) wrote | #6 |
| Ben Scholzen 'DASPRiD' (dasprid) wrote | #7 |
| Ben Scholzen 'DASPRiD' (dasprid) wrote | #8 |
| Colin Watson (cjwatson) wrote | #9 |
| Jason Tackaberry (tack) wrote | #10 |
| affects: | debian-installer (Ubuntu Lucid) → partman-md (Ubuntu Lucid) |
| Changed in partman-md (Ubuntu Lucid): | |
| assignee: | nobody → Colin Watson (cjwatson) |
| importance: | Undecided → High |
| milestone: | none → ubuntu-10.04 |
| status: | New → Fix Committed |
| Launchpad Janitor (janitor) wrote | #11 |
| Changed in partman-md (Ubuntu Lucid): | |
| status: | Fix Committed → Fix Released |
| Jason Tackaberry (tack) wrote | #12 |
| Steve Langasek (vorlon) wrote | #13 |
| Alvin Thompson (alvint-deactivatedaccount) wrote | #14 |
| Jason Tackaberry (tack) wrote | #15 |
| NickJ (nickd-jones) wrote | #16 |
Correction: /dev/md0 (/boot) is formatted as ext3, not ext4.