You are not logged in.
I have been using arch linux for a while now (about a year) and I have installed 3 kernels, linux, linux-lts and linux-zen, with DKMS. When I try to boot into linux-zen or linux kernel after a shutdown, the journal service fails to start, however, with linux-lts it boots fine. After reboot, I am able to load linux-zen. I am unsure as to what could be the cause. This issue started after linux 6.5 update. My laptop is HP-ENVY-15t. I will provide any details needed. Please help.
Last edited by parton (2023-11-29 21:20:06)
Offline
the journal fails to load
What does this mean, exactly? Please provide exact commands and full outputs rather than vague descriptions.
Jin, Jîyan, Azadî
Offline
Failed to start journal service, I edited the original post.
Offline
systemctl status systemd-journaldOffline
Here's the output of the systemd-journal. I dunno how to get this for the linux-zen kernel as it won't boot.
● systemd-journald.service - Journal Service
Loaded: loaded (/usr/lib/systemd/system/systemd-journald.service; static)
Active: active (running) since Thu 2023-11-30 10:51:06 EST; 14min ago
TriggeredBy: ● systemd-journald-dev-log.socket
● systemd-journald.socket
○ systemd-journald-audit.socket
Docs: man:systemd-journald.service(8)
man:journald.conf(5)
Main PID: 483 (systemd-journal)
Status: "Processing requests..."
Tasks: 1 (limit: 18957)
FD Store: 59 (limit: 4224)
Memory: 18.4M
CPU: 544ms
CGroup: /system.slice/systemd-journald.service
└─483 /usr/lib/systemd/systemd-journald
Nov 30 10:51:06 Vachaspati systemd-journald[483]: Collecting audit messages is disabled.
Nov 30 10:51:06 Vachaspati systemd-journald[483]: Journal started
Nov 30 10:51:06 Vachaspati systemd-journald[483]: Runtime Journal (/run/log/journal/db8cae62a74a41c7bb47cc53e103a52e) is 8.0M, max 318.5M, 310.5M free.
Nov 30 10:51:05 Vachaspati systemd[1]: systemd-journald.service: Deactivated successfully.
Nov 30 10:51:07 Vachaspati systemd-journald[483]: Time spent on flushing to /var/log/journal/db8cae62a74a41c7bb47cc53e103a52e is 87.232ms for 1062 entries.
Nov 30 10:51:07 Vachaspati systemd-journald[483]: System Journal (/var/log/journal/db8cae62a74a41c7bb47cc53e103a52e) is 44.4M, max 50.0M, 5.5M free.
Nov 30 10:51:07 Vachaspati systemd-journald[483]: Received client request to flush runtime journal.
Nov 30 10:51:07 Vachaspati systemd-journald[483]: /var/log/journal/db8cae62a74a41c7bb47cc53e103a52e/system.journal: Journal file uses a different sequence number ID, rotating.
Nov 30 10:51:07 Vachaspati systemd-journald[483]: Rotating system journal.
Nov 30 10:51:15 Vachaspati systemd-journald[483]: /var/log/journal/db8cae62a74a41c7bb47cc53e103a52e/user-1000.journal: Journal file uses a different sequence number ID, rotating.Offline
How do you know that journald doesn't start if the kernel doesn't boot and wtf would you care?
The immediate problem is that the kernel doesn't boot. Maybe elaborate a bit on that.
That's btw. why vague descriptions of what you believe might be happening and an empty bag as as useful as the bag.
Offline
The message I get when I try to boot in linux-zen is "Failed to start Journal service", and I don't see a login screen. I don't get this error when booting using linux-lts or with linux-zen when I reboot the system from linux-lts. If I already knew the exact problem, I'd have fixed it by reading the wiki and not post a question here. That's why I described the problem.
Offline
Please share your bootloader configuration file(s).
Jin, Jîyan, Azadî
Offline
No, you described a symptom. And did a terrible job at that.
That's why you're asked to not paraphrase.
I don't see a login screen.
Try to boot the multi-user.target, 2nd link below.
Offline