I removed one of the drives from the array, created new config and let it recreate parity. But it seems that it's using unassigned device (the one I removed) for some reason. You can see the reads amount on the screen, it's on par with the array disks and is growing with them. dstat and the GUI shows 0MB/s read and write on it though, so it might be a visual bug. But on the other hand, it won't let me spin-down this drive, logs will show:
QuoteOct 16 11:10:40 Tower emhttpd: spinning down /dev/sdc
Oct 16 11:10:40 Tower emhttpd: read SMART /dev/sdc
I don't know if it's just a visual bug or Unraid one and I'm screwing up my parity.
I first asked on UA's thread and got a response, so I'm writing here now:
-
1
Recommended Comments
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.