SMART Error followed by boot failure

[SilentFox]

I have been running a FreeNAS install for several months on the hardware in my signature below.

The issues began with a SMART error during a routine scrub of the single ZFS RAIDZ1 Storage volume as follows:

Code:

Device: /dev/ada2, Read SMART Self-Test Log Failed
Device: /dev/ada2, Read SMART Error Log Failed
Device: /dev/ada2, not capable of SMART self-check
Device: /dev/ada2, 1 Currently unreadable (pending) sectors
Device: /dev/ada2, failed to read SMART Attribute Data

I did not have access to the console at the time since the system was physically remote. Several days later, I attempted to login to the system via the Web GUI which was unreachable. On accessing the console, I noticed the system had hung with a kernel panic, as per the below screenshot:

I hard reset the system, and on first boot was met with the following error, which some research suggested a faulty port or boot drive (which is a Lexar 32GB Jumpdrive S23 USB 3.0):

I rebooted again, planning to switch to verbose mode. This time, the system progressed further and proceeded to import the ZFS volume as follows:

The pool import stayed this way for an hour or so, and then a further kernel panic occurred as follows:

I left the system off overnight, and have rebooted again today. This time, for reasons I don't understand, the system has rebooted successfully.
It is however, showing the following error:

Code:

March 12, 2018, 10:07 p.m. - Device: /dev/ada2, 2 Currently unreadable (pending) sectors

The Volume status still shows the Scrub Status as "In Progress". EDIT: this has now completed last night.

Full details from smartctl:

Code:

smartctl 6.5 2016-05-07 r4318 [FreeBSD 11.1-STABLE amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:	 western digital Red
Device Model:	 WDC WD40EFRX-68N32N0
Serial Number:	WD-WCC7K5FL873K
LU WWN Device Id: 5 0014ee 26407a93b
Firmware Version: 82.00A82
User Capacity:	4,000,787,030,016 bytes [4.00 TB]
Sector Sizes:	 512 bytes logical, 4096 bytes physical
Rotation Rate:	5400 rpm
Form Factor:	  3.5 inches
Device is:		In smartctl database [for details use: -P show]
ATA Version is:   ACS-3 T13/2161-D revision 5
SATA Version is:  SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:	Mon Mar 12 23:05:44 2018 GMT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00) Offline data collection activity
									   was never started.
									   Auto Offline Data Collection: Disabled.
Self-test execution status:	  (   0) The previous self-test routine completed
									   without error or no self-test has ever
									   been run.
Total time to complete Offline
data collection:				(44160) seconds.
Offline data collection
capabilities:					(0x7b) SMART execute Offline immediate.
									   Auto Offline data collection on/off support.
									   Suspend Offline collection upon new
									   command.
									   Offline surface scan supported.
									   Self-test supported.
									   Conveyance Self-test supported.
									   Selective Self-test supported.
SMART capabilities:			(0x0003) Saves SMART data before entering
									   power-saving mode.
									   Supports SMART auto save timer.
Error logging capability:		(0x01) Error logging supported.
									   General Purpose Logging supported.
Short self-test routine
recommended polling time:		(   2) minutes.
Extended self-test routine
recommended polling time:		( 468) minutes.
Conveyance self-test routine
recommended polling time:		(   5) minutes.
SCT capabilities:			  (0x303d) SCT Status supported.
									   SCT Error Recovery Control supported.
									   SCT Feature Control supported.
									   SCT Data Table supported.

SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME		  FLAG	 VALUE WORST THRESH TYPE	  UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate	 0x002f   154   143   051	Pre-fail  Always	   -   2135
  3 Spin_Up_Time			0x0027   177   177   021	Pre-fail  Always	   -   6108
  4 Start_Stop_Count		0x0032   100   100   000	Old_age   Always	   -   10
  5 Reallocated_Sector_Ct   0x0033   200   200   140	Pre-fail  Always	   -   0
  7 Seek_Error_Rate		 0x002e   200   200   000	Old_age   Always	   -   0
  9 Power_On_Hours		  0x0032   093   093   000	Old_age   Always	   -   5522
 10 Spin_Retry_Count		0x0032   100   253   000	Old_age   Always	   -   0
 11 Calibration_Retry_Count 0x0032   100   253   000	Old_age   Always	   -   0
 12 Power_Cycle_Count	   0x0032   100   100   000	Old_age   Always	   -   10
192 Power-Off_Retract_Count 0x0032   200   200   000	Old_age   Always	   -   5
193 Load_Cycle_Count		0x0032   200   200   000	Old_age   Always	   -   9
194 Temperature_Celsius	 0x0022   121   115   000	Old_age   Always	   -   29
196 Reallocated_Event_Count 0x0032   200   200   000	Old_age   Always	   -   0
197 Current_Pending_Sector  0x0032   200   200   000	Old_age   Always	   -   2
198 Offline_Uncorrectable   0x0030   100   253   000	Old_age   Offline	  -   0
199 UDMA_CRC_Error_Count	0x0032   200   200   000	Old_age   Always	   -   0
200 Multi_Zone_Error_Rate   0x0008   199   199   000	Old_age   Offline	  -   616

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description	Status				  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline	Completed without error	   00%	  5376		 -
# 2  Extended offline	Completed without error	   00%	  5352		 -
# 3  Extended offline	Completed without error	   00%	  5016		 -
# 4  Extended offline	Completed without error	   00%	  4704		 -
# 5  Extended offline	Completed without error	   00%	  4609		 -
# 6  Extended offline	Completed without error	   00%	  4273		 -
# 7  Extended offline	Completed without error	   00%	  3961		 -
# 8  Extended offline	Completed without error	   00%	  3865		 -
# 9  Extended offline	Completed without error	   00%	  3529		 -
#10  Extended offline	Completed without error	   00%	  3218		 -
#11  Extended offline	Completed without error	   00%	  3146		 -
#12  Extended offline	Completed without error	   00%	  2810		 -
#13  Extended offline	Completed without error	   00%	  2498		 -
#14  Extended offline	Completed without error	   00%	  2402		 -
#15  Extended offline	Completed without error	   00%	  2066		 -
#16  Extended offline	Completed without error	   00%	  1754		 -
#17  Extended offline	Completed without error	   00%	  1682		 -
#18  Extended offline	Completed without error	   00%	  1347		 -
#19  Extended offline	Completed without error	   00%	  1035		 -
#20  Extended offline	Completed without error	   00%	   939		 -
#21  Extended offline	Completed without error	   00%	   603		 -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
   1		0		0  Not_testing
   2		0		0  Not_testing
   3		0		0  Not_testing
   4		0		0  Not_testing
   5		0		0  Not_testing

I am concerned that my system lacks stability given the issues when rebooting last night. I do not have a great deal of experience with FreeNAS and am concerned tinkering too much could compromise my data. Please could someone assist with troubleshooting steps?

- First I would like to iron out the issues with the boot drive (if the above indicates such an issue). I have just taken a backup of the configuration (via General>Save Config) but unfortunately do not have a config-file which pre-dates the above issues.
- Is there anything else I should do to verify the functionality of my boot drive?

- Second, my research suggests I should look to replace the drive if I am receiving SMART errors - it is well within warranty. Is this correct? Is there any other testing I can do?

Overall, I am concerned at both the boot issues and SMART errors occurring at similar times - it suggests there may be some other issue with the system which has led to both problems - is there a way of troubleshooting this in particular?

Please do let me know if any further information or log files are needed to assist.

 

[SilentFox]

My current plan - given research suggests a USB boot drive is an inherently less reliable solution - is to change the boot drive to use a Sandisk SSD, installed in the optical bay of the Microserver Gen8.
Installation methodology:
1. Backup config
2. Shutdown
3. Remove USB, install SSD
4. Install fresh FreeNAS install on SSD.
5. Boot SSD and apply config file.
6. Hope that everything continues to work.

Is this an accurate list - I'm not entirely sure how 5 and 6 will go so any suggestions gratefully received.

 

[dlavigne]

Did you try this? Did it work out for you?

 

[SilentFox]

Did you try this? Did it work out for you?

I did indeed. The updated methodology for switching boot drives / fresh install of FreeNAS with config backup (for the benefit of anyone finding this) is as follows:

1. Take backup of config file (from System> General > Save config) I included the password tokens.
2. Check exact version of FreeNAS (from /etc/version - result was FreeNas-11.1-RELEASE (dc7d195f4))
3. Download this version from https://download.freenas.org/
4. Install FreeNAS onto SSD (SanDisk SSD Plus) installed in Bay 1 of the Microserver.
Installation itself when the disk was in the optical bay went without a hitch. However, I realised (once the boot failed and I did some more research) that, when in AHCI mode, the HP Microserver Gen8 will not boot from the separate SATA port on the motherboard, only from the 4 bays. I therefore installed the SSD into an old Western Digital Velociraptor 2.5" to 3.5" drive sled (I bought mine on eBay for around £10) and installed it in Bay 1 of the Microserver. It needed to be in Bay 1 in order to boot first (i.e. otherwise the Microserver tried to boot from the data drives - FreeNAS did not care that I moved the disks around in the Microserver).
I understand the Microserver will boot from the separate SATA port when in RAID or legacy mode (but I don't want the HP B120i RAID module to be enabled since I want to pass the disks straight to FreeNAS without any kind of hardware RAID in the middle, and legacy mode is rumoured to come with performance limitations).
If anyone has any tips/corrections on this point then I'd appreciate them.
5. Boot Microserver, login with newly created password (during install process).
6. Decline the invitation to import disks/ create array.
7. Go to System> General> Upload config.
8. Reboot back to FreeNAS which appears the same as before. The one minor thing I have lost is a shell file stored in /usr/opt which I was using to delete files older than a certain date, hence the cron job which calls this file now fails. Is this an expected consequence of the config file backup/ restore?
Note: first reboot seemed to take longer as the system checked a few more things, etc. but I'm not sure. Passwords remained the same as original config.

Hope the above helps someone.

By way of update to my first post, I am currently waiting for a replacement HDD from WD, under their Advanced RMA programme. I am hoping they ship an identical model (WD40EFRX-68N32N0) so I don't have a potential issue with mismatched drive sizes.

I did not need to run Data Lifeguard Diagnostics for the RMA to be authorised, just reported the increasing number of unreadable (pending) sectors, which at last count had increased to 16.

 

[Chris Moore]

A small difference in the drive will not be a problem.
The configuration backup only stores the system config, not the files that you have added. You have to backup those files separately.
You can probably boot with the old boot drive. Grab the file. Then boot with the new media again. It should work easily.

Sent from my SAMSUNG-SGH-I537 using Tapatalk

 

[SilentFox]

A small difference in the drive will not be a problem.
The configuration backup only stores the system config, not the files that you have added. You have to backup those files separately.
You can probably boot with the old boot drive. Grab the file. Then boot with the new media again. It should work easily.

Sent from my SAMSUNG-SGH-I537 using Tapatalk

Thanks for the clarification / tip. Can I not just plug in the old drive whilst the current system is booted and get it to mount so I can copy the file off that way?


Sent from my iPhone using Tapatalk

 

[Chris Moore]

Thanks for the clarification / tip. Can I not just plug in the old drive whilst the current system is booted and get it to mount so I can copy the file off that way?

That might be possible, but you would need to be careful about it because it would have the name, "freenas-boot", which is the same as the boot pool currently active in the system and it could present a problem.

Here is what you would do, if you want to try it.
Connect the USB drive.
At a command prompt type: zpool import freenas-boot old-boot
What that does is rename freenas-boot to old-boot when it is imported.
If the freenas-boot pool was not cleanly exported, you will have to use the command like this instead:
zpool import -f freenas-boot old-boot and that -f means force.
At this point, there will be a 'folder' named /old-boot at the root of the filesystem which should contain all the contents of the old boot pool.

I hope that works for you.

 

[Ericloewe]

That might be possible, but you would need to be careful about it because it would have the name, "freenas-boot", which is the same as the boot pool currently active in the system and it could present a problem.

Not if the system is already up. ZFS will simply refuse to import a second freenas-boot pool.

The problem lies with having two pools named freenas-boot during boot. FreeNAS is not discriminating at all and effectively takes the first one it sees, even if it's a very different version. Ask me how I know that...

 

[SilentFox]

Not if the system is already up. ZFS will simply refuse to import a second freenas-boot pool.

The problem lies with having two pools named freenas-boot during boot. FreeNAS is not discriminating at all and effectively takes the first one it sees, even if it's a very different version. Ask me how I know that...

Thanks for the clarification - I presume Chris' instructions above will nevertheless work and allow me to browse the older freenas-boot pool?

 

[Chris Moore]

Thanks for the clarification - I presume Chris' instructions above will nevertheless work and allow me to browse the older freenas-boot pool?

He was pointing out that if there were two pools with the same name, the system would import the first one if found and refuse to import the second one during boot. Once the system is up and running, if you connect additional drives, you have to manually import them. That is where my instructions come in. The command I gave you will rename the pool as part of the import process which mounts the pool as a 'directory' off the root of the file system. If you were going to keep it mounted, you would want to set a mount point, but you probably don't want to do that.
When you are done with it, you can export this pool and this is the command you would use:

zpool export old-boot
If you get an error like 'cannot unmount' or 'Device busy', you can add the -f to the command like this:
zpool export -f old-boot

 

[Chris Moore]

PS. There are whole books dedicated to all the details. I am not trying to cover the whole story, just give you enough to get you through this.

Here is a link to a reference if you want to know more: https://www.freebsd.org/doc/handbook/zfs-zpool.html

 

[SilentFox]

That is where my instructions come in.

Thanks Chris, that makes sense and I appreciate you taking the time to explain the relevant bits!
I've bookmarked the reference you provided.

 

[SilentFox]

Overnight the first scrub of the boot pool took place (since install onto SSD). This reported checksum errors and the boot pool is stated to be degraded.

What's baffling is this is on a brand new drive and thus my concern of a broader issue with the system has reared its head again.

Aside from backing up my config (done) and reinstalling yet again, I'm not sure how to go about addressing this. I have pondered whether this arises from an issue with system memory but given it's ECC RAM, is this not unlikely?

Is anyone able to help?


Sent from my iPhone using Tapatalk

 

[SilentFox]

I've reinstalled FreeNAS and restored my config file once again. I am already seeing checksum errors and the boot volume has immediately become degraded following a scrub. I suspect I have an issue with the disk or the sled (WD Velociraptor 2.5" to 3.5") used to mount it into the Microserver Bay backplane.

 

[SilentFox]

Having done some research, I have my fingers crossed that this is a formatting error (bit of a long shot) similar to what is described here:
https://forums.freenas.org/index.php?threads/boot-drive-degrades.57500/
My plan is therefore to pull the SSD drive, use SDFormatter (if it will work - EDIT: which didn't work) to format the drive, do a Windows full format and then attempt the FreeNAS reinstall again.

 

[SilentFox]

As part of my troubleshooting steps, I have reinstalled FreeNAS and then, before applying any previous config, I have scrubbed the boot pool and it has immediately shown checksum errors and shows status as degraded. I believe this suggests a drive cabling/ sled or formatting issue, so will proceed to format the drive once I have a USB/SATA interface in order to do this.

The output of zpool status -v is as follows:

Code:

  pool: freenas-boot
 state: DEGRADED
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 4K in 0 days 00:00:03 with 31 errors on Sat Mar 24 06:07:37 2018
config:

		NAME		STATE	 READ WRITE CKSUM
		freenas-boot  DEGRADED	 0	 0	31
		  ada0p2	DEGRADED	 0	 0	66  too many errors

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

		<metadata>:<0x2d>
		<metadata>:<0x3d>
		//usr/local/lib/python3.6/site-packages/formtools/__pycache__
		freenas-boot/ROOT/default@2018-03-24-12:59:57:/usr/local/lib/python3.6/site-packages/pysmi/writer
		freenas-boot/ROOT/default@2018-03-24-12:59:57:/usr/local/lib/python3.6/site-packages/pysmi/writer/__pycache__
		freenas-boot/ROOT/default@2018-03-24-12:59:57:/usr/local/lib/migrate93/django/db/models/sql
		freenas-boot/ROOT/default@2018-03-24-12:59:57:/usr/local/lib/migrate93/django/db/models/sql/__pycache__
		freenas-boot/ROOT/default@2018-03-24-12:59:57:/usr/local/lib/python3.6/site-packages/ply/yacc.py
		freenas-boot/ROOT/default@2018-03-24-12:59:57:/usr/local/lib/python3.6/site-packages/pysnmp-4.3.9-py3.6.egg-info
		freenas-boot/ROOT/default@2018-03-24-12:59:57:/usr/local/lib/python3.6/site-packages/pysnmp
		freenas-boot/ROOT/default@2018-03-24-12:59:57:/usr/local/lib/python3.6/site-packages/pysnmp/__pycache__
		freenas-boot/ROOT/default@2018-03-24-12:59:57:/usr/local/lib/python3.6/site-packages/chardet/__pycache__/latin1prober.cpython-36.opt-1.pyc
		freenas-boot/ROOT/default@2018-03-24-12:59:57:/usr/local/lib/python3.6/site-packages/chardet/__pycache__/utf8prober.cpython-36.opt-1.pyc
		freenas-boot/ROOT/default@2018-03-24-12:59:57:/usr/local/lib/python3.6/site-packages/cryptography/hazmat/backends/openssl/__pycache__/cmac.cpython-36.opt-1.pyc
		freenas-boot/ROOT/default@2018-03-24-12:59:57:/usr/local/www/dojo/dojox/widget/nls/pt
		freenas-boot/ROOT/default@2018-03-24-12:59:57:/usr/local/www/dojo/dojox/widget/nls/ro
		freenas-boot/ROOT/default@2018-03-24-12:59:57:/usr/local/lib/migrate93/freenasUI
		freenas-boot/ROOT/default@2018-03-24-12:59:57:/usr/local/lib/migrate93/freenasUI/__pycache__
		freenas-boot/ROOT/default@2018-03-24-12:59:57:/usr/local/lib/migrate93/freenasUI/account
		freenas-boot/ROOT/default@2018-03-24-12:59:57:/usr/local/www/dojo/dojox/widget/nls/ru
		freenas-boot/ROOT/default@2018-03-24-12:59:57:/usr/local/lib/python3.6/site-packages/pysmi/tests/__pycache__
		freenas-boot/ROOT/default@2018-03-24-12:59:57:/usr/local/bin/cmpdump.py
		freenas-boot/ROOT/default@2018-03-24-12:59:57:/usr/local/lib/python3.6/site-packages/aiohttp/__pycache__/web_server.cpython-36.opt-1.pyc
		freenas-boot/ROOT/default@2018-03-24-12:59:57:/usr/local/www/dojo/dojox/widget/nls/sk
		freenas-boot/ROOT/default@2018-03-24-12:59:57:/usr/local/lib/migrate93/django/db/models
		freenas-boot/ROOT/default@2018-03-24-12:59:57:/usr/local/lib/migrate93/django/db/models/__pycache__
		freenas-boot/ROOT/default@2018-03-24-12:59:57:/usr/local/www/dojo/dojox/widget/nls/sl
		freenas-boot/ROOT/default@2018-03-24-12:59:57:/usr/local/lib/python3.6/site-packages/django/contrib/postgres/forms
		freenas-boot/ROOT/default@2018-03-24-12:59:57:/usr/local/lib/python3.6/site-packages/django/contrib/postgres/forms/__pycache__
		freenas-boot/ROOT/default@2018-03-24-12:59:57:/usr/local/lib/migrate93/django/db/models/fields
		freenas-boot/ROOT/default@2018-03-24-12:59:57:/usr/local/lib/migrate93/django/db/models/fields/__pycache__
root@freenas:~ #

 

[Chris Moore]

Having done some research, I have my fingers crossed that this is a formatting error (bit of a long shot) similar to what is described here:
https://forums.freenas.org/index.php?threads/boot-drive-degrades.57500/
My plan is therefore to pull the SSD drive, use SDFormatter (if it will work) to format the drive, do a Windows full format and then attempt the FreeNAS reinstall again.

You did all that to test the drive and it still has errors? Did you look at the drive health when you had it connected to the Windows computer?
You can use a utility like this: https://sourceforge.net/projects/gsmartcontrol/
To view the drive SMART data in Windows to see what it has to say for itself.
You said it was a new drive, so I am more likely to think there is something wrong with the system the drive is connected to. It is difficult to troubleshoot one of those micro servers, but I would be looking at the interface in the server instead of the drive.

 

[SilentFox]

You did all that to test the drive and it still has errors? Did you look at the drive health when you had it connected to the Windows computer?
...I am more likely to think there is something wrong with the system the drive is connected to. It is difficult to troubleshoot one of those micro servers, but I would be looking at the interface in the server instead of the drive.

Thankfully it didn't take long to do all that. I can't easily connect it to a Windows system without opening up my desktop so I'm awaiting delivery of a SATA/USB dock to make this and future similar tasks quicker.

I agree with you that I suspect the system is at fault but thought I'd try to eliminate other possibilities first. I think/hope it's less likely to be the system / Bay1 connection since it has been happily hosting one of the data drives for months without an error. That leaves the sled. Unfortunately changing that is more difficult since I don't have a spare and would need to find one on eBay again.

I'll double check the smart data from the drive on Windows - realising I might have to connect it via SATA directly to the motherboard to do this. Is the Windows utility going to give me any more detail than smartctl?
EDIT: GSmartControl worked fine via a SATA/USB interface. The output appeared identical to smartctl under FreeNAS, and appears to be running that same utility (albeit v. 6.6 as opposed to 6.5 under FreeNAS 11.0) in the background.



Sent from my iPhone using Tapatalk

 

[SilentFox]

view the drive SMART data in Windows to see what it has to say for itself.

No SMART errors on the SanDisk SSD Plus were reported by GSmartControl. I did the short and long test. The only notable piece of data was the bad block count of 98, but GSmartControl said that a low bad block count was normal for SSDs, and it appears (from a brief online search) that the number of re-allocated sectors is the important bit. The tests were performed whilst the SSD drive was inserted into a SATA/ USB dock.

Onto the re-format per my earlier post. My next step (if that doesn't work) after that is to pull the 3 data drives, switch to SATA Legacy mode (from AHCI), and boot the SSD from the ODD port, therefore removing the Sled from the equation.

Full SMART output for the SSD below:

Code:

smartctl 6.6 2017-11-05 r4594 [i686-w64-mingw32-w10-1709(64)] (sf-6.6-1)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:	 SanDisk SSD PLUS 120 GB
Serial Number:	174501A00D7D
LU WWN Device Id: 5 001b44 8b66f088c
Firmware Version: UE3000RL
User Capacity:	120,040,980,480 bytes [120 GB]
Sector Size:	  512 bytes logical/physical
Rotation Rate:	Solid State Device
Form Factor:	  2.5 inches
Device is:		Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2 T13/2015-D revision 3
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:	Sun Mar 25 10:41:05 2018 GMTST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM feature is:   Disabled
Rd look-ahead is: Enabled
Write cache is:   Enabled
DSN feature is:   Unavailable
ATA Security is:  Disabled, NOT FROZEN [SEC1]

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)   Offline data collection activity
				   was never started.
				   Auto Offline Data Collection: Disabled.
Self-test execution status:	  (   0)   The previous self-test routine completed
				   without error or no self-test has ever
				   been run.
Total time to complete Offline
data collection:		(  120) seconds.
Offline data collection
capabilities:			 (0x15) SMART execute Offline immediate.
				   No Auto Offline data collection support.
				   Abort Offline collection upon new
				   command.
				   No Offline surface scan supported.
				   Self-test supported.
				   No Conveyance Self-test supported.
				   No Selective Self-test supported.
SMART capabilities:			(0x0003)   Saves SMART data before entering
				   power-saving mode.
				   Supports SMART auto save timer.
Error logging capability:		(0x01)   Error logging supported.
				   General Purpose Logging supported.
Short self-test routine
recommended polling time:	 (   2) minutes.
Extended self-test routine
recommended polling time:	 (  21) minutes.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME		  FLAGS	VALUE WORST THRESH FAIL RAW_VALUE
  5 Reallocated_Sector_Ct   -O--CK   100   100   000	-	0
  9 Power_On_Hours		  -O--CK   100   100   000	-	175
 12 Power_Cycle_Count	   -O--CK   100   100   000	-	12
165 Unknown_Attribute	   -O--CK   100   100   000	-	1
166 Unknown_Attribute	   -O--CK   100   100   ---	-	0
167 Unknown_Attribute	   -O--CK   100   100   ---	-	0
168 Unknown_Attribute	   -O--CK   100   100   ---	-	0
169 Unknown_Attribute	   -O--CK   100   100   ---	-	98
170 Unknown_Attribute	   -O--CK   100   100   ---	-	0
171 Unknown_Attribute	   -O--CK   100   100   000	-	0
172 Unknown_Attribute	   -O--CK   100   100   000	-	0
173 Unknown_Attribute	   -O--CK   100   100   000	-	0
174 Unknown_Attribute	   -O--CK   100   100   000	-	6
184 End-to-End_Error		-O--CK   100   100   ---	-	0
187 Reported_Uncorrect	  -O--CK   100   100   000	-	0
188 Command_Timeout		 -O--CK   100   100   ---	-	0
194 Temperature_Celsius	 -O---K   062   040   000	-	38 (Min/Max 16/40)
199 UDMA_CRC_Error_Count	-O--CK   100   100   ---	-	0
230 Unknown_SSD_Attribute   -O--CK   100   100   000	-	0
232 Available_Reservd_Space PO--CK   100   100   005	-	100
233 Media_Wearout_Indicator -O--CK   100   100   ---	-	0
234 Unknown_Attribute	   -O--CK   100   100   000	-	8
241 Total_LBAs_Written	  ----CK   100   100   000	-	2
242 Total_LBAs_Read		 ----CK   100   100   000	-	4
244 Unknown_Attribute	   -O--CK   000   100   ---	-	0
							||||||_ K auto-keep
							|||||__ C event count
							||||___ R error rate
							|||____ S speed/performance
							||_____ O updated online
							|______ P prefailure warning

General Purpose Log Directory Version 1
SMART		   Log Directory Version 1 [multi-sector log support]
Address	Access  R/W   Size  Description
0x00	   GPL,SL  R/O	  1  Log Directory
0x01		   SL  R/O	  1  Summary SMART error log
0x02		   SL  R/O	  1  Comprehensive SMART error log
0x03	   GPL	 R/O	 16  Ext. Comprehensive SMART error log
0x04	   GPL,SL  R/O	  8  Device Statistics log
0x06		   SL  R/O	  1  SMART self-test log
0x07	   GPL	 R/O	  1  Extended self-test log
0x10	   GPL	 R/O	  1  NCQ Command Error log
0x11	   GPL	 R/O	  1  SATA Phy Event Counters log
0x30	   GPL,SL  R/O	  9  IDENTIFY DEVICE data log
0x80-0x9f  GPL,SL  R/W	 16  Host vendor specific log
0xa1	   GPL,SL  VS	   1  Device vendor specific log
0xa2	   GPL,SL  VS	   2  Device vendor specific log
0xa3	   GPL,SL  VS	   1  Device vendor specific log
0xa7	   GPL,SL  VS	   1  Device vendor specific log
0xa9	   GPL,SL  VS	   3  Device vendor specific log

Warning! SMART Extended Comprehensive Error Log Structure error: invalid SMART checksum.
SMART Extended Comprehensive Error Log Version: 1 (16 sectors)
No Errors Logged

SMART Extended Self-test Log Version: 1 (1 sectors)
Num  Test_Description	Status				  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline	Completed without error	   00%	   175		 -
# 2  Short offline	   Completed without error	   00%	   175		 -

Selective Self-tests/Logging not supported

SCT Commands not supported

Device Statistics (GP Log 0x04)
Page  Offset Size		Value Flags Description
0x01  =====  =			   =  ===  == General Statistics (rev 1) ==
0x01  0x008  4			  12  ---  Lifetime Power-On Resets
0x01  0x010  4			 175  ---  Power-on Hours
0x01  0x018  6		 4968199  ---  Logical Sectors Written
0x01  0x028  6		10312059  ---  Logical Sectors Read
0x01  0x038  6			 175  ---  Date and Time TimeStamp
0x05  =====  =			   =  ===  == Temperature Statistics (rev 1) ==
0x05  0x008  1			  38  ---  Current Temperature
0x05  0x010  1			   -  ---  Average Short Term Temperature
0x05  0x018  1			   -  ---  Average Long Term Temperature
0x05  0x020  1			  39  ---  Highest Temperature
0x05  0x028  1			  23  ---  Lowest Temperature
0x05  0x030  1			  28  ---  Highest Average Short Term Temperature
0x05  0x038  1			  28  ---  Lowest Average Short Term Temperature
0x05  0x040  1			   -  ---  Highest Average Long Term Temperature
0x05  0x048  1			   -  ---  Lowest Average Long Term Temperature
0x05  0x050  4			   0  ---  Time in Over-Temperature
0x05  0x058  1			  95  ---  Specified Maximum Operating Temperature
0x05  0x060  4			   0  ---  Time in Under-Temperature
0x05  0x068  1			   0  ---  Specified Minimum Operating Temperature
0x07  =====  =			   =  ===  == Solid State Device Statistics (rev 1) ==
0x07  0x008  1			   0  N--  Percentage Used Endurance Indicator
								|||_ C monitored condition met
								||__ D supports DSN
								|___ N normalized value

SATA Phy Event Counters (GP Log 0x11)
ID	  Size	 Value  Description
0x0003  2			0  R_ERR response for device-to-host data FIS
0x0004  2			0  R_ERR response for host-to-device data FIS
0x0006  2			0  R_ERR response for device-to-host non-data FIS
0x0007  2			0  R_ERR response for host-to-device non-data FIS
0x0009  2			0  Transition from drive PhyRdy to drive PhyNRdy
0x000a  2			1  Device-to-host register FISes sent due to a COMRESET
0x000f  2			0  R_ERR response for host-to-device data FIS, CRC
0x0012  2			0  R_ERR response for host-to-device non-data FIS, CRC
0x0001  2			0  Command failed due to ICRC error

 

[SilentFox]

Unfortunately but perhaps unsurprisingly, the same error occurred after reinstalling FreeNAS and scrubbing the boot volume. Onto phase 2 - pull the 3 data drives, switch to SATA Legacy mode (from AHCI), and boot the SSD from the ODD port, therefore removing the Sled from the equation.

One thing I have noticed is that the list of files with permanent errors (below) is very similar to that experienced the last few times. Is this coincidence or does it suggest there's an issue with my installation disk? I've tried installing both from an SD card (connected via USB) and from an ISO mounted via HP ILO.

Code:

  pool: freenas-boot
 state: DEGRADED
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 1K in 0 days 00:00:03 with 29 errors on Sun Mar 25 03:42:											 50 2018
config:

		NAME		STATE	 READ WRITE CKSUM
		freenas-boot  DEGRADED	 0	 0	29
		  ada0p2	DEGRADED	 0	 0	60  too many errors

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

		<metadata>:<0x3b>
		<metadata>:<0x44>
		<metadata>:<0x45>
		<metadata>:<0x48>
		<metadata>:<0x4b>
		freenas-boot/ROOT/default@2018-03-25-10:39:37:<0x0>
		freenas-boot/ROOT/default@2018-03-25-10:39:37:/usr/local/www/dojo/dojox/											 form/nls/ro
		freenas-boot/ROOT/default@2018-03-25-10:39:37:/data/zfs
		freenas-boot/ROOT/default@2018-03-25-10:39:37:/usr/local/lib/python3.6/s											 ite-packages/Crypto/Hash/__pycache__/HMAC.cpython-36.opt-1.pyc
		freenas-boot/ROOT/default@2018-03-25-10:39:37:/usr/local/lib/python3.6/s											 ite-packages/botocore/__pycache__/errorfactory.cpython-36.opt-1.pyc
		freenas-boot/ROOT/default@2018-03-25-10:39:37:/usr/local/www/freenasUI/l											 ocale/zh_Hans/LC_MESSAGES/django.mo
		freenas-boot/ROOT/default@2018-03-25-10:39:37:/var/db/services.db
		freenas-boot/ROOT/default@2018-03-25-10:39:37:/usr/local/bin/nsq_to_http
		freenas-boot/ROOT/default@2018-03-25-10:39:37:/usr/local/www/dojo/dojox/											 form/nls/nb
		freenas-boot/ROOT/default@2018-03-25-10:39:37:/usr/local/www/freenasUI/m											 iddleware/notifier.py
		freenas-boot/ROOT/default@2018-03-25-10:39:37:/usr/local/www/dojo/dojox/											 form/nls/nl
		freenas-boot/ROOT/default@2018-03-25-10:39:37:/usr/local/lib/python3.6/s											 ite-packages/boto3/resources
		freenas-boot/ROOT/default@2018-03-25-10:39:37:/usr/local/lib/python3.6/s											 ite-packages/dns/__pycache__/rrset.cpython-36.opt-1.pyc
		freenas-boot/ROOT/default@2018-03-25-10:39:37:/usr/local/www/dojo/dojox/											 form/nls/pl
		freenas-boot/ROOT/default@2018-03-25-10:39:37:/usr/local/lib/migrate93/d											 jango/contrib/gis/tests/geoapp/fixtures/initial_data.json.gz
		freenas-boot/ROOT/default@2018-03-25-10:39:37:/conf/base/var/at
		freenas-boot/ROOT/default@2018-03-25-10:39:37:/usr/local/lib/migrate93/d											 jango/contrib/gis/tests/geogapp
		freenas-boot/ROOT/default@2018-03-25-10:39:37:/usr/local/lib/migrate93/d											 jango/contrib/gis/tests/geogapp/__pycache__
		freenas-boot/ROOT/default@2018-03-25-10:39:37:/usr/local/www/dojo/dojox/											 form/nls/pt-pt
		freenas-boot/ROOT/default@2018-03-25-10:39:37:/usr/local/lib/python3.6/s											 ite-packages/daemon/__pycache__/pidfile.cpython-36.opt-1.pyc
		freenas-boot/ROOT/default@2018-03-25-10:39:37:/usr/local/lib/python3.6/s											 ite-packages/django/core/management/__pycache__/color.cpython-36.opt-1.pyc
		freenas-boot/ROOT/default@2018-03-25-10:39:37:/usr/local/www/dojo/dojox/