FWIW, I reinstalled from live and installed chrome. First reboot survived.
Before going into emergency, the last messages had to do with
nouveau getting a timeout on some device. BUT, surely if the display
controller was flakey, I would not be sending this on gmail, no?
On Sun, Dec 11, 2022 at 5:
You might get more information to show up if you remove the "rhgb quiet"
options on the kernel boot line, then a message that comes out just before
it decides to do the emergency boot might have useful information.
I agree that the most common problem that causes this for me is
failing to create a
In my experience (and I have debug 100's of emergency mode).The issue
is typically a filesystem issue. Either the fstab entry is wrong, or a
driver required by a critical filesystem is failing. The ugliest ones are
when the issue is inside the initramfs and that issue is causing the root
devi
> On 11 Dec 2022, at 21:43, Geoffrey Leach wrote:
>
> When things come ungluded on booting,the user is offered a root login,
> which seems to be referred to as "Emergency Mode"
>
> journalctl is suggested as a place to start looking for causes. In the
> output there are no priority 0 and 1 (an
When things come ungluded on booting,the user is offered a root login,
which seems to be referred to as "Emergency Mode"
journalctl is suggested as a place to start looking for causes. In the
output there are no priority 0 and 1 (and perhaps 2) problems. Running
the reboot with display of the proc
