<html>yes. I will cut and paste. turns out another thing someone did was manually do a mv /etc/rc5.d/S40smartd /etc/rc5.d/K40smartd I don't know what effect this may have had? -----Original Message----- F ------------------------------ Message: 5 Date: Mon, 10 Dec 2007 07:19:55 -0800 From: Sean Bruno <sean.bruno@dsl-only.net> Subject: Re: Raid 1 To: For users of Fedora <fedora-list@redhat.com> Message-ID: <1197299995.25236.3.camel@home-desk> Content-Type: text/plain On Mon, 2007-12-10 at 12:45 +0000, tony.chamberlain@lemko.com wrote: > > > We put Raid 1 (software) on an IBM server. I installed some software > and made sure everything > worked. Then we realized we needed to set up grub so the machine > would boot from either disk. > So under Linux Rescue we went into grub and did > > device (hd0) /dev/sda > root (hd0,0) > setup (hd0) > > device (hd1) /dev/sdb > root (hd1,0) > setup (hd1) > > But then when we booted, everything failed. I noticed a commone > message "initlog not found" so I looked on another machine and > foiund it under /sbin but not on this one. So I copied it to /sbin > and > rebooted. It got a lot farther this time, but then got stuck on not > being > able to find a default theme. > > I also noticed that linux rescue puts the linux under /mnt/sysimage > (so /etc is /mnt/sysimage/etc, /home is /mnt/sysimage/home, etc) > but in addition to those there was still a /etc, /home, etc. I > suppose > one was the mirrored disk. > > So it sounds like we might not have done something correctly. Anyone > have any idea? We did set up the whole raid system correctly during > Linux installation on a different machine, and then used that > anaconda-ks.cfg > file for this one (removing the "#"'s where the raid stuff was > commented out > in the config file). Can you post the output of "mdadm --detail /dev/mdX" for each raid device on your machine? It almost sounds like the RAID isn't working for you. Sean </html>