[Bug 655145] New: Unable to boot after online update
https://bugzilla.novell.com/show_bug.cgi?id=655145 https://bugzilla.novell.com/show_bug.cgi?id=655145#c0 Summary: Unable to boot after online update Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: Other OS/Version: SLES 10 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: kwbulk@gmail.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.11) Gecko/20101012 (CK-IBM) Firefox/3.6.11 ( .NET CLR 3.5.30729) (Note: the correct product is SLES 10, but at the time of submission, when I selected that product, I got the error "The selected Classification does not contain any products available for bug entry. Please select a different one.") Recently, I attempted an online update from Yast. After rebooting as it suggested, I can no longer boot my system. It appears that the modules necessary to activate my software RAID 5 configuration have been lost. Any suggestions on how to repair this? .. Calling quiesce... returning from prom_init doing fast boot SysRq : Changing Loglevel Loglevel set to 1 FATAL: Module ibmvscsic not found. FATAL: Module raid1 not found. Creating device nodes with udev mount: devpts already mounted or /dev/pts busy mount: according to mtab, devpts is already mounted on /dev/pts Boot logging started on /dev/hvc0(/dev/console) at Sat Nov 20 12:25:20 2010 FATAL: Module raid0 not found. FATAL: Module raid1 not found. FATAL: Module raid10 not found. FATAL: Module raid456 not found. Waiting for device /dev/md1 to appear: ..............................Could not find /dev/md1. Want me to fall back to /dev/md1? (Y/n) Reproducible: Always Steps to Reproduce: 1. Install SLES using software RAID 5 setup 2. Perform upgrade from YAST 3. Reboot Actual Results: SLES no longer boots Expected Results: Boot -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=655145 https://bugzilla.novell.com/show_bug.cgi?id=655145#c wei wang <wewang@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wewang@novell.com AssignedTo|bnc-team-screening@forge.pr |jsuchome@novell.com |ovo.novell.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=655145 https://bugzilla.novell.com/show_bug.cgi?id=655145#c3 --- Comment #3 from Kevin Wendzel <kwbulk@gmail.com> 2010-11-23 16:55:14 UTC --- Some additional information I've gained from personal debug: First off, there is an error in my original post. It's a software RAID 1 configuration, not RAID 5. I tried booting from the old kernel, and was able to get up to a login prompt, but since it appears the update deleted my old modules directory in /etc/modules, several key features (such as networking) no longer work. Here is some additional output from some debug I attempted, if it helps: Rescue:/boot> find / -name ibmvscsic* /lib/modules/2.6.32.24-0.2-ppc64/kernel/drivers/scsi/ibmvscsi/ibmvscsic.ko Rescue:/boot> find / -name raid1* /lib/modules/2.6.32.24-0.2-ppc64/kernel/drivers/md/raid10.ko /lib/modules/2.6.32.24-0.2-ppc64/kernel/drivers/md/raid1.ko Rescue:/boot> cat /etc/sysconfig/kernel #COMMENTS REMOVED! INITRD_MODULES="ibmvscsic raid1" NO_KMS_IN_INITRD="no" DOMU_INITRD_MODULES="xennet xenblk" MODULES_LOADED_ON_BOOT="" SKIP_RUNNING_KERNEL="" Rescue:/boot> ls -l total 58380 -rwxr-xr-x 1 root root 6941862 Nov 19 22:11 initrd.001 -rwxr-xr-x 1 root root 7153551 Nov 19 22:11 initrd.002 -rwxr-xr-x 1 root root 7153551 Nov 19 22:11 initrd.003 drwxr-xr-x 3 root root 4096 Nov 19 22:11 ppc -rwxr-xr-x 1 root root 19056806 Nov 19 22:11 vmlinux.001 -rwxr-xr-x 1 root root 19053606 Nov 19 22:11 vmlinux.002 -rwxr-xr-x 1 root root 405028 Nov 19 22:11 yaboot -rwxr-xr-x 1 root root 640 Nov 19 22:11 yaboot.cnf Rescue:/boot> diff initrd.002 initrd.003 Rescue:/boot> mkinitrd -k vmlinux.002 -i initrd.002 Kernel image: /boot/vmlinux.002 Initrd image: /boot/initrd.002 Kernel Modules: <not available> Could not find map /boot/System.map, please specify a correct file with -M. There was an error generating the initrd (9) Rescue:/boot> find / -name System.map Rescue:/boot> cat yaboot.cnf # header section partition = 1 timeout = 80 default = SLES11_SP1V1 root = /dev/md1 initrd = initrd.003 # remove initrd-size= line if yaboot.conf is not updated by lilo initrd-size = 7153551 # image section image = vmlinux.001 label = SLES11_SP1V1 root = /dev/md1 append = "quiet sysrq=1 crashkernel=512M-:256M" initrd = initrd.001 # remove initrd-size= line if yaboot.conf is not updated by lilo initrd-size = 6941862 image = vmlinux.002 label = SLES11_SP1 root = /dev/md1 append = "quiet sysrq=1 crashkernel=512M-:256M" initrd = initrd.002 # remove initrd-size= line if yaboot.conf is not updated by lilo initrd-size = 7153551 Rescue:/boot> cat /etc/sysconfig/kernel #COMMENTS REMOVED! INITRD_MODULES="ibmvscsic raid1" NO_KMS_IN_INITRD="no" DOMU_INITRD_MODULES="xennet xenblk" MODULES_LOADED_ON_BOOT="" SKIP_RUNNING_KERNEL="" -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=655145 https://bugzilla.novell.com/show_bug.cgi?id=655145#c4 --- Comment #4 from Kevin Wendzel <kwbulk@gmail.com> 2010-11-23 19:13:37 UTC --- I'm getting closer in my own debug. I did manage to get the system up by copying the new directory in /etc/modules to the old directory of the same name, and so can now access it remotely. When I first installed the system, I created a boot partition on /dev/sda1 and /dev/sdb1 as a RAID configuration. However, now I see the following on the system: sysmanagerdev:/mnt # ls -l /mnt/sda1 total 58380 -rwxr-xr-x 1 root root 6941862 Nov 19 22:11 initrd.001 -rwxr-xr-x 1 root root 7153551 Nov 19 22:11 initrd.002 -rwxr-xr-x 1 root root 7153551 Nov 19 22:11 initrd.003 drwxr-xr-x 3 root root 4096 Nov 19 22:11 ppc -rwxr-xr-x 1 root root 19056806 Nov 19 22:11 vmlinux.001 -rwxr-xr-x 1 root root 19053606 Nov 19 22:11 vmlinux.002 -rwxr-xr-x 1 root root 405028 Nov 19 22:11 yaboot -rwxr-xr-x 1 root root 640 Nov 19 22:11 yaboot.cnf sysmanagerdev:/mnt # ls -l /mnt/sdb1 total 58380 -rwxr-xr-x 1 root root 6941862 Nov 19 22:11 initrd.001 -rwxr-xr-x 1 root root 7153551 Nov 19 22:11 initrd.002 -rwxr-xr-x 1 root root 7153551 Nov 19 22:11 initrd.003 drwxr-xr-x 3 root root 4096 Nov 19 22:11 ppc -rwxr-xr-x 1 root root 19056806 Nov 19 22:11 vmlinux.001 -rwxr-xr-x 1 root root 19053606 Nov 19 22:11 vmlinux.002 -rwxr-xr-x 1 root root 405028 Nov 19 22:11 yaboot -rwxr-xr-x 1 root root 640 Nov 19 22:11 yaboot.cnf sysmanagerdev:/mnt # ls -l /boot total 48436 -rw-r--r-- 1 root root 2437695 Nov 2 11:35 System.map-2.6.32.24-0.2-ppc64 -rw-r--r-- 1 root root 1236 Jun 2 09:32 boot.readme -rw-r--r-- 1 root root 90921 Nov 2 11:52 config-2.6.32.24-0.2-ppc64 lrwxrwxrwx 1 root root 26 Nov 23 10:08 initrd -> initrd-2.6.32.24-0.2-ppc64 -rw------- 1 root root 10311348 Jun 8 21:49 initrd-2.6.32.12-0.7-ppc64-kdump -rw-r--r-- 1 root root 7142692 Nov 23 10:08 initrd-2.6.32.24-0.2-ppc64 -rw------- 1 root root 10303089 Nov 23 08:50 initrd-2.6.32.24-0.2-ppc64-kdump -rw-r--r-- 1 root root 155537 Nov 2 11:55 symvers-2.6.32.24-0.2-ppc64.gz lrwxrwxrwx 1 root root 27 Nov 19 22:12 vmlinux -> vmlinux-2.6.32.24-0.2-ppc64 -rw-r--r-- 1 root root 19056806 Nov 2 12:12 vmlinux-2.6.32.24-0.2-ppc64 It looks like the new kernel was installed directly in the "boot" folder on the root file system instead of in the root of the boot file system which should have been mounted on /boot. How did this happen? Yaboot is still very obviously trying to boot off of sd*1, which is certainly causing the problem. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com