Timeline for filesystem read only
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 29, 2012 at 15:13 | comment | added | derobert |
@Tim I'm talking about the first line of the post. At minimum (for e2fsck) you need to add -n (and I seem to recall previous versions having bugs around that). For reiserfs, I'm not sure. Keep in mind the fsck will often attempt a journal replay.
|
|
| Aug 29, 2012 at 15:09 | comment | added | Tim | @derobert very last line of my post: "boot with a Live CD or Rescue Disk for your system and un fsck -f on the disk to repair it." Seems clear to me, did you miss it? | |
| Aug 27, 2012 at 11:08 | comment | added | maniat1k | @derobert I'm have not run a fsck on a mounted partition; I'm used a liveCD to do that. | |
| Aug 26, 2012 at 20:44 | comment | added | Martin Schröder | @Solo: So it's reiserfs? Migrate to another fs. | |
| Aug 24, 2012 at 17:22 | comment | added | derobert | but also, you're having him run a fsck on a mounted partition. Generally not the best of ideas... | |
| Aug 24, 2012 at 17:15 | comment | added | derobert | @Tim: No, he wants to fsck the partition, not the whole disk. So /dev/sda1 or whatever. | |
| Aug 24, 2012 at 15:11 | comment | added | maniat1k |
Ok fsck.reiserfs -f /dev/sda gave me this output the reiserfs superblock cannot be found on /dev/sda. Failed to open the filesystem.
|
|
| Aug 24, 2012 at 14:59 | history | answered | Tim | CC BY-SA 3.0 |