Critical ZFS error after update

Status
Not open for further replies.

KEvinn

Dabbler
Joined
Dec 22, 2015
Messages
16
Hi,

After updating my Freenass yesterday to the latest firmware i have received a critical error saying the following:

CRITICAL: The volume HDD320GB (ZFS) state is ONLINE: One or more devices has experienced an error resulting in data corruption. Applications may be affected.

Im not sure how to fix this error. I ran this command (zpool status -v | more ) to see if it would give me more info but i have no clue what the permanent damaged files are and if this is something i should worry about. The command came up with the following info:

Code:
[root@freenas ~]# zpool status -v | more                                                                                           
  pool: HDD320GB                                                                                                                   
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 9h40m with 0 errors on Sun Jan  3 09:41:16 2016                                                        
config:                                                                                                                            
                                                                                                                                   
        NAME                                          STATE     READ WRITE CKSUM                                                   
        HDD320GB                                      ONLINE       0     0     0                                                   
          gptid/b7ea97d1-d4b4-11e4-83f8-001fc661a1a0  ONLINE       0     0     0                                                   
          gptid/87caef2f-136c-11e5-87ab-001fc661a1a0  ONLINE       0     0     0                                                   
          gptid/b8cb9859-7e5c-11e5-8c6a-001fc661a1a0  ONLINE       0     0     0                                                   
                                                                                                                                   
errors: Permanent errors have been detected in the following files:                                                                
                                                                                                                                   
        <metadata>:<0x220>                                                                                                         
        <metadata>:<0xec>                                                                                                          
                                                                                                                                   
  pool: freenas-boot                                                                                                               
state: ONLINE                                                                                                                     
  scan: scrub repaired 0 in 0h10m with 0 errors on Sat Jan  9 03:55:50 2016                                                        
config:                                                                                                                            
                                                                                                                                   
        NAME        STATE     READ WRITE CKSUM                                                                                     
        freenas-boot  ONLINE       0     0     0                                                                                   
          da0p2     ONLINE       0     0     0                                                                                     
                                                                                                                                   
errors: No known data errors


The files <metadata>:<0x220> & <metadata>:<0xec> are permanent damaged but as
I said i have no idea what these files are so if anyone can help me would be greatly appreciated.

Kind Regards,
Kevin
 

jgreco

Resident Grinch
Joined
May 29, 2011
Messages
18,680
Please post your hardware manifest. On a properly designed FreeNAS system with ECC and redundancy, this isn't supposed to happen, but it looks like you don't have any redundancy in your storage, which suggests maybe you have other hardware deficiencies as well.
 

SweetAndLow

Sweet'NASty
Joined
Nov 6, 2013
Messages
6,421
Using a striped pool so you don't have redundancy and any little bit of data corruption can't be fixed.
 

jgreco

Resident Grinch
Joined
May 29, 2011
Messages
18,680
Using a striped pool so you don't have redundancy and any little bit of data corruption can't be fixed.

Most metadata's supposed to be redundant regardless through the storage of a second copy.
 

KEvinn

Dabbler
Joined
Dec 22, 2015
Messages
16
It is an old gaming computer so i don't think its a perfect setup for Freenass. Also had 1 working HDD of 320GB so I configured it with RAID-0 if im not mistaken. After a few months when it was full i just bought extra HDDs and filled the array up. I was to lazy to wipe the diks and configure it in RAID 1 or 2, Its a 1,5 TB RAID 0 Plex streaming and Torrents seeding box now. Here are the specs:

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: American Megatrends Inc.
Version: 0403
Release Date: 04/24/2008
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 2048 kB

Base Board Information
Manufacturer: ASUSTeK Computer INC.
Product Name: Rampage Formula
Version: Rev 1.xx

Processor Information
Socket Designation: LGA775
Type: Central Processor
Family: Other
Manufacturer: Intel
Signature: Type 0, Family 6, Model 23, Stepping 7
Version: Intel(R) Core(TM)2 Quad CPU Q9450 @ 2.66GHz
Voltage: 1.2 V
External Clock: 333 MHz
Max Speed: 3800 MHz
Current Speed: 2666 MHz
Status: Populated, Enabled
Upgrade: Socket LGA775
L1 Cache Handle: 0x0005
L2 Cache Handle: 0x0006
L3 Cache Handle: 0x0007

Memory Module Information
Socket Designation: DIMM0
Bank Connections: 0 1
Current Speed: 30 ns
Type: DIMM
Installed Size: 2048 MB (Double-bank Connection)
Enabled Size: 2048 MB (Double-bank Connection)
Error Status: OK

Handle 0x000A, DMI type 6, 12 bytes
Memory Module Information
Socket Designation: DIMM1
Bank Connections: 2 3
Current Speed: 30 ns
Type: DIMM
Installed Size: 2048 MB (Double-bank Connection)
Enabled Size: 2048 MB (Double-bank Connection)
Error Status: OK

Handle 0x000B, DMI type 6, 12 bytes
Memory Module Information
Socket Designation: DIMM2
Bank Connections: 4 5
Current Speed: 30 ns
Type: DIMM
Installed Size: 2048 MB (Double-bank Connection)
Enabled Size: 2048 MB (Double-bank Connection)
Error Status: OK

Handle 0x000C, DMI type 6, 12 bytes
Memory Module Information
Socket Designation: DIMM3
Bank Connections: 6 7
Current Speed: 30 ns
Type: DIMM
Installed Size: 2048 MB (Double-bank Connection)
Enabled Size: 2048 MB (Double-bank Connection)
Error Status: OK
 

jgreco

Resident Grinch
Joined
May 29, 2011
Messages
18,680
Yeah, you lack both ECC and redundancy, so pool errors are not ... unexpected.
 

KEvinn

Dabbler
Joined
Dec 22, 2015
Messages
16
So, should I be worried with this error or ? Because is till have no idea what is corrupted.
 

jgreco

Resident Grinch
Joined
May 29, 2011
Messages
18,680
We don't know what's corrupted either, just that it's pool metadata. ZFS advises:

action: Restore the file in question if possible. Otherwise restore the
entire pool from backup.

Which seems to be correct. ZFS does not have tools to repair the pool, so making sure corruption does not enter the pool is important.
 
Status
Not open for further replies.
Top