Lucid/Maverick (server amd64) does not boot from RAID1

Bug #765779 reported by yasar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
NULL Project
Invalid
Undecided
Unassigned

Bug Description

Config:

HP Proliant Microserver N36L, 1GB RAM, 4x2TB-HDD, USB-CDROM, Bootable USB-Stick (for Install).

hdd layout:

/dev/md0: raid1, 1GB, /dev/sda1 and /dev/sdb1 (/boot) each 1GB
/dev/md1: raid1, 1GB, /dev/sdc1 and /dev/sdd1 (/scratch) each 1GB
/dev/md2: raid5, 12GB, /dev/sd[a-d]2 (swap) each 4GB
/dev/md3: raid5, 60GB, /dev/sd[a-d]3 (/) each 20GB
/dev/md4: raid5, 6TB, /dev/sd[a-d]4 (/srv) each (2TB-25GB)

I tried both, lucid and maverick to install on this box and everything goes ok, until the system reboots.

Grub gets a timeout for and I'm thrown in a busybox-shell. /proc/mdstat shows, that only /dev/md4 was started. I can't start md0 to md3 with mdadm, 'cause the systems complains about devices /dev/sdx are in use.

Tried also to create new initramdisks with raid-modules included, but no chance. I could have tried to build the raids with hardy and then upgrade, but hardy doesn't support the sata controller.

ya

Tags: boot install raid
Revision history for this message
yasar (ubuntu-bugreport-yait) wrote :

Before I also tried a installation with lvm, which had the same results.

Revision history for this message
Aiman Baharna (aiman) wrote :

Please file bug in Ubuntu if that is what you meant.

affects: lucid → null
Changed in null:
status: New → 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.