Repeated ZFS Corruption

lusken

Cadet
Joined
Apr 19, 2021
Messages
1
Pool Pool1 state is ONLINE: One or more devices has experienced an error resulting in data corruption. Applications may be affected.

I have an HP Z220 Workstation that I have re-purposed into my first FreeNAS server. When building I repurposed some Seagate ST4000VN0001-1SF1 4TB drives that were previously used in a QNAP server, but were replaced to increase storage. These drives were all working with 0 issues in the QNAP. Using 3 of the drives I configured Pool1 in RaidZ1

I started using the Freenas Server to store some Veem Backups, when I noticed that Pool1 keeps showing data corruption. This will be the third time now, that I have rebuild the zpool to clear the corruption. It will be good for about 2 weeks and then start to show corruption again. I have run the S.M.A.R.T test on each drive and scrubbed weekly, everything shows that there is no issue with the drives themselves.

I'm looking for suggestions where I should look next.

root@CTFNAS1[~]# zpool status
pool: Pool1
state: ONLINE
status: One or more devices has experienced an error resulting in data
corruption. Applications may be affected.
action: Restore the file in question if possible. Otherwise restore the
entire pool from backup.
see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-8A
scan: scrub repaired 640K in 02:45:43 with 6 errors on Sun Apr 18 02:45:43 2021
config:

NAME STATE READ WRITE CKSUM
Pool1 ONLINE 0 0 0
raidz1-0 ONLINE 0 0 0
gptid/fec00321-97b1-11eb-8648-6c3be51d8f0e ONLINE 0 0 12
gptid/fecf2a89-97b1-11eb-8648-6c3be51d8f0e ONLINE 0 0 9
gptid/fedc12e2-97b1-11eb-8648-6c3be51d8f0e ONLINE 0 0 7

errors: 4 data errors, use '-v' for a list

pool: freenas-boot
state: ONLINE
status: Some supported features are not enabled on the pool. The pool can
still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
the pool may no longer be accessible by software that does not support
the features. See zpool-features(5) for details.
scan: scrub repaired 0B in 00:00:07 with 0 errors on Wed Apr 14 03:45:07 2021
config:

NAME STATE READ WRITE CKSUM
freenas-boot ONLINE 0 0 0
ada0p2 ONLINE 0 0 0

errors: No known data errors
root@CTFNAS1[~]#
 

Borja Marcos

Contributor
Joined
Nov 24, 2014
Messages
125
I suffered a similar issue long ago on a server and it turned out to be a defective SAS controller. Errors affecting all of the disks suggest a common failure point. Controller, backplane, cables, power supply...

The pool survived actually! ZFS did a great job repairing data on the fly as advertised.
 
Top