NAS Posted March 14, 2015 Share Posted March 14, 2015 Long story short my parity disk complained of errors and when I went to investigate it was dropped out and I couldn't access it. Not good but not the first time in my life ive seen a disk drop adn not actually be broken. So after a reboot the disk is back but not part of array. Obviously next test was a short self test which passed. In fact at this point if i hadnt seen it dropped I wouldn't have thought anything was wrong. Stupidly though I decided to run the extended self test under dynamix rather than console (stupid as in doing it for the first time via the gui on a questionable disk rather than stick to what i know). Its been stuck/sitting on 10% for about 30mins now. Is this lack of feedback/progress expected? Is this actually running what I thinki it is "smartctl --test=long ?" Open to any thoughts. For reference so far: WD RED 6TB Parity attached to port: sde ID# ATTRIBUTE NAME FLAG VALUE WORST THRESH TYPE UPDATED FAILED RAW VALUE 1 Raw Read Error Rate 0x002f 200 200 051 Pre-fail Always Never 0 3 Spin Up Time 0x0027 227 200 021 Pre-fail Always Never 7616 4 Start Stop Count 0x0032 100 100 000 Old age Always Never 39 5 Reallocated Sector Ct 0x0033 200 200 140 Pre-fail Always Never 0 7 Seek Error Rate 0x002e 200 200 000 Old age Always Never 0 9 Power On Hours 0x0032 096 096 000 Old age Always Never 3581 10 Spin Retry Count 0x0032 100 100 000 Old age Always Never 0 11 Calibration Retry Count 0x0032 100 253 000 Old age Always Never 0 12 Power Cycle Count 0x0032 100 100 000 Old age Always Never 3 192 Power-Off Retract Count 0x0032 200 200 000 Old age Always Never 0 193 Load Cycle Count 0x0032 200 200 000 Old age Always Never 1156 194 Temperature Celsius 0x0022 120 118 000 Old age Always Never 32 196 Reallocated Event Count 0x0032 200 200 000 Old age Always Never 0 197 Current Pending Sector 0x0032 200 200 000 Old age Always Never 0 198 Offline Uncorrectable 0x0030 100 253 000 Old age Offline Never 0 199 UDMA CRC Error Count 0x0032 200 200 000 Old age Always Never 0 200 Multi Zone Error Rate 0x0008 100 253 000 Old age Offline Never 0 Link to comment
bonienl Posted March 14, 2015 Share Posted March 14, 2015 The webGui does exactly the same thing as you would do on console: smartctl -t long /dev/$port and it uses smartctl -l selftest /dev/$port to read the progress of the selftest periodically ($port is the reference to the disk) Link to comment
NAS Posted March 14, 2015 Author Share Posted March 14, 2015 Thanks for the clarification. Spookily it just updated to 20%. Kudos Link to comment
bonienl Posted March 14, 2015 Share Posted March 14, 2015 Patience is your friend Moving away from the web page and returning later won't restore the progress display (webGUI simply forgets the test is running) - small caveat, Link to comment
NAS Posted March 14, 2015 Author Share Posted March 14, 2015 Seconds before oyu posted this I clicked away absent mindely. However I would have expected this to work still smartctl -l selftest /dev/sde smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.18.5-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === 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% 3580 - Do you know off hand of any way to recover progress? Link to comment
NAS Posted March 14, 2015 Author Share Posted March 14, 2015 Looks like my array has come up without parity which is fine because i wouldnt trust it anyway howrever this has kicked in the spin down So I believe the spin down has killed the smartctl test Sanity check: smartctl -l selftest /dev/sde smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.18.5-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === 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% 3580 - # ps aux | grep sma root 13815 0.0 0.0 5100 1672 pts/0 S+ 10:44 0:00 grep sma Link to comment
NAS Posted March 14, 2015 Author Share Posted March 14, 2015 This is interesting. Even though -l shows nothing trying to kick off a new one shows progress: # smartctl -t long /dev/sde smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.18.5-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF OFFLINE IMMEDIATE AND SELF-TEST SECTION === Can't start self-test without aborting current test (80% remaining), add '-t force' option to override, or run 'smartctl -X' to abort test. Link to comment
NAS Posted March 14, 2015 Author Share Posted March 14, 2015 Better way: # smartctl -c /dev/sde smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.18.5-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF READ SMART DATA SECTION === General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 248) Self-test routine in progress... 80% of test remaining. Total time to complete Offline data collection: ( 7784) 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: ( 731) 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. Link to comment
NAS Posted March 16, 2015 Author Share Posted March 16, 2015 For what it is worth every now and again Dynamix would realise a smart test was happening and catch the progress again. Its strange. Link to comment
bonienl Posted March 16, 2015 Share Posted March 16, 2015 For what it is worth every now and again Dynamix would realise a smart test was happening and catch the progress again. Its strange. I believe this can happen depending on the status messages returned by SMART, but need to look into the code for details, can't tell top of my head since this part was written some time ago ... Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.