[SOLVED] Parity Failure - Read Errors


Recommended Posts

44 minutes ago, SidebandSamurai said:

new config, what would happen with my VMs and Dockers, plugins and how everything is setup?

The only thing New Config does is let you change drive assignments, and optionally (by default), rebuilds parity based on the new drive assignments.

Link to comment

Great, I have backed up my flash drive, I have created a text file with 

ls * -Ralh > /boot/disk2.txt

 

which created a disk2.txt which I also have on my local machine.  This is a listing of all the files on the drive before I pull it..  Wish I had CRCs of each file but I don't.  So I am not sure which files will be corrupted.  Wish me luck and see you on the other side.

 

Link to comment

Well this is what the otherside looks like 🙂  Everything is going smoothly so far.  What I did when I executed a new config I used the option to keep all drive assignments.  This helped grately in putting all the drives in there original slots except for Drive 2.   The Drive 2 slot is empty just like I want and when the new 10T drive comes in I will place it in there.

 

My thoughts for the failing Drive 2, I would use ddRescue to create a rescue image of the drive.  Then I could open the image and copy the files out of there, as I don't have another 3T drive I can use for this process.  I do have friends unraid server I am building for her that I could use for the recovery and place the image on the array.

 

Thoughts on this process?

Link to comment

I am updating this post to show the full process of recovering a drive.

I used my friends unraid server.  I installed NerdPack Gui from community apps, then I installed ddrescue.

 

I shut down the server and installed the defective drive2 for recovery.

 

Once the system was rebooted I started a Unraid terminal session and executed this command

 

root@Risa:/mnt/disk1# ddrescue -d /dev/sdf /mnt/disk1/recovery/disk2.img /mnt/disk1/recovery/disk2.log

 

This was my first pass,.  and resulted in this:

 

GNU ddrescue 1.23
Press Ctrl-C to interrupt
     ipos:    2931 GB, non-trimmed:        0 B,  current rate:       0 B/s
     opos:    2931 GB, non-scraped:        0 B,  average rate:    100 MB/s
non-tried:        0 B,  bad-sector:    32768 B,    error rate:     256 B/s
  rescued:    3000 GB,   bad areas:        4,        run time:  8h 16m 52s
pct rescued:   99.99%, read errors:       67,  remaining time:          0s
                              time since last successful read:      1m  4s
Finished                                      

 

Next I ran this command.

 

root@Risa:/mnt/disk1# ddrescue -d -r 3 /dev/sdf /mnt/disk1/recovery/disk2.img /mnt/disk1/recovery/disk2.log

 

You will notice teh -r 3 option.  this tells ddresuce to retry all bad areas 3 times.  Notice allso I am using the same log from the first time.  This log tells ddrescue where the bad sectors are and to retry them.

 

GNU ddrescue 1.23
Press Ctrl-C to interrupt
Initial status (read from mapfile)
rescued: 3000 GB, tried: 32768 B, bad-sector: 32768 B, bad areas: 4

Current status
     ipos:    2931 GB, non-trimmed:        0 B,  current rate:       0 B/s
     opos:    2931 GB, non-scraped:        0 B,  average rate:       7 B/s
non-tried:        0 B,  bad-sector:    28672 B,    error rate:     170 B/s
  rescued:    3000 GB,   bad areas:        5,        run time:      8m 41s
pct rescued:   99.99%, read errors:      171,  remaining time:         n/a
                              time since last successful read:      3m 56s
Finished                                   

 

If you will notice after the 2nd command, it only spent 8 minutes retrying bad sectors.  Since this did not recover any data, I will leave it as it is, mount the resulting image "disk2.img" and copy the data from that image to the new drive on my server once its in the array.

 

Thanks for all your help.

 

 

Edited by SidebandSamurai
Link to comment
  • SidebandSamurai changed the title to [SOLVED] Parity Failure - Read Errors

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.