Cannot boot with newly installed systemd if /tmp/ is filled with files
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
upstart (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
On a new lubuntu 14.10 install, after installing a bunch of new packages, I rebooted the machine and it stalls on startup. It stays on the four dots of plymouth (not the graphical version).
After trying various options in rescue mode, I end up understanding that the boot system has switched to systemd by looking at /var/log/dpkg.log (attached).
I then tried init=/lib/
So, in rescue mode, I did a mv /tmp/ to /fulltmp/ (an ls wouldn't return so I'm guessing the /tmp/ is really full and the disk is not rocket fast). I recreated /tmp and did a chmod 1777 /tmp, reboot and it works!
While describing this, am not entirelly sure upstart is exempt from this bug (how do I check which init was used after I've booted ?)
This is a very frustrating bug since it doesn't appear on startup even when removing quiet or splash.
tags: | added: patch |
Changed in systemd (Ubuntu): | |
status: | Triaged → Invalid |
You are still running upstart. However, it'd be good to check this under systemd as well. Under either init system, a tmpfs should be mounted on /tmp/ if the disk is full.