Arch Linux

WickedWizard

Member

From: Canada

Registered: 2018-10-15

Posts: 29

Failure on Start

Hello,

Need some help: today I rebooted my system and instead of loading my display manager I see on the screen:

/dev/nvme0n1p5: recovering journal
/dev/nvme0n1p5: clean, 2564196/24584192 files, 89190360/98319616 blocks
[FAILED] Failed to start Load Kernel Modules.
[FAILED] Failed to start Virtual Console Setup.
[FAILED] Failed to start Apply Kernal Variables.
[FAILED] Failed to start D-Bus System Message Bus.
[FAILED] Failed to start User Login Management.
[FAILED] Failed to start Permit User Sessions.
[FAILED] Failed to start Network Manager.
[FAILED] Failed to start Network Time Service.
[FAILED] Failed to start Network Manager.
[FAILED] Failed to start User Login Management.
[FAILED] Failed to start Network Manager.
[FAILED] Failed to start Network Time Service.
[FAILED] Failed to start Network Manager.
[FAILED] Failed to start User Login Management.
[FAILED] Failed to start Periodic Command Scheduler.
[FAILED] Failed to start Network Manager.
[FAILED] Failed to start Network Time Service.
[FAILED] Failed to start User Login Management.
[FAILED] Failed to start Network Time Service.
[FAILED] Failed to start User Login Management.

Rebooting doesn't help, though the "Failed to Start" warnings come in different orders.  Sometimes there is a warning:

[    40.768298] EXT4-fs (nvme0n1p5): failed to convert unwritten extents to written extents -- potential data loss!  (inode 20448035, error -30)

I can't change to a different TTY (CTRL+ALT+F2 etc)

It's a dual boot system and I can boot into Windows without issue (same drive).

Apologies if this is the wrong subforum.  Anyone have an idea?  Am I borked?  I have all my data backed up so not too bothered there.  But would rather not go through the trouble of reinstalling Arch if possible as I customized it over time to how I like it.

seth

Member

Registered: 2012-09-03

Posts: 52,218

Re: Failure on Start

It's a dual boot system

3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

The file system is obviously heavily corrupted, so you'll likely have to at least reinstall all packages

Don't reboot by holding down the power button and since it's an nvme maybe see https://wiki.archlinux.org/title/Solid_ … leshooting (but whether that has happened is impossible to say based on the provided symptoms)

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc