[opensuse] Bug: kernel-default-2.6.22.16-0.1 with RAID using /dev/mapper/
The YOU kernel failed to install on my box using software raid. Apparently the new kernel install does not handle /dev/mapper correctly. Be very careful with this update. When it failed it had already re-linked vmlinuz and initrd and rendered the system unbootable before this error was encountered. So anyone doing remote site updates be VERY VERY wary of this Kernel. If it was me, I'd disable any automatic YOU updates you have scheduled until this and the wireless problem are addressed. This is the first failed kernel update I have seen since 8.0? * Installing: kernel-default-2.6.22.16-0.1 [100%]Installation of [S15:1][package]kernel-default-2.6.22.16-0.1.i586 failed: (with --nodeps --force) Error: Subprocess failed. Error: RPM failed: Setting up /lib/modules/2.6.22.16-0.1-default Kernel image: /boot/vmlinuz-2.6.22.16-0.1-default Initrd image: /boot/initrd-2.6.22.16-0.1-default Root device: /dev/mapper/nvidia_haheegdb_part2 (mounted on / as ext3) Resume device: /dev/sda5 device-mapper: deps ioctl failed: No such device or address Command failed Device does not exist. Command failed Device does not exist. Command failed Device sda5 not found in sysfs Script /lib/mkinitrd/setup/72-block.sh failed! /sbin/mkinitrd failed error: %post(kernel-default-2.6.22.16-0.1.i586) scriptlet failed, exit status 1 (A)bort, (R)etry, (I)gnore? A -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin wrote:
The YOU kernel failed to install on my box using software raid. Apparently the new kernel install does not handle /dev/mapper correctly. Be very careful with this update. When it failed it had already re-linked vmlinuz and initrd and rendered the system unbootable before this error was encountered. So anyone doing remote site updates be VERY VERY wary of this Kernel. If it was me, I'd disable any automatic YOU updates you have scheduled until this and the wireless problem are addressed. This is the first failed kernel update I have seen since 8.0?
Lucky guy, when I updated my old server to 10.3 it didn't boot anymore, same with the next two kernel updates, until finally an update for mkinitrd resolved the mess. This also seems like a problem with mkinitrd, not the kernel itself. Also, an update for mkinitrd came out in the last days... -- Sandy List replies only please! Please address PMs to: news-reply2 (@) japantest (.) homelinux (.) com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 31 January 2008, David C. Rankin wrote:
The YOU kernel failed to install on my box using software raid. Apparently the new kernel install does not handle /dev/mapper correctly.
This bug (or close variants) have been in bugzilla since 5/2007: Bug 272989 - Incorrectly generated menu.lst Bug 346638 - yast generates faulty grub menu.lst after kernel update Bug 348257 - System configuration generates incorrect menu.lst file I have the 272989/348257 variant. I see someone has decided to mark 272989 resolved, but it is not. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----Original Message----- From: Mike [mailto:mikedl@comcast.net]
On Thursday 31 January 2008, David C. Rankin wrote:
The YOU kernel failed to install on my box using software raid. Apparently the new kernel install does not handle /dev/mapper correctly.
This bug (or close variants) have been in bugzilla since 5/2007:
Bug 272989 - Incorrectly generated menu.lst Bug 346638 - yast generates faulty grub menu.lst after kernel update Bug 348257 - System configuration generates incorrect menu.lst file
I have the 272989/348257 variant. I see someone has decided to mark 272989 resolved, but it is not.
Not to worry: New Bug filed: https://bugzilla.novell.com/show_bug.cgi?id=357514 Marcus is on it, so the solution is not far away ;-) David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax www.rankinlawfirm.com No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.516 / Virus Database: 269.19.17/1253 - Release Date: 1/31/2008 9:09 AM -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David Rankin wrote:
-----Original Message----- From: Mike [mailto:mikedl@comcast.net]
On Thursday 31 January 2008, David C. Rankin wrote:
The YOU kernel failed to install on my box using software raid. Apparently the new kernel install does not handle /dev/mapper correctly.
Listmates, A patch that solved this issue for me is available at: https://bugzilla.novell.com/show_bug.cgi?id=357514 Issue: mkinitrd crashes on kernel update The problem is the resume device option. Mkinitrd reads that from the kernel command line, where something like "resume=/dev/sda5" appears to be written on. (see kernel cli parameter reference below) The patch to makes the resume device non-fatal. The file patched is /lib/mkinitrd/scripts/setup-storage.sh and the patch is: diff --git a/scripts/setup-storage.sh b/scripts/setup-storage.sh index 924723d..11add69 100644 --- a/scripts/setup-storage.sh +++ b/scripts/setup-storage.sh @@ -194,7 +194,10 @@ resolve_device() { local x="$2" local realrootdev="$2" - [ "$2" ] || exit 0 + # root device was already checked and non-existing + # non-root device is not fatal, but may not be + # shown to the following block resolver modules + [ -b "$realrootdev" ] || exit 0 case "$realrootdev" in LABEL=*|UUID=*) The problem relates to: resume Specify the partition device for the suspend image. resume=suspend_device "Tell the kernel which disk device contains the suspended kernel image. If the data on the image is a valid kernel image created by the software suspend subsystem, it will be loaded into memory and the kernel will run it instead of continuing on with the normal boot process. suspend_device is the kernel device name, which might be different from what userspace thinks the device name is, so be careful with this option." **Chapter 9: Kernel Boot Command-Line Parameter Reference 12437 Page 94-95 Friday, December 1, 2006 10:05 AM Hopefully this will help anyone else bitten by this bug. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
David C. Rankin -
David Rankin
-
Mike -
Sandy Drobic