kernel ovzkernel-2.6.18_028stab023.1+31 for debian sarge doesn't boot [message #11885] |
Tue, 10 April 2007 21:41  |
thanh
Messages: 4 Registered: March 2007
|
Junior Member |
|
|
Hi,
I installed ovzkernel-2.6.18 for debian sarge from
http://debian.systs.org/ on a machine running inside vmware. During installation (apt-get ovzkernel-2.6.18) I got some warning:
add_modules_dep_2_5: modprobe failed
FATAL: Module sd_mod not found.
WARNING: This failure MAY indicate that your kernel will not boot!
but it can also be triggered by needed modules being compiled into
the kernel.
and indeed it doesn't boot. I did some searching and found that someone had a similar problem, and solved that problem by recreating initrd using something like
mkinitrd -o /boot/initrd.img-2.6.18-028stab023.1+31-openvz 2.6.18-028stab023.1+31-openvz
so I tried the same but also got the same warning and the kernel doesn't boot either. The vmware machine has a SCSI disk with the module
mptscsih (Fusion), so I tried to add that module to /etc/mkinitrd/modules and rerun mkinitrd, but also without success.
Any hints what else I should try please?
|
|
|
|
Re: kernel ovzkernel-2.6.18_028stab023.1+31 for debian sarge doesn't boot [message #11895 is a reply to message #11887] |
Wed, 11 April 2007 07:20  |
thanh
Messages: 4 Registered: March 2007
|
Junior Member |
|
|
curx wrote on Tue, 10 April 2007 18:07 |
Have you add the module mptbase, mptscsih, depends on mptbase !
|
Hi,
thanks for the hint. I followed that but the result is the same. btw, I forgot to tell more about the kernel panic symptom:
umount: devfs: not mounted
mount:unknown filesystem 'devfs'
umount: devfs: not mounted
pivot_root: No such file or directory
/sbin/init: 424: cannot open dev/console: No such file
Kernel panic: Attempted to kill init!
I was running the 2.6.9 ovz kernel (also from your site) without problem, however it seems that the current recommended version is 2.6.18 so I would like to switch to the new kernel.
I also read somewhere on the web that the initrd-tools in debian may not work for kernels newer than 2.6.12 -- could it be the reason?
Thanks for your time,
Thanh
|
|
|