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

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

  • Subject: Re: [OCLUG-Tech] Problem with a raid array at boot time
  • From: Bart Trojanowski <bart [ at ] jukie [ dot ] net>
  • Date: Fri, 20 Mar 2009 18:50:11 -0400
* Charles Nadeau <charles [ dot ] nadeau [ at ] gmail [ dot ] com> [090320 18:33]:
> I set both to "y", make -j5 && make -j5 modules_install (as per
> http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=1&chap=7#doc_chap3as
> I my distro is Gentoo) 

I gave you instructions :)

> >        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

If you only ran make modules_install then you only installed modules.
Did you also copy the vmlinuz file appropriately to /boot ?

> when I boot, I get this error message:
> "Kernel panic - not syncing: UFS: Unable to mount root fs on unknown-block(8,2)"

8,2 is /dev/sda2

UFS is a really really old file system... so that deson't make sense.

IIRC, sda was on your sata_nv driver, and you were mounting it as

Hmm... what probably happened is that 'ahci' is getting probed first and
it's giving you sda.  So your drive order has now been rotated by 4.

I don't know if you can force certain driver to be initialized first.
If there is a way, you can make sata_nv.

Otherwise, you can unplug and fix the order... or...  make ahci and md
as modules and keep sata_nv in the kernel.

> I'll now try this. Does it means I should remove my array from my
> /etc/fstab?

No, detecting and mounting are separate.  First the kernel has to know
about it before array before you can mount.  That's done either with the
kernel md automount feature or via mdadm tools ran at init time and

You may need the mdadm.conf properly configured if you disable kernel


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