Bug#286276: kernel-image-2.6.8-9-amd64-k8: Unable to mount md devices

[Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>]

Marc Singer <elf@buici.com> writes:

> On Sun, Dec 19, 2004 at 03:00:13PM +0100, Frederik Schueler wrote:
>> Hello,
>> 
>> On Sat, Dec 18, 2004 at 04:35:37PM -0800, Marc Singer wrote:
>> > I'm testing this kernel on a machine that resently boots to 2.6.7 with
>> > no initrd and, therefore, all drivers for boot are compiled into the
>> > kernel.
>> >  There are four drives in the array, all with type 0xfd.  The
>> > 2.6.7 kernel finds them automatically.  The 2.6.8 package does not,
>> > but that isn't the issue as this device isn't needed at boot-time.
>>  
>> Did you add the needed md and raid modules to your initrd?
>
> Since I don't care about it a boot-up, no.  The root partition as well
> as /usr and /sbin is on an IDE drive.

Having raid buildin enables the autodetection. Raid as modules needs
to get started manually.

>> > Once the kernel boots, I load the raid5 module and look at
>> > /proc/mdstat.  It looks OK.  mdadm --assemble /dev/md0, however,
>> > crashes.  I haven't saved error messages, though I could write then to
>> > a file if need be.
>> 
>> you need to put the modules into /etc/mkinitrd/modules, and recreate you
>> initrd with 
>> 
>> mkinitrd -o /boot/initrd.img-2.6.8-9-amd64-k8 2.6.8-9-amd64-k8
>> 
>> and rerun lilo, if you use it.
>> 
>> This should fix the problem.
>
> This isn't a boot-up problem.  The MD driver was crashing when I
> loaded the modules by hand after the system booted.
>
> Of course, I'll try it anyway just to see if it makes a difference.
> Thanks for responding.

If you can't get the modules to work or track down the bug compile a
kernel with buildin raid support. I'm using a standard 2.6.8 compiled
with gcc 3.3.4 (1:3.3.4-11) and raid buildin without problems.

MfG
        Goswin