Kinda: in a MIRRORED VDEV you can always add or remove drives[1], thus increasing or lowering the parity of the VDEV; the only way of increasing a MIRROR VDEV available space is by replacing all the drives of that VDEV with larger ones.
Glad to give back what this community gave (and still gives) me!
You cannot remove the last drive of a VDEV if there is not enough free space in the other VDEVs to host the “wannabe removed” VDEV’s data. ↩︎
So, you recommend running Short test on a daily basis? Is there any way to get these reports over email? That would be quite easy instead of logging in daily.
It seems like @joeschmuck Multi Report has that feature.
@Davvo Unlike the burn in test for the HDDs and SSDs, is there any way to test the network components? Such as NICs and the modules.
Also, I think I’ll start the burn in test tomorrow for the HDD. Do you have any recommendations for the tool? I can use Windows or Linux. I’m aware of SeaTools, HD Tune Pro, HD Sentinel. If there’s any industry standard software or tool you guys use to burn in tests, please let me know.
There’s no real burn-in for SSDs because you don’t want to mess with their write cycles. You might use read-only tests such as solnet-array if you want to.
Anything that puts the drives to continuous use… If there’s a flaky cable/connector, inssuficient cooling, or anything else that could cause issues, using the system long enough will trigger an error.
Really, stop worrying and start doing.
