victorhooi
Contributor
- Joined
- Mar 16, 2012
- Messages
- 184
Hi,
I have a FreeNAS 11.0 system with 4 x 8TB Seagate Archive drives in a RAID-Z1 configuration.
A few days ago, I got an alert in FreeNAS:
> Critical: <Datetime> - Device /dev/ad0, unable to open device.
> Critical: <Datetime> - The volume datastore state is DEGRADED: One or more devices has been removed by the administrator. Sufficient replicas exist for the pool to continue functioning in a degraded state.
I looked in the Disks view in the FreeNAS GUI to get the serial number of /dev/ada0. I then powered down the NAS, in order to look at the disk, and confirm which one it was.
I assumed at this time that the disk was kaput and needed to be replaced.
I powered back up the NAS - and then this time, the volume "datastore" seems to be ONLINE.
In alerts, I see:
> CRITICAL: June 29, 2017, 9:10 a.m. - The volume datastore state is ONLINE: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected.
I checked the output of zpool status:
Checking the physical devices to gptid:
It seems the disk with 2 in the CKHSUM column is indeed ada0.
What happened here?
My understanding is that resilvering is when ZFS uses the checksum from the other disks to rebuild the damaged data.
What are the suggested next steps?
Regards,
Victor
I have a FreeNAS 11.0 system with 4 x 8TB Seagate Archive drives in a RAID-Z1 configuration.
A few days ago, I got an alert in FreeNAS:
> Critical: <Datetime> - Device /dev/ad0, unable to open device.
> Critical: <Datetime> - The volume datastore state is DEGRADED: One or more devices has been removed by the administrator. Sufficient replicas exist for the pool to continue functioning in a degraded state.
I looked in the Disks view in the FreeNAS GUI to get the serial number of /dev/ada0. I then powered down the NAS, in order to look at the disk, and confirm which one it was.
I assumed at this time that the disk was kaput and needed to be replaced.
I powered back up the NAS - and then this time, the volume "datastore" seems to be ONLINE.
In alerts, I see:
> CRITICAL: June 29, 2017, 9:10 a.m. - The volume datastore state is ONLINE: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected.
I checked the output of zpool status:
Code:
% sudo zpool status datastore ... pool: datastore state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: http://illumos.org/msg/ZFS-8000-9P scan: resilvered 166M in 0h0m with 0 errors on Thu Jun 29 09:08:39 2017 config: NAME STATE READ WRITE CKSUM datastore ONLINE 0 0 0 raidz1-0 ONLINE 0 0 0 gptid/1b019b58-5db5-11e6-92fe-10604b92dc14 ONLINE 0 0 0 gptid/1bd01f4e-5db5-11e6-92fe-10604b92dc14 ONLINE 0 0 0 gptid/1b586c61-5db5-11e6-92fe-10604b92dc14 ONLINE 0 0 0 gptid/1c918aec-5db5-11e6-92fe-10604b92dc14 ONLINE 0 0 2 errors: No known data errors
Checking the physical devices to gptid:
Code:
% glabel status Name Status Components gptid/1c918aec-5db5-11e6-92fe-10604b92dc14 N/A ada0p2 gptid/1b586c61-5db5-11e6-92fe-10604b92dc14 N/A ada1p2 gptid/1bd01f4e-5db5-11e6-92fe-10604b92dc14 N/A ada2p2 gptid/1b019b58-5db5-11e6-92fe-10604b92dc14 N/A ada3p2 gptid/8134852c-59f1-11e7-9c60-000c29c82ac0 N/A da0p1
It seems the disk with 2 in the CKHSUM column is indeed ada0.
What happened here?
My understanding is that resilvering is when ZFS uses the checksum from the other disks to rebuild the damaged data.
What are the suggested next steps?
Regards,
Victor