Couple of you here already asked me to replace this drive, but I’m just letting it go “until death do us part” given pool reports always come back healthy… another Multi-zone error logged.
6 months operation, 30 or so spin ups. Still not a great deal of work for a HDD. Are you going to create a cron job, log all the smart parameters to a file and plot it’s demise after the fact?
buy a referb drive. better safe than sorry, unless it’s the 2nd part of a raid 1 array, then you could test is out a little longer to see whats actually wrong. either its a bad drive or a bad board.
@SgtAwesomesauce craziest thing ever - looked at the serial on the drive closest to the Plexi door… it’s the one with MultiZone Error rates.
Couple days ago it recorded 11… New HDD just arrived off Amazon. Now the question is whether I’d be able to do it without really having a backup anywhere else… eek!
Should I first setup a replication stack, replicate all existing data, THEN attempt resilvering the replaced drive? It’s only Raidz2.
It’ll still resilver a new drive fine, but good time to consider relplacing all the drives with larger ones, or to replicate to a different zpool of higher capacity.
Personally I’d keep the array, and just cycle larger drives (remember to set the auto-resize if it’s not already turned on in free as)
Yup, that is how cycling works, replace and resilver one drive at a time.
It’s slow (with 2-4TB drives) but works a charm. Over that, and not sure if the time will be worth it, or replicating better, but for now, that’s the easy, safe way
Thanks, and yeah, wouldn’t go near it myself…
I can’t find autoexpand=on in the Freenas GUI, I went to the shell, set the property, exported then imported =magic! But I only have version 9