When I upgraded Debian from 5.0 to 6.0 my custom kernel doesn't want to boot I get this error: "Kernel panic - not syncing: VFS: Unable to mount root fs on unkown-block(0,0)"
Only kernel that it boots is the one supplied with debian so I went ahead to compile again custom kernel.
My device where system drive is connected to:
00:1f.2 IDE interface: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 4 port SATA IDE Controller (rev 02)
partition type: /dev/sda1 on / type ext3 (rw,errors=remount-ro)
So when I try to boot new kernel I get this error: "Kernel panic - not syncing: VFS: Unable to mount root fs on unkown-block(0,0)" even though I have compiled drivers into kernel and I have compiled EXT2, 3 and 4 support.
Next I tried to make initrd but mkinitrd doesn't supprt new kernels in my case 2.6.35.13 I get this error msg: "/usr/sbin/mkinitrd: Cannot determine SCSI module"
Can you please recommend me tool with which I can make initrd boot image or why I'm getting this message when partition is compiled into kernel and as you can see in the picture kernel sees all the drives.
My grub line looks like this:
title Debian GNU/Linux, kernel 2.6.35.13
root (hd0,0)
kernel /boot/vmlinuz-2.6.35.13 root=UUID=88823d52-a192-44b6-8459-18207f2303f5 ro
#initrd /boot/initrd.2.6.35.13
Initrd is hashed because I cannot make initrd image.
Partition which are compiled into kernel:
Quote:
#
# File systems
#
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
# CONFIG_EXT2_FS_XIP is not set
CONFIG_EXT3_FS=y
CONFIG_EXT3_DEFAULTS_TO_ORDERED=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
CONFIG_EXT4_FS=y
CONFIG_EXT4_FS_XATTR=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
|
http://i268.photobucket.com/albums/j.../linux-VFS.jpg