[K12OSN] Attempting to Setup SATA RAID

[Brad Johnson]

On Jan 27, 2006, at 2:01 PM, Steve Hampton wrote:

> Hi List,
>
> If anyone has ran into this problem before, and knows a quick solution
> please share it with me, otherwise I am giving up on this .  I have
> researched it to death and I have trouble shot it to the point that I
> know it is a linux problem, I am just hoping there is a quick fix for
> it. I will detail the problem below.
>
> I have an intel motherboard with an onboard Silicon Image SATA RAID
> controller.  I have been running my k12ltsp server without a safty
> net, i know shame on me, but I finally decidied to setup RAID 1 so
> that I would have a safety net.
>
> I have a Seagate 120GB SATA drive with my K12 install on it.  I added
> a Western Dig. 120GB SATA drive and then rebooted, went into the
> Silicon Image  Configuration tool at bootup and created a RAID set and
> mirrored my first drive to the second one.  Then when I rebooted the
> machine grub comes up i choose the kernel and then right after it
> begins to load the kernel before the INIT version and it says
> "Starting Fedora Core"
>
> It fails with the error "IRQ 10 Nobody cares!"  and then freezes with
> "Disableing irq 10" to fix the problem I simply have to reboot, delete
> my Raid set in the Silicon Image config tool and then turn the machine
> off unhook the second drive and i am using the server now to write
> this email.  But I would like for this to work.  Below is the relevent
> info from my grub file if that helps
>
> title Fedora Core (2.6.12-1.1381_FC3)
>         root (hd0,0)
>         kernel /vmlinuz-2.6.12-1.1381_FC3 ro root=LABEL=/ rhgb quiet
>         initrd /initrd-2.6.12-1.1381_FC3.img
>
> Thanks
> Steve
>
>
> Open Source, The Right Thing To Do!
>
> _______________________________________________
> K12OSN mailing list
> K12OSN at redhat.com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>
>


Hi Steve,

I had the same problem setting up an new server yesterday...not an  
intel board...actually an asus Nvidia opteron board.  Long story  
short...same errors.  BIOS update made errors go away, so you may  
want to explore that possiblity.

Brad