[gentoo-user] initrd for LVM no longer works

[gentoo-user] initrd for LVM no longer works

[Dietrich Moerman]

Hello,

I am using kernel 2.6.20-gentoo-r6 and an LVM setup with all partitions except /boot in LVM volumes. I use lvm2create_initrd to create the initrd. This worked with the previous kernel (2.6.19), however with the new initrd the system does not boot (kernel panic - init not found).

I am pretty sure the kernel itself is not the cause, since booting 2.6.19 with the new initrd didn't work as well. Also, ramdisk has a size of 10240 KB set up in the kernel, which should be enough since the initrd is only 5 MB when uncompressed. Mounting the initrd shows that init exists in the usual sbin/init place.

Sadly I don't have the old working initrd anymore, I wouldn't know what could be possibly wrong right now.

Any help is appreciated.
Thanks.


--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] initrd for LVM no longer works

[Dietrich Moerman]

In the mean time, I also tried to build a manual initrd containing all the tools and commands in linuxrc I need to activate LVM volumes. But the problem remains, the kernel boots but when initrd is extracted and mounted everything seems to go wrong, and the system again stops giving "Kernel panic - not syncing: No init found".

I have ran out of ideas, I guess this must be the most bizarre Linux related problem I have ever encountered.

Any ideas are still welcome. If the problems remains, I guess I'll have to ditch LVM and go back to regular partitions which don't need an initrd to boot from.


--
gentoo-user@gentoo.org mailing list

Re: [gentoo-user] initrd for LVM no longer works

[Dietrich Moerman]

Dietrich Moerman schreef:
> In the mean time, I also tried to build a manual initrd containing all the tools and commands in linuxrc I need to activate LVM volumes. But the problem remains, the kernel boots but when initrd is extracted and mounted everything seems to go wrong, and the system again stops giving "Kernel panic - not syncing: No init found".
> 
> I have ran out of ideas, I guess this must be the most bizarre Linux related problem I have ever encountered.
> 
> Any ideas are still welcome. If the problems remains, I guess I'll have to ditch LVM and go back to regular partitions which don't need an initrd to boot from.
> 
> 

Okay, the problem is fixed. The guilty part seemed to be /dev/ram0. Both
the initrd I generated using lvm2create_initrd and the manual one didn't
work with /dev/ram0, but the manual one does with /dev/ram1.

Why the previous initrd did work is a big question to me. I suspect I'm
going to have big troubles with the RAM within some time.

-- 
MVG
Dietrich Moerman
http://dmoerman.be
-- 
gentoo-user@gentoo.org mailing list