Hi there,

 

As per the title I have an old 3TB drive in my array that appears to have kicked the bucket. UnRaid has disabled the drive and I am unable to access any SMART data/reports when I click into the drive settings. No bother as I am happy to replace it.

 

Currently here in Australia I can get a 12TB external drive for shucking at the best $ per TB, but both of my parity drives are only 10TB. This is the first time I have had a drive fail, so would like to make sure I go about this process correctly.

 

My questions are:

- Should I replace a 10TB Parity drive first with the new 12TB drive so that I can then replace the disabled 3TB drive with that former 10TB parity drive?

- Would I need to pre-clear the 10TB drive that was previoulsy setup as a parity before adding it into the array?

- Can I have 1x 12TB drive and 1x 10TB drive work side by side as my 2x Parity Drive setup? Or will I need to get 2x12TB drives to change over both current parity drives? (All array drives are 10TB or less)

 

Thanks!

 

 

 

Edited April 26, 20233 yr by nametaken_thisonetoo
Clarity

31 minutes ago, nametaken_thisonetoo said:

Should I replace a 10TB Parity drive first with the new 12TB drive so that I can then replace the disabled 3TB drive with that former 10TB parity drive?

YES

31 minutes ago, nametaken_thisonetoo said:

Would I need to pre-clear the 10TB drive that was previoulsy setup as a parity before adding it into the array?

NO

32 minutes ago, nametaken_thisonetoo said:

Can I have 1x 12TB drive and 1x 10TB drive work side by side as my 2x Parity Drive setup?

YES

 

28 minutes ago, trurl said:

YES

NO

YES

 

Thanks!

I've also noticed that the disabled drive is now also listed as an Unassigned Device (still disabled). Is this normal, and is it worth trying to mount it that way?

attach diagnostics to your NEXT post in this thread

8 hours ago, trurl said:

attach diagnostics to your NEXT post in this thread

No probs, thanks again.

themagiceye-diagnostics-20230427-0744.zip

23 hours ago, nametaken_thisonetoo said:

the disabled drive is now also listed as an Unassigned Device

This often happens. It disconnected as sde and reconnected as sdm, then it became disabled when a write to sde failed.

 

Emulated disk3 is mounted, its files can be accessed, and the emulated contents are what will be rebuilt.

 

Looks like it was a bad connection rather than a bad disk. SMART for that disk looks OK, though it hasn't had an extended self-test run on it. You could rebuild to that same disk, but you do need to increase capacity, so replacing it with a larger disk is a good plan.

 

Many of your disks are too full, so after you increase capacity you might consider redistributing some of that with unBALANCE or Dynamix File Manager plugins.