The boot volume state is ONLINE: One or more devices has experienced an error resulting in data corr

[NineFingers]

I had a power outage at my house, and my FreeNAS is showing the above error.

Clearly, it's showing that //data/rrd_dir.tar.bz2 has an issue. Can this file be removed? Restored? Ideas?

Code:

root@MassNAS:~ # zpool status -v
  pool: freenas-boot
 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 0 days 00:00:22 with 0 errors on Mon Nov 26 03:45:22 2018
config:

	NAME		STATE	 READ WRITE CKSUM
	freenas-boot  ONLINE	   0	 0	 1
	  da1p2	 ONLINE	   0	 0	 2

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

		//data/rrd_dir.tar.bz2

  pool: zvol
 state: ONLINE
  scan: scrub repaired 0 in 0 days 06:26:07 with 0 errors on Sun Nov 18 06:26:08 2018
config:

	NAME											STATE	 READ WRITE CKSUM
	zvol											ONLINE	   0	 0	 0
	  raidz2-0									  ONLINE	   0	 0	 0
		gptid/6e8dc5df-f656-11e7-9501-0cc47a3000e0  ONLINE	   0	 0	 0
		gptid/1a2813be-9b68-11e8-9b16-0cc47a3000e0  ONLINE	   0	 0	 0
		gptid/d072b02e-a1a4-11e8-b7a6-0cc47a3000e0  ONLINE	   0	 0	 0
		gptid/b128e0af-a324-11e8-aa0b-0cc47a3000e0  ONLINE	   0	 0	 0
		gptid/731e3f32-f68e-11e7-b650-0cc47a3000e0  ONLINE	   0	 0	 0
		gptid/edc382a2-a0e1-11e8-b393-0cc47a3000e0  ONLINE	   0	 0	 0

errors: No known data errors

  pool: zvol2
 state: ONLINE
  scan: scrub repaired 0 in 0 days 01:46:14 with 0 errors on Sun Oct 28 01:46:15 2018
config:

	NAME										  STATE	 READ WRITE CKSUM
	zvol2										 ONLINE	   0	 0	 0
	  gptid/76ddda4e-f727-11e7-ad7e-0cc47a3000e0  ONLINE	   0	 0	 0
	  gptid/77ab849b-f727-11e7-ad7e-0cc47a3000e0  ONLINE	   0	 0	 0

errors: No known data errors
root@MassNAS:~ #

 

[Chris Moore]

Sorry, I see you are using an SSD for boot. It is probably just some file corruption to do with the power loss.
Even with an SSD, you need to have two so there is redundancy for ZFS to be able to self correct when there is a data error.
In this scenario, you need to backup your config, reinstall and then restore your config. Your data should be fine and will automatically be reconnected when you restore the saved config.
After that, you might want to upgrade to 11.1-U6 version of the OS.

 

[NineFingers]

Sorry, I see you are using an SSD for boot. It is probably just some file corruption to do with the power loss.
Even with an SSD, you need to have two so there is redundancy for ZFS to be able to self correct when there is a data error.
In this scenario, you need to backup your config, reinstall and then restore your config. Your data should be fine and will automatically be reconnected when you restore the saved config.
After that, you might want to upgrade to 11.1-U6 version of the OS.

Thanks for the reply! I guess I need to update my signature line... I'm actually on the current U6 release.

If it's as simple as a re-install, I'll get on that soon. Is there any risk to running as-is for a week or so?

 

[NineFingers]

To bring everybody up to speed...

I went into my boot menu, and activated the 11.1-U5 environment, rebooted, and (as you would expect) the error went away. I then added another SSD to my boot volume so that I now had a mirror for the boot. Next, I deleted the 11.1-U6 boot environment, and re-applied the U6 update.

All is good in the land!

I love this product!