You are not logged in.

#1 2021-04-08 14:26:09

dboardman3
Member
Registered: 2018-01-24
Posts: 3

System failing to boot occassionally

I've been using this arch installation for nearly 2 years - and suddenly it has begun to fail the boot process occasionally. The screen is black with a blinking cursor. This is the output of journalctl:


drew@pizza ~ $ sudo journalctl -p 3 -xb
-- Journal begins at Sat 2020-01-18 10:52:33 CST, ends at Thu 2021-04-08 09:21:23 CDT. --
Apr 08 09:21:04 pizza kernel: kvm: disabled by bios
Apr 08 09:21:04 pizza kernel: kvm: disabled by bios
Apr 08 09:21:04 pizza kernel: kvm: disabled by bios
Apr 08 09:21:05 pizza systemd[1]: Failed to start PostgreSQL database server.
░░ Subject: A start job for unit postgresql.service has failed
░░ Defined-By: systemd
░░ Support: [url]https://lists.freedesktop.org/mailman/listinfo/systemd-devel[/url]
░░
░░ A start job for unit postgresql.service has finished with a failure.
░░
░░ The job identifier is 101 and the job result is failed.
Apr 08 09:21:05 pizza kernel: kvm: disabled by bios
Apr 08 09:21:05 pizza kernel: hid-generic 0003:0D8C:0319.0006: No inputs registered, leaving
Apr 08 09:21:05 pizza kernel: kvm: disabled by bios
Apr 08 09:21:05 pizza kernel: kvm: disabled by bios
Apr 08 09:21:05 pizza kernel: kvm: disabled by bios
Apr 08 09:21:05 pizza kernel: kvm: disabled by bios
Apr 08 09:21:05 pizza gnome-session-binary[568]: Unrecoverable failure in required component org.gnome.Shell.desktop
Apr 08 09:21:05 pizza kernel: kvm: disabled by bios
Apr 08 09:21:05 pizza kernel: kvm: disabled by bios
Apr 08 09:21:12 pizza ntpd[453]: bind(24) AF_INET6 2601:249:8080:eaf0::3bb9#123 flags 0x11 failed: Cannot assign requested address
Apr 08 09:21:12 pizza ntpd[453]: unable to create socket on enp35s0 (5) for 2601:249:8080:eaf0::3bb9#123
Apr 08 09:21:12 pizza ntpd[453]: bind(24) AF_INET6 2601:249:8080:eaf0:e841:ddc5:5b04:a20e#123 flags 0x11 failed: Cannot assign requested address
Apr 08 09:21:12 pizza ntpd[453]: unable to create socket on enp35s0 (6) for 2601:249:8080:eaf0:e841:ddc5:5b04:a20e#123
Apr 08 09:21:14 pizza gdm-password][956]: gkr-pam: unable to locate daemon control file
Apr 08 09:21:16 pizza pulseaudio[1120]: GetManagedObjects() failed: org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.bluez.service not found.

Is this due to the gnome desktop error? How would I go about resolving this?

Last edited by dboardman3 (2021-04-08 14:27:36)

Offline

#2 2021-04-08 14:56:59

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 5,809
Website

Re: System failing to boot occassionally

Enable an early KMS start for the video card. There have been several threads about this recently.

For example: https://bbs.archlinux.org/viewtopic.php?id=265240

Offline

#3 2021-04-08 15:00:43

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 12,520

Re: System failing to boot occassionally

-p3 lacks context and -x is useless, post a full -b if you want a proper assessment

However just from the symptoms this is highly likely to be the KMS early boot race, so check out: https://wiki.archlinux.org/index.php/Ke … _KMS_start

Offline

Board footer

Powered by FluxBB