Recently I've spent a few days in fight with the following new kernel panics:
insmod: error inserting '/lib/dm-region-hash.ko': -1 File exists
mount: could not find filesystem '/dev/root'
After some googling I didn't find any useful fixes, so I started to dig deeper and figured that default built initrd image does't include LVM utility. Here
(
Read more... )
Comments 40
Reply
Reply
Reply
Reply
First error fixed.
But...
My message is ....
(echo Scanning logical volumes
lvm vgscan --ignorelockingfailure
echo Activating logical volumes
lvm vgchange -ay --ignorelockingfailure contents) <-- append line
resume LABEL=SWAP-sda5
echo Creating root device.
mkrootdev -t ext3 -o defaults,ro sda1
I don't know
Do you know what is mean?
If you know it, I wait for your reply.
Please!
Reply
# cat /boot/grub/grub.conf
and the output
# vgscan -vv
Reply
#
# Note that you do not have to retun grub after making change ~~
# NOTICE: You do not have a /boot partition. This means that
# all kernel and initrd paths are relative to /, eg.
# root (hd0,0)
# kernel /boot/vmlinuz-version ro root=/dev/sda1
# initrd /boot/initrd-version.img
#boot=/dev/sda
default=1
timeout=5
splashimage=(hd0,0) /boot/grub/splash.xpm.gz
hddenmenu
title CentOS(2.6.33)
root (hd0,0)
kernel /boot/vmlinuz-2.6.33 ro root=LABEL=/ rhgb quiet
initrd /boot/initrd-2.6.33.img
title CentOS(2.6.18-164.EL5)
root (hd0, 0)
kernel /boot/vmlinuz-2.6.18-164.el5 ro root=LABEL=/ rhgb quiet
initrd /boot/initrd-2.6.18-164.el5.img
Reply
-mkrootdev -t ext3 -o defaults,ro sda1
+mkrootdev -t ext3 -o defaults,ro /dev/sda1
in init script
Reply
I am using LVM, but am not sure if this is the problem after following your guide I still get
"Could not find filesystem /dev/root".
I have no clue how to proceed and I need to install a kernel > 2.6.21 ( I am trying 2.6.33 ) onto CentOS 5.4 for support for hardware sensors.
I understand this is not the topic of this post but I would appreciate any advice you could provide in trouble shooting this.
Reply
UPD: you might need to set CONFIG_SYS_DEPRECATED_V2=y in kernel config
This has indeed fixed my problem.
Thanks funky_dennis.
Reply
Reply
Running into this problem and I have:
# grep 'CONFIG_SYSFS_DEPRECATED_V2' /usr/src/linux-2.6.33.2/.config
CONFIG_SYSFS_DEPRECATED_V2=y
But it still gives me that error. Is it supposed to be CONFIG_SYSFS_DEPRECATED_V2 or CONFIG_SYS_DEPRECATED_V2?
Reply
Thanks your detail message. Recently, I upgrade my kernel to the newest version and met the same issue. When my os was on booting, I saw the same error. But now, I already fix it and refer your documents.
By Anderson.Chen in Taiwan
Reply
Reply
Leave a comment