On 9/12/20 1:04 PM, Quinn Comendant wrote:
I don't see any errors from `systemctl status initrd-parse-etc.service` or `journalctl -b 0` (I've pasted the full output here:https://write.as/at21opjv3o9fin1t.txt)
I see errors in the journalctl output. Look into these:
Sep 12 19:41:12 myhost systemd-vconsole-setup[84]: /usr/bin/setfont failed with error code 71. Sep 12 19:41:12 myhost systemd-vconsole-setup[84]: ................... Sep 12 19:41:12 myhost systemd-vconsole-setup[84]: setfont: putfont: 512,8x16: failed: -1 Sep 12 19:41:12 myhost systemd-vconsole-setup[84]: putfont: PIO_FONT: Invalid argument Sep 12 19:41:12 myhost systemd-vconsole-setup[117]: /usr/bin/setfont failed with error code 71.
Sep 12 19:41:13 myhost systemd[1]: [/etc/systemd/system.conf:15] Unknown lvalue 'TimeoutSec' in section 'Manager'
The former errors might be normal on a system with no VGA, and you mentioned seeing this over serial. Do you see those errors on systems that boot normally? Do any of those system share a hardware configuration with the system that doesn't?
The latter error seems more likely to be the cause of the emergency shell, but that's a guess.
On 12 Sep 2020 13:40:40, Gordon Messmer wrote:
I see errors in the journalctl output. Look into these:
The `setfont` errors also occur on other VMs that do boot successfully. Their hardware configuration only differs in the amount of disk space and RAM assigned.
Unknown lvalue 'TimeoutSec' in section 'Manager'
Oh, that was a change I made just during the last reboot in an attempt to speed up the reboot process (server gets stuck on "A stop job is running for LSB…" for 5min after issuing a reboot command). It's not the cause.
Thanks, Quinn
-
Gordon Messmer -
Quinn Comendant