http://bugzilla.opensuse.org/show_bug.cgi?id=929594 Bug ID: 929594 Summary: Boot failure after applying online updates Classification: openSUSE Product: openSUSE Distribution Version: 13.2 Hardware: x86-64 OS: openSUSE 13.2 Status: NEW Severity: Critical Priority: P5 - None Component: Bootloader Assignee: jsrain@suse.com Reporter: darren@freemaninstruments.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- I know this could be hard to track down, but you should at least be aware of it, as unbootable systems are pretty hard for most users to recover. And it's also a security issue as you're posting security updates that may not be effective in a number of cases. I applied a large number of online updates in a batch. One of the updates was to a newer kernel, 3.16.7-21. When it got to that part of the installation process, it failed because /boot was full. (It is 128M. Everything else is on LVM2 via LUKS.) So I manually deleted the oldest kernel, 3.16.6-2, and its initrd from /boot, then hit retry, then all was good. On the next reboot, the only GRUB2 menu item for Linux was pointing to the kernel that I had deleted :/ Fortunately I was able to edit the command line within GRUB2 and simply use "vmlinuz" and "initrd", with no version info. The symlink had updated correctly, but evidently I had been booting the older kernel for a while, as I already had a newer one installed, 3.16.7-7, but was not using it at the time that I applied this recent update. So it appears to be a bootloader configuration issue. The new kernel booted fine, the symlinks were updated fine, but GRUB2 is directly referencing a particular kernel version that no longer exists. It never got updated with either of the online updates that were applied since 3.16.6-2. I'm not sure if the full /boot has anything to do with it. I suspect that is irrelevant. It's just the reason that I discovered I was using an older kernel than the most recent one installed. This probably also explains all the problems I was having with VirtualBox not having a kernel module available. I was not running the kernel that matched the kernel package that was installed. -- You are receiving this mail because: You are on the CC list for the bug.