https://jeltsch.org/en/tags/reiserfsck/Recent content in Reiserfsck on Michael’s DomainHugoen-usCopyright © 2002 - 2026 Michael Jeltsch.Fri, 24 Jul 2026 00:18:18 +0300https://jeltsch.org/en/reiserfsck_and_repairing_the_root_partition_using_the_knoppix_cd/Mon, 21 May 2007 00:00:00 +0000https://jeltsch.org/en/reiserfsck_and_repairing_the_root_partition_using_the_knoppix_cd/<p>When I booted my laptop today, I got the following error message:Fsck failed. Please repair manually and reboot. The root file system is currently mounted read-only. To remount it read-write do: bash mount -n -o remount,rw / Attention: Only CONTROL-D will reboot the system in this maintainance mode. sgutdown or reboot will not work. Give root password to log inI logged in and executed:<code>reiserfsck --fix-fixable /dev/hda7</code>Several error messages appeared, among them in the end:<code>reiserfs_open: the reiserfs superblock cannot be found on /. Failed to open the filesystem.</code>Then it said somthing like that the superblock is corrupted and if I am sure that I am dealing with a reiserfs partition, I can rebuild it using the command:<code>reiserfsck --rebuild-sb</code>Then I realized, that /dev/hda7 is my encrypted filesystem and therefore no superblock was found. I repeated the command:<code>reiserfsck --fix-fixable /dev/hda6</code>It told me that the option &ldquo;&ndash;fix-fixable&rdquo; will be ignored. I don&rsquo;t know why. Maybe because I have mounted the system from the same partition I am about to fix. Anyway, the message in the beginning <code>The root file system is currently mounted read-only. To remount it read-write do: bash mount -n -o remount,rw /</code>tempted me to remount it in read-write mode and to execute the command again. But with no result. So I booted from the Knoppix CD and executed from there. The filesystem replayed, but no errors were found.Then I remembered that I had modified the fstab yesterday by adding: <code>/dev/sda1 /media/firewire reiserfs noauto,user 1 2</code>I thought that the noauto option prevents the partition from being accessed during bootup. Apparently not and the problematic entry a the two numbers in the end (1 2). They determine whether a filesystem is checked on bootup. I set them to &ldquo;0 0&rdquo; and tried to reboot.Voila, everything is fine again.Otherwise I might have tired to rebuild the superblock from Knoppix:<code>reiserfsck --rebuild-sb /dev/hda6</code></p>