mobias1313 Posted March 21, 2013 Share Posted March 21, 2013 The smart report gets run by the preclear script. You can look in the logs folder and it will be in there. I use simple features and just look in logs under utils but you can also find it through the command line. I am not sure about using the regular webui but I would assume you can look there. The drive does not need to be in the array. However if you reboot the server the report will be gone. Quote Link to comment
RobJ Posted March 22, 2013 Share Posted March 22, 2013 thanks fore response. How do i run a smart report? i don't see an option in preclear_disk and because the drive isn't part of the array i cannot run a test using the webgui. Please see the Troubleshooting page, Obtaining a SMART report section. Quote Link to comment
Ockingshay Posted March 22, 2013 Share Posted March 22, 2013 thanks fore response. How do i run a smart report? i don't see an option in preclear_disk and because the drive isn't part of the array i cannot run a test using the webgui. Please see the Troubleshooting page, Obtaining a SMART report section. Thanks Rob, just what i was looking for, and here it is: root@Ruby:/boot# smartctl -a -A /dev/sdg smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD30EFRX-68AX9N0 Serial Number: WD-WMC1T1315735 Firmware Version: 80.00A80 User Capacity: 3,000,592,982,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 9 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Fri Mar 22 08:27:17 2013 GMT 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: ( 121) The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: (39120) 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: (0x70bd) 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 192 192 051 Pre-fail Always - 64 3 Spin_Up_Time 0x0027 191 176 021 Pre-fail Always - 5425 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 13 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 100 100 000 Old_age Always - 209 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 - 13 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 11 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 1 194 Temperature_Celsius 0x0022 128 118 000 Old_age Always - 22 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 3 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 100 253 000 Old_age Offline - 0 SMART Error Log Version: 1 ATA Error Count: 2 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 2 occurred at disk power-on lifetime: 65 hours (2 days + 17 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 d0 01 1c e3 Error: UNC at LBA = 0x031c01d0 = 52167120 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 00 80 01 1c e3 08 2d+17:30:42.860 READ DMA c8 00 00 80 02 1c e3 08 2d+17:30:42.839 READ DMA ec 00 00 00 00 00 a0 08 2d+17:30:42.839 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 2d+17:30:42.839 SET FEATURES [set transfer mode] Error 1 occurred at disk power-on lifetime: 17 hours (0 days + 17 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 d0 01 1c e3 Error: UNC at LBA = 0x031c01d0 = 52167120 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- c8 00 00 80 01 1c e3 08 17:06:33.759 READ DMA c8 00 00 80 02 1c e3 08 17:06:33.732 READ DMA ec 00 00 00 00 00 a0 08 17:06:31.503 IDENTIFY DEVICE ef 03 46 00 00 00 a0 08 17:06:31.503 SET FEATURES [set transfer mode] SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: read failure 90% 209 52130993 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. It doesn't look as though it can complete: Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: read failure 90% 209 52130993 stuck like that for hours now. Quote Link to comment
RobJ Posted March 22, 2013 Share Posted March 22, 2013 It doesn't look as though it can complete: Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: read failure 90% 209 52130993 stuck like that for hours now. Looks like you ran a short test just before obtaining this SMART report. Unlike the long test, the short test does not check the entire media surface (it would take hours), so it seems somewhat significant that even the short test found a bad sector. That should be statistically extremely rare, since it only spot checks a relatively very small number of tracks. Short and long SMART tests seem to stop at the first error they find, so it's probably not stuck here. Assuming you hadn't rebooted, what is significant is that you had no trouble accessing the drive and its SMART report. My previous guess from the syslog entries above was that the drive had been disabled for some reason, and therefore was just spewing errors from a stubborn and persistent module ignorant of that fact. This shows the drive is still operational in this session. So unless you are able to access the very first part of that huge syslog, especially when the very first drive errors occurred, we don't yet have a good clue as to what is wrong with it. The syslog errors look like interface issues, yet there are also bad sectors, a completely different and generally unrelated problem. The SMART report otherwise looked pretty good, relatively speaking. It shows 3 Pending sectors, which aren't good and will have to be dealt with, but cannot in any way explain the lack of progress on the PreRead, or the very long wait up til now, or the errors from that syslog piece above (or its 2.5GB size). I'd shut down and reboot, then grab a fresh copy of the syslog and a SMART report for this drive, then start a tail of the syslog in a separate console/Telnet/PuTTY session, then start a Preclear again of this drive. When/If the tail shows drive errors again, then grab another copy of the syslog and another SMART report and post them here. I'm also bothered by the rather high sector number (5,860,520,752) repeated in your syslog entries. It's a Preclear so no ReiserFS on the drive to explain a large seek, you report it is still at 0% of the PreRead, so no progress beyond the first few gigabytes of the drive, and the SMART report and test show no sectors beyond 52,167,120, within the first few gigabytes. So why are there errors accessing something so far out on the drive? Who or what is requesting that sector? Quote Link to comment
Joe L. Posted March 22, 2013 Share Posted March 22, 2013 I'm also bothered by the rather high sector number (5,860,520,752) repeated in your syslog entries. It's a Preclear so no ReiserFS on the drive to explain a large seek, you report it is still at 0% of the PreRead, so no progress beyond the first few gigabytes of the drive, and the SMART report and test show no sectors beyond 52,167,120, within the first few gigabytes. So why are there errors accessing something so far out on the drive? Who or what is requesting that sector? In addition to linearly reading blocks of 200 "cylinders" from the first sector to the last, both the pre-read and the post-read ALSO intersperse reading the very first sector, the very last sector, and three other random sectors in between for every 200 sectors read. basically, it works like this: Looping start # read a random block. # read the first block, bypassing the buffer cache by use of iflag=direct # read a random block. # read the last block, bypassing the buffer cache by use of iflag=direct # read a random block. # Then, read the next set of blocks linearly, from start to end, 200 "cylinders" at a time. Looping end It is easy for the pre-read or post-read to attempt to read a high numbered sector. Joe L. Quote Link to comment
RobJ Posted March 23, 2013 Share Posted March 23, 2013 In addition to linearly reading blocks of 200 "cylinders" from the first sector to the last, both the pre-read and the post-read ALSO intersperse reading the very first sector, the very last sector, and three other random sectors in between for every 200 sectors read. It is easy for the pre-read or post-read to attempt to read a high numbered sector. I never knew that! I had always thought that the PreRead was a completely linear, sequential read. That of course explains why it is a little slower than the write zeroes phase. Quote Link to comment
UhClem Posted March 23, 2013 Share Posted March 23, 2013 In addition to linearly reading blocks of 200 "cylinders" from the first sector to the last, both the pre-read and the post-read ALSO intersperse reading the very first sector, the very last sector, and three other random sectors in between for every 200 sectors read. basically, it works like this: Looping start # read a random block. # read the first block, bypassing the buffer cache by use of iflag=direct # read a random block. # read the last block, bypassing the buffer cache by use of iflag=direct # read a random block. # Then, read the next set of blocks linearly, from start to end, 200 "cylinders" at a time. Looping end Joe, I understand what you intend the above dislocation enhancement to accomplish, but I'd suggest that you (take a step back and really) think about it. What it does do is cause a slight (probably undetectable) seek noise, and increase the elapsed time of those phases (apparently noticeably). [Neither of which were your actual intent (but unavoidable side effects of your intent).] --UhClem Quote Link to comment
Joe L. Posted March 25, 2013 Share Posted March 25, 2013 In addition to linearly reading blocks of 200 "cylinders" from the first sector to the last, both the pre-read and the post-read ALSO intersperse reading the very first sector, the very last sector, and three other random sectors in between for every 200 sectors read. basically, it works like this: Looping start # read a random block. # read the first block, bypassing the buffer cache by use of iflag=direct # read a random block. # read the last block, bypassing the buffer cache by use of iflag=direct # read a random block. # Then, read the next set of blocks linearly, from start to end, 200 "cylinders" at a time. Looping end Joe, I understand what you intend the above dislocation enhancement to accomplish, but I'd suggest that you (take a step back and really) think about it. I had given it a lot of thought. The intent is to put the disk through a bit of a torture test. I purposely wanted the disk to do something other than a linear read. I knew it would take a bit more time. If the disk heads cannot be positioned to tracks, then I do not want the disk in my server. All the read results of the random and first/last sectors are thrown away, the entire idea is to force the disk to seek in a random way all over the disk. It definitely slows the process down a little. When reading (in the post-read phase) the same process is performed but the linear blocks contents analyzed. Don't worry, if a disk cannot seek, it will try again... I've rarely seen anyone with "seek" issues, and there probably have been thousands pre-cleared, but plenty with un-readable sectors where the checksum at the end of the sector does not match the contents of the sector. What it does do is cause a slight (probably undetectable) seek noise, and increase the elapsed time of those phases (apparently noticeably). [Neither of which were your actual intent (but unavoidable side effects of your intent).] --UhClem It was not my intent to make the disk make more audible noise... but it was my intent to exercise the disk and not just give it the easy task of a linear read. In fact, if you read the comments in the code it says: # Torture the disk, by reading random blocks from all over # calculate three (random) block numbers to be read somewhere # between block 1 and the max blocks on the drive, the goal is to shake the drive to an early # death if it has any mechanical issues, before it is holding data in our unRAID array. # read three random blocks from the disk and two fixed blocks. We use a random # blocks to try to ensure they are not in the cache memory # and to get the disk head moving randomly on the disk. # # the two fixed blocks are "direct" read, bypassing the buffer cache. They are the first # and last cylinder on the disk. # read a random block. # read the first block here, bypassing the buffer cache by use of iflag=direct # read a random block. # read the last block here, bypassing the buffer cache by use of iflag=direct # read a random block. # Now, also read the blocks linearly, from start to end, 200 cylinders at a time. Quote Link to comment
UhClem Posted March 26, 2013 Share Posted March 26, 2013 I had given it a lot of thought. I know you did, and I respect that. (I've been in that position many times, and) That is precisely why I said "take a step back"--meaning to try to get a different view/perspective. The intent is to put the disk through a bit of a torture test. I purposely wanted the disk to do something other than a linear read. I knew it would take a bit more time. If the disk heads cannot be positioned to tracks, then I do not want the disk in my server. But, here's the problem (as I see it): For a marginal drive, that little head-fake () might just cause the subsequent read attempt to be off-track and/or un-settled, BUT, if so, the drive will detect that; also, even if the drive doesn't detect that it hasn't settled sufficiently, and proceeds with the read, it will obviously get ECC failure. In all of those cases, the drive will merely RETRY the read (but this time with no/negligible prior head motion), and succeed. That little dislocation-dance (every 200 "cylinders") is just a (very minor) "waste of time" [looks like only about 0.5% extra], but has no chance of leading to any "feedback". Remember, a drive will RETRY a read 10-20 times before giving up and returning UNC to the driver (and the driver will RETRY 4-5 times before giving up and returning error to the calling program). However, I definitely agree that a new drive should really get a mechanical pummeling!! (But, instead of a couple of gnats, how about a swarm of horseflies.) I give my drives 5+ minutes of constant seeking, which also serves to verify that the drive's seek time is within spec. [seektest -n 20000 /dev/sdX -- my own little hack; don't know if Linux has something like it]. If any relevant component is sub-par, or inclined to be, now's the time to find out. To quote Crocodile Dundee: "Now, that's a torture test." (compared to the little twitches in preclear). I'll repeat this test occasionally (at least a few times per year). Following that initial torture session, I do a thorough surface integrity test (xfrtest ... /dev/sdX -- another personal hack). I try to repeat this once/twice per year, tracking the (very quantitative) results. --UhClem Quote Link to comment
Joe L. Posted March 26, 2013 Share Posted March 26, 2013 Believe it or not, I do appreciate the feedback. (I learned long ago I simply do not know it all) We have different approaches to the same desired result. The preclear script was originally written to do just that, pre-clear a drive and write the appropriate "preclear-signature" to the disk. Over time, the additional feature of performing a pre-read, and then a post-read were added to force the disk to identify sectors it could not read reliably. At that point, it became a tool to burn in a new disk and get it past the infant mortality stage before using it for precious data. Although your 5 minute "seek" test is as valid a test as any, it barely subjects the disk to the same temperature changes that occur over a far longer preclear cycle. Those same temperature changes will definitely exist when reconstructing a failed drive, or even when checking/calculating parity. For that reason, I do not feel a 5 minute is the definitive test of a drive's ability to seek when it gets warmer. Granted, rapid seeking might uncover some mechanical resonance related issue my less aggressive, but random seeking might not..., but they both test for much the same issue. Unfortunately, your custom seektest is not stock on unRAID (I had to use only what was distributed in the base unRAID distribution) Remember, I specifically wanted to the disk to identify unreadable sectors prior to the subsequent "writing" of zeros so SMART firmware could trigger a re-allocation of the sectors marked as un-readable. I still had to perform the read of the entire disk... so why not perform a bit of seek exercise too and the tiny additional time it added (your estimate .5%) did not change the preclear time very much, so it was far better than just a linear "read" of track after track. If the disk has difficulty in seeking, but recovers internally without posting an error externally, it does show in the speed of the preclear process and in the SMART report. There have been plenty of disks RMA'd because their preclear speed was a fraction of other equivalent drives. for a drive surface test, badblocks in full read/write 4 pass mode is as good as any and included with recent versions of unRAID. However, even it cannot be trusted... See here: http://lime-technology.com/forum/index.php?topic=23792.0 Joe L. Quote Link to comment
UhClem Posted March 27, 2013 Share Posted March 27, 2013 Note that I "stuck my nose in" here because it seemed like both RobJ and JoeL agreed that the time added to the script/cycle run (by the "feature" you described) was of some significance. It was only in the process of composing my previous (ie 2nd) response that I made an effort to quantify it (~0.5%). I'll bet neither of you realized it was so negligible--if I had, I wouldn't have bothered ... but then, look at all the fun we'd have missed. I still contend that a more apt rationale for adding the "feature" would be "I didn't want the drive to get bored." [Those 6 seeks every ~20 seconds are not going to affect the temperature. Here's a little experiment I just did. I had a spinning, but idle, drive at 30C. I did 5 minutes worth of flat-out reading (similar to your pre-read w/o the dance). When it finished, the drive was at 31C. I let the drive rest for 15 minutes; back to 30C. Then did 5 minutes of flat-out seeking (seektest); when finished, the drive was at 35C (that was ~1400 seeks per 20 sec.).] If the disk has difficulty in seeking, but recovers internally without posting an error externally, it does show in the speed of the preclear process and in the SMART report. No, it does not. In even the most perverse case, where each and every seek resulted in a read-retry, it would not even have doubled that overhead. Ie, instead of ~0.5% extra, it would have been <~1.0%. How is that going to "show in the speed of the preclear process"? Also, it does not show in a SMART report. (In anticipation of a misguided reply ... Seek_Error_Rate is not only undocumented, but also looks to not even be "implemented" on most drives (only Seagate)) There have been plenty of disks RMA'd because their preclear speed was a fraction of other equivalent drives. Huh? 995/1000 is a fraction, right? Seriously, any measurable speed difference was not caused in any way by the dislocation dance. ========== And, now for something completely different ... Here's a challenge: Add 10-20 lines to the preclear script that will cause the post-read phase to run just as fast as the pre-read phase for many/most users. For the rest, no change (but there would be such clamoring that they could easily/quickly join the party). [same exact functionality/results as now.] Who's wants to be the hero??? Think about it-- ~5-10 hours saved per cycle for a 2TB drive. [No questions ... just think ] --UhClem Quote Link to comment
actionfreak Posted March 30, 2013 Share Posted March 30, 2013 If I have an WD EARS drive with the jumper on the back and Unraid 4.7... should i use the -A option? Quote Link to comment
Kyrak Posted April 11, 2013 Share Posted April 11, 2013 I just precleared a drive that I had been using for a while in my Windows PC and got a lot of old age and a few prefail although they don't seem to be critical ones. Can you guys take a quick look and verify that this drive is still ok to put into production? : ========================================================================1.13 (Misc) : == invoked as: ./preclear_disk.sh /dev/sdf (Misc) : == ST33000651AS 9XK0KNPJ (Misc) : == Disk /dev/sdf has been successfully precleared (Misc) : == with a starting sector of 1 (Misc) : == Ran 1 cycle (Misc) : == (Misc) : == Using :Read block size = 8225280 Bytes (Misc) : == Last Cycle's Pre Read Time : 7:52:01 (105 MB/s) (Misc) : == Last Cycle's Zeroing time : 7:26:25 (112 MB/s) (Misc) : == Last Cycle's Post Read Time : 22:15:33 (37 MB/s) (Misc) : == Last Cycle's Total Time : 37:35:00 (Misc) : == (Misc) : == Total Elapsed Time 37:35:00 (Misc) : == (Misc) : == Disk Start Temperature: 30C (Misc) : == (Misc) : == Current Disk Temperature: 30C, (Misc) : == (Misc) : ============================================================================ (Misc) : ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf (Misc) : ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE (Misc) : Raw_Read_Error_Rate = 106 119 6 ok 10987154 (Misc) : Seek_Error_Rate = 63 61 30 ok 2572344 (Misc) : Spin_Retry_Count = 100 100 97 near_thresh 0 (Misc) : End-to-End_Error = 100 100 99 near_thresh 0 (Misc) : Airflow_Temperature_Cel = 70 70 45 near_thresh 30 (Misc) : Hardware_ECC_Recovered = 34 32 0 ok 240539654399634 (Misc) : No SMART attributes are FAILING_NOW (Misc) : (Misc) : 0 sectors were pending re-allocation before the start of the preclear. (Misc) : 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. (Misc) : 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. (Misc) : 0 sectors are pending re-allocation at the end of the preclear, (Misc) : the number of sectors pending re-allocation did not change. (Misc) : 0 sectors had been re-allocated before the start of the preclear. (Misc) : 0 sectors are re-allocated at the end of the preclear, (Misc) : the number of sectors re-allocated did not change. (Misc) : ============================================================================ (Misc) : ============================================================================ (Misc) : == (Misc) : == S.M.A.R.T Initial Report for /dev/sdf (Misc) : == (Misc) : Disk: /dev/sdf (Misc) : smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) (Misc) : Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net (Misc) : (Misc) : === START OF INFORMATION SECTION === (Misc) : Device Model: ST33000651AS (Misc) : Serial Number: 9XK0KNPJ (Misc) : Firmware Version: CC43 (Misc) : User Capacity: 3,000,592,982,016 bytes (Misc) : Device is: Not in smartctl database [for details use: -P showall] (Misc) : ATA Version is: 8 (Misc) : ATA Standard is: ATA-8-ACS revision 4 (Misc) : Local Time is: Sun Apr 7 23:23:47 2013 EDT (Misc) : SMART support is: Available - device has SMART capability. (Misc) : SMART support is: Enabled (Misc) : (Misc) : === START OF READ SMART DATA SECTION === (Misc) : SMART overall-health self-assessment test result: PASSED (Misc) : (Misc) : General SMART Values: (Misc) : Offline data collection status: (0x82)^IOffline data collection activity (Misc) : ^I^I^I^I^Iwas completed without error. (Misc) : ^I^I^I^I^IAuto Offline Data Collection: Enabled. (Misc) : Self-test execution status: ( 0)^IThe previous self-test routine completed (Misc) : ^I^I^I^I^Iwithout error or no self-test has ever (Misc) : ^I^I^I^I^Ibeen run. (Misc) : Total time to complete Offline (Misc) : data collection: ^I^I ( 609) seconds. (Misc) : Offline data collection (Misc) : capabilities: ^I^I^I (0x7b) SMART execute Offline immediate. (Misc) : ^I^I^I^I^IAuto Offline data collection on/off support. (Misc) : ^I^I^I^I^ISuspend Offline collection upon new (Misc) : ^I^I^I^I^Icommand. (Misc) : ^I^I^I^I^IOffline surface scan supported. (Misc) : ^I^I^I^I^ISelf-test supported. (Misc) : ^I^I^I^I^IConveyance Self-test supported. (Misc) : ^I^I^I^I^ISelective Self-test supported. (Misc) : SMART capabilities: (0x0003)^ISaves SMART data before entering (Misc) : ^I^I^I^I^Ipower-saving mode. (Misc) : ^I^I^I^I^ISupports SMART auto save timer. (Misc) : Error logging capability: (0x01)^IError logging supported. (Misc) : ^I^I^I^I^IGeneral Purpose Logging supported. (Misc) : Short self-test routine (Misc) : recommended polling time: ^I ( 1) minutes. (Misc) : Extended self-test routine (Misc) : recommended polling time: ^I ( 255) minutes. (Misc) : Conveyance self-test routine (Misc) : recommended polling time: ^I ( 2) minutes. (Misc) : SCT capabilities: ^I (0x103f)^ISCT Status supported. (Misc) : ^I^I^I^I^ISCT Error Recovery Control supported. (Misc) : ^I^I^I^I^ISCT Feature Control supported. (Misc) : ^I^I^I^I^ISCT Data Table supported. (Misc) : (Misc) : SMART Attributes Data Structure revision number: 10 (Misc) : Vendor Specific SMART Attributes with Thresholds: (Misc) : ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE (Misc) : 1 Raw_Read_Error_Rate 0x000f 119 099 006 Pre-fail Always - 233352352 (Misc) : 3 Spin_Up_Time 0x0003 093 088 000 Pre-fail Always - 0 (Misc) : 4 Start_Stop_Count 0x0032 098 098 020 Old_age Always - 2421 (Misc) : 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 (Misc) : 7 Seek_Error_Rate 0x000f 061 060 030 Pre-fail Always - 1365521 (Misc) : 9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 2279 (Misc) : 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 (Misc) : 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 325 (Misc) : 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 (Misc) : 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 (Misc) : 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 (Misc) : 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 (Misc) : 189 High_Fly_Writes 0x003a 099 099 000 Old_age Always - 1 (Misc) : 190 Airflow_Temperature_Cel 0x0022 070 048 045 Old_age Always - 30 (Min/Max 29/30) (Misc) : 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 (Misc) : 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 65 (Misc) : 193 Load_Cycle_Count 0x0032 099 099 000 Old_age Always - 2518 (Misc) : 194 Temperature_Celsius 0x0022 030 052 000 Old_age Always - 30 (0 23 0 0) (Misc) : 195 Hardware_ECC_Recovered 0x001a 032 006 000 Old_age Always - 271906022927520 (Misc) : 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 (Misc) : 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 (Misc) : 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 (Misc) : 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 147055385250063 (Misc) : 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 568991941 (Misc) : 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 1957264083 (Misc) : (Misc) : SMART Error Log Version: 1 (Misc) : No Errors Logged (Misc) : (Misc) : SMART Self-test log structure revision number 1 (Misc) : Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error (Misc) : # 1 Short offline Completed without error 00% 1599 - (Misc) : # 2 Short offline Completed without error 00% 1599 - (Misc) : (Misc) : SMART Selective self-test log data structure revision number 1 (Misc) : SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS (Misc) : 1 0 0 Not_testing (Misc) : 2 0 0 Not_testing (Misc) : 3 0 0 Not_testing (Misc) : 4 0 0 Not_testing (Misc) : 5 0 0 Not_testing (Misc) : Selective self-test flags (0x0): (Misc) : After scanning selected spans, do NOT read-scan remainder of disk. (Misc) : If Selective self-test is pending on power-up, resume after 0 minute delay. (Misc) : == (Misc) : ============================================================================ (Misc) : (Misc) Apr 9 12:58:50 Tower last message repeated 2 times : ============================================================================ (Misc) : == (Misc) : == S.M.A.R.T Final Report for /dev/sdf (Misc) : == (Misc) : Disk: /dev/sdf (Misc) : smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) (Misc) : Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net (Misc) : (Misc) : === START OF INFORMATION SECTION === (Misc) : Device Model: ST33000651AS (Misc) : Serial Number: 9XK0KNPJ (Misc) : Firmware Version: CC43 (Misc) : User Capacity: 3,000,592,982,016 bytes (Misc) : Device is: Not in smartctl database [for details use: -P showall] (Misc) : ATA Version is: 8 (Misc) : ATA Standard is: ATA-8-ACS revision 4 (Misc) : Local Time is: Tue Apr 9 12:58:47 2013 EDT (Misc) : SMART support is: Available - device has SMART capability. (Misc) : SMART support is: Enabled (Misc) : (Misc) : === START OF READ SMART DATA SECTION === (Misc) : SMART overall-health self-assessment test result: PASSED (Misc) : (Misc) : General SMART Values: (Misc) : Offline data collection status: (0x82)^IOffline data collection activity (Misc) : ^I^I^I^I^Iwas completed without error. (Misc) : ^I^I^I^I^IAuto Offline Data Collection: Enabled. (Misc) : Self-test execution status: ( 0)^IThe previous self-test routine completed (Misc) : ^I^I^I^I^Iwithout error or no self-test has ever (Misc) : ^I^I^I^I^Ibeen run. (Misc) : Total time to complete Offline (Misc) : data collection: ^I^I ( 609) seconds. (Misc) : Offline data collection (Misc) : capabilities: ^I^I^I (0x7b) SMART execute Offline immediate. (Misc) : ^I^I^I^I^IAuto Offline data collection on/off support. (Misc) : ^I^I^I^I^ISuspend Offline collection upon new (Misc) : ^I^I^I^I^Icommand. (Misc) : ^I^I^I^I^IOffline surface scan supported. (Misc) : ^I^I^I^I^ISelf-test supported. (Misc) : ^I^I^I^I^IConveyance Self-test supported. (Misc) : ^I^I^I^I^ISelective Self-test supported. (Misc) : SMART capabilities: (0x0003)^ISaves SMART data before entering (Misc) : ^I^I^I^I^Ipower-saving mode. (Misc) : ^I^I^I^I^ISupports SMART auto save timer. (Misc) : Error logging capability: (0x01)^IError logging supported. (Misc) : ^I^I^I^I^IGeneral Purpose Logging supported. (Misc) : Short self-test routine (Misc) : recommended polling time: ^I ( 1) minutes. (Misc) : Extended self-test routine (Misc) : recommended polling time: ^I ( 255) minutes. (Misc) : Conveyance self-test routine (Misc) : recommended polling time: ^I ( 2) minutes. (Misc) : SCT capabilities: ^I (0x103f)^ISCT Status supported. (Misc) : ^I^I^I^I^ISCT Error Recovery Control supported. (Misc) : ^I^I^I^I^ISCT Feature Control supported. (Misc) : ^I^I^I^I^ISCT Data Table supported. (Misc) : (Misc) : SMART Attributes Data Structure revision number: 10 (Misc) : Vendor Specific SMART Attributes with Thresholds: (Misc) : ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE (Misc) : 1 Raw_Read_Error_Rate 0x000f 106 099 006 Pre-fail Always - 10987154 (Misc) : 3 Spin_Up_Time 0x0003 093 088 000 Pre-fail Always - 0 (Misc) : 4 Start_Stop_Count 0x0032 098 098 020 Old_age Always - 2421 (Misc) : 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 (Misc) : 7 Seek_Error_Rate 0x000f 063 060 030 Pre-fail Always - 2572344 (Misc) : 9 Power_On_Hours 0x0032 098 098 000 Old_age Always - 2316 (Misc) : 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 (Misc) : 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 325 (Misc) : 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 (Misc) : 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 (Misc) : 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 (Misc) : 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 (Misc) : 189 High_Fly_Writes 0x003a 099 099 000 Old_age Always - 1 (Misc) : 190 Airflow_Temperature_Cel 0x0022 070 048 045 Old_age Always - 30 (Min/Max 29/32) (Misc) : 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 (Misc) : 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 65 (Misc) : 193 Load_Cycle_Count 0x0032 099 099 000 Old_age Always - 2518 (Misc) : 194 Temperature_Celsius 0x0022 030 052 000 Old_age Always - 30 (0 23 0 0) (Misc) : 195 Hardware_ECC_Recovered 0x001a 034 006 000 Old_age Always - 240539654399634 (Misc) : 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 (Misc) : 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 (Misc) : 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 (Misc) : 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 197637215095092 (Misc) : 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 441089338 (Misc) : 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 3525003717 (Misc) : (Misc) : SMART Error Log Version: 1 (Misc) : No Errors Logged (Misc) : (Misc) : SMART Self-test log structure revision number 1 (Misc) : Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error (Misc) : # 1 Short offline Completed without error 00% 1599 - (Misc) : # 2 Short offline Completed without error 00% 1599 - (Misc) : (Misc) : SMART Selective self-test log data structure revision number 1 (Misc) : SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS (Misc) : 1 0 0 Not_testing (Misc) : 2 0 0 Not_testing (Misc) : 3 0 0 Not_testing (Misc) : 4 0 0 Not_testing (Misc) : 5 0 0 Not_testing (Misc) : Selective self-test flags (0x0): (Misc) : After scanning selected spans, do NOT read-scan remainder of disk. (Misc) : If Selective self-test is pending on power-up, resume after 0 minute delay. (Misc) : == (Misc) : ============================================================================ (Misc) : (Misc)[16895] Thanks! Quote Link to comment
Joe L. Posted April 12, 2013 Share Posted April 12, 2013 You are misreading the smartctl report. EVERY parameter is in one of two categories. It is either an indicator that will increase over time (old age) or one that is an indication of a potential failure (pre-fail) If the "Normalized" value is at or lower than the affiliated "threshold" that that parameter "fails", otherwise, it passes. All your smart parameters pass. In some cases, the "raw" value can be interpreted as an actual count. In others, it cannot. As an example, the Power-off-retract count looks like an actual count. You've powered off the PC that drive was in 65 times while it was active. (when it still had the disk heads loaded) On the other hand, The "Head-Flying-Hours of 197637215095092 is not likely to be an actual count... A failure might just indicate the disk is getting older. Others might be an indication of an imminent failure. Quote Link to comment
Kyrak Posted April 14, 2013 Share Posted April 14, 2013 Thanks Joe! That makes a lot more sense now. Up to 15 TB I go! Quote Link to comment
00b5 Posted April 14, 2013 Share Posted April 14, 2013 Update 4-17-2013: After resetting the bios settings (and removing any mild overclocking), the original hdd that didn't preclear worked fine (and is now in the array). ------------------------------------------------------------------ Just finished my two first preclears ever, but one says it didn't preclear. Not sure what all the info in this report means, so if someone can point me in some direction, that would be great! ========================================================================1.13 == invoked as: ./preclear_disk.sh -A /dev/sdc == == Disk /dev/sdc has NOT been successfully precleared == Postread detected un-expected non-zero bytes on disk== == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 6:13:06 (89 MB/s) == Last Cycle's Zeroing time : 5:40:46 (97 MB/s) == Last Cycle's Post Read Time : 12:58:49 (42 MB/s) == Last Cycle's Total Time : 24:53:49 == == Total Elapsed Time 24:53:49 == == Disk Start Temperature: 33C == == Current Disk Temperature: 27C, == ============================================================================ No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ ============================================================================ == == S.M.A.R.T Initial Report for /dev/sdc == Disk: /dev/sdc smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: SAMSUNG HD204UI Serial Number: S2HGJ1BZ811173 Firmware Version: 1AQ10001 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: ATA-8-ACS revision 6 Local Time is: Sat Apr 13 01:35:24 2013 PDT 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)^IOffline data collection activity ^I^I^I^I^Iwas never started. ^I^I^I^I^IAuto Offline Data Collection: Disabled. Self-test execution status: ( 0)^IThe previous self-test routine completed ^I^I^I^I^Iwithout error or no self-test has ever ^I^I^I^I^Ibeen run. Total time to complete Offline data collection: ^I^I (21300) seconds. Offline data collection capabilities: ^I^I^I (0x5b) SMART execute Offline immediate. ^I^I^I^I^IAuto Offline data collection on/off support. ^I^I^I^I^ISuspend Offline collection upon new ^I^I^I^I^Icommand. ^I^I^I^I^IOffline surface scan supported. ^I^I^I^I^ISelf-test supported. ^I^I^I^I^INo Conveyance Self-test supported. ^I^I^I^I^ISelective Self-test supported. SMART capabilities: (0x0003)^ISaves SMART data before entering ^I^I^I^I^Ipower-saving mode. ^I^I^I^I^ISupports SMART auto save timer. Error logging capability: (0x01)^IError logging supported. ^I^I^I^I^IGeneral Purpose Logging supported. Short self-test routine recommended polling time: ^I ( 2) minutes. Extended self-test routine recommended polling time: ^I ( 255) minutes. SCT capabilities: ^I (0x003f)^ISCT Status supported. ^I^I^I^I^ISCT Error Recovery Control supported. ^I^I^I^I^ISCT Feature Control supported. ^I^I^I^I^ISCT 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 100 100 051 Pre-fail Always - 2 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 3 Spin_Up_Time 0x0023 067 067 025 Pre-fail Always - 10178 4 Start_Stop_Count 0x0032 095 095 000 Old_age Always - 5859 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 5288 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 81 181 Program_Fail_Cnt_Total 0x0022 100 100 000 Old_age Always - 35283 191 G-Sense_Error_Rate 0x0022 100 100 000 Old_age Always - 4 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 194 Temperature_Celsius 0x0002 064 062 000 Old_age Always - 33 (Min/Max 16/38) 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 0 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 5860 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] Note: selective self-test log revision number (0) not 1 implies that no selective self-test has ever been run SMART Selective self-test log data structure revision number 0 Note: revision number not 1 implies that no selective self-test has ever been run SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Completed [00% left] (0-65535) 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. == ============================================================================ ============================================================================ == == S.M.A.R.T Final Report for /dev/sdc == Disk: /dev/sdc smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: SAMSUNG HD204UI Serial Number: S2HGJ1BZ811173 Firmware Version: 1AQ10001 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: ATA-8-ACS revision 6 Local Time is: Sun Apr 14 02:29:13 2013 PDT 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)^IOffline data collection activity ^I^I^I^I^Iwas never started. ^I^I^I^I^IAuto Offline Data Collection: Disabled. Self-test execution status: ( 0)^IThe previous self-test routine completed ^I^I^I^I^Iwithout error or no self-test has ever ^I^I^I^I^Ibeen run. Total time to complete Offline data collection: ^I^I (21300) seconds. Offline data collection capabilities: ^I^I^I (0x5b) SMART execute Offline immediate. ^I^I^I^I^IAuto Offline data collection on/off support. ^I^I^I^I^ISuspend Offline collection upon new ^I^I^I^I^Icommand. ^I^I^I^I^IOffline surface scan supported. ^I^I^I^I^ISelf-test supported. ^I^I^I^I^INo Conveyance Self-test supported. ^I^I^I^I^ISelective Self-test supported. SMART capabilities: (0x0003)^ISaves SMART data before entering ^I^I^I^I^Ipower-saving mode. ^I^I^I^I^ISupports SMART auto save timer. Error logging capability: (0x01)^IError logging supported. ^I^I^I^I^IGeneral Purpose Logging supported. Short self-test routine recommended polling time: ^I ( 2) minutes. Extended self-test routine recommended polling time: ^I ( 255) minutes. SCT capabilities: ^I (0x003f)^ISCT Status supported. ^I^I^I^I^ISCT Error Recovery Control supported. ^I^I^I^I^ISCT Feature Control supported. ^I^I^I^I^ISCT 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 100 100 051 Pre-fail Always - 2 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 3 Spin_Up_Time 0x0023 067 067 025 Pre-fail Always - 10178 4 Start_Stop_Count 0x0032 095 095 000 Old_age Always - 5859 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 5312 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 81 181 Program_Fail_Cnt_Total 0x0022 100 100 000 Old_age Always - 35283 191 G-Sense_Error_Rate 0x0022 100 100 000 Old_age Always - 4 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 194 Temperature_Celsius 0x0002 064 062 000 Old_age Always - 27 (Min/Max 16/38) 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 0 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 5860 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] Note: selective self-test log revision number (0) not 1 implies that no selective self-test has ever been run SMART Selective self-test log data structure revision number 0 Note: revision number not 1 implies that no selective self-test has ever been run SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Completed [00% left] (0-65535) 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. == I was using this disk in my win7 machine for years as my primary large storage drive. Should I just run the preclear again on it? I did run two at once, the other one finished fine: ========================================================================1.13 == invoked as: ./preclear_disk.sh -A /dev/sdb == WDC WD20EARS-00MVWB0 WD-WCAZA5820437 == Disk /dev/sdb has been successfully precleared Quote Link to comment
Joe L. Posted April 14, 2013 Share Posted April 14, 2013 The disk should have contained all zeros after being written with all zeros. The post-read phase (after writing the disk with zeros) read some non-zero bytes. The problem can be a bad disk, or bad memory on the MB, or a bad disk controller, or a insufficient power supply. (poor cabling, too many splitters, poor connections to the drive rack, etc) you are lucky to find this before putting the disk in your array and you should try to figure out the actual cause, if you do not, you'll get constant odd parity errors and be unable to figure out which disk (if a disk) is causing them, since it could be nearly anything except the "mouse" that is causing them. One good thing... you can now have some condolence that perhaps one or more of the crashes or loss of data on your windows box might not have been caused by the coding at Microsoft. 8) You can try to prove it is the disk, or not... at the least, run a full memory test on your server, as it might be bad RAM (or ram not configured properly, bad timing, bad voltage, or wrong clock speed) Joe L. Quote Link to comment
00b5 Posted April 15, 2013 Share Posted April 15, 2013 The disk should have contained all zeros after being written with all zeros. The post-read phase (after writing the disk with zeros) read some non-zero bytes. The problem can be a bad disk, or bad memory on the MB, or a bad disk controller, or a insufficient power supply. (poor cabling, too many splitters, poor connections to the drive rack, etc) you are lucky to find this before putting the disk in your array and you should try to figure out the actual cause, if you do not, you'll get constant odd parity errors and be unable to figure out which disk (if a disk) is causing them, since it could be nearly anything except the "mouse" that is causing them. One good thing... you can now have some condolence that perhaps one or more of the crashes or loss of data on your windows box might not have been caused by the coding at Microsoft. 8) You can try to prove it is the disk, or not... at the least, run a full memory test on your server, as it might be bad RAM (or ram not configured properly, bad timing, bad voltage, or wrong clock speed) Joe L. This setup was my previous Win7 machine with no issues, and pretty much ran 24/7 (part of why i'm now moving to a UNRAID server, instead of just a Win7 box with large hdds). I think I did have it with a mild OC, but its been so long since I did it, I really can't recall 100% I did go into the BIOS and do a reset to defaults, adjusted my boot order again, and loaded back into unraid, and started another preclear. Thanks for the direction, will update with what happens on the 2nd preclear attempt. I also have two other drives that I can start on preclears, so that will help narrow down the potential issue. Quote Link to comment
00b5 Posted April 17, 2013 Share Posted April 17, 2013 Update: After resetting the bios settings (and removing any mild overclocking), the original hdd that didn't preclear worked fine (and is now in the array). I since precleared two more drives, and they also cleared successfully (all were just one pass, since they were existing drives that were in use). Seems like I must have completely forgotten that I was using the Gigabyte windows O/C software to do a mild level 1 overclocking (which was always 100% stable) but is totally not needed for the UNRAID server. Thanks again! Quote Link to comment
tr0910 Posted April 21, 2013 Share Posted April 21, 2013 Just reporting a strange result with 1.13 on my rc12a server this morning. I hot-plugged a questionable drive in for badblocks testing, and did a preclear -l to see where it was mounted. Here is what was reported: root@Server1:/boot# precleardisk.sh -l ====================================1.13 Disks not assigned to the unRAID array (potential candidates for clearing) ======================================== /dev/sdd = ata-Hitachi_HDS5C3030ALA630_MJ1313YNG28SGC /dev/sdn = ata-Hitachi_HDS5C3030ALA630_MJ1323YNG1UKKC /dev/sdi = ata-SAMSUNG_HD203WI_S1UYJ1WZ405310 /dev/sdb = ata-SAMSUNG_HD204UI_S2H7J90B713135 /dev/sde = ata-ST3000DM001-1CH166_W1F1NVGS /dev/sdo = ata-ST3000DM001-9YN166_S1F02LQJ /dev/sdm = ata-ST3000DM001-9YN166_W1F0MED2 /dev/sdh = ata-ST3000DM001-9YN166_W1F0N4JK /dev/sdl = ata-ST3000DM001-9YN166_W1F0ZTJA /dev/sdf = ata-ST3000DM001-9YN166_W1F115AC /dev/sdk = ata-ST3000DM001-9YN166_W1F12HY5 /dev/sdj = ata-ST32000542AS_5XW1CSPD /dev/sda = ata-WDC_WD20EARS-00MVWB0_WD-WMAZA3919347 /dev/sdg = ata-WDC_WD30EZRS-00J99B0_WD-WCAWZ0361944 These are all drives as part of my unRaid server. Thankfully I knew that sdo is the one by comparing with unMenu. Did hot-plugging cause this? Quote Link to comment
tr0910 Posted April 21, 2013 Share Posted April 21, 2013 Half hour later, reran the preclear -l and all is good again, with only the correct drive listed. hmmm..... Quote Link to comment
Joe L. Posted April 21, 2013 Share Posted April 21, 2013 Just reporting a strange result with 1.13 on my rc12a server this morning. I hot-plugged a questionable drive in for badblocks testing, and did a preclear -l to see where it was mounted. Here is what was reported: root@Server1:/boot# precleardisk.sh -l ====================================1.13 Disks not assigned to the unRAID array (potential candidates for clearing) ======================================== /dev/sdd = ata-Hitachi_HDS5C3030ALA630_MJ1313YNG28SGC /dev/sdn = ata-Hitachi_HDS5C3030ALA630_MJ1323YNG1UKKC /dev/sdi = ata-SAMSUNG_HD203WI_S1UYJ1WZ405310 /dev/sdb = ata-SAMSUNG_HD204UI_S2H7J90B713135 /dev/sde = ata-ST3000DM001-1CH166_W1F1NVGS /dev/sdo = ata-ST3000DM001-9YN166_S1F02LQJ /dev/sdm = ata-ST3000DM001-9YN166_W1F0MED2 /dev/sdh = ata-ST3000DM001-9YN166_W1F0N4JK /dev/sdl = ata-ST3000DM001-9YN166_W1F0ZTJA /dev/sdf = ata-ST3000DM001-9YN166_W1F115AC /dev/sdk = ata-ST3000DM001-9YN166_W1F12HY5 /dev/sdj = ata-ST32000542AS_5XW1CSPD /dev/sda = ata-WDC_WD20EARS-00MVWB0_WD-WMAZA3919347 /dev/sdg = ata-WDC_WD30EZRS-00J99B0_WD-WCAWZ0361944 These are all drives as part of my unRaid server. Thankfully I knew that sdo is the one by comparing with unMenu. Did hot-plugging cause this? Apparently the hot-plug made the /boot/config/disk.cfg file unreadable OR, more likely, the device ID changed under /sys/devices/$id/block and therefore, the preclear script could not match the disks in the .cfg file with those under/sys/devices. Joe L. Quote Link to comment
navi Posted April 22, 2013 Share Posted April 22, 2013 I would really appreciate if someone could check these reports for me. I precleared two Seagate ST3000DM001 in my HP N40L Microserver. 8 hours into the first cycle I had a power cut, only a couple of seconds, but when the power returned Unraid was unreachable so I had to reboot and start again. sda report: ========================================================================1.13 == invoked as: ./preclear_disk.sh -c 3 /dev/sda == ST3000DM001-1CH166 Z1F2F8B5 == Disk /dev/sda has been successfully precleared == with a starting sector of 1 == Ran 3 cycles == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 6:18:52 (131 MB/s) == Last Cycle's Zeroing time : 5:14:49 (158 MB/s) == Last Cycle's Post Read Time : 18:41:46 (44 MB/s) == Last Cycle's Total Time : 23:57:36 == == Total Elapsed Time 78:21:43 == == Disk Start Temperature: 31C == == Current Disk Temperature: 31C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 116 117 6 ok 112650792 Seek_Error_Rate = 60 100 30 ok 1210303 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 98 100 0 ok 2 Airflow_Temperature_Cel = 69 69 45 near_thresh 31 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ sdb report: ========================================================================1.13 == invoked as: ./preclear_disk.sh -c 3 /dev/sdb == ST3000DM001-1CH166 Z1F2DDN5 == Disk /dev/sdb has been successfully precleared == with a starting sector of 1 == Ran 3 cycles == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 6:29:24 (128 MB/s) == Last Cycle's Zeroing time : 5:26:31 (153 MB/s) == Last Cycle's Post Read Time : 19:03:20 (43 MB/s) == Last Cycle's Total Time : 24:30:52 == == Total Elapsed Time 80:12:20 == == Disk Start Temperature: 30C == == Current Disk Temperature: 30C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 116 117 6 ok 101291920 Seek_Error_Rate = 60 100 30 ok 1221246 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 99 100 0 ok 1 Airflow_Temperature_Cel = 70 70 45 near_thresh 30 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ I am slightly concerned that both drives had changed Seek Error Rates but perhaps the fact that both values are 60 is significant? As the post will be too long I'll post the pre and post SMART reports in following messages. Thanks in advance. Quote Link to comment
navi Posted April 22, 2013 Share Posted April 22, 2013 sda SMART start: Disk: /dev/sda smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST3000DM001-1CH166 Serial Number: Z1F2F8B5 Firmware Version: CC26 User Capacity: 3,000,592,982,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Thu Apr 18 22:37:51 2013 BST 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: ( 89) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No 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: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) SCT Status 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 117 100 006 Pre-fail Always - 163994104 3 Spin_Up_Time 0x0003 098 098 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 3 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 192696 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 7 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 3 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 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 069 064 045 Old_age Always - 31 (Min/Max 31/31) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 3 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 9 194 Temperature_Celsius 0x0022 031 040 000 Old_age Always - 31 (0 15 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 5325759447047 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 1425377704 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 6012640206 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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. sda SMART finish: Disk: /dev/sda smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST3000DM001-1CH166 Serial Number: Z1F2F8B5 Firmware Version: CC26 User Capacity: 3,000,592,982,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Mon Apr 22 04:59:34 2013 BST 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: ( 89) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No 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: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) SCT Status 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 116 099 006 Pre-fail Always - 112650792 3 Spin_Up_Time 0x0003 098 098 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 3 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 060 060 030 Pre-fail Always - 1210303 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 86 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 3 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 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 098 098 000 Old_age Always - 2 190 Airflow_Temperature_Cel 0x0022 069 064 045 Old_age Always - 31 (Min/Max 31/35) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 3 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 9 194 Temperature_Celsius 0x0022 031 040 000 Old_age Always - 31 (0 15 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 74453258076245 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 19006977352 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 47646353108 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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
navi Posted April 22, 2013 Share Posted April 22, 2013 sdb SMART start: Disk: /dev/sdb smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST3000DM001-1CH166 Serial Number: Z1F2DDN5 Firmware Version: CC26 User Capacity: 3,000,592,982,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Thu Apr 18 22:38:46 2013 BST 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: ( 97) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No 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: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) SCT Status 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 117 100 006 Pre-fail Always - 167459744 3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 2 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 192840 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 7 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 2 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 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 070 065 045 Old_age Always - 30 (Min/Max 30/31) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 2 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 8 194 Temperature_Celsius 0x0022 030 040 000 Old_age Always - 30 (0 15 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 11154030067719 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 1093339040 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 6012640206 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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. sdb SMART finish: Disk: /dev/sdb smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST3000DM001-1CH166 Serial Number: Z1F2DDN5 Firmware Version: CC26 User Capacity: 3,000,592,982,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Mon Apr 22 06:51:07 2013 BST 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: ( 97) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No 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: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) SCT Status 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 116 100 006 Pre-fail Always - 101291920 3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 2 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 060 060 030 Pre-fail Always - 1221246 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 87 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 2 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 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 099 099 000 Old_age Always - 1 190 Airflow_Temperature_Cel 0x0022 070 065 045 Old_age Always - 30 (Min/Max 30/34) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 2 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 8 194 Temperature_Celsius 0x0022 030 040 000 Old_age Always - 30 (0 15 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 88240103096407 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 18674938728 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 47646417092 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] 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
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.