It took a long time to get it started after I restarted the vm.
This was clean install, worked fine for 2 days then froze so I had to restart.
Maybe a downside of “btrfs”?
Now I can get to the Suse screen but if I choose failsafe or standard grub sticks on initrd /initrd -3.1.0 -1.2 desktop
I then have to reboot using ctrl alt insert (for the vm) and it just loops back to this.
It also appears this has corrupted my other vms which won’t boot either.
I am a newb with troubleshooting.
Any help appreciated.
Well that is good to know, it’s hard to figure out what happened.
On one reboot (normal) I may have still had the cd pointing to the iso datastore but it isn’t there anymore for some reason.
I changed it back to client device.
Any idea on how to get this Suse booted?
Since the vm will power on, it still seems like it’s something in Suse or I need to try something else.
But the screen that comes up I think is recovery, it only gives failsafe, standard or F5 for init level(?) but that doesn’t do anything.
I’m using vmware Vsphere (on win xp client) with Esxi 4.0 on an hp proliant server.
I’ve posted in their forum too, no results yet.
On 2012-02-03 17:36, petecha wrote:
> But the screen that comes up I think is recovery, it only gives
> failsafe, standard or F5 for init level(?) but that doesn’t do anything.
That’s the standard boot screen. What happens when select one of the
entries? Describe in detail.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
Well it was hanging on the line that ended with “/initd” after Grub stage 2 shows loading.
It was going very slowly and just sticks.
But now I can’t even connect to the vms to boot it so I will pursue the vm/hardware side of causes.
thanks