---------- Forwarded message ---------- From: Charles Nadeau <charles [ dot ] nadeau [ at ] gmail [ dot ] com> Date: Fri, Mar 20, 2009 at 6:59 PM Subject: Re: [OCLUG-Tech] Problem with a raid array at boot time To: Bart Trojanowski <bart-oclug [ at ] jukie [ dot ] net> On Fri, Mar 20, 2009 at 12:34 PM, Bart Trojanowski <bart-oclug [ at ] jukie [ dot ] net>wrote: > * 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 I can't find this in my .config: CONFIG_MD=y CONFIG_BLK_DEV_MD=y # CONFIG_MD_LINEAR is not set CONFIG_MD_RAID0=y CONFIG_MD_RAID1=y CONFIG_MD_RAID10=y CONFIG_MD_RAID456=y CONFIG_MD_RAID5_RESHAPE=y # CONFIG_MD_MULTIPATH is not set # CONFIG_MD_FAULTY is not set I reverted to my old settings, recompiled the kernel, copied the new kernel to /boot and rebooted using it. Now I can't mount my array, I am getting this in dmesg: st0: Block limits 1 - 16777215 bytes. Symbol init_mm is marked as UNUSED, however this module is using it. This symbol will go away in the future. Please evalute if this is the right api to use and if it really is, submit a report the linux kernel mailinglist together with submitting your code for inclusion. [7531]: VMCI: Driver initialized. [7531]: Module vmmon: registered with major=10 minor=165 [7531]: Module vmmon: initialized md: bind<sdf2> md: bind<sdg2> md: bind<sdh2> md: bind<sdi2> ReiserFS: md0: warning: sh-2006: read_super_block: bread failed (dev md0, block 2, size 4096) ReiserFS: md0: warning: sh-2006: read_super_block: bread failed (dev md0, block 16, size 4096) ReiserFS: md0: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on md0 ReiserFS: md0: warning: sh-2006: read_super_block: bread failed (dev md0, block 2, size 4096) ReiserFS: md0: warning: sh-2006: read_super_block: bread failed (dev md0, block 16, size 4096) ReiserFS: md0: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on md0 ReiserFS: md0: warning: sh-2006: read_super_block: bread failed (dev md0, block 2, size 4096) ReiserFS: md0: warning: sh-2006: read_super_block: bread failed (dev md0, block 16, size 4096) ReiserFS: md0: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on md0 Not being able my array stresses me... I'll try again with both AHCI and MD as modules this time. Thanks! Charles > > 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/<http://www.jukie.net/%7Ebart/sig/> > -- Charles Nadeau Ph.D. http://charlesnadeau.blogspot.com/ http://radio.weblogs.com/0111823/ -- Charles Nadeau Ph.D. http://charlesnadeau.blogspot.com/ http://radio.weblogs.com/0111823/