I am just getting started with unRAID.  I have always used Windows Home Server and luckily got away without any failed drives on it. (knock...knock)

 

My issue is this.  I setup a machine with 2 drives and 1 parity to test.  I put data on and made sure that some was on both the data drives.  I then let the parity drive do its thing.  When trying to duplicate a drive failure by unplugging one of the drives and then put in a new one  realized all the drives that I had to put in were bigger than the parity drive.  So I then proceeded to get the array working back like normal and then upgrade the parity drive in the same way.  The issue is when I plugged in the new larger drive where the old parity drive was and then changed it from no device to the long drive name, it paused for a second and then went back to no device and there was no other drive option. I tried rebooting and everything and it would never come back, so then I plug the old parity drive back in and then it would see it and would rebuild the parity.

 

Am I doing something wrong?

 

I can try it again and pull a syslog but it was adding things so fast I couldnt see any errors.

 

Thanks for any help.

JK

I am just getting started with unRAID.  I have always used Windows Home Server and luckily got away without any failed drives on it. (knock...knock)

 

My issue is this.  I setup a machine with 2 drives and 1 parity to test.  I put data on and made sure that some was on both the data drives.  I then let the parity drive do its thing.  When trying to duplicate a drive failure by unplugging one of the drives and then put in a new one  realized all the drives that I had to put in were bigger than the parity drive.  So I then proceeded to get the array working back like normal and then upgrade the parity drive in the same way.  The issue is when I plugged in the new larger drive where the old parity drive was and then changed it from no device to the long drive name, it paused for a second and then went back to no device and there was no other drive option. I tried rebooting and everything and it would never come back, so then I plug the old parity drive back in and then it would see it and would rebuild the parity.

 

Am I doing something wrong?

 

I can try it again and pull a syslog but it was adding things so fast I couldnt see any errors.

 

Thanks for any help.

JK

 

I'm not an expert by any means but did you 'preclear' the new drive that you wanted to use as your parity? I'm pretty sure I read that you need to run 'preclear' first to zero the drive before adding it to your array.

 

I could be wrong but just a thought.

That could be it.  I will do some research on the preclear and try that tonight.

 

Thanks

JK

That could be it.  I will do some research on the preclear and try that tonight.

 

Thanks

JK

 

If you've never run preclear on your drives I would suggest running it on all of them. From what I've read its recommended to do it on all of the drives before adding it to the array.

 

Note: It did take approx 30 hours for my 3TB drives and just a little under for my 3TB drive. You can however run the preclear script on different drives at the same time to save some time.

While there does seem to be a bug in v5 that requires a pre-clear instead of letting v5 clear the drive to ADD a drive to the array;  it should NOT be necessary when replacing a drive -- whether parity or data -- as the drive will simply be rebuilt (no pre-clearing necessary by any means).

 

Any chance you're running v4.7 and tried to use a drive > 2TB for the new parity?

 

If that's not it, list the exact drive sizes you're currently using and what you had tried to use for the new parity drive.

 

Only data drives require clearing. Unraid will never clear the parity drive. Attach a syslog when the problem occurs,

These drive replacement/adding issues seem to be related to Simple Features in some other cases.

 

Any chance you're using Simple Features?