I’m running 12.2 as a VirtualBox guest on a 12.2 host. The guest booted fine this morning. After a kernel update, KDE didn’t start on the guest and I get a terminal window that reads:
Welcome to emergency mode. Use “systemctl default” or ^D to enter default mode.
I can log in, but very few system services are working, including networking.
dmesg shows many messages like:
systemd[1]: Job <some service>/start failed with result ‘dependency’.
where <some service> is many different services, including cups.path, graphical.target, multi-user.target, xdm.service, and network.service.
On 2013-03-18 18:16, dilireus wrote:
>
> I’m running 12.2 as a VirtualBox guest on a 12.2 host. The guest booted
> fine this morning. After a kernel update, KDE didn’t start on the guest
> and I get a terminal window that reads:
Well, you have to handle the problem as any other system that boots into
emergency mode. VB is not related to this, IMO.
Unfortunately, systemd is very bad at explaining what is the problem
that dumps you into emergency mode. Systemv was much better, it told you
what the problem was.
You might read the boot log and find out - good luck.
Typical problems are a filesystem check failure, a partition that can
not mount, bad entries in fstab… For instance, you have an entry in
fstab for removable media and then the media is not available. Bang!
Try to remember what you did last.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
The only log file in /var/log that’s updating is Xorg. /var/log/messages and /var/log/boot.log have not received any new messages in the past 2 reboots.
Try to remember what you did last.
All I did was apply the latest recommended updates, which included a kernel update (3.4.33-2.24-default), and reboot. It’s been failing ever since.
Maybe reinstall the extras? New kernel usually needs a video driver reinstall. Can you get to a command line?
On 2013-03-18 21:36, gogalthorp wrote:
> Maybe reinstall the extras? New kernel usually needs a video driver
> reinstall.
Not when the machine is a virtual machine 
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
On 2013-03-18 19:26, dilireus wrote:
>
> robin_listas;2537398 Wrote:
>>
>> You might read the boot log and find out - good luck.
>>
>
> The only log file in /var/log that’s updating is Xorg.
> /var/log/messages and /var/log/boot.log have not received any new
> messages in the past 2 reboots.
With systemd ‘boot.log’ is not created nor updated. Only with systemv.
But that ‘/var/log/messages’ is not updated is very strange.
Unbelievable unless you are looking at the wrong disk, or it is mounted
read-only. And it is not RO because you say xorg log is updated.
>> Try to remember what you did last.
>
> All I did was apply the latest recommended updates, which included a
> kernel update (3.4.33-2.24-default), and reboot. It’s been failing ever
> since.
Mmmm… :-?
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
Ok, this isn’t a fluke. I just updated a VB guest on another computer and it’s hosed as well. Same exact issue. The first machine is HP Intel-based. This current machine is AMD. Both are running openSUSE 12.2 as host and guest. In both instances, the host is at the same patch level as the guests and run without any issues whatsoever. The guests are just broken and I have no idea how to proceed.