One or more devices has experienced an unrecoverable error. - How do I proceed?

Status
Not open for further replies.

NASbox

Guru
Joined
May 8, 2012
Messages
650
I just had a disk drop off my main RAIDZ2 pool and I need some guidance to troubleshoot/recover.

I am running FreeNAS-8.3.1-RELEASE-x64 (r13452), and am getting ready to upgrade.

Disk Configuration:
/dev/ada0,1,2,3 - TANK - RAIDZ2
/dev/ada4,5 - SCRATCH - RAIDZ
/dev/ada6 - attached to a hot swap disk caddy for backup.

I have been using UFS over USB for backup, but since this isn't compatible (and not the most reliable, I am in the process of creating ZFS backups before I do the migration). I plan on moving to a larger case, adding memory and doing a processor upgrade just prior to the system upgrade.

I just successfully completed a complete rsync backup of "TANK" to a single disk ZFS pool I created on theremovable disk on /dev/ada6
I attached the disk, created a single disk pool BACKUP01, rsync'd the data on TANK to it, and then scrubbed BACKUP01 successfully.
BACKUP01 was still attached/spinning when the automatic scrub on TANK started.

I just happened to do a zpool status and I noticed that /dev/ada0 had DROPPED OFF from pool TANK
(The command smartctl -a /dev/ada0 would not work, and ls /dev/ad* showed it was gone).

I did a check of /var/log/messages, and the only thing I could find relating to this error was:
Code:
(ada0:ahcich2:0:0:0): lost device

Here's the output from: zpool status TANK
Code:
  pool: TANK
 state: ONLINE
status: One or more devices has experienced an unrecoverable error.  An
		attempt was made to correct the error.  Applications are unaffected.
action: Determine if the device needs to be replaced, and clear the errors
		using 'zpool clear' or replace the device with 'zpool replace'.
   see: http://www.sun.com/msg/ZFS-8000-9P
  scan: scrub in progress since Sun Aug 20 00:00:01 2017
		3.97T scanned out of 14.1T at 421M/s, 6h59m to go
		0 repaired, 28.15% done
config:

		NAME											STATE	 READ WRITE CKSUM
		TANK											ONLINE	   0	 0	 0
		  raidz2-0									  ONLINE	   0	 0	 0
			gptid/73fc17c0-1916-11e5-b2b5-c860006d863b  ONLINE	   7  117K	 0
			gptid/bcd021f7-dbd8-11e4-adc9-c860006d863b  ONLINE	   0	 0	 0
			gptid/fcd3d3cb-f747-11e4-95cc-c860006d863b  ONLINE	   0	 0	 0
			gptid/76e6e5f1-0f39-11e5-8bc3-c860006d863b  ONLINE	   0	 0	 0

errors: No known data errors


Here's the output from the nightly security message:
Code:
freenas.WORKGROUP changes in mounted filesystems:
--- /var/log/mount.today	2017-08-18 03:01:01.000000000 -0400
+++ /tmp/security.JumAse6s	2017-08-20 03:01:02.000000000 -0400
@@ -4,7 +4,6 @@
 /dev/ufs/FreeNASs1a	/			ufs	ro		1 1
 /dev/ufs/FreeNASs4	/data			ufs	rw,noatime	 2 2
 /dev/ufs/USBDRIVE	/mnt/USBDRIVE		ufs	rw		2 2
-BACKUP01		/mnt/BACKUP01		zfs	rw,nfsv4acls	 0 0
 SCRATCH			/mnt/SCRATCH		zfs	rw,nfsv4acls	 0 0
 TANK			/mnt/TANK		zfs	rw,noatime,nfsv4acls	 0 0
 TANK/barry		/mnt/TANK/barry		zfs	rw,noatime,nfsv4acls	 0 0

Checking for uids of 0:
root 0

Checking for passwordless accounts:

Checking login.conf permissions:

Checking for ports with mismatched checksums:

freenas.WORKGROUP kernel log messages:
+++ /tmp/security.vxG5TZCL	2017-08-20 03:01:03.000000000 -0400
+ugen2.3: <Logitech> at usbus2
+ukbd0: <USB Keyboard> on usbus2
+kbd2 at ukbd0
+uhid0: <USB Keyboard> on usbus2
+ugen2.3: <Logitech> at usbus2 (disconnected)
+ukbd0: at uhub4, port 3, addr 3 (disconnected)
+uhid0: at uhub4, port 3, addr 3 (disconnected)
+ugen2.3: <Logitech> at usbus2
+ukbd0: <USB Keyboard> on usbus2
+kbd2 at ukbd0
+uhid0: <USB Keyboard> on usbus2
+ugen2.3: <Logitech> at usbus2 (disconnected)
+ukbd0: at uhub4, port 3, addr 3 (disconnected)
+uhid0: at uhub4, port 3, addr 3 (disconnected)
+(ada0:ahcich2:0:0:0): lost device
+GEOM_ELI: Detached ada6p1.eli on last close.
+(ada6:ahcich1:0:0:0): lost device
+(ada6:ahcich1:0:0:0): removing device entry
+ugen2.3: <Logitech> at usbus2
+ukbd0: <USB Keyboard> on usbus2
+kbd2 at ukbd0
+uhid0: <USB Keyboard> on usbus2
+ugen2.4: <Logitech> at usbus2
+ums0: <Logitech USB Optical Mouse, class 0/0, rev 2.00/72.00, addr 4> on usbus2
+ums0: 3 buttons and [XYZ] coordinates ID=0
+ugen2.3: <Logitech> at usbus2 (disconnected)
+ukbd0: at uhub4, port 3, addr 3 (disconnected)
+uhid0: at uhub4, port 3, addr 3 (disconnected)
+ugen2.4: <Logitech> at usbus2 (disconnected)
+ums0: at uhub4, port 4, addr 4 (disconnected)
+swap_pager: I/O error - pagein failed; blkno 70,size 4096, error 6
+vm_fault: pager read error, pid 2840 (python)
+pid 2840 (python), uid 0: exited on signal 11

freenas.WORKGROUP login failures:

freenas.WORKGROUP refused connections:

-- End of security output --


NOTE: The following series of messages is expected, and is caused by a KVM switch:
+ugen2.3: <Logitech> at usbus2
+ukbd0: <USB Keyboard> on usbus2
+kbd2 at ukbd0
+uhid0: <USB Keyboard> on usbus2
+ugen2.3: <Logitech> at usbus2 (disconnected)
+ukbd0: at uhub4, port 3, addr 3 (disconnected)
+uhid0: at uhub4, port 3, addr 3 (disconnected)

I have 4 computers on a KVM switch (Windows Box, 2 Linux Boxes, FreeNAS), so every time I switch from machine to machine the mouse/keyboard come and go. I have been doing this for several years without any problem.

The following messages were caused by an intentional "Detach" executed from the GUI followed by unplugging the drive.
+GEOM_ELI: Detached ada6p1.eli on last close.
+(ada6:ahcich1:0:0:0): lost device
+(ada6:ahcich1:0:0:0): removing device entry

I am not sure what this means?
+++ /tmp/security.JumAse6s 2017-08-20 03:01:02.000000000 -0400
@@ -4,7 +4,6 @@



Here are the last few lines of dmesg:
Code:
kbd2 at ukbd0
uhid0: <USB Keyboard> on usbus2
ugen2.3: <Logitech> at usbus2 (disconnected)
ukbd0: at uhub4, port 3, addr 3 (disconnected)
uhid0: at uhub4, port 3, addr 3 (disconnected)
(ada0:ahcich2:0:0:0): lost device
GEOM_ELI: Detached ada6p1.eli on last close.
(ada6:ahcich1:0:0:0): lost device
(ada6:ahcich1:0:0:0): removing device entry
ugen2.3: <Logitech> at usbus2
ukbd0: <USB Keyboard> on usbus2
kbd2 at ukbd0
uhid0: <USB Keyboard> on usbus2
ugen2.4: <Logitech> at usbus2
ums0: <Logitech USB Optical Mouse, class 0/0, rev 2.00/72.00, addr 4> on usbus2
ums0: 3 buttons and [XYZ] coordinates ID=0
ugen2.3: <Logitech> at usbus2 (disconnected)
ukbd0: at uhub4, port 3, addr 3 (disconnected)
uhid0: at uhub4, port 3, addr 3 (disconnected)
ugen2.4: <Logitech> at usbus2 (disconnected)
ums0: at uhub4, port 4, addr 4 (disconnected)
swap_pager: I/O error - pagein failed; blkno 70,size 4096, error 6
vm_fault: pager read error, pid 2840 (python)
pid 2840 (python), uid 0: exited on signal 11

Other than the device lost message there is no hint of anything happening.

After I noticed the error, I detached the backup for safekeeping and stopped the scrub with zpool scrub -s TANK

The system is sitting idle with the power still on and a console shell open so as not to destroy any information. Anything else I should check?

How can I determine why the drive became detached?

System History/Possible explanations:
It is possible that adding the hot swap disk caddy may have loosened a cable on /dev/ada0 (although the pool did run fine for a couple of days).
It is also possible a may have some freak memory error (not running ECC memory - system is built with an ASUS consumer grade motherboard.) The system has been very stable over the last year. Only one crash caused by a crash on a windows box that was connected by a CIFS share. When the Win box hung, FreeNAS got locked up and I had to reset it. Other than that been rock solid - no trouble at all.

Unless someone has a better (safer suggestion), my plan is to
  1. shut down, reseat the cable on ada0
  2. restart and see if the BIOS recognized the disk (if not RMA!)
  3. if disk recognized, attempt to do a smartctl -x /dev/ada0 to see what is going on (if something obvious RMA/replace disk)
  4. Run a long self test (if something found RMA/replace disk)
  5. If nothing found to this point run memtest for an hour or so
  6. If all ok zpool clear TANK and run another scrub.
  7. If OK return system to production and observe carefully for a week or two
BTW Is there a way to run a long disk test and memtest at the same time?

Thanks in advance for any assistance/suggestions/recommendations.
 

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,080
I just had a disk drop off my main RAIDZ2 pool and I need some guidance to troubleshoot/recover.

I am running FreeNAS-8.3.1-RELEASE-x64 (r13452), and am getting ready to upgrade.

Disk Configuration:
/dev/ada0,1,2,3 - TANK - RAIDZ2
/dev/ada4,5 - SCRATCH - RAIDZ
/dev/ada6 - attached to a hot swap disk caddy for backup.

I have been using UFS over USB for backup, but since this isn't compatible (and not the most reliable, I am in the process of creating ZFS backups before I do the migration). I plan on moving to a larger case, adding memory and doing a processor upgrade just prior to the system upgrade.

I just successfully completed a complete rsync backup of "TANK" to a single disk ZFS pool I created on theremovable disk on /dev/ada6
I attached the disk, created a single disk pool BACKUP01, rsync'd the data on TANK to it, and then scrubbed BACKUP01 successfully.
BACKUP01 was still attached/spinning when the automatic scrub on TANK started.

I just happened to do a zpool status and I noticed that /dev/ada0 had DROPPED OFF from pool TANK
(The command smartctl -a /dev/ada0 would not work, and ls /dev/ad* showed it was gone).

I did a check of /var/log/messages, and the only thing I could find relating to this error was:
Code:
(ada0:ahcich2:0:0:0): lost device

Here's the output from: zpool status TANK
Code:
  pool: TANK
 state: ONLINE
status: One or more devices has experienced an unrecoverable error.  An
		attempt was made to correct the error.  Applications are unaffected.
action: Determine if the device needs to be replaced, and clear the errors
		using 'zpool clear' or replace the device with 'zpool replace'.
   see: http://www.sun.com/msg/ZFS-8000-9P
  scan: scrub in progress since Sun Aug 20 00:00:01 2017
		3.97T scanned out of 14.1T at 421M/s, 6h59m to go
		0 repaired, 28.15% done
config:

		NAME											STATE	 READ WRITE CKSUM
		TANK											ONLINE	   0	 0	 0
		  raidz2-0									  ONLINE	   0	 0	 0
			gptid/73fc17c0-1916-11e5-b2b5-c860006d863b  ONLINE	   7  117K	 0
			gptid/bcd021f7-dbd8-11e4-adc9-c860006d863b  ONLINE	   0	 0	 0
			gptid/fcd3d3cb-f747-11e4-95cc-c860006d863b  ONLINE	   0	 0	 0
			gptid/76e6e5f1-0f39-11e5-8bc3-c860006d863b  ONLINE	   0	 0	 0

errors: No known data errors


Here's the output from the nightly security message:
Code:
freenas.WORKGROUP changes in mounted filesystems:
--- /var/log/mount.today	2017-08-18 03:01:01.000000000 -0400
+++ /tmp/security.JumAse6s	2017-08-20 03:01:02.000000000 -0400
@@ -4,7 +4,6 @@
 /dev/ufs/FreeNASs1a	/			ufs	ro		1 1
 /dev/ufs/FreeNASs4	/data			ufs	rw,noatime	 2 2
 /dev/ufs/USBDRIVE	/mnt/USBDRIVE		ufs	rw		2 2
-BACKUP01		/mnt/BACKUP01		zfs	rw,nfsv4acls	 0 0
 SCRATCH			/mnt/SCRATCH		zfs	rw,nfsv4acls	 0 0
 TANK			/mnt/TANK		zfs	rw,noatime,nfsv4acls	 0 0
 TANK/barry		/mnt/TANK/barry		zfs	rw,noatime,nfsv4acls	 0 0

Checking for uids of 0:
root 0

Checking for passwordless accounts:

Checking login.conf permissions:

Checking for ports with mismatched checksums:

freenas.WORKGROUP kernel log messages:
+++ /tmp/security.vxG5TZCL	2017-08-20 03:01:03.000000000 -0400
+ugen2.3: <Logitech> at usbus2
+ukbd0: <USB Keyboard> on usbus2
+kbd2 at ukbd0
+uhid0: <USB Keyboard> on usbus2
+ugen2.3: <Logitech> at usbus2 (disconnected)
+ukbd0: at uhub4, port 3, addr 3 (disconnected)
+uhid0: at uhub4, port 3, addr 3 (disconnected)
+ugen2.3: <Logitech> at usbus2
+ukbd0: <USB Keyboard> on usbus2
+kbd2 at ukbd0
+uhid0: <USB Keyboard> on usbus2
+ugen2.3: <Logitech> at usbus2 (disconnected)
+ukbd0: at uhub4, port 3, addr 3 (disconnected)
+uhid0: at uhub4, port 3, addr 3 (disconnected)
+(ada0:ahcich2:0:0:0): lost device
+GEOM_ELI: Detached ada6p1.eli on last close.
+(ada6:ahcich1:0:0:0): lost device
+(ada6:ahcich1:0:0:0): removing device entry
+ugen2.3: <Logitech> at usbus2
+ukbd0: <USB Keyboard> on usbus2
+kbd2 at ukbd0
+uhid0: <USB Keyboard> on usbus2
+ugen2.4: <Logitech> at usbus2
+ums0: <Logitech USB Optical Mouse, class 0/0, rev 2.00/72.00, addr 4> on usbus2
+ums0: 3 buttons and [XYZ] coordinates ID=0
+ugen2.3: <Logitech> at usbus2 (disconnected)
+ukbd0: at uhub4, port 3, addr 3 (disconnected)
+uhid0: at uhub4, port 3, addr 3 (disconnected)
+ugen2.4: <Logitech> at usbus2 (disconnected)
+ums0: at uhub4, port 4, addr 4 (disconnected)
+swap_pager: I/O error - pagein failed; blkno 70,size 4096, error 6
+vm_fault: pager read error, pid 2840 (python)
+pid 2840 (python), uid 0: exited on signal 11

freenas.WORKGROUP login failures:

freenas.WORKGROUP refused connections:

-- End of security output --


NOTE: The following series of messages is expected, and is caused by a KVM switch:
+ugen2.3: <Logitech> at usbus2
+ukbd0: <USB Keyboard> on usbus2
+kbd2 at ukbd0
+uhid0: <USB Keyboard> on usbus2
+ugen2.3: <Logitech> at usbus2 (disconnected)
+ukbd0: at uhub4, port 3, addr 3 (disconnected)
+uhid0: at uhub4, port 3, addr 3 (disconnected)

I have 4 computers on a KVM switch (Windows Box, 2 Linux Boxes, FreeNAS), so every time I switch from machine to machine the mouse/keyboard come and go. I have been doing this for several years without any problem.

The following messages were caused by an intentional "Detach" executed from the GUI followed by unplugging the drive.
+GEOM_ELI: Detached ada6p1.eli on last close.
+(ada6:ahcich1:0:0:0): lost device
+(ada6:ahcich1:0:0:0): removing device entry

I am not sure what this means?
+++ /tmp/security.JumAse6s 2017-08-20 03:01:02.000000000 -0400
@@ -4,7 +4,6 @@



Here are the last few lines of dmesg:
Code:
kbd2 at ukbd0
uhid0: <USB Keyboard> on usbus2
ugen2.3: <Logitech> at usbus2 (disconnected)
ukbd0: at uhub4, port 3, addr 3 (disconnected)
uhid0: at uhub4, port 3, addr 3 (disconnected)
(ada0:ahcich2:0:0:0): lost device
GEOM_ELI: Detached ada6p1.eli on last close.
(ada6:ahcich1:0:0:0): lost device
(ada6:ahcich1:0:0:0): removing device entry
ugen2.3: <Logitech> at usbus2
ukbd0: <USB Keyboard> on usbus2
kbd2 at ukbd0
uhid0: <USB Keyboard> on usbus2
ugen2.4: <Logitech> at usbus2
ums0: <Logitech USB Optical Mouse, class 0/0, rev 2.00/72.00, addr 4> on usbus2
ums0: 3 buttons and [XYZ] coordinates ID=0
ugen2.3: <Logitech> at usbus2 (disconnected)
ukbd0: at uhub4, port 3, addr 3 (disconnected)
uhid0: at uhub4, port 3, addr 3 (disconnected)
ugen2.4: <Logitech> at usbus2 (disconnected)
ums0: at uhub4, port 4, addr 4 (disconnected)
swap_pager: I/O error - pagein failed; blkno 70,size 4096, error 6
vm_fault: pager read error, pid 2840 (python)
pid 2840 (python), uid 0: exited on signal 11

Other than the device lost message there is no hint of anything happening.

After I noticed the error, I detached the backup for safekeeping and stopped the scrub with zpool scrub -s TANK

The system is sitting idle with the power still on and a console shell open so as not to destroy any information. Anything else I should check?

How can I determine why the drive became detached?

System History/Possible explanations:
It is possible that adding the hot swap disk caddy may have loosened a cable on /dev/ada0 (although the pool did run fine for a couple of days).
It is also possible a may have some freak memory error (not running ECC memory - system is built with an ASUS consumer grade motherboard.) The system has been very stable over the last year. Only one crash caused by a crash on a windows box that was connected by a CIFS share. When the Win box hung, FreeNAS got locked up and I had to reset it. Other than that been rock solid - no trouble at all.

Unless someone has a better (safer suggestion), my plan is to
  1. shut down, reseat the cable on ada0
  2. restart and see if the BIOS recognized the disk (if not RMA!)
  3. if disk recognized, attempt to do a smartctl -x /dev/ada0 to see what is going on (if something obvious RMA/replace disk)
  4. Run a long self test (if something found RMA/replace disk)
  5. If nothing found to this point run memtest for an hour or so
  6. If all ok zpool clear TANK and run another scrub.
  7. If OK return system to production and observe carefully for a week or two
BTW Is there a way to run a long disk test and memtest at the same time?

Thanks in advance for any assistance/suggestions/recommendations.
I don't know why you would want to run memtest. Just see what is going on with the drive.

Sent from my SAMSUNG-SGH-I537 using Tapatalk
 

NASbox

Guru
Joined
May 8, 2012
Messages
650
I don't know why you would want to run memtest. Just see what is going on with the drive.
Am I wrong in assuming a memory error could be responsible for the drive dropping off?

Should I just shut down the system at this point?
Any diagnostic information I haven't looked at?
Any SAFE way to try to reattach ada0 without a reboot?
 

rs225

Guru
Joined
Jun 28, 2014
Messages
878
This looks like a drive or cabling problem, not memory. A smartctl -a /dev/ada0 is probably just as good as -x, especially if you are going to post it. A short test would be good also. Long test is only needed if everything else looks good and you aren't going to replace the drive immediately.
 

NASbox

Guru
Joined
May 8, 2012
Messages
650
Anything else I need to look at/check before powering down?
Or should I just go ahead and power down.

Thanks... sorry I've never lost a drive like this before, so it's new territory.
 

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,080
From the zpool status you posted, it doesn't look like the drive is not being detected at a hardware level, it looks like ZFS may have dropped it from the pool because of errors. Can you post the output of camcontrol devlist and glabel status ?
These will help verify which device is having a problem. You can also post the results of the smartctl -a /dev/ada? (using the appropriate drive number) so we can try to determine the nature of the fault with the drive.
I would say it is definitely a bad drive, but lets see what kind of defect, if we can.
 

NASbox

Guru
Joined
May 8, 2012
Messages
650
From the zpool status you posted, it doesn't look like the drive is not being detected at a hardware level, it looks like ZFS may have dropped it from the pool because of errors. Can you post the output of camcontrol devlist and glabel status ?
These will help verify which device is having a problem. You can also post the results of the smartctl -a /dev/ada? (using the appropriate drive number) so we can try to determine the nature of the fault with the drive.
I would say it is definitely a bad drive, but lets see what kind of defect, if we can.

Thanks for the reply Chris. Here is the output from the command you requested. It's pretty obvious to me, the drive is off the system.

camcontrol devlist
Code:
#><WDC WD60EFRX-68MYMN1 82.00A82>	at scbus3 target 0 lun 0 (pass1,ada1)
<WDC WD60EFRX-68MYMN1 82.00A82>	at scbus4 target 0 lun 0 (pass2,ada2)
<WDC WD60EFRX-68MYMN1 82.00A82>	at scbus5 target 0 lun 0 (pass3,ada3)
<Hitachi HDS724040ALE640 MJAOA3B0>  at scbus6 target 0 lun 0 (pass4,ada4)
<Hitachi HDS724040ALE640 MJAOA3B0>  at scbus7 target 0 lun 0 (pass5,ada5)
<Lexar JumpDrive 1100>			 at scbus8 target 0 lun 0 (pass6,da0)
<Corsair Voyager VEGA 000B>		at scbus9 target 0 lun 0 (pass7,da1)


glabel status
Code:
									  Name  Status  Components
gptid/73fc17c0-1916-11e5-b2b5-c860006d863b	 N/A  ada0p2
gptid/bcd021f7-dbd8-11e4-adc9-c860006d863b	 N/A  ada1p2
gptid/fcd3d3cb-f747-11e4-95cc-c860006d863b	 N/A  ada2p2
gptid/76e6e5f1-0f39-11e5-8bc3-c860006d863b	 N/A  ada3p2
gptid/eb2ee48c-a398-11e2-bc5c-c860006d863b	 N/A  ada4p2
gptid/ec0615be-a398-11e2-bc5c-c860006d863b	 N/A  ada5p2
							  ufs/USBDRIVE	 N/A  da0p2
							 ufs/FreeNASs3	 N/A  da1s3
							 ufs/FreeNASs4	 N/A  da1s4
							ufs/FreeNASs1a	 N/A  da1s1a
					ufsid/50c8c7da3400b84f	 N/A  da1s2a
							ufs/FreeNASs2a	 N/A  da1s2a


smartctl -a /dev/ada0
Code:
smartctl 5.43 2012-06-30 r3573 [FreeBSD 8.3-RELEASE-p6 amd64] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

/dev/ada0: No such file or directory
Smartctl: please specify device type with the -d option.

Use smartctl -h to get a usage summary


Anything else I need to do/try before I powerdown the system and check the connections?

I can do a lot more investigation once I power down/up again, but I just want to make sure I'm not loosing any information before I proceed to power down.

Input/suggestions please? Thanks.
 

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,080
At this point, I would shut it down and check the connection, but I kind of doubt the cable came loose. When you power back up, check in the BIOS to see if the drive is listed. The way this all looks, I would suspect the PCB on the drive failed. I just had a WD Red in a system at work do that. It actually showed up in the BIOS but it never came ready where the OS would detect it and try to use it.
From the way this looks, I would say it is time to start the RMA process on that drive.
 

NASbox

Guru
Joined
May 8, 2012
Messages
650
I shut down and the shutdown process hung:

Code:
Fatal trap 12: page fault while in kernel mode
cpuid =1; apic id = 02
fault virtual address = 0x204
fault code			   = supervisor read data, page not present


index.php


I suspect this was caused by the loss of the swap area on /dev/ada0.

I ran a short test and then generated the requested diagnostic output.

smartctl -a /dev/ada0
Code:
smartctl 5.43 2012-06-30 r3573 [FreeBSD 8.3-RELEASE-p6 amd64] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:	 WDC WD60EFRX-68MYMN1
Serial Number:	WD-WX21D15A7LXN\
LU WWN Device Id: 5 0014ee 2b688b128
Firmware Version: 82.00A82
User Capacity:	6,001,175,126,016 bytes [6.00 TB]
Sector Sizes:	 512 bytes logical, 4096 bytes physical
Device is:		Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  ACS-2 (unknown minor revision code: 0x001f)
Local Time is:	Sun Aug 20 18:35:15 2017 EDT
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:				( 1904) 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:		( 673) 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   200   200   051	Pre-fail  Always	   -	   0
  3 Spin_Up_Time			0x0027   229   198   021	Pre-fail  Always	   -	   7525
  4 Start_Stop_Count		0x0032   100   100   000	Old_age   Always	   -	   209
  5 Reallocated_Sector_Ct   0x0033   200   200   140	Pre-fail  Always	   -	   0
  7 Seek_Error_Rate		 0x002e   100   253   000	Old_age   Always	   -	   0
  9 Power_On_Hours		  0x0032   077   077   000	Old_age   Always	   -	   16919
10 Spin_Retry_Count		0x0032   100   100   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	   -	   36
192 Power-Off_Retract_Count 0x0032   200   200   000	Old_age   Always	   -	   10
193 Load_Cycle_Count		0x0032   194   194   000	Old_age   Always	   -	   19164
194 Temperature_Celsius	 0x0022   111   101   000	Old_age   Always	   -	   41
196 Reallocated_Event_Count 0x0032   200   200   000	Old_age   Always	   -	   0
197 Current_Pending_Sector  0x0032   200   200   000	Old_age   Always	   -	   0
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   200   200   000	Old_age   Offline	  -	   0

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  Short offline	   Completed without error	   00%	 16918		 -
# 2  Extended offline	Completed without error	   00%		85		 -
# 3  Extended offline	Completed without error	   00%		51		 -
# 4  Extended offline	Completed without error	   00%		12		 -
# 5  Short offline	   Completed without error	   00%		 0		 -
# 6  Short offline	   Completed without error	   00%		 0		 -
# 7  Conveyance offline  Completed without error	   00%		 0		 -

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
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.


camcontrol devlist
Code:
<WDC WD60EFRX-68MYMN1 82.00A82>	at scbus2 target 0 lun 0 (pass0,ada0)
<WDC WD60EFRX-68MYMN1 82.00A82>	at scbus3 target 0 lun 0 (pass1,ada1)
<WDC WD60EFRX-68MYMN1 82.00A82>	at scbus4 target 0 lun 0 (pass2,ada2)
<WDC WD60EFRX-68MYMN1 82.00A82>	at scbus5 target 0 lun 0 (pass3,ada3)
<Hitachi HDS724040ALE640 MJAOA3B0>  at scbus6 target 0 lun 0 (pass4,ada4)
<Hitachi HDS724040ALE640 MJAOA3B0>  at scbus7 target 0 lun 0 (pass5,ada5)
<Lexar JumpDrive 1100>			 at scbus8 target 0 lun 0 (pass6,da0)
<Corsair Voyager VEGA 000B>		at scbus9 target 0 lun 0 (pass7,da1)



glabel status
Code:
									  Name  Status  Components
gptid/73fc17c0-1916-11e5-b2b5-c860006d863b	 N/A  ada0p2
gptid/bcd021f7-dbd8-11e4-adc9-c860006d863b	 N/A  ada1p2
gptid/fcd3d3cb-f747-11e4-95cc-c860006d863b	 N/A  ada2p2
gptid/76e6e5f1-0f39-11e5-8bc3-c860006d863b	 N/A  ada3p2
gptid/eb2ee48c-a398-11e2-bc5c-c860006d863b	 N/A  ada4p2
gptid/ec0615be-a398-11e2-bc5c-c860006d863b	 N/A  ada5p2
							  ufs/USBDRIVE	 N/A  da0p2
							 ufs/FreeNASs3	 N/A  da1s3
							 ufs/FreeNASs4	 N/A  da1s4
							ufs/FreeNASs1a	 N/A  da1s1a
					ufsid/50c8c7da3400b84f	 N/A  da1s2a
							ufs/FreeNASs2a	 N/A  da1s2a


Any good reason not to just do a zpool reset and then another scrub?
 

Attachments

  • FreeNAS Crash.jpg
    FreeNAS Crash.jpg
    83.1 KB · Views: 1,250
Last edited:

Stux

MVP
Joined
Jun 2, 2016
Messages
4,419
At this point, I would shut it down and check the connection, but I kind of doubt the cable came loose. When you power back up, check in the BIOS to see if the drive is listed. The way this all looks, I would suspect the PCB on the drive failed. I just had a WD Red in a system at work do that. It actually showed up in the BIOS but it never came ready where the OS would detect it and try to use it.
From the way this looks, I would say it is time to start the RMA process on that drive.

Yep. Had an IronWolf 4TB fail after three weeks like this. Just sort of failed over a few hours as then disappeared
 

NASbox

Guru
Joined
May 8, 2012
Messages
650
Yep. Had an IronWolf 4TB fail after three weeks like this. Just sort of failed over a few hours as then disappeared
Just wondering if the drive came back, or if it stayed gone?
 

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,080
Code:
9 Power_On_Hours		 0x0032 077 077 000	Old_age Always	 -	 16919

193 Load_Cycle_Count		0x0032 194 194 000	Old_age Always	 -	 19164


Your SMART status says the load cycle count is higher than the power on hours. Are you doing some sort of spin-down or power saving feature here? That could account for the premature failure.
Even though this drive came back and you can see it now to get SMART status, I don't know if I would trust it.
What does the zpool status say?
 

NASbox

Guru
Joined
May 8, 2012
Messages
650
Code:
9 Power_On_Hours		 0x0032 077 077 000	Old_age Always	 -	 16919
193 Load_Cycle_Count		0x0032 194 194 000	Old_age Always	 -	 19164

Your SMART status says the load cycle count is higher than the power on hours. Are you doing some sort of spin-down or power saving feature here? That could account for the premature failure.

Even though this drive came back and you can see it now to get SMART status, I don't know if I would trust it.
You were sharp to notice that. I don't know if the "spindown" settings got corrupted or are uncorrectly set. I believe that the WD drives have a habit of "unloading" during long periods of idle-I'm not sure if the drive spins down, or the heads just get retracted. (I have a job that snapshots a smartctl -a on all drives each night, and saves them. This behaviour has been going on since the day the drive was installed (over 700 days ago) - complete history attached. IIRC, the rated LCC is 300K - at the current rate, the drives would be able to spin for about 30 years before the reach the rated value of 300K. (I have seen windows blow a drive over 300K in a year!) If you know any way to turn this off, I'd love to know.
Code:
193 Load_Cycle_Count		0x0032   200   200   000	Old_age   Always	   -	   3
193 Load_Cycle_Count		0x0032   200   200   000	Old_age   Always	   -	   5
193 Load_Cycle_Count		0x0032   200   200   000	Old_age   Always	   -	   7
193 Load_Cycle_Count		0x0032   200   200   000	Old_age   Always	   -	   7
193 Load_Cycle_Count		0x0032   200   200   000	Old_age   Always	   -	   27
193 Load_Cycle_Count		0x0032   200   200   000	Old_age   Always	   -	   52
193 Load_Cycle_Count		0x0032   200   200   000	Old_age   Always	   -	   73
193 Load_Cycle_Count		0x0032   200   200   000	Old_age   Always	   -	   86
193 Load_Cycle_Count		0x0032   200   200   000	Old_age   Always	   -	   106
193 Load_Cycle_Count		0x0032   200   200   000	Old_age   Always	   -	   118
193 Load_Cycle_Count		0x0032   200   200   000	Old_age   Always	   -	   137
193 Load_Cycle_Count		0x0032   200   200   000	Old_age   Always	   -	   149
193 Load_Cycle_Count		0x0032   200   200   000	Old_age   Always	   -	   169
193 Load_Cycle_Count		0x0032   200   200   000	Old_age   Always	   -	   181
193 Load_Cycle_Count		0x0032   200   200   000	Old_age   Always	   -	   199
193 Load_Cycle_Count		0x0032   200   200   000	Old_age   Always	   -	   213
193 Load_Cycle_Count		0x0032   200   200   000	Old_age   Always	   -	   238
193 Load_Cycle_Count		0x0032   200   200   000	Old_age   Always	   -	   269
193 Load_Cycle_Count		0x0032   200   200   000	Old_age   Always	   -	   297

What does the zpool status say?

UPDATE: After restarting the system, I noticed that the system cleared the error without my intervention.
zpool status TANK
Code:
  pool: TANK
state: ONLINE
  scan: scrub canceled on Sun Aug 20 02:49:20 2017
config:

		NAME											STATE	 READ WRITE CKSUM
		TANK											ONLINE	   0	 0	 0
		  raidz2-0									  ONLINE	   0	 0	 0
			gptid/73fc17c0-1916-11e5-b2b5-c860006d863b  ONLINE	   0	 0	 0
			gptid/bcd021f7-dbd8-11e4-adc9-c860006d863b  ONLINE	   0	 0	 0
			gptid/fcd3d3cb-f747-11e4-95cc-c860006d863b  ONLINE	   0	 0	 0
			gptid/76e6e5f1-0f39-11e5-8bc3-c860006d863b  ONLINE	   0	 0	 0

errors: No known data errors
 

Attachments

  • FreeNAS ada0 193LCC.txt
    64.1 KB · Views: 397
Last edited:

Stux

MVP
Joined
Jun 2, 2016
Messages
4,419

Stux

MVP
Joined
Jun 2, 2016
Messages
4,419
UPDATE: After restarting the system, I noticed that the system cleared the error without my intervention.

zpool status TANK
Code:
  pool: TANK
state: ONLINE
  scan: scrub canceled on Sun Aug 20 02:49:20 2017
config:

		NAME											STATE	 READ WRITE CKSUM
		TANK											ONLINE	   0	 0	 0
		  raidz2-0									  ONLINE	   0	 0	 0
			gptid/73fc17c0-1916-11e5-b2b5-c860006d863b  ONLINE	   0	 0	 0
			gptid/bcd021f7-dbd8-11e4-adc9-c860006d863b  ONLINE	   0	 0	 0
			gptid/fcd3d3cb-f747-11e4-95cc-c860006d863b  ONLINE	   0	 0	 0
			gptid/76e6e5f1-0f39-11e5-8bc3-c860006d863b  ONLINE	   0	 0	 0

errors: No known data errors

Errors get cleared on restart. Scrub the pool.
 

Chris Moore

Hall of Famer
Joined
May 2, 2015
Messages
10,080

NASbox

Guru
Joined
May 8, 2012
Messages
650
I just started a scrub so we'll see what happens.

Given the smart data is OK, is it possible the issue is the cabling or the controller on the motherboard?
If so is there any way to determine the cause with certainty?

I'm also wondering if the problem could have been caused by a crash?
As I recall a crashed SAMBA connection caused FreeNAS to hang so that I had to reset it.

Assuming the scrub passes what should I do going forward?
 

Stux

MVP
Joined
Jun 2, 2016
Messages
4,419
Make sure you have short and long smart tests scheduled, and keep an eye on it.
 

NASbox

Guru
Joined
May 8, 2012
Messages
650
Make sure you have short and long smart tests scheduled, and keep an eye on it.

Will do - at least in the short term.

Given that the server does fairly light duty, I'm wondering if a lot of self tests/scrubs on a routine basis may actually cause problems?

Is scrub a read only operation, or does it "refresh" data by reading and rewriting? What about self test?
 

Stux

MVP
Joined
Jun 2, 2016
Messages
4,419
I run twice-weekly short tests and fortnightly long. Scrubs are alternate fortnights

Scrubs are generally read only. Unless there's an error.
 
Status
Not open for further replies.
Top