Query failing drive

Status
Not open for further replies.

Sput

Dabbler
Joined
Jan 3, 2014
Messages
11
Afternoon all,

Ive had one of the daily reports that my system sends, and I think its telling me theres a problem with a disk:

pool: Data
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: scrub repaired 0 in 1h7m with 0 errors on Sun Feb 16 01:07:51 2014
config:

The scrub as you can see repaired nothing on sunday. Ive done a " smartclt -a /dev/ada3 " as this is a drive that had some checksum errors on, from logging into the GUI of the system. Below is the output from it:




[root@freenas] ~# smartctl -a /dev/ada3

smartctl 6.1 2013-03-16 r3800 [FreeBSD 9.1-STABLE amd64] (local build)

Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org



=== START OF INFORMATION SECTION ===

Model Family: Seagate Barracuda 7200.12

Device Model: ST31000528AS

Serial Number: 9VP23X4L

LU WWN Device Id: 5 000c50 019a19b01

Firmware Version: CC37

User Capacity: 1,000,204,886,016 bytes [1.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 T13/1699-D revision 4

SATA Version is: SATA 2.6, 3.0 Gb/s

Local Time is: Tue Mar 11 14:59:54 2014 GMT



==> WARNING: A firmware update for this drive may be available,

see the following Seagate web pages:

http://knowledge.seagate.com/articles/en_US/FAQ/207931en

http://knowledge.seagate.com/articles/en_US/FAQ/213891en



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: ( 121) The previous self-test completed having

the read element of the test failed.

Total time to complete Offline

data collection: ( 600) 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: ( 1) minutes.

Extended self-test routine

recommended polling time: ( 176) minutes.

Conveyance self-test routine

recommended polling time: ( 2) minutes.

SCT capabilities: (0x103f) SCT Status supported.

SCT Error Recovery Control supported.

SCT Feature Control supported.

SCT Data Table supported.



SMART Attributes Data Structure revision number: 10

Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE

1 Raw_Read_Error_Rate 0x000f 090 086 006 Pre-fail Always - 46349014

3 Spin_Up_Time 0x0003 095 094 000 Pre-fail Always - 0

4 Start_Stop_Count 0x0032 099 099 020 Old_age Always - 1982

5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0

7 Seek_Error_Rate 0x000f 074 060 030 Pre-fail Always - 26105367

9 Power_On_Hours 0x0032 088 088 000 Old_age Always - 10787

10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0

12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 991

183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0

184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0

187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 168

188 Command_Timeout 0x0032 100 099 000 Old_age Always - 12885098499

189 High_Fly_Writes 0x003a 098 098 000 Old_age Always - 2

190 Airflow_Temperature_Cel 0x0022 072 054 045 Old_age Always - 28 (Min/Max 26/34)

194 Temperature_Celsius 0x0022 028 046 000 Old_age Always - 28 (0 16 0 0 0)

195 Hardware_ECC_Recovered 0x001a 028 004 000 Old_age Always - 46349014

197 Current_Pending_Sector 0x0012 088 088 000 Old_age Always - 499

198 Offline_Uncorrectable 0x0010 088 088 000 Old_age Offline - 499

199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0

240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 155666794689911

241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 4255591489

242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 1411971293



SMART Error Log Version: 1

ATA Error Count: 132 (device log contains only the most recent five errors)

CR = Command Register [HEX]

FR = Features Register [HEX]

SC = Sector Count Register [HEX]

SN = Sector Number Register [HEX]

CL = Cylinder Low Register [HEX]

CH = Cylinder High Register [HEX]

DH = Device/Head Register [HEX]

DC = Device Command Register [HEX]

ER = Error register [HEX]

ST = Status register [HEX]

Powered_Up_Time is measured from power on, and printed as

DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,

SS=sec, and sss=millisec. It "wraps" after 49.710 days.



Error 132 occurred at disk power-on lifetime: 10736 hours (447 days + 8 hours)

When the command that caused the error occurred, the device was active or idle.



After command completion occurred, registers were:

ER ST SC SN CL CH DH

-- -- -- -- -- -- --

40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455



Commands leading to the command that caused the error were:

CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name

-- -- -- -- -- -- -- -- ---------------- --------------------

60 00 10 ff ff ff 4f 00 26d+15:43:40.201 READ FPDMA QUEUED

60 00 10 ff ff ff 4f 00 26d+15:43:40.201 READ FPDMA QUEUED

2f 00 01 10 00 00 00 00 26d+15:43:40.118 READ LOG EXT

60 00 10 ff ff ff 4f 00 26d+15:43:37.054 READ FPDMA QUEUED

60 00 10 ff ff ff 4f 00 26d+15:43:37.054 READ FPDMA QUEUED



Error 131 occurred at disk power-on lifetime: 10736 hours (447 days + 8 hours)

When the command that caused the error occurred, the device was active or idle.



After command completion occurred, registers were:

ER ST SC SN CL CH DH

-- -- -- -- -- -- --

40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455



Commands leading to the command that caused the error were:

CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name

-- -- -- -- -- -- -- -- ---------------- --------------------

60 00 10 ff ff ff 4f 00 26d+15:43:37.054 READ FPDMA QUEUED

60 00 10 ff ff ff 4f 00 26d+15:43:37.054 READ FPDMA QUEUED

2f 00 01 10 00 00 00 00 26d+15:43:36.971 READ LOG EXT

60 00 10 ff ff ff 4f 00 26d+15:43:33.924 READ FPDMA QUEUED

60 00 10 ff ff ff 4f 00 26d+15:43:33.924 READ FPDMA QUEUED



Error 130 occurred at disk power-on lifetime: 10736 hours (447 days + 8 hours)

When the command that caused the error occurred, the device was active or idle.



After command completion occurred, registers were:

ER ST SC SN CL CH DH

-- -- -- -- -- -- --

40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455



Commands leading to the command that caused the error were:

CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name

-- -- -- -- -- -- -- -- ---------------- --------------------

60 00 10 ff ff ff 4f 00 26d+15:43:33.924 READ FPDMA QUEUED

60 00 10 ff ff ff 4f 00 26d+15:43:33.924 READ FPDMA QUEUED

2f 00 01 10 00 00 00 00 26d+15:43:33.841 READ LOG EXT

60 00 10 ff ff ff 4f 00 26d+15:43:30.798 READ FPDMA QUEUED

60 00 10 ff ff ff 4f 00 26d+15:43:30.797 READ FPDMA QUEUED



Error 129 occurred at disk power-on lifetime: 10736 hours (447 days + 8 hours)

When the command that caused the error occurred, the device was active or idle.



After command completion occurred, registers were:

ER ST SC SN CL CH DH

-- -- -- -- -- -- --

40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455



Commands leading to the command that caused the error were:

CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name

-- -- -- -- -- -- -- -- ---------------- --------------------

60 00 10 ff ff ff 4f 00 26d+15:43:30.798 READ FPDMA QUEUED

60 00 10 ff ff ff 4f 00 26d+15:43:30.797 READ FPDMA QUEUED

2f 00 01 10 00 00 00 00 26d+15:43:30.694 READ LOG EXT

61 00 10 90 02 40 40 00 26d+15:43:27.662 WRITE FPDMA QUEUED

60 00 10 ff ff ff 4f 00 26d+15:43:27.662 READ FPDMA QUEUED



Error 128 occurred at disk power-on lifetime: 10736 hours (447 days + 8 hours)

When the command that caused the error occurred, the device was active or idle.



After command completion occurred, registers were:

ER ST SC SN CL CH DH

-- -- -- -- -- -- --

40 51 00 ff ff ff 0f Error: WP at LBA = 0x0fffffff = 268435455



Commands leading to the command that caused the error were:

CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name

-- -- -- -- -- -- -- -- ---------------- --------------------

61 00 10 90 02 40 40 00 26d+15:43:27.662 WRITE FPDMA QUEUED

60 00 10 ff ff ff 4f 00 26d+15:43:27.662 READ FPDMA QUEUED

60 00 10 ff ff ff 4f 00 26d+15:43:27.661 READ FPDMA QUEUED

60 00 10 90 02 40 40 00 26d+15:43:27.661 READ FPDMA QUEUED

ea 00 00 00 00 00 40 00 26d+15:43:27.594 FLUSH CACHE EXT



SMART Self-test log structure revision number 1

Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error

# 1 Extended offline Completed: read failure 90% 10772 1953523871

# 2 Short offline Completed: read failure 80% 10748 1953523871



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.


As, it has said :
SMART Self-test log structure revision number 1

Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error

# 1 Extended offline Completed: read failure 90% 10772 1953523871

# 2 Short offline Completed: read failure 80% 10748 1953523871

Is this telling me that it cannot read the drive, and therefore should be replaced?


Any light that someone could shed would be great, and sorry the posts so long, the smartctl outputted a lot of data.

Regards
Sput
 

Yatti420

Wizard
Joined
Aug 12, 2012
Messages
1,437
The drive is failing.. Ensure you replace the correct drive..
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,525
That's a drive that's failing.... fast.
 

Sput

Dabbler
Joined
Jan 3, 2014
Messages
11
Feared as much, two new WD reds on order from Amazon,

Find the failing drive, take the disk off line, remove and insert new drive, bring into the pool and start reslivering again. Ill dig out the manual for the correct process.

ada3 9VP23X4L
ada3p2 0 0 34

Disk with the 9VP..... serial is the one to go.

Thanks for the assistance
 

Sput

Dabbler
Joined
Jan 3, 2014
Messages
11
Afternoon all,

Ive taken delivery of the new drives, but I fear im being stupid. Im looking to put the failing disk to an offline status so as to remove it from the raidz2 before physically removing the disk.

The userguide says :
Before physically removing the failed device, go to Storage → Volumes → View Volumes → Volume Status and locate the failed disk. Once you have located the failed device in the GUI, perform the following steps

http://doc.freenas.org/index.php/Volumes#Replacing_a_Failed_Drive

However, I cant find the "volume status", I can go storage on the left hand side, view volume, and I then don't see a status button or link to then go to take a disk offline. The volume is reporting healthy, but I can see there is a disk problem, so where do I go to remove the disk from the volume?

Many thanks
James
 

Attachments

  • freenas volumes.png
    freenas volumes.png
    177.2 KB · Views: 295

Sput

Dabbler
Joined
Jan 3, 2014
Messages
11
Ahh fear not, I have clicked more buttons and theres an icon at the bottem of the screen to press to get that staus on screen. I have replaced drive and reslivering is taking place as we speak :D
 

Sput

Dabbler
Joined
Jan 3, 2014
Messages
11
Disk swapped, and raid happy again :D

Though theres some notices about disk 2 appearing too, so Ill keep a beady eye on that one.

Thanks to all.
 
Status
Not open for further replies.
Top