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