I’m a step further. Good luck remembered that for this vserver a “rescue system” is available. Gentoo, as far as I’ve seen. Booted the rescue system, and now have access to all (virtual) disks of my “original” vserver. Mounted all native partitions and all (LVM) logical volumnes.
I now have access to the file system in an environment where I can type and use all characters
Browsing through /var/log/messages, I can see that these reboots to the emergency system haven’t written anything to /var/log/messages.
Can anyone please tell me where to find the boot log for the boot into “emergency mode”?
IMO anyone who deploys in a cloud service should clearly define and understand what can and can’t be done.
And, the service has a duty to either provide you with the tools to do your own troubleshooting or they should be willing to do it themselves.
A big hint for these kinds of services is the source of the virtual machine…
They might provide one for convenience, but find out what it would take for you to upload and deploy your own machine to their service… If it can be done, then you have a certain measure of control. If you can’t or it’s extremely difficult, then walk away.
Agree more or less, more more At my hosting company, you can’t upload your own machine, would be cool, totally agree. But they provide a very wide range of linux base images, like Fedora, Cent OS, Debian, Ubuntu, and, a pity but rarely available, OpenSuse. Which of course was the reason for me to choose them All distros in several releases.
I can do inside my vps whatever I want. If not illegal (e.g. spamming). So of course I usually can run journalctl directly on my vps. In theory, reality was, that Emergency Mode means no network, and the only access point left was the VNC based access from the physical machine hosting my vps. This vnc access is funny, you can see all boot menus etc., long before OpenSuse or in fact Grub2 starts. BUT it has had a very strange keyboard layout at first, e.g. no “-” on all keys (tested ALL, believe me ;-)), very bad idea for any flags to be passed to any command. I’ve workaounded this with using the second chance for access, the rescue system. If started, another virtual machine is started, same IPv4, Gentoo in this case, very basic, but you can access = mount all of your virtual disk files. Doing this I’ve created scripts for all commands I later on, again im my “own” vps within Emergency Mod, could finally execute. Painful, but necessary during the night, with no support available (8:00 to 23:00).
Next morning my hosting company’s support immediately reacts, found their mistake with the strange keyboard layout and switched at once.
From then on it was not that much trouble anymore and purely an OpenSuse-related issue.
And that is what I still want to find out:
**Why does a LVM schema which worked totally fine on 42.1 refuses to work on 42.2? ** Leading me into this painful Emergency Mode “experience”