This morning I came to work a hour earlier than usual. I started my work PC and waited for it to boot into Debian Jessie. And waited… waited… waited…
This sounds strange, doesn’t it? It generally boots rather quickly. In fact Debian hangs during boot with this message:
A start job is running for Create Volatile Files and Directories
Followed by a timer and no limit. You can leave it there, but it does not finish and just hangs there. So, let’s try understand the problem.
The problem here is quite obvious: in the previous session you updated systemd to version 215-5+b1. If you have a look at your system’s
/tmp directory (you can’t do it now, but we’ll do it later for sake of knowledge), you find out that it’s bloated. Here’s the bug report.
Thankfully, the solution is pretty straightforward. Reboot your computer with Ctrl+Alt+Del and wait for Grub to load, then press e to edit Debian’s entry. After the line with
/boot/vmlinuz... add the following:
--add rw init=/bin/bash
And press F10 to boot. Debian will load as a shell with root permissions, so you can do whatever you want (but be careful, because you can cause big issues too!
Now it’s time to check your
ls -l /tmp
You should wait some minutes until it finishes, and the output may scare you. It’s bloated, as I told you before. What can you do now? Just remove and recreate it.
rm -rf /tmp mkdir /tmp chmod 1777 /tmp
Now restart your PC and check it out: Debian will boot correctly!
Is systemd ready to go towards a Debian stable release? I don’t think so. The team has to work hard to accomplish this step. So, good luck guys, and please test it a little more next time!
See edit above.
Source: Debian User Forums