Bug#601823: marked as done (Root on LVM on Raid1 won't boot custom kernel, stock kernel works fine)
Your message dated Sat, 30 Oct 2010 16:19:15 +0000
with message-id <20101030161915.GA15146@vostochny.stro.at>
and subject line Re: Bug#601823: Root on LVM on Raid1 won't boot custom kernel, stock kernel works fine
has caused the Debian Bug report #601823,
regarding Root on LVM on Raid1 won't boot custom kernel, stock kernel works fine
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
601823: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=601823
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.98.5
Severity: wishlist
Hi there,
this is most likely not a bug, but rather an error on my part, but I
thought you might be interested in this. I installed a Squeeze system on
an LVM sitting on a Linux softraid 1 array. I have a seperate boot
partition that I finally put on a raid as well, but also tested the
following when the boot partition was still on a "normal" partition on
the first disk.
The stock kernel boots fine, but I wanted to build my own kernel. I
build it using make-kpkg --uc --us --bzimage --initrd kernel_image. All
necessary kernel options are set correctly (checked that four times) for
both initramfs, dm and raid. But still the kernel doesn't boot into
root. It drops right into busybox when it tries to access root. It even
says it mounts the "other" raid (the one that boot is now sitting on).
Don't know if this is the right place, but in the past I have build a
lot of kernels and installed lots of systems on softraid. Now on Squeeze
it won't work in combination (softraid and my own kernel).
Maybe you will be able to reproduce this one easily. I use AMD64
architecture btw.
I confirmed that initramfs is working, because it is loading a bunch of
modules for the network and block devices.
Error message is:
mdadm: No devices listed in conf file were found.
Failure: failed to assemble all arrays
And it does load the raid1 modules right above that error message.
append="rootdelay=10" also didn't help.
Thx,
Malte
--- End Message ---
--- Begin Message ---
On Sat, Oct 30, 2010 at 02:55:05AM +0200, bugreport@2c2.de wrote:
> Package: initramfs-tools
> Version: 0.98.5
> Severity: wishlist
>
> Hi there,
>
> this is most likely not a bug, but rather an error on my part, but I
> thought you might be interested in this.
Please ask on relevant user or dev mailinglist for help.
As not reproducible by official image this is not a bug,
also hard to tell without the custum .config.
Please try to work from the working one and minimise changes with it.
> I installed a Squeeze system on
> an LVM sitting on a Linux softraid 1 array. I have a seperate boot
> partition that I finally put on a raid as well, but also tested the
> following when the boot partition was still on a "normal" partition on
> the first disk.
> The stock kernel boots fine, but I wanted to build my own kernel. I
> build it using make-kpkg --uc --us --bzimage --initrd kernel_image. All
> necessary kernel options are set correctly (checked that four times) for
> both initramfs, dm and raid. But still the kernel doesn't boot into
> root. It drops right into busybox when it tries to access root. It even
> says it mounts the "other" raid (the one that boot is now sitting on).
>
> Don't know if this is the right place, but in the past I have build a
> lot of kernels and installed lots of systems on softraid. Now on Squeeze
> it won't work in combination (softraid and my own kernel).
>
> Maybe you will be able to reproduce this one easily. I use AMD64
> architecture btw.
>
> I confirmed that initramfs is working, because it is loading a bunch of
> modules for the network and block devices.
>
> Error message is:
> mdadm: No devices listed in conf file were found.
> Failure: failed to assemble all arrays
>
> And it does load the raid1 modules right above that error message.
>
> append="rootdelay=10" also didn't help.
>
> Thx,
>
> Malte
happy hacking + good weekend
--
maks
--- End Message ---
Reply to: