Jump to content
unravelit

Parity drive died during a data drive replacement[SOLVED]

29 posts in this topic Last Reply

Recommended Posts

Hey all,

 

A minor issue, but one that has caused me to haul on the brakes until I get advice!

 

I pulled a 2tb data drive (after removing it from the array) and replaced it with an 8tb unit. Unfortunately on power up, my older seagate 8tb drive which is the parity drive was doing the good old spin up and down routine, and took forever to come up. It does come up then throws read errors and goes offline. SMART stupidly considers the drive healthy, but it obviously is sick.

 

I am so far not too concerned, as I think I can just "go back" to having the original 2tb drive back in, and replace the parity drive with my new 8tb drive.

 

But, I also think I need to convince unraid that the 2tb drive belongs in the array so it doesn't try to virtualize it with a dead parity drive?! After removing the 2tb drive from the array, it has been untouched.

 

I'm running the latest stable release (checked for updates prior to this excitement and I was already up to date)/

 

What do I need to do to achieve this? Any advice is greatly appreciated.

Edited by unravelit
Solved!

Share this post


Link to post
2 hours ago, unravelit said:

I pulled a 2tb data drive (after removing it from the array)

Just to make sure there is no misunderstanding, what exactly do you mean by "removing it from the array"?

Share this post


Link to post

Also, go to Tools-Diagnostics and attach the complete Diagnostics zip file to your NEXT post. 

Share this post


Link to post
15 minutes ago, trurl said:

Just to make sure there is no misunderstanding, what exactly do you mean by "removing it from the array"?

got it - I was following the usual steps for replacing a drive - I did this:

Stop the array

Unassign the old drive if still assigned (to unassign, set it to No Device)

 

then did a clean shutdown.

 

Diag zip added. It took a while to boot, and the parity drive is now not even showing up. Looks like it went from sick to dead...

 

 

stuff2-diagnostics-20191108-1140.zip

Share this post


Link to post

Haven't looked at the diagnostics yet.

49 minutes ago, unravelit said:

Stop the array

Unassign the old drive if still assigned (to unassign, set it to No Device)

OK. That isn't the way I would normally use the term "remove" when speaking about the array. If I said I removed a drive, I would mean I had shrunk the array by New Config without the drive and rebuilt parity.

 

Until there is an actual change in disk assignments the drive hasn't been removed in any sense. It is not strictly necessary to unassign the old drive. Simply assigning the replacement to the same slot and starting the array will begin the rebuild.

 

If you have not yet assigned the replacement, then as far as Unraid is concerned, you can simply assign the old drive back to the same slot and start the array.

 

 

Share this post


Link to post

After looking at your diagnostics, it seems you have already assigned the new disk to slot2. Have you actually started the array?

Share this post


Link to post

I think you should be able to simply assign the original drive to slot2, and the new disk to parity, and then start the array to begin rebuilding parity. If it complains about that then maybe you would have to New Config to get the assignments like you want. But it shouldn't matter since the end result will be to rebuild parity, which is what you want anyway. It is only if you were trying to get it to rebuild a data disk that you would have to do something more complicated.

Share this post


Link to post

Apologies, I meant to say this in my first post but got distracted.... Originally I had no idea the parity drive was sick, so had assigned the new disk to slot 2 and started the array.

 

It all looked right and was working, but I noted the rebuild was going to take 200+ days, the write speed was only around 400kb/sec. That is when I found the parity drive was dying - constantly spinning down and restarting.

 

I stopped the rebuild.

 

Now I am tempted to put back the original drive in slot 2, but I am thinking that unraid won't know what to do with it.

 

Cheers

Share this post


Link to post

Parity is not showing up in Diagnostics so I don't know for sure if it is bad or not, but it doesn't really matter. What I would really want to see is SMART for the original disk2. Can you plug it back in and post new diagnostics?

Share this post


Link to post
1 minute ago, unravelit said:

Original drive back in slot 2

I assume you mean WD-WCAZA0850387. It is not actually assigned to any slot. That disk looks OK. I guess you were only replacing it in order to upsize?

 

Is your original parity ZA1AGKMJ? I see it briefly in syslog but it can't really communicate and there is no SMART for it. Could just be a bad connection.

 

Post a screenshot of Main - Array Devices just to make sure I fully understand what you have now.

Share this post


Link to post

If we could get SMART for parity and it turned out to be OK then you could just proceed with your original plan. Check all connections, SATA and power, both ends. Make sure to check any power splitters along the way. Then post another diagnostic.

 

If there really was a problem with parity, Unraid may have been able to tell you this before you tried to replace the other disk. Did you check the Dashboard for any SMART warnings?

 

Do you have Notifications configured to alert you immediately by email or other agent when Unraid detects a problem?

Share this post


Link to post

Yep, was upsizing from 2tb to 8tb.

 

ZA1AGKMJ is the original parity. Even the BIOS is saying it can't find this disk at the moment.

Cheers

 

Screenshot 2019-11-09 00.29.37.png

Share this post


Link to post
3 minutes ago, trurl said:

If we could get SMART for parity and it turned out to be OK then you could just proceed with your original plan. Check all connections, SATA and power, both ends. Make sure to check any power splitters along the way. Then post another diagnostic.

 

If there really was a problem with parity, Unraid may have been able to tell you this before you tried to replace the other disk. Did you check the Dashboard for any SMART warnings?

 

Do you have Notifications configured to alert you immediately by email or other agent when Unraid detects a problem?

I have checked and rechecked the parity drive connections.  I will do it one more time :D

 

I have email notifications set up for immediate alert - the parity drive gave me an overtemp warning (it got up to 46 degrees) today, and does on occasion when the weather is hot and no air con on. No other issues reported. I had received a normal temp alert before doing the changes.

 

Prior to the change over work, all drives were "thumbs up" for SMART.

 

I would try it in an external bay to try and pull smart but the one I have only supports 2tb max.

Share this post


Link to post

OK, let's proceed without the original parity and maybe later you can see if it can be made to work. Maybe it really did just decide to die at this inopportune moment.

 

Go to Tools - New Config, assign the original disk2 to slot2, and the new disk to parity. Starting the array will begin parity rebuild. If it offers to format anything, DON'T.

 

Share this post


Link to post

OK, so I pulled the little proliant out and unplugged and REALLY plugged everything back in - it is an annoyingly tight case. Aaaaand.... the parity drive is back - well, at least it is visible but not assigned. And not misbehaving right now (the spin up/down business) - so I grabbed a diag

 

 

My face is red, as you can't see it. I was sure everything was fine, and have "checked" everything several times. Just ... not well.

 

stuff2-diagnostics-20191108-1353.zip

Share this post


Link to post

OK, original parity SMART looks OK. Forget about New Config for now.

 

Can you assign that original parity to parity slot, and assign nothing to slot2? If it offers to rebuild parity, don't start the array. If it doesn't want to rebuild parity, start the array and see if you can see the "emulated" disk2 files. The emulated disk is exactly what will be rebuilt when you assign the new disk to slot2.

 

Share this post


Link to post

Might be best to post another screenshot before starting the array. In any case, shouldn't be anything to worry about since you still have the original disk2. Just don't format anything.

Share this post


Link to post

I tried that, and the parity drive shows up as a blue dot drive "NEW DEVICE"

 

I don't get an option to start the array at all with just the parity drive added as it says

 

"Too many wrong and/or missing disks!"

 

So it sees the parity drive, but doesn't seem to know it is meant to be the parity drive...

Screenshot 2019-11-09 01.38.15.png

Share this post


Link to post

The simplest way forward will probably be to New Config with all the original disks back where they were. Then maybe a non-correcting parity check before trying it with the new disk assigned to slot2.

Share this post


Link to post

OK. All drives are currently in their proper places.

 

I have never done a new config before, and not too sure what it involves (or how I can muck it up!)

Share this post


Link to post

The only thing New Config does is let you assign the disks however you want, and then optionally (by default) rebuild parity. Check the box saying parity is already valid, then you can run a non-correcting parity check to make sure everything is as expected.

 

You can't really muck it up unless you assign a data disk to the parity slot, or agree to format any disk that has data on it.

Share this post


Link to post

Thanks again for your help so far. All the drives came back looking right... and a non-write parity check is under way (and will take the normal ~19 hrs).

 

All my disks are badly over filled, I know you are not meant to go over ~90 percent, but times are desperate, hence the 8tb upgrade :D

 

Awesome help!1675876365_Screenshot2019-11-0902_25_59.thumb.png.96705b14823bf8fd2adc51b7bef8e6c0.png

Share this post


Link to post
11 minutes ago, unravelit said:

and a non-write parity check is under way

You might as well cancel and start a correcting check, since there are already a few errors, and they are expected after what happened.

Share this post


Link to post
21 minutes ago, johnnie.black said:

You might as well cancel and start a correcting check, since there are already a few errors, and they are expected after what happened.

yes

Share this post


Link to post

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.