1 |
On Sunday 21 August 2005 20:29, David Busby wrote: |
2 |
> List, |
3 |
> I've got a Super Micro P4SCT+ that uses the Marvell SATA controller that |
4 |
> Linux doesn't know out-of-the-box. There was the mv_sata module provided |
5 |
> by ABit that I found, and it compiles and loads into my 2.6.12 kernel. I |
6 |
> can see the drives and have made a raid out of them no problem. I'm |
7 |
> currently booting off the Intel SATA in the machine from /dev/sda The |
8 |
> other drives are /dev/sdb,c,d. OK, so what I want to do is this: Remove |
9 |
> the current /dev/sda and bump the /dev/sdb,c,d each up by one and then boot |
10 |
> of them. /dev/sdb1,c1,d1 are set as RAID0+hotspare and configured/grub-ed |
11 |
> etc. What I can't do is get the initrd to work. I've added the module and |
12 |
> can see when it boots that it finds those devices but then it looks like it |
13 |
> cannot see my devices. I get a Kernel Panic not init found, then it says |
14 |
> to try passing init= to the kernel. I don't understand that, what must I |
15 |
> do? I'm using udev so perhaps when the kernel is booting it cannot see my |
16 |
> devices in /dev ? |
17 |
|
18 |
I've got one of those controllers, on a Supermicro PCI card. |
19 |
I boot from other drives, so don't have any initrd stuff. I do still have a |
20 |
problem with it though. |
21 |
That problem is that once the module is loaded, it takes several seconds to |
22 |
actually find, and register those drives, before they are available for use. |
23 |
So long in fact that if I load it, then 3 raid modules automatically during |
24 |
start up, by the time mdadm gets run the drives still aren't there! |
25 |
I simple modified the modules init script to put a 1 second pause between each |
26 |
modprobe. |
27 |
Perhaps a similar pause after loading the module in your initrd would help. |
28 |
|
29 |
-- |
30 |
Mike Williams |
31 |
-- |
32 |
gentoo-user@g.o mailing list |