disk disappeared :(

[Athanasios Kakargias]

I own a HP Microserver and have a zfs raidz1 with 3xWD 2TB drives (WD2003FYYS ) and one just dissapeared...

pool status:

Show

Checking status of zfs pools:
NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT
razor 5.45T 1.72T 3.73T 31% 1.00x DEGRADED /mnt
zingle 464G 420G 44.1G 90% 1.00x ONLINE /mnt

pool: razor
state: DEGRADED
status: One or more devices has been removed by the administrator.
Sufficient replicas exist for the pool to continue functioning in a
degraded state.
action: Online the device using 'zpool online' or replace the device with
'zpool replace'.
scan: scrub repaired 0 in 2h4m with 0 errors on Sun Feb 23 07:04:36 2014
config:

NAME STATE READ WRITE CKSUM
razor DEGRADED 0 0 0
raidz1-0 DEGRADED 0 0 0
gptid/43deba0c-6cf8-11e3-a53b-3c4a9279bf49 ONLINE 0 0 0
4918402034610113019 REMOVED 0 0 0 was /dev/gptid/9b64c79d-6d98-11e3-889a-3c4a9279bf49
gptid/e5d034f4-6dc5-11e3-9697-3c4a9279bf49 ONLINE 0 0 0

errors: No known data errors

pool: zingle
state: ONLINE
status: One or more devices are configured to use a non-native block size.
Expect reduced performance.
action: Replace affected devices with devices that support the
configured block size, or migrate data to a properly configured
pool.
scan: scrub repaired 0 in 2h3m with 0 errors on Fri Jan 24 07:03:10 2014
config:

NAME STATE READ WRITE CKSUM
zingle ONLINE 0 0 0
ada0 ONLINE 0 0 0 block size: 512B configured, 4096B native

errors: No known data errors

-- End of daily output --

kernel log below:

Show

micronas.local kernel log messages:
> (ada2:ahcich2:0:0:0): lost device
> swap_pager: I/O error - pagein failed; blkno 928,size 32768, error 6
> vm_fault: pager read error, pid 49380 (Plex Media Server)
> pid 49380 (Plex Media Server), uid 972: exited on signal 11
> cam_periph_alloc: attempt to re-allocate valid device ada2 rejected flags 0x18 refcount 2
> adaasync: Unable to attach to new device due to status 0x6
> cam_periph_alloc: attempt to re-allocate valid device ada2 rejected flags 0x18 refcount 2
> adaasync: Unable to attach to new device due to status 0x6
> cam_periph_alloc: attempt to re-allocate valid device ada2 rejected flags 0x18 refcount 2
> adaasync: Unable to attach to new device due to status 0x6
> cam_periph_alloc: attempt to re-allocate valid device ada2 rejected flags 0x18 refcount 2
> adaasync: Unable to attach to new device due to status 0x6
> cam_periph_alloc: attempt to re-allocate valid device ada2 rejected flags 0x18 refcount 2
> adaasync: Unable to attach to new device due to status 0x6
> cam_periph_alloc: attempt to re-allocate valid device ada2 rejected flags 0x18 refcount 2
> adaasync: Unable to attach to new device due to status 0x6
> cam_periph_alloc: attempt to re-allocate valid device ada2 rejected flags 0x18 refcount 2
> adaasync: Unable to attach to new device due to status 0x6
> cam_periph_alloc: attempt to re-allocate valid device ada2 rejected flags 0x18 refcount 2
> adaasync: Unable to attach to new device due to status 0x6
> cam_periph_alloc: attempt to re-allocate valid device ada2 rejected flags 0x18 refcount 2
> adaasync: Unable to attach to new device due to status 0x6
> cam_periph_alloc: attempt to re-allocate valid device ada2 rejected flags 0x18 refcount 2
> adaasync: Unable to attach to new device due to status 0x6
> (noperiph:ahcich2:0:-1:-1): rescan already queued
> cam_periph_alloc: attempt to re-allocate valid device ada2 rejected flags 0x18 refcount 2
> adaasync: Unable to attach to new device due to status 0x6
> cam_periph_alloc: attempt to re-allocate valid device ada2 rejected flags 0x18 refcount 2
> adaasync: Unable to attach to new device due to status 0x6
> cam_periph_alloc: attempt to re-allocate valid device ada2 rejected flags 0x18 refcount 2
> adaasync: Unable to attach to new device due to status 0x6
> cam_periph_alloc: attempt to re-allocate valid device ada2 rejected flags 0x18 refcount 2
> adaasync: Unable to attach to new device due to status 0x6
> cam_periph_alloc: attempt to re-allocate valid device ada2 rejected flags 0x18 refcount 2
> adaasync: Unable to attach to new device due to status 0x6
> (noperiph:ahcich2:0:-1:-1): rescan already queued
> cam_periph_alloc: attempt to re-allocate valid device ada2 rejected flags 0x18 refcount 2
> adaasync: Unable to attach to new device due to status 0x6
> cam_periph_alloc: attempt to re-allocate valid device ada2 rejected flags 0x18 refcount 2
> adaasync: Unable to attach to new device due to status 0x6
> cam_periph_alloc: attempt to re-allocate valid device ada2 rejected flags 0x18 refcount 2
> adaasync: Unable to attach to new device due to status 0x6

-- End of security output --

It didn't show up after a reboot, and I even put it in another bay, as I run it headless, and have no desktop to check the drive, is it safe to assume the drive to be dead?

 

[Yatti420]

Have you checked to see if the drive is dead? Nothing in BIOS about it?

 

[Athanasios Kakargias]

just found a monitor to go to bios, drive appears now on bios and on boot has returned back on the pool.
zpool status now shows:
pool: razor
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://illumos.org/msg/ZFS-8000-9P
scan: resilvered 20K in 0h0m with 0 errors on Tue Mar 4 16:56:59 2014
config:

NAME STATE READ WRITE CKSUM
razor ONLINE 0 0 0
raidz1-0 ONLINE 0 0 0
gptid/43deba0c-6cf8-11e3-a53b-3c4a9279bf49 ONLINE 0 0 0
gptid/9b64c79d-6d98-11e3-889a-3c4a9279bf49 ONLINE 0 0 3
gptid/e5d034f4-6dc5-11e3-9697-3c4a9279bf49 ONLINE 0 0 0

errors: No known data errors
I have a smart long selftest job every 15 days or so, also they have a swap area, could it be that the drive went offline for a smart test at the same time with a swap request? and could not go back onine?

 

[Athanasios Kakargias]

here is a smart output on the drive... It seems ok?

Show

smartctl 6.2 2013-07-26 r3841 [FreeBSD 9.2-RELEASE amd64] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Western Digital RE4
Device Model: WDC WD2003FYYS-02W0B0
Firmware Version: 01.01D01
User Capacity: 2,000,398,934,016 bytes [2.00 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 7200 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 2.6, 3.0 Gb/s
Local Time is: Tue Mar 4 17:33:32 2014 EET
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: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
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: (29880) 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: ( 304) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x303f) 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 253 253 021 Pre-fail Always - 7650
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 239
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 080 080 000 Old_age Always - 14872
10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 199
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 82
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 156
194 Temperature_Celsius 0x0022 117 101 000 Old_age Always - 35
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 200 200 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% 13218 -
# 2 Short offline Completed without error 00% 12835 -
# 3 Short offline Completed without error 00% 12505 -
# 4 Short offline Completed without error 00% 12347 -
# 5 Short offline Completed without error 00% 12113 -
# 6 Short offline Completed without error 00% 11756 -
# 7 Short offline Completed without error 00% 11421 -
# 8 Short offline Completed without error 00% 10902 -
# 9 Short offline Completed without error 00% 10576 -
#10 Short offline Completed without error 00% 10194 -
#11 Short offline Completed without error 00% 9933 -
#12 Short offline Completed without error 00% 9584 -
#13 Short offline Completed without error 00% 9237 -
#14 Short offline Completed without error 00% 8855 -
#15 Short offline Completed without error 00% 8520 -

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.

here is my system info


FreeNAS-9.2.0-RELEASE-x64 (ab098f4)
Platform AMD Athlon(tm) II Neo N36L Dual-Core Processor
Memory 5066MB

 

[cyberjock]

1. That hard drive hasn't had a SMART test run in over 1500 hours.
2. You have less than the minimum RAM for ZFS. While probably not the cause of your problems, it can cause tons of other problems.

 

[Athanasios Kakargias]

1. It seems the drive was deselected from the smart job? anyway I run a short one from the console and said "passed" I don't really know how to read the values...
I run a long one now that will complete after 304 minutes. do I get back then...

btw does this look normal?:
Spin_Up_Time 0x0027 253 253 021 Pre-fail Always - 7650

2. Yes I know, that requirement used to be lower though when I set it up, some years ago wasn't it? I will upgrade it to 8 in time, as now with plex memory usage seems to peak to the ceiling at times...

 

[cyberjock]

When the long test finishes use pastebin to paste the output of smartctl -a /dev/XXXX and someone here will let you know what it all means.

Disk disappearing is what I call a "bad thing"(TM). You're doing the right thing by agressively looking for the cause.

 

[Athanasios Kakargias]

hopefully? I get some indication as drive is still under warranty. I would rather see HELLO_IAM_ABOUT_TO FAIL and RMA it, than be left in ALL_OK_FOR_NOW ...
Anyway I call it a night and get back tomorrow...
thanx for helping.

 

[Athanasios Kakargias]

here is a long test on the device...
I guess the values are normal, at least no errors reported?

Googling I found this

 

[cyberjock]

Yeah, those values are normal.

That post is a long explained version of what I was thinking might have happened to you. Unfortunately, the hard drive doesn't give any indication of the problem. So you need to look elsewhere. Basically your SATA controller, SATA cable, and PSU/cabling is suspect. I'd replace the SATA cable since that's the easiest and see if it happens again. If it does, then try the PSU since that's the next easiest. Lastly, if that doesn't work look at either getting a SATA/SAS controller or buying a different motherboard. :(

 

[Athanasios Kakargias]

that could be tough as they latch into hp microserver backplane, could a power spike be the cause? or the psu failing to provide enough power?
Going to check if there are loose cables somewhere...

Freenas versioning follows freebsd versioning? because on my link it appears that freebsd was patched since 9.1 ?