Arch Linux

tancrackers

Member

From: USA

Registered: 2012-04-11

Posts: 44

"a start job is running for hold until boot process finishes up"

I am running an up-to-date version of arch linux.
I am unable to open a terminal with ctrl+f2; it only leaves a blinker without ability to input commands.
I decided to try ctrl+alt+f1 to see what was happening.
I see a recurring "a start job is running for hold until boot process finishes up (Xmin/No Limit)"

I haven't noticed a pattern in it, and I see nothing in journalctl that points to this.

If it matters, I have LVM partition encrypted with dm-crypt, LVM on luks.
/dev/sda is split as such:
/dev/sda1 -> /boot
/dev/sda2 -> LVM on luks
inside:

/dev/mapper/MyStorage-rootvol
/dev/mapper/MyStorage-homevol
/dev/mapper/MyStorage-swapvol

I noticed this follows the message:

Starting Cleanup of Temporary Directories...
Failed to start Cleanup of Temporary Directories

I tried

systemctl stop systemd-tmpfiles-clean.timer

and restarted this process, but to no avail.

I can supply more information if needed.

---

Block ads forever! http://adblockplus.org/en/

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,424

Website

Re: "a start job is running for hold until boot process finishes up"

So does this prevent you from bringing the system up, or is it just a temporary setback?
Does it happen every boot, or intermittently?

Not a Sysadmin issue, moving to Kernel and Hardware...

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

TingPing

Member

Registered: 2011-01-21

Posts: 6

Re: "a start job is running for hold until boot process finishes up"

I was also getting this systemd message and I tracked the issue down to the gdm-plymouth service after a plymouth update.

---

AUR - Github

Wilco

Member

Registered: 2008-11-09

Posts: 440

Re: "a start job is running for hold until boot process finishes up"

Downgrade systemd, going from 219 to 218 solved my boot issues