I'm trying to turn an existing Debian Sarge installation on hda into a RAID1 setup by building the md devices on hdc (with hda missing), copying the system to the md devices, rebooting, and then re-partitioning hda and adding it to the array. I'm doing it via a remote SSH session to make sure I understand it before renting a remote dedicated server that I'll do the same to. I can do it without problems on a setup with just / and swap partitions. I'm running into problems rebooting into the degraded array, though, when I use three partitions - /, /boot and swap. Apparantly /dev/md1 (the / filesytem) is not up when needed during the reboot into the md array, since I get: mdadm: /dev/md0 has been started with 1 drive (out of 2) pivot_root: No such file or directory /sbin/init: 432: cannot open /dev/console: No such file Kernel panic: Attempted to kill init! I have /boot on /dev/md0 (hda1 and hdc1), / on /dev/md1 (hda2 and hdc2) , and swap on /dev/md2 (hda3 and hdc3). my /boot/grub/menu.lst has: title Debian GNU/Linux, kernel 2.6.8-2-386 RAID root (hd0,0) kernel /vmlinuz-2.6.8-2-386 root=/dev/md1 ro initrd /initrd.img-2.6.8-2-386RAID savedefault boot title Debian GNU/Linux, kernel 2.6.8-2-386 root (hd0,0) kernel /vmlinuz-2.6.8-2-386 root=/dev/hda2 ro initrd /initrd.img-2.6.8-2-386 savedefault boot on both hda1 and /dev/md0 The whole procedure in mind numbing detail is at: http://www.issociate.de/board/post/25205/How_to_build_bootable_RAID_1_as_a_module_with_Grub_on_Debian_Sarge.html Question: Is getting /dev/md1 up in time the job of initrd.img? Did I hose this at the initrd.img level, grub level, or elsewhere? Thanks in advance, Steve