diff --git a/manual.html b/manual.html index a855493f..cf797f71 100644 --- a/manual.html +++ b/manual.html @@ -466,11 +466,11 @@ snapraid fix -m
-DO NOT PANIC! You will be able to recover it! +DO NOT PANIC! You will be able to recover them!
-The first thing you have to do is to avoid further changes at you disk array. +The first thing you have to do is to avoid further changes at your disk array. Disable any remote connection to it, any scheduled process, including any scheduled SnapRAID nightly sync or scrub.
@@ -478,11 +478,11 @@ Then proceed with the following steps.
-Change the SnapRAID configuration file to make the "disk" option -of the failed disk to point to the place where you have enough empty +Change the SnapRAID configuration file to make the "data" or "parity" +option of the failed disk to point to the place where you have enough empty space to recover the files.
For example, if you have that disk "d1" failed, you can change from: @@ -500,6 +500,10 @@ to: data d1 /mnt/new_spare_disk/ +
+If the disk to recover is a parity disk, change the appropriate "parity" +option. +If you have more broken disks, change all their configuration options.
Where NAME is the name of the disk, like "d1" as in our previous example. +In case the disk to recover is a parity disk, use the "parity", "2-parity" +names. +If you have more broken disks, use multiple -d options to specify all +of them.
This command will take a long time.