installer allows raid0 on /boot

Bug #106802 reported by Matt LaPlante
4
Affects Status Importance Assigned to Milestone
partman-md (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I downloaded the alternate cd for 7.04 (http://releases.ubuntu.com/7.04/ubuntu-7.04-beta-alternate-i386.iso) to mess around with the installer. One issue that occurred to me was that it would allow the user to assign /boot to a RAID0 array. This works grandly, right up until you get to the grub-install phase. grub and lilo both fail to install at this point, and the installation is wasted. AFAIK, booting from a raid0 partition created by the installer just isn't possible. It seems fairly trivial logically (without knowing the code behind the installer) that it should be able to check if the current partition is raid0 when trying to assign /boot, and disallow it. This might save some people a bit of confusion and wasted time later on.

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

I thought lilo-installer was meant to be able to install with /boot on RAID; but if this isn't possible then partman-md could certainly check for this condition.

Revision history for this message
Soren Hansen (soren) wrote :

Booting from raid is perfectly possible. IMHO, rather than checking for it and not allowing it, it should be fixed to make it actually work.

Revision history for this message
Matt LaPlante (cybrmatt) wrote :

Saying Raid works is ambiguous; I know for example that Raid 1 works. It's raid 0 that's not working, and I'm not seeing any immediate documentation that suggests otherwise. Can you point to some?

Revision history for this message
xteejx (xteejx) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in partman-md (Ubuntu):
status: New → Incomplete
Revision history for this message
xteejx (xteejx) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in partman-md (Ubuntu):
status: Incomplete → Invalid
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.