I can’t login to the OS but it’s probably not an install/ Boot/ Login issue, so please pardon me if this is out of place.
When I try to bring up the OS (basic intel_64 box) the system boots and seems to load kernel but then fails to mount the OS root partition. I can’t find log records of the screen messages (perhaps not logged), but screen said something like: '… can’t see ‘/dev/disk/by-id/scsi-SATA_SAMSUNG_HD501LJS0MUJ13P302610-part11’ do you want me to default to ‘/dev/disk/by-id/scsi-SATA_SAMSUNG_HD501LJS0MUJ13P302610-part11’ y or n.
Same result each time I try loading current kernel (vmlinuz-2.6.29-rc5-1-default). Same result when I try loading previous kernel (vmlinuz-2.6.25.20-0.1-default).
The disk bootloader calls GRUB in its own part. Installed OS is ‘chainloaded’ from secondary bootloader in OS root. Can’t see errors in menu.lst. Entry for latest kernel is:
title openSUSE 11.0 - 2.6.29-rc5-1
root (hd0,10)
kernel /boot/vmlinuz-2.6.29-rc5-1-default root=/dev/disk/by-id/scsi-SATA_SAMSUNG_HD501LJS0MUJ13P302610-part11 resume=/dev/sda6 splash=silent showopts vga=0x317
initrd /boot/initrd-2.6.29-rc5-1-default
Last menu.lst mod date is Feb 27 2009
I also have 10.3 installed, it boots fine (hence this post). I can mount the partition mentioned above (also listed in fstab as /dev/disk/by-id/scsi-SATA_SAMSUNG_HD501LJS0MUJ13P302610-part11) and can rw files in /home /boot and /etc.
What may have caused this? Something obvious an ordinary user has missed? Can I fix it? Can I prevent it happening again?
Grateful thanks to the opensuse community.
Tallowwood
Australia
I see you’re running the 2.6.29 kernel. I’ve had some mean trouble with the rc5 and rc6: harddisks disappeared and appeared while running, GRUB errors, a “hanging” videocard, only to be “repaired” by pulling the plugs from the system, and, finally even this, reseating the videocard. This, and reverting to the 2.6.27 kernel solved it all.
Note, that running a kernel different from the used openSUSE release is not advised, but we do that anyway.
Thanks for responding Knurpht.
So problem may be caused by an engineering ‘bug’ rather than a user error.
What “2.6.27 kernel” did you apply? Was this a generic kernel or ‘SuSE’ version?
I don’t know how to install new kernel to unmounted ‘system’. I’ll start reading up on that.
For info of any ‘engineers’ reading this thread, the screen message actually said:
"Could not find /dev/disk/by-id/scsi_SATAxxxx-partxx
"Want me to fall back to /dev/disk/by-id/scsi_SATAxxxx-partxx ? Y/n.
Y brings up /bin/sh (I don’t know how to use that)
n stops all ‘md’ devices, reboots
cheers
Tallowwood
As you are a newbie in SUSE. Fresh installation will be the best option for you.
I’m in no rush to reinstall. I would like to know what is causing 11 to do this, and how to prevent it. SuSE 10.3 is old but still very stable, so I’m using that for now.
Installed 11.1 to another part and found similar issues after 3 reboots, but it did load after digging into the swap partition a couple of times.
Any other useful suggestions? The kernel process runs from bootloader in the partition it can’t see - kernel is not spawning any devices in /dev . Can’t mount anything from /bin/sh. This problem is know to be happening to others.
I am working on the ‘standard’ kernel suggestion (thanks).
There must be a better option than ‘just reinstall windows’? Maybe not.
Bells and whistles are all fine and good but even for a “newbie” stability is critical. Is this the “green” screen of death?