Help with seemingly harmlessly corrupted installation

[James Snell]

My FreeNAS rig is installed to two USB flash drives in a mirror RAID. I've run on this for several months and since the beginning there's been this error message about a corrupt root volume and yet it seems to have no effect. I'd prefer to fix the damage, any tips would be most welcome.

Here's the relevant output from zpool status -v:

Code:

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 1.21M in 0h2m with 11 errors on Mon Feb 20 03:47:43 2017													
config:																															
																																	
		NAME		STATE	 READ WRITE CKSUM																					
		freenas-boot  ONLINE	   0	 0	 0																					
		  mirror-0  ONLINE	   0	 0	 0																					
			da0p2   ONLINE	   0	 0	 0																					
			da1p2   ONLINE	   0	 0	 0																					
																																	
errors: Permanent errors have been detected in the following files:																
																																	
		freenas-boot/ROOT/9.10.2-U2@2017-01-15-16:53:30:/usr/local/www/data/docs/_images/iperf.png								
		freenas-boot/ROOT/9.10.2-U2@2017-01-15-16:53:30:/usr/local/lib/libiconv.so.2.5.1											
		freenas-boot/ROOT/9.10.2-U2@2017-01-15-16:53:30:/usr/local/lib/python2.7/site-packages/bsd/acl.so						  
		freenas-boot/ROOT/9.10.2-U2@2017-01-15-16:53:30:/usr/local/www/data/docs/_images/translate.png							
		freenas-boot/ROOT/9.10.2-U2@2017-01-15-16:53:30:/usr/local/go/pkg/bootstrap/bin/link										
		freenas-boot/ROOT/9.10.2-U2@2017-01-15-16:53:30:/usr/local/go/pkg/tool/freebsd_amd64/compile								
		freenas-boot/ROOT/9.10.2-U1:/usr/local/lib/python2.7/nntplib.pyc															
		freenas-boot/ROOT/9.10.2-U1:/usr/local/lib/python2.7/bsddb/test/test_dbenv.pyc											
		freenas-boot/ROOT/9.10.2-U1:/var/db/pkg/local.sqlite																		
		freenas-boot/ROOT/9.10.2-U1:<0x209f4>

 

[nojohnny101]

Have you tried anything yet? Backup config, fresh install, restore config?

 

[James Snell]

Have you tried anything yet? Backup config, fresh install, restore config?

I performed the base installation and then imported my previous configuration. That's it. I've actually ignorred this for months, thankfully I can't tell there's anything wrong, except for this message itself.

 

[SweetAndLow]

Just reinstall on New boot media

Sent from my Nexus 5X using Tapatalk

 

[nojohnny101]

Did you also verify the installation media when you downloaded it (checksum)?

 

[James Snell]

Did you also verify the installation media when you downloaded it (checksum)?

That's a good suggestion. No, I basically never do that. I expect the glorious TCP to keep me safe from myself.

Just doing a fresh reinstall kinda sucks cause this is backing some traffic and seems fine. Sure that should fix it, but since it seems so minor, it'd be nice to just fix it online. I suppose if I fetched the files in question and placed them appropriately, perhaps then it'd be fine? I'd sort of expect the updater to do something like that, though I guess if it works off of diffs, then that would never happen.