CentOS - Sep 2020 - Server entering Emergency Shell, but continues fine after pressing Enter

Hi Thomas,

On 10 Sep 2020 10:06:01, Thomas Bendler wrote:
> If I'm not mistaken, problems after UTMP point to problems with X/
hardware
> configuration. So I guess you might find more information when you also
> have a look at the log files of systemd.
I don't see any hardware issues. Here's the output from `journalctl -p 5
-xb`: https://write.as/2vjgz6pfmopg7fnf.txt The time of the last interruption
during boot was at Sep 10 15:01:46.

Thanks,
Quinn

I had similar issue on 7.6 - the LVM timeouts were too short and it was timing
out as we had a lot of multipath devices. Once those were up , you could just
continue.

journalctl will show you what has happened.


Best Regards,
Strahil Nikolov






? ?????????, 10 ????????? 2020 ?., 18:57:02 ???????+3, Quinn Comendant <quinn
at strangecode.com> ??????:





Hi Thomas,

On 10 Sep 2020 10:06:01, Thomas Bendler wrote:
> If I'm not mistaken, problems after UTMP point to problems with X/
hardware
> configuration. So I guess you might find more information when you also
> have a look at the log files of systemd.
I don't see any hardware issues. Here's the output from `journalctl -p 5
-xb`: https://write.as/2vjgz6pfmopg7fnf.txt The time of the last interruption
during boot was at Sep 10 15:01:46.

Thanks,

Quinn
_______________________________________________
CentOS mailing list
CentOS at centos.org
https://lists.centos.org/mailman/listinfo/centos

Hi Strahil,

On 10 Sep 2020 17:42:03, Strahil Nikolov via CentOS
wrote:
> I had similar issue on 7.6 - the LVM timeouts were too short and it was
timing out [?]
I don't see any timeout errors in the boot log or output from journalctl
-xb.

I've tried increasing the timeout by updating the Grub config with
`mount.timeout=300s`, is that the correct way to increase LVM timeouts? It has
no effect.

Quinn