Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Stock kernel not working with raid / lvm setup

149 views
Skip to first unread message

MRH

unread,
Jul 9, 2013, 7:00:02 PM7/9/13
to
For years I've been using self-build kernels (from kernel.org) for this
or that reason. Recently I decided to use debian stock kernel instead.
Should be so much easier and faster. Well, it did not work.

I have installed
linux-headers-3.9-1-amd64
linux-image-3.9-1-amd64
(I run amd64, debian wheezy/sid)

but on reboot it could not load raid modules - seems they are neither
compiled in nor installable as modules. I'm getting the following messages:

------------
modprobe: module dm-raid45 not found in modules.dep
...
modadm: No devices listed in conf file were found
...
Volume group "blahblah" not found
...
Gave up waiting for root device
------------

The kernel I build works fine. Does it mean I cannot use Debian stock
kernel and have to keep building my own?


--
Kind regards,
Michal R. Hoffmann


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/51DC9394...@o2.pl

MRH

unread,
Jul 10, 2013, 6:20:02 PM7/10/13
to
On 10/07/13 01:11, Dick William Thomas wrote:
> On 09/07/13 23:49, MRH wrote:
>> For years I've been using self-build kernels (from kernel.org) for this
>> or that reason. Recently I decided to use debian stock kernel instead.
>> Should be so much easier and faster. Well, it did not work.
>>
>> I have installed
>> linux-headers-3.9-1-amd64
>> linux-image-3.9-1-amd64
>> (I run amd64, debian wheezy/sid)
>>
>> but on reboot it could not load raid modules - seems they are neither
>> compiled in nor installable as modules. I'm getting the following messages:
>>
>> ------------
>> modprobe: module dm-raid45 not found in modules.dep
>> ...
>> modadm: No devices listed in conf file were found
>> ...
>> Volume group "blahblah" not found
>> ...
>> Gave up waiting for root device
>> ------------
>>
>> The kernel I build works fine. Does it mean I cannot use Debian stock
>> kernel and have to keep building my own?
>>
>>
> have you tried adding
>
> rootdelay=5 to the grub boot command line?
>

This has helped, thank you!

I needed to add it to the lines in
/etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="rootdelay=5 quiet"
GRUB_CMDLINE_LINUX="rootdelay=5"

then run (as root):
update-grub


--
Kind regards,
Michal R. Hoffmann


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/51DDDC1B...@o2.pl
0 new messages