From d1a34f8780ea4fcd91d7457bc1315dd4c2bcac4a Mon Sep 17 00:00:00 2001 From: Andrea Mazzoleni Date: Wed, 28 Dec 2016 09:39:06 +0100 Subject: [PATCH] Update recovering manual --- snapraid.1 | 22 +++++++++++++++------- snapraid.d | 22 +++++++++++++++------- snapraid.txt | 22 +++++++++++++++------- 3 files changed, 45 insertions(+), 21 deletions(-) diff --git a/snapraid.1 b/snapraid.1 index d4fa7dbd..7cce19ec 100644 --- a/snapraid.1 +++ b/snapraid.1 @@ -551,21 +551,21 @@ snapraid fix \-m .PD .RE .SS Recovering -The worst happened, and you lost a disk! +The worst happened, and you lost one or more disks! .PP -DO NOT PANIC! You will be able to recover it! +DO NOT PANIC! You will be able to recover them! .PP -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. .PP Then proceed with the following steps. .SS STEP 1 \-> Reconfigure -You need some space to recover, even better if you already have an additional -disk, but in case, also an external USB or remote disk is enough. +You need some space to recover, even better if you already have additional +spare disks, but in case, also an external USB or remote disk is enough. .PP -Change the SnapRAID configuration file to make the \[dq]disk\[dq] option -of the failed disk to point to the place where you have enough empty +Change the SnapRAID configuration file to make the \[dq]data\[dq] or \[dq]parity\[dq] +option of the failed disk to point to the place where you have enough empty space to recover the files. .PP For example, if you have that disk \[dq]d1\[dq] failed, you can change from: @@ -585,6 +585,10 @@ data d1 /mnt/new_spare_disk/ .PP .PD .RE +.PP +If the disk to recover is a parity disk, change the appropriate \[dq]parity\[dq] +option. +If you have more broken disks, change all their configuration options. .SS STEP 2 \-> Fix Run the fix command, storing the log in an external file with: .PP @@ -596,6 +600,10 @@ snapraid \-d NAME \-l fix.log fix .RE .PP Where NAME is the name of the disk, like \[dq]d1\[dq] as in our previous example. +In case the disk to recover is a parity disk, use the \[dq]parity\[dq], \[dq]2\-parity\[dq] +names. +If you have more broken disks, use multiple \-d options to specify all +of them. .PP This command will take a long time. .PP diff --git a/snapraid.d b/snapraid.d index 95809aa0..6cc0bf94 100644 --- a/snapraid.d +++ b/snapraid.d @@ -290,22 +290,22 @@ Getting Started :snapraid fix -m Recovering - The worst happened, and you lost a disk! + The worst happened, and you lost one or more disks! - 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. Then proceed with the following steps. STEP 1 -> Reconfigure - You need some space to recover, even better if you already have an additional - disk, but in case, also an external USB or remote disk is enough. + You need some space to recover, even better if you already have additional + spare disks, but in case, also an external USB or remote disk is enough. - 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: @@ -316,12 +316,20 @@ Getting Started :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. + STEP 2 -> Fix Run the fix command, storing the log in an external file with: :snapraid -d NAME -l fix.log fix 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. diff --git a/snapraid.txt b/snapraid.txt index 1d87377a..b5402067 100644 --- a/snapraid.txt +++ b/snapraid.txt @@ -311,22 +311,22 @@ Or to recover all the deleted files in all the drives with: 4.4 Recovering -------------- -The worst happened, and you lost a disk! +The worst happened, and you lost one or more disks! -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. Then proceed with the following steps. ---- 4.4.1 STEP 1 -> Reconfigure ---- -You need some space to recover, even better if you already have an additional -disk, but in case, also an external USB or remote disk is enough. +You need some space to recover, even better if you already have additional +spare disks, but in case, also an external USB or remote disk is enough. -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: @@ -337,12 +337,20 @@ 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. + ---- 4.4.2 STEP 2 -> Fix ---- Run the fix command, storing the log in an external file with: snapraid -d NAME -l fix.log fix 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.