On Sat, 9 Aug 2014 15:06:22 +0300 Mark Goldstein wrote: <snipped>
Any advice on how to recover the system / investigate the failure?
Regards
Hi Mark, My system is running 12.3 x86_64 and it has twice experienced a somewhat comparable broken state following the last two kernel updates. I also have additional operating environments installed: Mint 14 and Vista. I presumed this behavior was an artifact of having just migrated the installed systems to an SSD. This could actually still be the case but I'm not certain. My solution has been to boot to rescue mode from my openSUSE *12.2* install DVD Side note: The 12.3 GM DVD requires additional boot parameters due to an ACPI related bug that I simply prefer to avoid. YMMV. Continuing... I mount the affected '/' partition to /mnt , then 'mount --bind /dev /mnt/dev' 'mount --bind /proc /mnt/proc' 'mount --bind /sys /mnt/sys' 'chroot /mnt' 'mkinitrd' I reinstall grub2: 'grub2-install /dev/sda' (select the desired device/partition here) 'grub2-mkconfig -o /boot/grub2/grub.cfg' When this is done, I 'exit', 'umount -a', 'eject /dev/sr0', remove the DVD and 'poweroff' (I want a cold start.) Notes and caveats: This failed the first time because I'd forgotten to adapt Mint's boot configuration to the SSD, which threw off detection and resulted in a broken boot configuration. To remedy this, I first treated Mint as though it were the 'primary' installed environment ... using Mint-specific grub2 installation commands, btw ... and the subsequent pass treating openSUSE 12.3 as 'primary' succeeded. I haven't needed to touch the Mint 14 configuration on the subsequent boot / initrd repairs. Another aspect of this: The same problem has been experienced during the same kernel updates on my daughter's computer. It also has openSUSE 12.3 and Vista installed (no Mint.) Finally, both of these systems have nVidia graphics adapters with the proprietary drivers installed. They, of course, need to be re-installed when the kernel is updated. Here are relevant excerpts of the error messages from the first incident on my system: - - - - - 8< - - - - - (4/6) Installing: nvidia-uvm-gfxG03-kmp-desktop-331.89_k3.7.10_1.1-28.1 ...............................................[done] Additional rpm output: /usr/src/kernel-modules/nvidia-uvm-331.89-desktop/rm / NVIDIA: calling KBUILD... make[1]: Entering directory `/usr/src/linux-3.7.10-1.36' make -C /usr/src/linux-obj/x86_64/desktop \ KBUILD_SRC=/usr/src/linux-3.7.10-1.36 \ KBUILD_EXTMOD="/usr/src/kernel-modules/nvidia-uvm-331.89-desktop/rm" -f /usr/src/linux-3.7.10-1.36/Makefile \ modules test -e include/generated/autoconf.h -a -e include/config/auto.conf || ( \ echo >&2; \ echo >&2 " ERROR: Kernel configuration is invalid."; \ echo >&2 " include/generated/autoconf.h or include/config/auto.conf are missing.";\ echo >&2 " Run 'make oldconfig && make prepare' on kernel src to fix it."; \ echo >&2 ; \ /bin/false) - - - - - 8< - - - - - and - - - - - 8< - - - - - Kernel image: /boot/vmlinuz-3.7.10-1.32-desktop Initrd image: /boot/initrd-3.7.10-1.32-desktop Root device: /dev/sda5 (mounted on / as ext4) Could not expand UUID=456a524c-9adf-4472-8fb0-88bbdbd62b53 to real device Kernel Modules: thermal_sys thermal processor fan scsi_dh scsi_dh_hp_sw scsi_dh_rdac scsi_dh_emc scsi_dh_alua xhci-hcd hid-logitech-dj Features: acpi plymouth block usb resume.userspace resume.kernel Kernel image: /boot/vmlinuz-3.7.10-1.36-desktop Initrd image: /boot/initrd-3.7.10-1.36-desktop Root device: /dev/sda5 (mounted on / as ext4) Could not expand UUID=456a524c-9adf-4472-8fb0-88bbdbd62b53 to real device Kernel Modules: thermal_sys thermal processor fan scsi_dh scsi_dh_hp_sw scsi_dh_rdac scsi_dh_emc scsi_dh_alua xhci-hcd hid-logitech-dj Features: acpi plymouth block usb resume.userspace resume.kernel Perl-Bootloader: 2014-07-22 18:21:43 <3> pbl-4616.2 Core::RunCommand.1642: Error: Command '/usr/sbin/grub2-install --target=i386-pc --force --skip-fs-probe "(hd0,4)" >/var/log/YaST2/y2log_bootloader 2>&1' failed with code 256 and output: /usr/sbin/grub2-bios-setup: error: disk `hd0,4' not found. There was an error generating the initrd (1) - - - - - 8< - - - - - I don't know for a fact that you're experiencing the identical problem, Mark, but there were enough similarities in your post that I thought it couldn't hurt to share this information with you. Good luck! Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org