Comment 37 for bug 858122

I also experienced this bug, because I had the shutdown script order messed up by VMware Workstation.
Everything was fixed by manually creating the links to /run and /run/lock as per #18, and restoring the correct shutdown script order as per #22.
So, as a side effect of the /run problem, this fixed a long standing problem with the shutdown sequence. I used to stupidly wonder why fsck often reported "orphan nodes deleted" on reboot, now it won't happen any more !