I just tried to install 10.04 amd64 server on a box with 3 500G WD and 1 500G Hitachi Drives. I wanted to setup Raid 5 and then LVM for all the partitions. I used the latest ISO files.
Raid 5 for sda1,sdb1,sdc1,sdd1
LVM named system: /, /boot, /home, /var, /tmp, /usr, /usr/local, /opt
After installation and the box rebooted, I got error and initramfs prompt.
ALERT!! /dev/mapper/system-root does not exist. Dropping to a shell!
cat /proc/mdstat and I saw that md0 raid 5 with sd[abcd] is resyncing...
ls /dev/mapper
control
ls /dev/md*
/dev/md0p1 /dev/md0
As you can see there is no system-root and etc under /dev/mapper.
I saw that in /etc/mdadm/mdadm.conf
ARRAY /dev/md0 level=raid5 num-devices=4 UUID=........
ls /dev/disk/by-*
/dev/disk/by-id/ /dev/disk/by-path
As you can see there is no /dev/disk/by-uuid in /dev/disk.
Previously, I encountered similar problems when installed on a system with 2 250GB WD disks (1 big Raid1 and then LVM all partitions). I then tried to set 3 Raid 1 small partitions for swap, / and /boot and 1 big Raid1 on LVM for other partitions. With this set up, 10.04 amd64 server was able to successfully booted up.
This is a very serious bug considering that a lot of people will be running server edition with some types of RAIDx and the installation failed to correctly set these up. This bug is a show stopper and makes users pondering the quality of each Ubuntu releases.
I just tried to install 10.04 amd64 server on a box with 3 500G WD and 1 500G Hitachi Drives. I wanted to setup Raid 5 and then LVM for all the partitions. I used the latest ISO files.
Raid 5 for sda1,sdb1,sdc1,sdd1
LVM named system: /, /boot, /home, /var, /tmp, /usr, /usr/local, /opt
After installation and the box rebooted, I got error and initramfs prompt.
ALERT!! /dev/mapper/ system- root does not exist. Dropping to a shell!
cat /proc/cmdline /vmlinuz- 2.6.32- 21-server root=/dev/ mapper/ system- root ro quiet
BOOT_IMAGE=
cat /proc/mdstat and I saw that md0 raid 5 with sd[abcd] is resyncing...
ls /dev/mapper
control
ls /dev/md*
/dev/md0p1 /dev/md0
As you can see there is no system-root and etc under /dev/mapper.
I saw that in /etc/mdadm/ mdadm.conf
ARRAY /dev/md0 level=raid5 num-devices=4 UUID=........
ls /dev/disk/by-*
/dev/disk/by-id/ /dev/disk/by-path
As you can see there is no /dev/disk/by-uuid in /dev/disk.
Previously, I encountered similar problems when installed on a system with 2 250GB WD disks (1 big Raid1 and then LVM all partitions). I then tried to set 3 Raid 1 small partitions for swap, / and /boot and 1 big Raid1 on LVM for other partitions. With this set up, 10.04 amd64 server was able to successfully booted up.
This is a very serious bug considering that a lot of people will be running server edition with some types of RAIDx and the installation failed to correctly set these up. This bug is a show stopper and makes users pondering the quality of each Ubuntu releases.