Hope someone can guide me through this. I was in the process of upgrading two of my 3tb disks with 6tb when I ran into this. Here is what's happened so far:

 

1) Ran preclears on both of the new drives.

2) Ran parity check (no errors)

3) Pulled one 3tb drive and replaced with 6tb drive.

4) Started data rebuild.

 

Then when the rebuild was 70% through, I got 33,000,000+ errors on a different 3tb drive. I thought I could just stop the array, put the original 3tb drive back in place and then replace the failed drive instead, but after pulling up the array it didn't give me that option. What would be the recommended process from here?

Post a screenshot and syslog.

I already shut the system down, but here's a screenshot I took before. I can run SMART reports on the drive, but I was hoping there was a way to just go ahead and replace it since I was replacing one anyway. Since I still have the other 3tb drive that I was in the process of replacing, is there anyway to put that one back in without having to rebuild the data? I did move one 3gb file over during the data rebuild that went awry, but still have that on my pc if it were needed again.

 

http://imgur.com/sTnkLEv

I checked all the connections this morning and gave it another shot and got the same errors. Syslog is here:

https://www.dropbox.com/s/86ajz613ip28rpd/Tower_Syslog.html?dl=0

 

SMART report attached

smart13.txt

Disk13 has 3 pending sectors so normally rebuilding it would be the way to go if you hadn't already invalidated the disk12 slot.

 

The only way to get unRAID to use the original disk12 is New Config, reassign all your drives, and rebuild parity. The parity rebuild might go just as badly as the previous data rebuild did though with more read errors on disk13.

 

Might be a good idea to get smart on all the other drives to see if there are any other potential problems waiting to happen.

 

Do you have backups of anything you consider irreplaceable?

It's a media server, so nothing irreplaceable; just time to determine the affected media, rip, and transfer back over. What would be the recommended steps from here?

I haven't seen v5 in quite a while. Is New Config in the Utils page? Use the screenshot you already posted to keep track of what drive belongs in each slot. Put the original disk12 in its slot. New Config will make you reassign all your drives. Make very sure you don't put a data drive in the parity slot. When you start the array it will rebuild parity. If that works then you can replace disk13 and rebuild it onto a new drive.

Yes, newconfig is there. Will give that a shot and report back. If I get more errors out of 13, should I just let it keep going?

Yes, newconfig is there. Will give that a shot and report back. If I get more errors out of 13, should I just let it keep going?

Yes. Since rebuilding parity only writes the parity drive and only reads the data drives, even if there are problems with the parity build the data will not be any worse than it is now. Then you can rebuild disk13 onto a new drive and keep the original disk13 in reserve in case there are any problems from that rebuild.

ok, I started the parity rebuild last night, but not sure if it worked. I was expecting that to take about 2 days as it has in the past with parity checks on a 6tb drive. When I checked this morning, Disk 13 is red balled, and the parity drive is flashing orange. Syslog and screenshot below.

 

https://www.dropbox.com/s/gczhuqjsq2ogy7w/Tower_Syslog%202.htm?dl=0

 

https://www.dropbox.com/s/rvwjk9jl235n9jv/unraid.jpg?dl=0

Parity sync did not complete. Possibly some of disk13 can still be read.

 

You might try a new config with just disk13 and see if you can copy stuff from it to your PC. Then when you have saved as much as you can, you can new config with all your other disks and a new, empty disk13 and copy stuff back.

 

Or just new config with a new, empty disk13, then put the old disk13 in another computer and see if you can read it there. Don't know what other computers you might have available. I know there are some utilities available to let you read Linux filesystems on Windows, for example.

 

The new disk you tried to rebuild disk12 to should be precleared again if you want to use it as a new disk in the disk13 slot. Then unRAID will let you format it. If you try to use it in a new config without preclearing it unRAID might think it has valid data and not offer to format it.

Thanks for the help and suggestions. I've pulled data off of my unraid drives before on a windows machine, so I'll probably just go that route.

 

So for clarity, I should do the following:

 

Pull disk 13 and pull files to separate PC

 

Replace disk 13 with a new drive (the 6tb one I already have precleared, but didn't attempt to use yet)

 

Leave Disk 12 with the original 3tb drive (data in tact from before attempted disk upgrade)

 

Run newconfig

 

Preclear the second 6tb drive again (that was attempted to use in disk 12 for upgrade)

 

Upgrade Disk 12 with 6tb drive

 

Does that seem like a complete step by step guide?

 

I'll also run smart reports on all the drives before further attempts.

Well each of those steps imply a few steps of their own, but sounds like you've done those before.

 

After you get everything working again you might consider upgrading to v6. One of the great new features is it will check your disks SMART attributes and send you an email if any of them start to look like a problem.

Yes, I've had to do a few of those steps before; just not often enough to have the process down without having to read and research first.

 

I was already looking at v6 once everything is up and running. I wasn't even aware that version 6 was out until I came here to look for help on this problem.

 

Thanks for the help, and hopefully that will be it for the time being.