Permanent errors have been detected

Status
Not open for further replies.

Tock

Dabbler
Joined
Jul 15, 2014
Messages
11
As the title suggests I have a small problem^^. Freenas Version: FreeNAS-9.10.2-U2 (e1497f2)

Specs:

Mainboard: Asrock C2750D4I
RAM: 32 GB Kingston ValueRAM DDR3-1333 ECC DIMM
PSU: 360 Watt Seasonic G Serie
Storage: 6x 6TB WD Red in encrypted RaidZ-2

Zpool status -v output:

Code:
  pool: Volume_1
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: http://illumos.org/msg/ZFS-8000-8A
  scan: scrub repaired 0 in 7h51m with 1 errors on Sun May  7 11:39:03 2017
config:

	NAME												STATE	 READ WRITE CKSUM
	Volume_1											ONLINE	   0	 0	 1
	  raidz2-0										  ONLINE	   0	 0	 2
		gptid/10e9b928-275f-11e7-8b90-d05099265246.eli  ONLINE	   0	 0	 0
		gptid/fb708c46-250f-11e7-849d-d05099265246.eli  ONLINE	   0	 0	 0
		gptid/04f13591-16de-11e7-a58e-d05099265246.eli  ONLINE	   0	 0	 0
		gptid/6f9bc2e3-166b-11e7-94d6-d05099265246.eli  ONLINE	   0	 0	 0
		gptid/c815bcfa-2587-11e7-ba66-d05099265246.eli  ONLINE	   0	 0	 0
		gptid/3da8bf3a-27d8-11e7-b7c3-d05099265246.eli  ONLINE	   0	 0	 0

errors: Permanent errors have been detected in the following files:

		<0x115f>:<0x3723f>

  pool: freenas-boot
state: ONLINE
  scan: scrub repaired 0 in 0h4m with 0 errors on Sun May  7 03:49:58 2017
config:

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

errors: No known data errors


It is an encrypted pool thats maybe why it could not detect which file is corrupted. My problem with this is why does ZFS not know which drive is at fault? Why did Raid-Z2 not help against a single file error? What can I do to find out which file it is?
 
Last edited:

Robert Trevellyan

Pony Wrangler
Joined
May 16, 2014
Messages
3,778
It kinda looks like the errors are in metadata, based on which row of the zpool status output they appear on. If so, that explains why the file can't be identified, and may force you into backing up the data and rebuilding the pool.

And @DrKK has a message for you about encrypting your pool.
 

Jailer

Not strong, but bad
Joined
Sep 12, 2014
Messages
4,977
And with corrupt metadata and nothing showing on the drives I'd be running memcheck on your memory to make sure it's good.
 

DrKK

FreeNAS Generalissimo
Joined
Oct 15, 2013
Messages
3,630

Stux

MVP
Joined
Jun 2, 2016
Messages
4,419
Strange.
 

joeschmuck

Old Man
Moderator
Joined
May 28, 2011
Messages
10,994
Status
Not open for further replies.
Top