j.metts Posted January 9, 2012 Share Posted January 9, 2012 I have had a new drive go offline twice now. The first time I was able to shutdown, reseat all connections, and run a SMART report on it. Everything appeared to check out fine, so I had the drive rebuild itself. Everything was working just fine until I came back from a trip to see DISK_DSBL on the drive again. This time I looked in the syslog before shutting down (failed to do that the first time), and I found this portion about the drive. Am I having a power problem with this drive? I have a Corsair 450W running 6 drives. I am currently rebuilding everything on a new backup drive I had, but if this is a power issue, not sure if a new drive is the answer. Thanks for any help. Jan 7 09:38:34 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jan 7 09:38:34 Tower kernel: ata4.00: failed command: CHECK POWER MODE Jan 7 09:38:34 Tower kernel: ata4.00: cmd e5/00:00:00:00:00/00:00:00:00:00/00 tag 0 Jan 7 09:38:34 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jan 7 09:38:34 Tower kernel: ata4.00: status: { DRDY } Jan 7 09:38:34 Tower kernel: ata4: hard resetting link Jan 7 09:38:40 Tower kernel: ata4: link is slow to respond, please be patient (ready=0) Jan 7 09:38:44 Tower kernel: ata4: COMRESET failed (errno=-16) Jan 7 09:38:44 Tower kernel: ata4: hard resetting link Jan 7 09:38:50 Tower kernel: ata4: link is slow to respond, please be patient (ready=0) Jan 7 09:38:54 Tower kernel: ata4: COMRESET failed (errno=-16) Jan 7 09:38:54 Tower kernel: ata4: hard resetting link Jan 7 09:39:00 Tower kernel: ata4: link is slow to respond, please be patient (ready=0) Jan 7 09:39:29 Tower kernel: ata4: COMRESET failed (errno=-16) Jan 7 09:39:29 Tower kernel: ata4: limiting SATA link speed to 1.5 Gbps Jan 7 09:39:29 Tower kernel: ata4: hard resetting link Jan 7 09:39:34 Tower kernel: ata4: COMRESET failed (errno=-16) Jan 7 09:39:34 Tower kernel: ata4: reset failed, giving up Jan 7 09:39:34 Tower kernel: ata4.00: disabled Jan 7 09:39:34 Tower kernel: ata4: EH complete Here's the recent Smart Report on it too. Initially I thought the drive might have overheated, but I'm not sure how to read that in the Smart Report. Under the temp area it says worst is 095, but 95C? That can't be possible. smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD2001FASS-00W2B0 Serial Number: WD-WMAY00471750 Firmware Version: 01.00101 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sun Jan 8 19:39:39 2012 EST 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: (0x85) Offline data collection activity was aborted by an interrupting command from host. 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: (29700) 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: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3037) SCT Status supported. SCT Feature Control 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 - 1 3 Spin_Up_Time 0x0027 253 150 021 Pre-fail Always - 8300 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 33 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 100 100 000 Old_age Always - 390 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 - 19 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 13 193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 5235 194 Temperature_Celsius 0x0022 105 095 000 Old_age Always - 47 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 - 1 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 14 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% 390 - # 2 Short offline Completed without error 00% 390 - # 3 Short offline Completed without error 00% 389 - # 4 Short offline Completed without error 00% 389 - # 5 Short offline Completed without error 00% 191 - 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. Quote Link to comment
dgaschk Posted January 9, 2012 Share Posted January 9, 2012 It's not 95C. The current value of 105 corresponds to the raw value of 47C. A lower value is worse with failure at 0. Attach the entire syslog. zip it if needed. Quote Link to comment
j.metts Posted January 9, 2012 Author Share Posted January 9, 2012 See attached for the syslog. The syslog file was split due to the size it got with the constant spindown requests to the offline drive. syslog.txt.zip Quote Link to comment
j.metts Posted January 10, 2012 Author Share Posted January 10, 2012 Any thoughts with the syslog? Let me know if there is anything else I should provide. Thanks! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.