openSUSE is starting to drive me a bit nuts. Actually what I'm trying to do is simply install VMWare server on a recent as possible SUSE and run 2 virtual machines, both the same SUSE. Of course 11.2 32 bit doesn't run VMWare server 2 so it's back to 11.1. The trouble is, 11.1 won't install properly on my PC.

The install process, booted and installed from the 11.1 network install iso image on CD, runs fine. The PC reboots from hard disk and stops at the grub prompt. I've tried the auto-repair option and reinstalled it from scratch a second time always with the same results. It seems the root partition is hosed, and that's where my understanding hits its limits. Can anyone help?

Incidentally should anyone be able to advise on the VMWare conundrum I'd also be interested. Maybe in another thread...

Thanks in advance.

Do you get a Grub error message?

No error message, just grub prompt. I see the other threads suggested below and I'll try some of the remedies although they're all about dual boot machines. Mine fails on a single install, clean hard disk...

It seems that the openSUSE installer had tried to retain some old partitions that were on the disk, and probably got itself confused. I've deleted them all and will re-install yet again on a truly clean disk...

You probably had an ext4 filesystem which wasn't previously supported.

I have found that since 11.1, GRUB insists on using "Disk ID" to identify partitions, which means it uses the disk serial number and partition number, rather than the path - so:instead of:This can lead to confusion if you don't remake the fstab & menu.lst files when you do an upgrade or install and keep any of the old config.

The solution seems to be that when you have a boot problem, boot the install disc and run "Repair Installed System". Once it starts, select the "Expert Tools", and run the "Install New Boot loader". When you get to the next screen click on the "Other" button at bottom right and select "Propose New Configuration". This will search for any partition with a /boot directory, and read its contents. It will then offer all the bootable options it thinks are there, and you can then choose which you want to keep. When you click "OK" it will write a new GRUB config to disk and when you reboot it should all work.

I've had problem on several machines with Suse 11.1 not booting after kernel upgrades with similar results to yours. In each case I found that doing the above will fix it, even on multiple boot machines with various combinations of Windows and Linux.

Thanks for the tips, they helped get it working. The search even found a long lost partition I thought was deleted. It seems when YAST says 'I'm going to delete all data on your disk' it's only being half truthful...