Simon Tiplady
Dabbler
- Joined
- Jun 19, 2015
- Messages
- 20
While I was away I received an automated email from my FreeNAS server that it was resilvering a drive.
I hadn't seen or noticed any issues prior to this, but being away meant I didn't have a great deal of access and sort of forgot about it. Until I was working remotely today and realised I couldn't SSH into it.
I've taken a look tonight and couldn't access even over the local network, web GUI wasn't accessible either, and as I started to use a keyboard direct to the server, switched tty with ALT+F2 and typed "root" it then froze and nothing was responsive. Only option appeared to be to use the restart button on the case.
Ok, so it only appears to be 30.7M that required resilvering, but how can I find out what caused the resilver and if I should be ordering some spare harddrives ready to replace...
From the Reporting page of the Web GUI it looks like the stats stopped recording at around 4:35am on Sun Jan 29, this is before the resilver appeared to have finished. stats are not stored to the z2 storage.
Code:
The volume z2 (ZFS) state is ONLINE: One or more devices is currently being resilvered. The pool will continue to function, possibly in a degraded state.
I hadn't seen or noticed any issues prior to this, but being away meant I didn't have a great deal of access and sort of forgot about it. Until I was working remotely today and realised I couldn't SSH into it.
I've taken a look tonight and couldn't access even over the local network, web GUI wasn't accessible either, and as I started to use a keyboard direct to the server, switched tty with ALT+F2 and typed "root" it then froze and nothing was responsive. Only option appeared to be to use the restart button on the case.
zpool status
is showing:Code:
# zpool status z2 pool: z2 state: ONLINE scan: resilvered 30.7M in 0h24m with 0 errors on Sun Jan 29 05:04:48 2017 config: NAME STATE READ WRITE CKSUM z2 ONLINE 0 0 0 raidz2-0 ONLINE 0 0 0 gptid/bbfac008-1e39-11e5-bcb6-74d435beb194 ONLINE 0 0 0 gptid/bc6092b0-1e39-11e5-bcb6-74d435beb194 ONLINE 0 0 0 gptid/bcc6dad2-1e39-11e5-bcb6-74d435beb194 ONLINE 0 0 0 gptid/bd254b2e-1e39-11e5-bcb6-74d435beb194 ONLINE 0 0 0 errors: No known data errors
Ok, so it only appears to be 30.7M that required resilvering, but how can I find out what caused the resilver and if I should be ordering some spare harddrives ready to replace...
From the Reporting page of the Web GUI it looks like the stats stopped recording at around 4:35am on Sun Jan 29, this is before the resilver appeared to have finished. stats are not stored to the z2 storage.
Last edited by a moderator: