Raid 1 boot problem

[Gone fishing]

I've set up a raid1 on Gutsy server RC, I've go it set up so it works using these instructions: http://advosys.ca/viewpoints/2007/04/setting-up-software-raid-in-ubuntu-server/ (I've set up three raid1 partitions /, /home and swap) The problem is if I test it by disconnecting one of the drives Gutsy wont boot.

If I run the following commands

jhjk@lampserver:~$ grep /dev/md /etc/fstab
# /dev/md0
# /dev/md1
# /dev/md2
jhjk@lampserver:~$

jhjk@lampserver:~$ df -h / /home
Filesystem Size Used Avail Use% Mounted on
/dev/md0 15G 2.6G 12G 19% /
/dev/md1 131G 225M 124G 1% /home

jhjk@lampserver:~$ cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md2 : active raid1 sda3[0] sdb3[1]
1991936 blocks [2/2] [UU]

md1 : active raid1 sda2[0] sdb2[1]
138672960 blocks [2/2] [UU]

md0 : active raid1 sda1[0] sdb1[1]
15623104 blocks [2/2] [UU]

unused devices: <none>

and

jhjk@lampserver:~$ sudo mdadm --query --detail /dev/md0
/dev/md0:
Version : 00.90.03
Creation Time : Wed Oct 17 00:51:54 2007
Raid Level : raid1
Array Size : 15623104 (14.90 GiB 16.00 GB)
Used Dev Size : 15623104 (14.90 GiB 16.00 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 0
Persistence : Superblock is persistent

Update Time : Wed Oct 17 09:52:49 2007
State : active
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0

UUID : 2aa5c0cf:d2ed8c33:31b70149:8694a062
Events : 0.7

Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
jhjk@lampserver:~$

similar results for md1 and md2

However if I test it by unplugging a hard drive it wont boot

I've also tried creating a small non Raid /boot partition, but again if I unplug a drive the system wont boot (grub starts fails to mount the raid)

[rihad (rihad)]

Does my case look similar?

I've installed 7.10 amd64 on a Intel Server System 1500 with 2 SAS drives, which unfortunately has a SW raid system incompatible with open OS', so I'm trying to use Linux mdadm. The first partition on both drives was created and marked as bootable, and raid autodetect. The installation goes well and the system boots ok on /dev/md0, and /proc/mdstat and mdadm -D show everything's in sync. After shutting down the system and unplugging one of the drives -- it doesn't matter which -- the systems waits for 2-3 minutes at the "loading, please wait' prompt, then spits out some errors like "stdin: error 0" and then the output similar to what happens when you run modprobe with no arguments, and some more "no such file or directory" regarding parts under the root fs (like /dev/ /sys/ /proc etc.), eventually dropping into a busybox shell.

I also tried running this on both drives, with no effect whatsoever.
Quote:
grub-install /dev/sda
grub
grub: device (hd0) /dev/sdb
grub: root (hd0,0)
grub: setup (hd0)
grub: quit

[Gone fishing (humpmihk-msn)]

Yep that looks like it.

It seems to be a bug but I found this in the bugs and it looks like so
solution https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/120375 . I
seem to remember being dumped at some thing like ram file system scree,

However, I gave up and use Opensuse, which, I can't say I like as much
as Ubuntu particularly on the Desktop (but this is a server), every
thing worked (including the RAID) without too much struggle and I am not
an ubergeek.

Any way good luck

rihad wrote:
> Does my case look similar?
>
> I've installed 7.10 amd64 on a Intel Server System 1500 with 2 SAS
> drives, which unfortunately has a SW raid system incompatible with open
> OS', so I'm trying to use Linux mdadm. The first partition on both
> drives was created and marked as bootable, and raid autodetect. The
> installation goes well and the system boots ok on /dev/md0, and
> /proc/mdstat and mdadm -D show everything's in sync. After shutting down
> the system and unplugging one of the drives -- it doesn't matter which
> -- the systems waits for 2-3 minutes at the "loading, please wait'
> prompt, then spits out some errors like "stdin: error 0" and then the
> output similar to what happens when you run modprobe with no arguments,
> and some more "no such file or directory" regarding parts under the root
> fs (like /dev/ /sys/ /proc etc.), eventually dropping into a busybox
> shell.
>
> I also tried running this on both drives, with no effect whatsoever.
> Quote:
> grub-install /dev/sda
> grub
> grub: device (hd0) /dev/sdb
> grub: root (hd0,0)
> grub: setup (hd0)
> grub: quit
>
>

[Gone fishing (humpmihk-msn)]

Yep that looks like it.

It seems to be a bug but I found this in the bugs and it looks like so
solution https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/120375 . I
seem to remember being dumped at some thing like ram file system screen,

However, I gave up and used Opensuse, which, I can't say I like as much
as Ubuntu, particularly on the Desktop (but this is a server), every
thing worked, however, (including the RAID) without too much struggle
and I am not
an ubergeek.

Any way good luck