https://bugs.launchpad.net/ubuntu/+bug/371614/comments/2 should explain it.
My Filesystem is fine! No errors, checked 3 times! Reproduce it with "quiet splash" as kernel parameter and uncomment RAMRUN=yes /etc/default/rcS (only if you have ext2/ext3 filesystem, see source code). On my system a "quiet splash" fails at the fsck and as a result (don't ask me why) it stays mounted read-only. But the boot continues (lots of error messages about a read-only fs, but no root-prompt). checkroot.sh (with quiet as boot-parameter) is only working correct, if /var/run is writable (means RAMRUN=yes in /etc/defaults/rcS). The script wants to write to a progress file, which is only possible, if /var/run is mounted into the RAM. Fixing the bug by skipping the hole $PROGRESSFILE thing or forcing the user to use RAMRUN. Or better you shuld check for a writable /var/run/ directory before using it! replacing the block: PROGRESS_FILE=... ... rm -f $PROGRESS_FILE with fsck $force $fix -t $roottype $rootdev solved the problem. -- Upgrade 8.10 --> 9.04 : ext3 Filesystem read-only https://bugs.launchpad.net/bugs/371614 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
