Booting fail with last two kernels

[pepel]

I have a booting fail with kernel versions: 2.6.27.9-159.fc10.x86_64 and 2.6.27.7-134.fc10.x86_64. I see this message:

Unable to access resume device (/dev/dm-1)
mount: error mounting /dev/root on /sysroot as ext3: No such file or directory

With kernel 2.6.27.5-117.fc10.x86_64, booting passes normally. How to fix this bug?

[glennzo]

Just a thought. Can you post the output of the command

cat /boot/grub/menu.lst

please? You will probably have to run the command as root if you haven't set up sudo.

[pravee1216]

I got the solution and found success. This is a Fedora-SCSI issue which can be solved with the following

1) Boot from rescue mode (use Fedora10 DVD )
2) chroot /mnt/sysimage/
3) /sbin/mkinitrd -f --with=scsi_wait_scan /boot/initrd-2.6.27.5-117.fc10.i686.PAE.img 2.6.27.5-117.fc10.i686.PAE

Note: Please replace "initrd-2.6.27.5-117.fc10.i686.PAE.img" and "2.6.27.5-117.fc10.i686.PAE" with the correct distro image & version you have (applicable in case of any change )

4) exit
5) reboot

That's it. Now Fedora can scan SCSI and boot from /dev/root.

Cheers

Praveen Raj

[pepel]

glennzo, this is my menu.lst file. Originally, after system updating, I had my menu.lst file like this:

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd1,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd1,0)/grub/splash.xpm.gz
hiddenmenu
title Windows Vista
rootnoverify (hd0,0)
chainloader +1
title Fedora (2.6.27.9-159.fc10.x86_64)
root (hd1,0)
kernel /vmlinuz-2.6.27.9-159.fc10.x86_64 ro root=/dev/dm-0 rhgb quiet
initrd /initrd-2.6.27.9-159.fc10.x86_64.img
title Fedora (2.6.27.7-134.fc10.x86_64)
root (hd1,0)
kernel /vmlinuz-2.6.27.7-134.fc10.x86_64 ro root=/dev/dm-0 rhgb quiet
initrd /initrd-2.6.27.7-134.fc10.x86_64.img
title Fedora (2.6.27.5-117.fc10.x86_64)
root (hd1,0)
kernel /vmlinuz-2.6.27.5-117.fc10.x86_64 ro root=UUID=970e56c0-a8fa-4397-8e76-e1000db21ae7 rhgb quiet
initrd /initrd-2.6.27.5-117.fc10.x86_64.img

The system was not loaded, and I try the following two variants. It is had no effect too.

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd1,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd1,0)/grub/splash.xpm.gz
hiddenmenu
title Windows Vista
rootnoverify (hd0,0)
chainloader +1
title Fedora (2.6.27.9-159.fc10.x86_64)
root (hd1,0)
kernel /vmlinuz-2.6.27.9-159.fc10.x86_64 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.27.9-159.fc10.x86_64.img
title Fedora (2.6.27.7-134.fc10.x86_64)
root (hd1,0)
kernel /vmlinuz-2.6.27.7-134.fc10.x86_64 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.27.7-134.fc10.x86_64.img
title Fedora (2.6.27.5-117.fc10.x86_64)
root (hd1,0)
kernel /vmlinuz-2.6.27.5-117.fc10.x86_64 ro root=UUID=970e56c0-a8fa-4397-8e76-e1000db21ae7 rhgb quiet
initrd /initrd-2.6.27.5-117.fc10.x86_64.img

and

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd1,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd1,0)/grub/splash.xpm.gz
hiddenmenu
title Windows Vista
rootnoverify (hd0,0)
chainloader +1
title Fedora (2.6.27.9-159.fc10.x86_64)
root (hd1,0)
kernel /vmlinuz-2.6.27.9-159.fc10.x86_64 ro root=UUID=970e56c0-a8fa-4397-8e76-e1000db21ae7 rhgb quiet
initrd /initrd-2.6.27.9-159.fc10.x86_64.img
title Fedora (2.6.27.7-134.fc10.x86_64)
root (hd1,0)
kernel /vmlinuz-2.6.27.7-134.fc10.x86_64 ro root=UUID=970e56c0-a8fa-4397-8e76-e1000db21ae7 rhgb quiet
initrd /initrd-2.6.27.7-134.fc10.x86_64.img
title Fedora (2.6.27.5-117.fc10.x86_64)
root (hd1,0)
kernel /vmlinuz-2.6.27.5-117.fc10.x86_64 ro root=UUID=970e56c0-a8fa-4397-8e76-e1000db21ae7 rhgb quiet
initrd /initrd-2.6.27.5-117.fc10.x86_64.img

I have two hard disks. First is SATA (boot record, Windows Vista), second is IDE (no boot record, Linux Fedora 10). Boot record (grub) is written down on first SATA disk. May be the problem in it?

[glennzo]

That confuses me. Show me the current menu.lst please. Also, once booted open a terminal and type

blkid

and post that output here.

[pepel]

Current is:

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd1,0)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd1,0)/grub/splash.xpm.gz
hiddenmenu
title Windows Vista
rootnoverify (hd0,0)
chainloader +1
title Fedora (2.6.27.9-159.fc10.x86_64)
root (hd1,0)
kernel /vmlinuz-2.6.27.9-159.fc10.x86_64 ro root=UUID=970e56c0-a8fa-4397-8e76-e1000db21ae7 rhgb quiet
initrd /initrd-2.6.27.9-159.fc10.x86_64.img
title Fedora (2.6.27.7-134.fc10.x86_64)
root (hd1,0)
kernel /vmlinuz-2.6.27.7-134.fc10.x86_64 ro root=UUID=970e56c0-a8fa-4397-8e76-e1000db21ae7 rhgb quiet
initrd /initrd-2.6.27.7-134.fc10.x86_64.img
title Fedora (2.6.27.5-117.fc10.x86_64)
root (hd1,0)
kernel /vmlinuz-2.6.27.5-117.fc10.x86_64 ro root=UUID=970e56c0-a8fa-4397-8e76-e1000db21ae7 rhgb quiet
initrd /initrd-2.6.27.5-117.fc10.x86_64.img

[pepel]

blkid output:

[pepel@localhost Документы]$ blkid
/dev/sda2: UUID="7EAE85AAAE855B91" TYPE="ntfs"
/dev/sda1: UUID="9E3C7F693C7F3AFB" TYPE="ntfs"
/dev/sdb1: LABEL="/boot" UUID="89f5f76b-6ec2-4868-8a3d-0d7e98383044" TYPE="ext3" SEC_TYPE="ext2"
/dev/sdb2: UUID="q9gCyk-2mv5-Ar5t-8A9H-F92l-p4tI-47okOF" TYPE="lvm2pv"
/dev/mapper/VolGroup00-LogVol00: UUID="970e56c0-a8fa-4397-8e76-e1000db21ae7" TYPE="ext3"
/dev/mapper/VolGroup00-LogVol01: TYPE="swap" UUID="beccffec-33b8-4c3d-bb36-cdb68ced1571"
/dev/VolGroup00/LogVol00: UUID="970e56c0-a8fa-4397-8e76-e1000db21ae7" TYPE="ext3"
/dev/VolGroup00/LogVol01: TYPE="swap" UUID="beccffec-33b8-4c3d-bb36-cdb68ced1571"
/dev/dm-0: UUID="970e56c0-a8fa-4397-8e76-e1000db21ae7" TYPE="ext3"
/dev/dm-1: TYPE="swap" UUID="beccffec-33b8-4c3d-bb36-cdb68ced1571"

[glennzo]

Try this for the newest kernel.

title Fedora (2.6.27.9-159.fc10.x86_64)
root (hd1,0)
kernel /vmlinuz-2.6.27.9-159.fc10.x86_64 ro root=UUID=89f5f76b-6ec2-4868-8a3d-0d7e98383044 rhgb quiet
initrd /initrd-2.6.27.9-159.fc10.x86_64.img

[Dillio]

I'm having problems booting the 159 x64 kernel as well. Whenever I boot, it goes through the Fedora loading screen, and then a flashing cursor comes up, and it just sits there. When I boot the 134 kernel, it boots as normal. It doesn't even get to the point where it loads the Nvidia driver (and shows the flash screen). Ideas? I've booted into the 134 kernel to make sure there are no updates remaining using yum, and there are none.

[pepel]

Try this for the newest kernel.

No, it has no effect. I see the same message and system doesn't boot.

[glennzo]

Well, I'm stumped. Essentially, if one kernel boots and the other(s) don't you need to make sure that the other entries are identical to the line for the kernel that works, the only exception being the kernel version numbers.

[pepel]

How I can keep the older kernel after system kernel update? I need work and I can't accept that my system will broken after next system update. May be, in future, this bug will be fixed.

[glennzo]

In the file /etc/yum.conf there is a line that says installonly_limit=3. This is the number of kernels the system will keep. You can change the 3 to 4 or 5 or whatever you like.

[pepel]

glennzo, thanks for your help.

[glennzo]

You're very welcome. Wish I had the answer to your booting issues but I just can't get my head around this one.