New problem in 18.10...

I just discovered that the way I've always used fsck at the root access in recovery mode no longer works. It used to be:

fsck -f /

But now it tells me that the disk is mounted r/w, and it won't run. Sure enough the disk IS mounted r/w. This is new behavior. Trying to remount the disk as ro doesn't work either.

mount -o remount,ro /

And, running fsck from the recovery mode menus doesn't work either.

Running fsck while booted to a Ubuntu Live USB works of course.

Anybody got an idea why I can't fsck in recovery mode, and what's changed that causes the disk to be mounted r/w?

  • possible duplicate of askubuntu.com/questions/98559/… – s1mmel Jan 23 at 9:11
  • @s1mmel Thanks for your comment, however, the link goes to a question from 2012, and it doesn't address my problem in 18.10, whereas something has changed in 18.xx that causes the disk to be mounted r/w, and thus, you can't run fsck in recovery mode like you could in 17.xx. – heynnema Jan 23 at 15:46
  • SNIP --> I read online that I shouldn't mount the root file system if I want to run fsck, so I chose the option "do not use a root file system". <-- SNIP. Did you see such an option? – s1mmel Jan 23 at 15:57
  • @s1mmel Where are you seeing "do not use root file system"? Is this in 18.xx? In 17.xx recovery mode had the disk mounted r/o, and you could run fsck. In 18.xx this isn't the case, and not only can you not run fsck from the recovery menu, but you can't run it from the root prompt, without an error about / being mounted r/w. – heynnema Jan 23 at 16:06
  • It was written in the question itself. – s1mmel Jan 24 at 11:09

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Browse other questions tagged or ask your own question.