As I got a little too hasty in my proactive drive replacement, I forgot to offline the disk before replacing it. I then went into the GUI and did a replace drive, thinking it would see my new drive and add it in. I figured the only downside of not offlining first was that the relic object would still remain.
After a resliver, it still showed as unavailable.
I tried shutting down and just unplugging the new drive and booting which is now reslivering again. ONce that is complete, my hope is that plugging that disk back in will bring it up again.
First, well aware I should have taken a closer gander at the now integrated guide. RTFM, my bad...
Question, if this doesn't work as slick as I'm thinking, is there a way to completely remove the new disk object from the system so when I plug it back in, it reads it as a new disk and I can resliver and go on my merry way? I had done a manual disk replacement in the past that went pretty smooth but can't seem to dig up the steps.
Any help would be appreciated. Thanks.
~# zpool status
pool: Data1
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 Fri Feb 26 07:10:05 2016
34.0G scanned out of 5.89T at 99.6M/s, 17h7m to go
9.54M resilvered, 0.56% done
config:
NAME STATE READ WRITE CKS UM
Data1 DEGRADED 0 0 0
raidz1-0 DEGRADED 0 0 0
gptid/eeed3795-f81f-11e3-8136-6805ca15ac37 ONLINE 0 0 0
13462077411673510043 UNAVAIL 0 0 0 was /dev/gptid/b670664f-dc20-11e5-b085-0cc47a7d8aa1
gptid/157c258a-4347-11e2-9232-001a4d5f84aa ONLINE 0 0 0
gptid/948c811d-ff03-11e2-9cb6-6805ca15ac37 ONLINE 0 0 0
errors: No known data errors
pool: freenas-boot
state: ONLINE
scan: none requested
config:
NAME STATE READ WRITE CKSUM
freenas-boot ONLINE 0 0 0
gptid/f7878b12-ca21-11e5-b5d0-0cc47a7d8aa1 ONLINE 0 0 0
errors: No known data errors
camcontrol devlist
<ST2000DM001-1CH164 CC24> at scbus1 target 0 lun 0 (ada0,pass0)
<Hitachi HDS723020BLA642 MN6OA800> at scbus2 target 0 lun 0 (ada1,pass1)
<WDC WD20EFRX-68EUZN0 80.00A80> at scbus3 target 0 lun 0 (ada2,pass2)
<SanDisk SDSSDA120G Z22000RL> at scbus6 target 0 lun 0 (ada3,pass3)
>>I'd expect this as ada3 was the disk I unplugged.
gpart show
=> 34 3907029101 ada0 GPT (1.8T)
34 94 - free - (47k)
128 4194304 1 freebsd-swap (2.0G)
4194432 3902834696 2 freebsd-zfs (1.8T)
3907029128 7 - free - (3.5k)
=> 34 3907029101 ada1 GPT (1.8T)
34 94 - free - (47k)
128 4194304 1 freebsd-swap (2.0G)
4194432 3902834703 2 freebsd-zfs (1.8T)
=> 34 3907029101 ada2 GPT (1.8T)
34 94 - free - (47k)
128 4194304 1 freebsd-swap (2.0G)
4194432 3902834696 2 freebsd-zfs (1.8T)
3907029128 7 - free - (3.5k)
=> 34 234441581 ada3 GPT (111G)
34 1024 1 bios-boot (512k)
1058 6 - free - (3.0k)
1064 234440544 2 freebsd-zfs (111G)
234441608 7 - free - (3.5k)
>Again, what I'd expect to see.
After a resliver, it still showed as unavailable.
I tried shutting down and just unplugging the new drive and booting which is now reslivering again. ONce that is complete, my hope is that plugging that disk back in will bring it up again.
First, well aware I should have taken a closer gander at the now integrated guide. RTFM, my bad...
Question, if this doesn't work as slick as I'm thinking, is there a way to completely remove the new disk object from the system so when I plug it back in, it reads it as a new disk and I can resliver and go on my merry way? I had done a manual disk replacement in the past that went pretty smooth but can't seem to dig up the steps.
Any help would be appreciated. Thanks.
~# zpool status
pool: Data1
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 Fri Feb 26 07:10:05 2016
34.0G scanned out of 5.89T at 99.6M/s, 17h7m to go
9.54M resilvered, 0.56% done
config:
NAME STATE READ WRITE CKS UM
Data1 DEGRADED 0 0 0
raidz1-0 DEGRADED 0 0 0
gptid/eeed3795-f81f-11e3-8136-6805ca15ac37 ONLINE 0 0 0
13462077411673510043 UNAVAIL 0 0 0 was /dev/gptid/b670664f-dc20-11e5-b085-0cc47a7d8aa1
gptid/157c258a-4347-11e2-9232-001a4d5f84aa ONLINE 0 0 0
gptid/948c811d-ff03-11e2-9cb6-6805ca15ac37 ONLINE 0 0 0
errors: No known data errors
pool: freenas-boot
state: ONLINE
scan: none requested
config:
NAME STATE READ WRITE CKSUM
freenas-boot ONLINE 0 0 0
gptid/f7878b12-ca21-11e5-b5d0-0cc47a7d8aa1 ONLINE 0 0 0
errors: No known data errors
camcontrol devlist
<ST2000DM001-1CH164 CC24> at scbus1 target 0 lun 0 (ada0,pass0)
<Hitachi HDS723020BLA642 MN6OA800> at scbus2 target 0 lun 0 (ada1,pass1)
<WDC WD20EFRX-68EUZN0 80.00A80> at scbus3 target 0 lun 0 (ada2,pass2)
<SanDisk SDSSDA120G Z22000RL> at scbus6 target 0 lun 0 (ada3,pass3)
>>I'd expect this as ada3 was the disk I unplugged.
gpart show
=> 34 3907029101 ada0 GPT (1.8T)
34 94 - free - (47k)
128 4194304 1 freebsd-swap (2.0G)
4194432 3902834696 2 freebsd-zfs (1.8T)
3907029128 7 - free - (3.5k)
=> 34 3907029101 ada1 GPT (1.8T)
34 94 - free - (47k)
128 4194304 1 freebsd-swap (2.0G)
4194432 3902834703 2 freebsd-zfs (1.8T)
=> 34 3907029101 ada2 GPT (1.8T)
34 94 - free - (47k)
128 4194304 1 freebsd-swap (2.0G)
4194432 3902834696 2 freebsd-zfs (1.8T)
3907029128 7 - free - (3.5k)
=> 34 234441581 ada3 GPT (111G)
34 1024 1 bios-boot (512k)
1058 6 - free - (3.0k)
1064 234440544 2 freebsd-zfs (111G)
234441608 7 - free - (3.5k)
>Again, what I'd expect to see.