[opensuse] Can't boot 11.1 system after 2.6.27.19-3.2 kernel update!!
Original AMD64 11.1 install about a month ago, no problems. After the 2.6.27.19-3.2 kernel update about 10 days ago, menu.lst was blank (after the first stanza); bug report filed. I tried to repair the system with the 11.1 repair option, but the system
This problem is driving me crazy - unfortunately, I have to recreate info from memory as I cannot get the system to boot and there is no way to get info off unless booted with a System Rescue CD. thinks /dev/sda6 (the root partition) is a USB DEVICE AND TIMEOUTS!
Briliant idea - copy a kernel from another machine and try booting, AND IT BOOTED FINE! [Except that machine didn't have nVidia and this one did, so no X). Tried Repair again to rebuild the module/kernel config, AND THE SYSTEM IS NOW BACK TO LOOKING FOR A USB DRIVE INSTEAD OF A SATA DRIVE.
Has anyone seen anything like this before? This system was very stable before this last upgrade, .. I had Virtual Box installed, upgraded to 4GB of memory and was getting ready to build some VMs. Any thoughts would be appreciated, .. Lee -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Mar 8, 2009 at 6:00 PM, L. V. Lammert
This problem is driving me crazy - unfortunately, I have to recreate info from memory as I cannot get the system to boot and there is no way to get info off unless booted with a System Rescue CD.
Original AMD64 11.1 install about a month ago, no problems. After the 2.6.27.19-3.2 kernel update about 10 days ago, menu.lst was blank (after the first stanza); bug report filed. I tried to repair the system with the 11.1 repair option, but the system thinks /dev/sda6 (the root partition) is a USB DEVICE AND TIMEOUTS! Briliant idea - copy a kernel from another machine and try booting, AND IT BOOTED FINE! [Except that machine didn't have nVidia and this one did, so no X). Tried Repair again to rebuild the module/kernel config, AND THE SYSTEM IS NOW BACK TO LOOKING FOR A USB DRIVE INSTEAD OF A SATA DRIVE.
Has anyone seen anything like this before? This system was very stable before this last upgrade, .. I had Virtual Box installed, upgraded to 4GB of memory and was getting ready to build some VMs.
Any thoughts would be appreciated, ..
Lee
If you have an opensuse disk lying around, select Install > Boot installed system rather than repair. You should be able to remove the new kernel, install the previous version and possibly reinstall grub to get your menu.lst rebuilt (or regenerate the menu.lst from the bootloader yast module). As a last resort if reinstalling the kernel doesn't work, use Upgrade from the disk - you get to keep your apps and most settings. Goodluck. Nkoli -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
L. V. Lammert wrote:
This problem is driving me crazy - unfortunately, I have to recreate info from memory as I cannot get the system to boot and there is no way to get info off unless booted with a System Rescue CD.
Original AMD64 11.1 install about a month ago, no problems. After the 2.6.27.19-3.2 kernel update about 10 days ago, menu.lst was blank (after the first stanza); bug report filed. I tried to repair the system with the 11.1 repair option, but the system thinks /dev/sda6 (the root partition) is a USB DEVICE AND TIMEOUTS! Briliant idea - copy a kernel from another machine and try booting, AND IT BOOTED FINE! [Except that machine didn't have nVidia and this one did, so no X). Tried Repair again to rebuild the module/kernel config, AND THE SYSTEM IS NOW BACK TO LOOKING FOR A USB DRIVE INSTEAD OF A SATA DRIVE.
Has anyone seen anything like this before? This system was very stable before this last upgrade, .. I had Virtual Box installed, upgraded to 4GB of memory and was getting ready to build some VMs.
Any thoughts would be appreciated, ..
Lee
Your problem is that usb module is initialized first and take sda device. Solution for you is use udev id instead of kernel device. You can do it during installation in storage by setting mount by. perl-Bootloader take root device from /proc/mounts (find what is '/'), so if you mount you '/' by id, then after next kernel upgrade system finding root by disc id and not kernel device. JR -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Josef Reidinger -
L. V. Lammert -
Nkoli