Tell me more ×
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It's 100% free, no registration required.
up vote 1 down vote favorite

While booting Ubuntu and mounting my casper-rw file for persistent storage, Ubuntu recommends me to check for errors using fsck. However, when I boot into my system, since the casper-rw is automatially mounted and cannot be unmounted, it refuses to repair errors in my casper file system.

Even If I boot without persistent option, fsck cannot repair my casper-rw file saying that its read-only file system. Is there any way to check and repair errors in casper-rw ?

share|improve this question
Could you elaborate a little more on where you got the "read-only filesystem" error? – shroff Dec 22 '10 at 8:54
This question seems abandoned, there is not further information or activity added to it for several months. I am flagging this to be closed by a moderator. If you think this issue is still affecting you you can flag a moderator to re-open it. – Bruno Pereira♦ Feb 3 '12 at 0:38

closed as too localized by Marco Ceppi♦ Feb 3 '12 at 0:55

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, see the FAQ.

1 Answer

up vote 1 down vote

This seems to be a common issue and has been going for some time. Using the ubuntu-11.04-desktop-i386.iso I am still having issues with this. https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/125702

The way I have mounted the casper-rw file is doing the following.

  • Mount your USB key
  • sudo fsck -y -t ext3 /media/[drive]/casper-rw

Some users, including myself, are still reporting issues even after doing this so ymmv.

You might want to start backing up your loop file and keeping it only as large as you need. Before doing this resize make sure you back it up but here are the basics.

  • Boot without using persistent or use another system
  • Insert and mount your device that contains the loop file
  • dd if=/dev/zero bs=1M count=1024 >> casper-rw
    • Where 1024 is larger than your current used
  • resize2fs casper-rw

Using this method you should be able to keep your loop files only as large as needed, have some backups and if all else fails be able to fsck them.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.