I removed a drive from my raid array, how can I get it to boot alone?

[Cindy1980]

I removed a drive from my raid 1 array, how can I get it to boot alone(without the raid card)? It keeps kernel panicing at boot, seems it is trying to load the module for the raid card.

When booting I notice:
loading aacraid.ko

and get the errors:
mkrootdev: label / not found
error 2 mounting ext3
error 2 mounting none

How do I get it to stop trying to load aacraid.ko?


Raid Type: 1 Mirroring
Drive Type: SATA
OS: RedHat Enterprise

I can access the drive ok when I boot from the cd in rescue mode, what do I need to change once Im in rescue mode?

 

[Chacalinc]

take a look to /etc/modules.con and comment the line where the module is. Also, check the /etc/fstab in order to comment all filesystem mounted at boot time in the disk drive in question.

Chacal, Inc.

 

[zeland]

You said you took the drive off your RAID controller. Is this a custom kernel you are using? Could it be that you don't have the proper drivers/modules compiled for the current SATA controller that you are connected to in your kernel?


--== Anything can go wrong. It's just a matter of how far wrong it will go till people think its right. ==--

 

[Trevoke]

What kind of RAID array is it?
Sounds like nailing jelly to a tree, really.
Maybe a RAID-1 might do it alright (mirror), but if it's RAID-0 or RAID-5, I don't think it'll work.

A RAID array creates a link in-between the hard drives, and breaking that links makes the OS flip you the finger.

-Haben sie fosforos?
-No tiengo caballero, but I have un briquet.

 

[Trevoke]

Ooh I hate it when I skip a line of the original post.

Chacalinc is right; it looks like it's simply trying to mount something that it can't find.

-Haben sie fosforos?
-No tiengo caballero, but I have un briquet.