Over the last month or so we’ve had three virtual boxes running vmware lock up for no reason we can determine. When we power them off and then on again, they will partially
boot and then hang. I have attached a screen shot of where they hang after the kernel is selected.
Odd thing is if we select a previous kernel, instead of the newest kernel, they would all boot fine (except for the one we are currently having issues with). After booting them we can then boot back to the newest kernel and everything seems fine again, no issues. Or so it was for the first two boxes which did this. The third box and last box, refuses to stay up after we get it back up with the newest kernel again.
Not sure if I should open a support ticket since I’m sorta floundering a bit trying to figure out what could be causing this. The only useful info we’ve noticed so far is the latest box
complained about “BTRFS error: could not find root” when we initially brought it up under the older kernel.
Hi
I’ve asked my SUSE contacts if it’s a known issue.
–
Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.2|GNOME 3.20.2|4.4.87-18.29-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
Oldest kernel on the box ( 3.12.62-60.62-default ) seems stable. The following two seem to have issues? 4.4.74-92.35 4.4.74-92.38 at least on this box…
Looking at the output of that it seems to only contain the information for the latest boot with the old kernel (can’t do anything useful before it looks up when we an get it up with the newst kernel). Is that useful since it is the newer kernel with the hanging issue?
[QUOTE=skunkboy;39728]Looking at the output of that it seems to only contain the information for the latest boot with the old kernel (can’t do anything useful before it looks up when we an get it up with the newst kernel). Is that useful since it is the newer kernel with the hanging issue?
Matt[/QUOTE]
Hi
You can look at past boots…
journalctl --help
journalctl --list-boots
Coredumps?
coredumpctl list
Any pointers or suggestions would be appreciated.[/color]
Have you verified that the version of SLES12 SP(x) is supported under
the version of VMware you are using?
I don’t know if this applies in your case… but if you are using ESXi
VMware recommends that VMs not be upgraded to new releases of the OS
but instead you do a new install.
–
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.
Yes our OS version is supported by our the version of ESXi that we are running.
We have been doing clean installs when going from SLES 11 to 12, not when going from 12sp1 to 12sp2, that seems insane, would have to reinstall the boxes every other year?
Yes our OS version is supported by our the version of ESXi that we are
running.
We have been doing clean installs when going from SLES 11 to 12, not
when going from 12sp1 to 12sp2, that seems insane, would have to
reinstall the boxes every other year?
Thanks,
Matt[/color]
Great! That’s one potential issue eliminated.
When issues are posted to these forums, we never know what the
background of the sysadmin might be and sometimes have to ask rather
obvious questions.
Personally, I don’t like the idea of having to do new installs for
major version upgrades but it is what it is.
–
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below this post.
Thank you.
We have not seen this again since I turned on boot log archiving on the boxes in question. Not sure if this was an actual fix, or we just had some other odd issue. But since it has stopped I’m not currently too worried about it…
