/var/run is a temporary read-write filesystem and is mounted by
S01mountkernfs.sh very early on in the boot process. fsck can still
write to /var/run even though the root filesystem is read-only, so I
very much doubt that is the issue here. Bare in mind that the default
Ubuntu configuration does not have a separate /var partition, so
everyone would have this problem if this was really the cause of your
issue. The only time that fsck would not be able to write to /var/run
would be if the mounting of /var/run failed for some reason.
Do you not get an error when fsck stops? Have you tried booting in
recovery mode to look for errors?
Thanks
** Changed in: sysvinit (Ubuntu)
Status: New => Incomplete
--
checkroot.sh blocks writing /var (fsck)
https://bugs.launchpad.net/bugs/246367
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
