Hi again,

1. make sure you have reiser4progs-1.0.6 installed
2. close all applications.
3. start single mode (init 1).
4. remount root partition to "readonly".
5. run fsck.reiser4 root_device_name (if you use cryptcompress, then pass
   options -n --fix for the first run).

Ooops. I did not pass the -n --fix options first, but let fsck.reiser4
run without any additional options - it stopped with 2 corruptions. I
decided not to do anything further because I already lost data with
reiser3's fsck.reiser.

When rebooting mount claims that it will only load reiser4 read-only
because it contains errors but it ends up that it can't be mounted at
all.

Now I tried to re-run with exactly the options you gave me (I had a
disk with the same kernel / toolset laying arround) gut it bails out
with "1 fatal corruption was found". It says the storage tree does not
exist.

Any options to get my data back without rebuilding the filesystem. How
likely is it to get my data back if I choose to rebuild it. I wrote
some quite tricky pieces of code lately ... would be sad to loose them
:-/

Thank you in advance, lg Clemens

Reply via email to