Originally my system consisted of a 3TB parity drive and 4 2TB  data drives running on UNRAID 5.0.4.  I was upgrading the parity drive with a 5TB with the plans of adding the old parity drive in as a new data drive.  In the middle of the parity sync after putting in the 5TB drive data disk 4 started giving read errors.  Now it is showing the red ball in front of it and if the array starts it says it is unformatted.  The new parity drive never completed the parity sync, I still have the old parity drive from approx 30 hrs ago and I now a few file changes have been made in that time, but I am willing to loose those if need be.  I need help on what I need to do.

                                                                        Thanks

You have posted this in V6 support. Are you still on V5 as you said?

 

Post a syslog and smart attributes for disk4

Sorry, didn't notice this was for version 6, yes I am still on version 5.  Here is my syslog and smart report.  The syslog just keeps repeating the last section over and over again (where it gets the disk inventory, etc., in fact it is still repeating right now).  I had to delete some of it off of the file I attached because it was too large, so sorry if it is cut off in a weird spot.  Thanks again.

smart.txt

syslog1.txt

For future reference, your syslog zips to only 17k. Text compresses very well.

 

You say you know some data was written since your old parity drive was in the system. Do you know whether or not all of the writes were to disk4?

I am not sure if any or all of the data would have been written to drive 4, or how to check with the array not started.  It would be data that I could live with out if I had to.  (would rather not but not the end of the world).

I am adding a screen shot of my array config page.  I don't like that it says configuration valid even with the red by drive 4, if i choose no device for drive 4 it still says config valid? 

Nothing obvious in smart. Probably bumped a cable when replacing parity.

 

Too bad we don't have the syslog from the parity build when the problem occurred. It's not clear whether we should try to proceed with the old parity or the new. How do you know the parity build did not complete?

it was only about 50% of the way done, drive 4 started kicking read errors, I left it alone for awhile but it kept doing it, so I canceled the parity sync, shut it down thinking the same thing, bad cable or so, I would fix that and start the sync again.  I have tried different cables, 2 different controller cards, but still get the same result from drive 4, red icon, I have not even got so far as to be able to do a parity sync again.  I re posted this in the UNRAID 5 forum also, hope that doesn't cause too much headache.

I have a new 3tb drive on its way, need input on what to do next.

Let's continue this on your V5 thread.

That would be great!

Not trying to be unkind to OP, but wanted to make two points related to this issue that he and others might find helpful in the future:

 

1 - Removable drive cages (e.g., 5in3s) are very valuable as they allow swapping disks without disturbing the cabling. What happens when you disturb cabling - THIS! It might seem like a luxury item, but pay for themselves in reduced time, aggravation, and stress!

 

2 - In my sig there is s best practice post on replacing parity. Had OP followed it, life would be a bit easier recovering from the red ball during parity build.