Also, can you ZPOOL attach a new drive to an existing raidz member, or is that for mirrors only?
Otherwise might one attach a new drive, then remove the old later on? Like a slower/ 2 step, manual replace?
For mirroring only
shame oh well
My understanding is that they’re working on RAIDZ expansion, but that’s a long way out and it’s likely to be a different vdev type entirely.
At least, that’s what I’m remembering.
1 Like
Oh I think I may have misread you before. You can attach to a raidz member and it will mirror it.
Raidz expansion though is kind of stalled. It needs people to test and review the current WIP code and provide feedback. I have that on my list of things to do and just started looking at it again yesterday.
Pssst
I suspect it boots only on oldddd agesa since all my systems are newer agesa
1 Like
More like there is a roughed out a PoC but nobody is actively working on it atm. Actually I’m in the process of rebasing the PR on the current master to see how much damage was done by the restructuring that’s been going on as of late. But basically the PR needs design review and testing and then finishing
1 Like
Ah, that makes sense. thanks for the update!
2 Likes
Heads up, I’ve modified the above script to burn-in my 10TB drives. As per @SgtAwesomesauce I’ve added a run of dd to zero out the disks before running badblocks.
5 Likes
Having spent 1 week burning in just 4x 10TB drives, today I wanted to start the resilvering process. Booted my FreeNAS box that has been off for a while, boom - 2x HDDs are dead 
Hobbling on 6x drives, all my parity drives are gone. Wish me luck. Backups? What backups… 
pool: big
state: DEGRADED
status: One or more devices is currently being resilvered. The pool will
continue to function, possibly in a degraded state.
action: Wait for the resilver to complete.
scan: resilver in progress since Thu Nov 7 19:01:24 2019
2.17T scanned at 1.51G/s, 61.9G issued at 157M/s, 23.0T total
7.48G resilvered, 0.26% done, 1 days 18:35:07 to go
config:
NAME STATE READ WRITE CKSUM
big DEGRADED 0 0 0
raidz2-0 DEGRADED 0 0 0
gptid/294440f5-7426-11e7-9d9c-2c4d54456e1f.eli ONLINE 0 0 0
gptid/2a0d7ca7-7426-11e7-9d9c-2c4d54456e1f.eli ONLINE 0 0 0
gptid/d3f98b7d-0162-11ea-864f-b4969130e724.eli ONLINE 0 0 0 (resilvering)
gptid/2ba2a597-7426-11e7-9d9c-2c4d54456e1f.eli ONLINE 0 0 0
gptid/2c63c532-7426-11e7-9d9c-2c4d54456e1f.eli ONLINE 0 0 0
15947505727906227010 UNAVAIL 0 0 0 was /dev/gptid/2d2af08b-7426-11e7-9d9c-2c4d54456e1f.eli
gptid/2ded0a48-7426-11e7-9d9c-2c4d54456e1f.eli ONLINE 0 0 0
gptid/2eb4f9d6-7426-11e7-9d9c-2c4d54456e1f.eli ONLINE 0 0 0
errors: No known data errors
1 Like
Oooof. Good luck.
1 Like
It’s pretty dead, wow…
pool: big
state: DEGRADED
status: One or more devices is currently being resilvered. The pool will
continue to function, possibly in a degraded state.
action: Wait for the resilver to complete.
scan: resilver in progress since Thu Nov 7 19:01:24 2019
2.46T scanned at 418M/s, 443G issued at 73.6M/s, 23.0T total
44.0G resilvered, 1.88% done, 3 days 17:19:43 to go
config:
NAME STATE READ WRITE CKSUM
big DEGRADED 0 0 964K
raidz2-0 DEGRADED 0 0 2.45M
gptid/294440f5-7426-11e7-9d9c-2c4d54456e1f.eli DEGRADED 0 0 0 too many errors (resilvering)
gptid/2a0d7ca7-7426-11e7-9d9c-2c4d54456e1f.eli DEGRADED 0 0 0 too many errors (resilvering)
gptid/d3f98b7d-0162-11ea-864f-b4969130e724.eli ONLINE 0 0 0 (resilvering)
gptid/2ba2a597-7426-11e7-9d9c-2c4d54456e1f.eli FAULTED 2 78 0 too many errors
gptid/2c63c532-7426-11e7-9d9c-2c4d54456e1f.eli DEGRADED 0 0 0 too many errors (resilvering)
15947505727906227010 UNAVAIL 0 0 0 was /dev/gptid/2d2af08b-7426-11e7-9d9c-2c4d54456e1f.eli
gptid/2ded0a48-7426-11e7-9d9c-2c4d54456e1f.eli DEGRADED 0 0 0 too many errors (resilvering)
gptid/2eb4f9d6-7426-11e7-9d9c-2c4d54456e1f.eli DEGRADED 0 0 0 too many errors (resilvering)
errors: 525903 data errors, use '-v' for a list
So, thankfully I have a Synology that did rsync backups of my critical stuff. Apart from that, this pool is pretty much dead.
I wonder if this is due to a backplane failure?
@noenken @SgtAwesomesauce what are my options now? Pull out all the old drives, start fresh with my 8x10TBs?
If you suspect a backplane, you should investigate that before anything else.
It heavily depends on your sensitivity to uptime and the value of the data.
Since it’s a Z2, you’ve got all your data there. You could pop in 2x10tb and replace the failed with those two.
You could also just give up on the pool and go for a new pool. Depends if you want to save the data or not.
What size are the original drives?
So yeah, earlier the pool booted up with 6x drives (originally Raidz2 and 8 drives), and I tried to resilver 2x10TB. However, it started showing all the drives as degraded and another as FAULTED. So 6 drives - the FAULTED = 5 drives, the pool is crippled right?
Oh, sorry, I missed that. Yeah, pool’s hosed.
If you wanted to do that, you should have just ran the 10TB disks in addition to the original disks.
1 Like
Hilariously enough, my Synology 8x 4TB is doing a RAID rebuild on one drive… wow!! It’s a Warranty replacement, fingers crossed.
Wow, that’s not hilarious, that’s scary.
Nuke the old pool, pop in your new disks, build the array and get that data on the new disks.
To me, it sounds like you’re time sensitive.
Also, I recommend making backups to B2 if you’ve got the cash/bandwidth to handle it. That sounds like a shortcoming of your setup: backups.
2 Likes