Dapper installer prevents LVM on software RAID

Bug #98540 reported by Hans
This bug report is a duplicate of:  Bug #22899: Installer complains about /dev/md/0p1. Edit Remove
2
Affects Status Importance Assigned to Milestone
parted (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

Tried to install Ubuntu 6.06.1 Server on a machine with two SATA drives. The basic drive layout I attempted included LVM on a software RAID:

/dev/md0 /boot ext3 100MB
/dev/md1 VolGroup00 LVM PV max

I created 'physical volume for RAID' partitions on both drives, created the MD devices, set md0 to ext3 for /boot, and set md1 to 'physical volume for LVM'. Then I selected 'Configure the Logical Volume Manager' and '<Yes>' to write the changes to disk. At this point, I get the following error:

"Error informing the kernel about modifications to partition /dev/md/1p1 -- Invalid argument. This means Linux won't know about any changes you made to /dev/md/1p1 until you reboot -- so you shouldn't mount it or use it in any way before rebooting.

Error!!!"

Unable to reproduce with Edgy, so it appears the bug has since been fixed. However, since Dapper is the LTS release, the fix should be applied to Dapper as well... especially for the server edition.

(As far as I can tell, the issue and resolution is provided in debian bug # 377391.)

Revision history for this message
Fabio Massimo Di Nitto (fabbione) wrote :

It's an harmless but annoying message. You can safely ignore it and continue the installation.

Fabio

Revision history for this message
Hans (hansomli) wrote :

I'll try the install again tonight. My earlier attempt appeared to have discrepancies between how I configured my partitions in the installer and the final result, though it quite possibly could have been a mistake on my part.

Revision history for this message
Hans (hansomli) wrote :

Reinstall was successful. Thanks!

While harmless, I consider this a "marketing" issue for an LTS server release. In my own experience, I almost dropped evaluating Ubuntu when I hit the error. (Certainly hadn't seen a similar error when installing RHEL on similar hardware.) However harmless, newbies may question whether the server release is production ready, which is unfortunate. I hope the fix will be backported to dapper since we're 12 months from the next LTS release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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