home | list info | list archive | date index | thread index

Re: [OCLUG-Tech] Problem with a raid array at boot time

* Charles Nadeau <charles [ dot ] nadeau [ at ] gmail [ dot ] com> [090319 22:35]:
> > Do you boot with an initrd or do you have a custom kernel?
> 
> I have a custom kernel

You clearly don't boot off this raid array, and I can see that you have
built MD and RAID modules into the kernel but left the ahci ones out.

I suggest you either edit your kernel-source/.config to have CONFIG_MD=m
(a module) or CONFIG_SATA_AHCI=y (a built-in).  Doing both should be
safe also.

Another alternative could be to set CONFIG_MD_AUTODETECT=n, which would
cause the kernel to not even try to bring up the raid array.

Then run:
        make oldconfig
        grep -e CONFIG_MD -e CONFIG_SATA_AHCI .config
        # verify that the CONFIG_MD and CONFIG_SATA_AHCI were not reverted

        make
        make install

That should make the kernel probe the hardware before brining up the
raid.

-Bart

> Ottawa Virtual Machines # lsmod
> Module                  Size  Used by
> vmnet                  32576  13
> vmmon                1840076  0
> snd_pcm_oss            41920  0
> snd_mixer_oss          16768  1 snd_pcm_oss
> snd_seq_oss            32640  0
> snd_seq_midi_event      8640  1 snd_seq_oss
> snd_seq                56992  4 snd_seq_oss,snd_seq_midi_event
> snd_seq_device          8148  2 snd_seq_oss,snd_seq
> snd_hda_intel         461740  7
> snd_pcm                84808  4 snd_pcm_oss,snd_hda_intel
> snd_timer              23376  4 snd_seq,snd_pcm
> nvidia               7804328  26
> snd                    66760  18
> snd_pcm_oss,snd_mixer_oss,snd_seq_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_pcm,snd_timer
> soundcore               8544  1 snd
> aic7xxx               146812  0
> snd_page_alloc          9616  2 snd_hda_intel,snd_pcm
> ahci                   34184  8
> i2c_nforce2             7296  0

-- 
				WebSig: http://www.jukie.net/~bart/sig/