[Bug 590000] New: Update kernel-default-2.6.25.20-0.7.x86_64 Install Failure
http://bugzilla.novell.com/show_bug.cgi?id=590000 http://bugzilla.novell.com/show_bug.cgi?id=590000#c0 Summary: Update kernel-default-2.6.25.20-0.7.x86_64 Install Failure Classification: openSUSE Product: openSUSE 11.0 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Kernel AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: drankinatty@suddenlinkmail.com QAContact: qa@suse.de Found By: --- Blocker: --- Created an attachment (id=349644) --> (http://bugzilla.novell.com/attachment.cgi?id=349644) All relevant logs from /var/log/YaST2 User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.0) Gecko/20100115 SUSE/3.6.0-1.2 Firefox/3.6 Guys, I experienced one of the first kernel install failures I have ever been faced with on 11.0 tonight and I'm not sure what is going on. This x86_64 box had 11.0 installed from the time it was released to the present and has had every kernel update installed without any problem. So why now? Looking at the error message given, it looks like the installer lost its mind and is trying to issue non-existent modprobe options and it looks like it can't find the partition it is running on -- strange :-( Below, I have included all the relevant diagnostics I can think of. I need help! failure log error: 2010-03-18 00:50:21 kernel-default-2.6.25.20-0.7.x86_64.rpm install failed rpm output: Free diskspace below /boot: 93126 blocks Setting up /lib/modules/2.6.25.20-0.7-default Kernel image: /boot/vmlinuz-2.6.25.20-0.7-default Initrd image: /boot/initrd-2.6.25.20-0.7-default modprobe: unrecognized option '--resolve-alias' Usage: modprobe [-v] [-V] [-C config-file] [-n] [-i] [-q] [-b] [-o <modname>] [ --dump-modversions ] <modname> [parameters...] modprobe -r [-n] [-i] [-v] <modulename> ... modprobe -l -t <dirname> [ -a <modulename> ...] Root device: /dev/mapper/nvidia_fdaacfde_part7 (mounted on / as ext3) Resume device: /dev/mapper/nvidia_fdaacfde_part6 Device mapper!nvidia_fdaacfde_part7 not found in sysfs /sbin/mkinitrd failed error: %post(kernel-default-2.6.25.20-0.7.x86_64) scriptlet failed, exit status 1 The existing grub menu.lst that has worked for over a year: ###Don't change this comment - YaST2 identifier: Original name: linux### title openSUSE 11.0 - 2.6.25.20-0.5 root (hd0,4) kernel /vmlinuz-2.6.25.20-0.5-default root=/dev/mapper/nvidia_fdaacfde_part7 resume=/dev/mapper/nvidia_fdaacfde_part6 splash=silent showopts vga=0x31a initrd /initrd-2.6.25.20-0.5-default What the installer did install in /boot [02:40 ecstasy:~] # l /boot total 20509 drwxr-xr-x 4 root root 3072 2010-03-18 02:30 ./ drwxr-xr-x 21 root root 4096 2010-03-17 23:48 ../ -rw------- 1 root root 512 2009-04-14 19:22 backup_mbr lrwxrwxrwx 1 root root 1 2008-10-17 22:02 boot -> ./ -rw-r--r-- 1 root root 83043 2009-08-14 07:39 config-2.6.25.20-0.5-default -rw-r--r-- 1 root root 83043 2010-03-01 10:36 config-2.6.25.20-0.7-default -rw------- 1 root root 49 2010-03-18 01:46 .directory drwxr-xr-x 2 root root 1024 2010-03-18 01:46 grub/ lrwxrwxrwx 1 root root 28 2010-03-18 02:12 initrd -> initrd-2.6.25.20-0.7-default -rw-r--r-- 1 root root 6114957 2009-08-20 17:34 initrd-2.6.25.20-0.5-default drwx------ 2 root root 12288 2008-10-17 21:59 lost+found/ -rw-r--r-- 1 root root 115828 2010-03-18 02:30 memtest.bin -rw-r--r-- 1 root root 593408 2010-01-20 18:52 message -rw-r--r-- 1 root root 240694 2009-08-14 07:40 symsets-2.6.25.20-0.5-default.tar.gz -rw-r--r-- 1 root root 240887 2010-03-01 10:56 symsets-2.6.25.20-0.7-debug.tar.gz -rw-r--r-- 1 root root 283169 2010-03-01 10:36 symsets-2.6.25.20-0.7-default.tar.gz -rw-r--r-- 1 root root 108555 2010-03-01 10:44 symsets-2.6.25.20-0.7-lockdep.tar.gz -rw-r--r-- 1 root root 277661 2010-03-01 10:45 symsets-2.6.25.20-0.7-xen.tar.gz -rw-r--r-- 1 root root 441111 2009-08-14 07:40 symtypes-2.6.25.20-0.5-default.gz -rw-r--r-- 1 root root 441121 2010-03-01 10:36 symtypes-2.6.25.20-0.7-default.gz -rw-r--r-- 1 root root 126896 2009-08-14 07:40 symvers-2.6.25.20-0.5-default.gz -rw-r--r-- 1 root root 126915 2010-03-01 10:36 symvers-2.6.25.20-0.7-default.gz -rw-r--r-- 1 root root 1176821 2009-08-14 07:34 System.map-2.6.25.20-0.5-default -rw-r--r-- 1 root root 1177117 2010-03-01 10:32 System.map-2.6.25.20-0.7-default -rw-r--r-- 1 root root 2505238 2009-08-14 07:39 vmlinux-2.6.25.20-0.5-default.gz -rw-r--r-- 1 root root 2505320 2010-03-01 10:36 vmlinux-2.6.25.20-0.7-default.gz lrwxrwxrwx 1 root root 29 2010-03-18 02:12 vmlinuz -> vmlinuz-2.6.25.20-0.7-default -rw-r--r-- 1 root root 2109784 2009-08-14 07:34 vmlinuz-2.6.25.20-0.5-default -rw-r--r-- 1 root root 2109912 2010-03-01 10:33 vmlinuz-2.6.25.20-0.7-default Yes, dev/mapper/nvidia_fdaacfde_part7 is really there: [02:40 ecstasy:~] # mount /dev/mapper/nvidia_fdaacfde_part7 on / type ext3 (rw,acl,user_xattr) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) debugfs on /sys/kernel/debug type debugfs (rw) udev on /dev type tmpfs (rw) devpts on /dev/pts type devpts (rw,mode=0620,gid=5) /dev/mapper/nvidia_fdaacfde_part5 on /boot type ext3 (rw,acl,user_xattr) /dev/mapper/nvidia_fdaacfde_part8 on /home type ext3 (rw,acl,user_xattr) fusectl on /sys/fs/fuse/connections type fusectl (rw) securityfs on /sys/kernel/security type securityfs (rw) proc on /var/lib/ntp/proc type proc (ro) /dev/mapper/nvidia_baaccaja_part5 on /mnt/arch type ext3 (rw) /dev/mapper/nvidia_baaccaja_part6 on /mnt/arch/boot type ext3 (rw) /dev/mapper/nvidia_baaccaja_part7 on /mnt/arch/home type ext3 (rw) /dev/mapper/nvidia_baaccaja_part9 on /mnt/arch/var type ext3 (rw) /dev/mapper/nvidia_baaccaja_part10 on /mnt/arch/srv type ext3 (rw) Does it have enough space: yep! 02:38 ecstasy:~> df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/nvidia_fdaacfde_part7 20G 17G 2.4G 88% / udev 4.0G 288K 4.0G 1% /dev /dev/mapper/nvidia_fdaacfde_part5 69M 26M 40M 40% /boot /dev/mapper/nvidia_fdaacfde_part8 437G 318G 97G 77% /home /dev/mapper/nvidia_baaccaja_part5 19G 8.1G 9.4G 47% /mnt/arch /dev/mapper/nvidia_baaccaja_part6 114M 29M 80M 27% /mnt/arch/boot /dev/mapper/nvidia_baaccaja_part7 37G 24G 12G 69% /mnt/arch/home /dev/mapper/nvidia_baaccaja_part9 15G 5.8G 8.0G 43% /mnt/arch/var /dev/mapper/nvidia_baaccaja_part10 29G 6.3G 22G 23% /mnt/arch/srv Is the raid setup OK -- yep again. [02:25 ecstasy:~] # dmraid -r /dev/sdd: nvidia, "nvidia_baaccaja", mirror, ok, 1465149166 sectors, data@ 0 /dev/sdc: nvidia, "nvidia_fdaacfde", mirror, ok, 976773166 sectors, data@ 0 /dev/sdb: nvidia, "nvidia_baaccaja", mirror, ok, 1465149166 sectors, data@ 0 /dev/sda: nvidia, "nvidia_fdaacfde", mirror, ok, 976773166 sectors, data@ 0 [02:39 ecstasy:~] # dmraid -s *** Active Set name : nvidia_baaccaja size : 1465149056 stride : 128 type : mirror status : ok subsets: 0 devs : 2 spares : 0 *** Active Set name : nvidia_fdaacfde size : 976773120 stride : 128 type : mirror status : ok subsets: 0 devs : 2 spares : 0 [02:39 ecstasy:~] # cat /proc/partitions major minor #blocks name 8 0 488386584 sda 8 1 1 sda1 8 5 72229 sda5 8 6 2104483 sda6 8 7 20972826 sda7 8 8 465234336 sda8 8 16 732574584 sdb 8 17 1 sdb1 8 21 19534977 sdb5 8 22 120456 sdb6 8 23 39062016 sdb7 8 24 1951866 sdb8 8 25 15358108 sdb9 8 26 30716248 sdb10 8 27 7510356 sdb11 8 28 618317721 sdb12 8 32 488386584 sdc 8 33 1 sdc1 8 37 72229 sdc5 8 38 2104483 sdc6 8 39 20972826 sdc7 8 40 465234336 sdc8 8 48 732574584 sdd 8 49 1 sdd1 8 53 19534977 sdd5 8 54 120456 sdd6 8 55 39062016 sdd7 8 56 1951866 sdd8 8 57 15358108 sdd9 8 58 30716248 sdd10 8 59 7510356 sdd11 8 60 618317721 sdd12 253 0 732574583 dm-0 253 1 488386583 dm-1 253 2 488384001 dm-2 253 3 72229 dm-3 253 4 2104483 dm-4 253 5 20972826 dm-5 253 6 732572001 dm-6 253 7 465234336 dm-7 253 8 19534977 dm-8 253 9 120456 dm-9 253 10 39062016 dm-10 253 11 1951866 dm-11 253 12 15358108 dm-12 253 13 30716248 dm-13 253 14 7510356 dm-14 253 15 618317721 dm-15 So why the install failure? Installer bug? I'm also attaching YaST/logs. Let me know if I can send anything else. I suspect it is dmraid related. Reproducible: Always Steps to Reproduce: 1. 2. 3. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=590000
http://bugzilla.novell.com/show_bug.cgi?id=590000#c1
--- Comment #1 from David Rankin
http://bugzilla.novell.com/show_bug.cgi?id=590000
http://bugzilla.novell.com/show_bug.cgi?id=590000#c2
--- Comment #2 from David Rankin
http://bugzilla.novell.com/show_bug.cgi?id=590000
http://bugzilla.novell.com/show_bug.cgi?id=590000#c
yang xiaoyu
http://bugzilla.novell.com/show_bug.cgi?id=590000
http://bugzilla.novell.com/show_bug.cgi?id=590000#c3
Michal Marek
Kernel image: /boot/vmlinuz-2.6.25.20-0.7-default Initrd image: /boot/initrd-2.6.25.20-0.7-default modprobe: unrecognized option '--resolve-alias' Usage: modprobe [-v] [-V] [-C config-file] [-n] [-i] [-q] [-b] [-o <modname>] [ --dump-modversions ] <modname> [parameters...]
Did you update mkinitrd from Factory? This might or might not be the cause of your problem, but please check if it also fails with the 11.0 mkinitrd (mkinitrd-2.2-19.2.$arch.rpm). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=590000
http://bugzilla.novell.com/show_bug.cgi?id=590000#c4
David Rankin
http://bugzilla.novell.com/show_bug.cgi?id=590000
http://bugzilla.novell.com/show_bug.cgi?id=590000#c5
--- Comment #5 from Michal Marek
http://bugzilla.novell.com/show_bug.cgi?id=590000
http://bugzilla.novell.com/show_bug.cgi?id=590000#c6
--- Comment #6 from David Rankin
http://bugzilla.novell.com/show_bug.cgi?id=590000
http://bugzilla.novell.com/show_bug.cgi?id=590000#c7
Michal Marek
http://bugzilla.novell.com/show_bug.cgi?id=590000
http://bugzilla.novell.com/show_bug.cgi?id=590000#c8
--- Comment #8 from David Rankin
participants (1)
-
bugzilla_noreply＠novell.com