Hi all,

I installed an Ubuntu Hardy Server which worked fine. The root was on a software raid1 /dev/md0 and the swap on another software raid1 /dev/md1.

The only problem is I made a mistake and it didn't work anymore.

Fortunately I knew it could happen, so when it was working I made an image of the root with partimage using SystemRescueCD.

When the Ubuntu Server was broken, I recovered using this image and put it back on the raid /dev/md0 which was the root of my system. Then I installed grub on the MBR in each disk.

When I reboot, grub runs fine. But the Ubuntu Server doesn't want to start and I have this error message:
ALERT DOES NOT FIND MD0
and it starts in busybox mode.

Unfortunately if I boot SystemRescueCD it finds perfectly my 2 software raid1.

I've checked the files mdadm.conf and menu.lst, and they seem correct.

Anyone knows why the recovered Ubuntu Hardy Server from a working image doesn't want to start? Why can't it find /dev/md0?

Thanks.

When I upgraded my normal 1 harddisk installation to raid-1, I needed to write following to the menu.lst.



Notice md=0,/dev/hda1,/dev/hdc
I wrote this under of "### END DEBIAN AUTOMAGIC KERNELS LIST"
I manually disconnected harddisk no. 1 and it still started. Then did same for harddisk no. 2 and it still started.

I also have Debian in another computer, which has been installed directly to RAID, but I haven't checked if it is able to boot from both harddisk. It has different configuration:



I think your raid-partitions are fine, but grub is messed up. If you can mount your md0 with sysresccd, you should be able to see state of harddisk with



After it will work again, please make extra backup of first 63 sectors with dd.


or something like that.