This bug report is being closed due to your last comment regarding this
being solved. For future reference you can manage the status of your own
bugs by clicking on the current status in the yellow line and then
choosing a new status in the revealed drop down box. You can learn more
about bug statu
Thanks, but I consider my problem solved.
-troy
--
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
ubuntu-bugs@lists.ubuntu.com
h
/var/run is just a tmpfs which has been supported for a very long time
(since 2.4 series kernels I believe).
Are you seeing any error messages when you boot in to recovery mode?
Perhaps you could also try removing the 'quiet' and 'splash' options
from the kernel command line. I can assist you if y
Chris is correct. My bad. Sorry for any confusion.
I'm not sure what it was, but:
1) VERBOSE=yes did work as a work-around. I did a lot of /forcefsck reboots
with and without this setting.
2) The problem stopped when I stopped booting 2.6.22-14 and started booting
2.6.24-19. The former may
/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 no
