WeeboTech Posted November 30, 2012 Share Posted November 30, 2012 So I have two drives running badblocks, same seagate, connected to the same controller started at the same time. One is running a lot faster than the other, is that indicative of a bad drive? root@NatesNAS2:~# badblocks -sv -w -o /tmp/badblocks.out.sde /dev/sde Checking for bad blocks in read-write mode From block 0 to 2930266583 Testing with pattern 0xaa: done Reading and comparing: done Testing with pattern 0x55: done Reading and comparing: done Testing with pattern 0xff: done Reading and comparing: done Testing with pattern 0x00: 49.41% done, 34:38:31 elapsed root@NatesNAS2:~# badblocks -sv -w -o /tmp/badblocks.out.sdf /dev/sdf Checking for bad blocks in read-write mode From block 0 to 2930266583 Testing with pattern 0xaa: done Reading and comparing: ndone Testing with pattern 0x55: ndone Reading and comparing: done Testing with pattern 0xff: done Reading and comparing: done Testing with pattern 0x00: 78.56% done, 34:39:17 elapsed One job may be having more priority then the other. Although you would think the kernel would schedule them evenly, any form of buffering could impact that. Look at the syslog to see if any of the drives are reporting issues, that would definitely slow it down. There are other situations that could affect it, Current use of machine, how the controllers are mapped and where they are in regards to the bus. Some SATA ports on the motherboard have a high bandwidth. Some PCIe slots are behind other types of controllers. It's hard to estimate what it should be without knowing the server's configuration and how the motherboard maps the slots and controllers. Quote Link to comment
squirrellydw Posted December 3, 2012 Share Posted December 3, 2012 Can some verify that everything looks good? ** Changed attributes in files: /tmp/smart_start_sdi /tmp/smart_finish_sdi ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 115 118 6 ok 98284504 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 96 98 0 ok 4 Airflow_Temperature_Cel = 72 74 45 ok 28 Temperature_Celsius = 28 26 0 ok 28 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 2. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 2. 0 sectors were pending re-allocation after post-read in cycle 1 of 2. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 2. 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. root@Tower:/boot# Quote Link to comment
Joe L. Posted December 4, 2012 Share Posted December 4, 2012 anyone?? looks fine. Quote Link to comment
squirrellydw Posted December 4, 2012 Share Posted December 4, 2012 Thanks Joe, I only need to look at this part correct? sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 2. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 2. 0 sectors were pending re-allocation after post-read in cycle 1 of 2. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 2. 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. Quote Link to comment
Joe L. Posted December 4, 2012 Share Posted December 4, 2012 Thanks Joe, I only need to look at this part correct? sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 2. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 2. 0 sectors were pending re-allocation after post-read in cycle 1 of 2. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 2. 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. no Quote Link to comment
garycase Posted December 4, 2012 Share Posted December 4, 2012 Joe -- Why is that a "No" I'd have thought "all zeroes" was the sign of a successful pre-clear operation. What else do we need to look for? Quote Link to comment
Razor444 Posted December 4, 2012 Share Posted December 4, 2012 Hi, i have a question: if i put new disk into NAS, and connect to NAS through telnet (or SSH terminal) and start preclearing and then exit telnet...will the preclear process stop or no? And if it won't, how can I connect again and see the progress status? Thanks Edit: And if i accidentally close telnet (or my isp drops), what will happen to the disk? What should I do then? Quote Link to comment
Joe L. Posted December 4, 2012 Share Posted December 4, 2012 Joe -- Why is that a "No" I'd have thought "all zeroes" was the sign of a successful pre-clear operation. What else do we need to look for? Because the section posted does not look at any of the other SMART parameters. It is NOT the report output from the pre-clear, but only part of it. It does not say that the disk was pre-cleared successfully, but only that there were zero re-allocated sectors and zero sectors pending re-allocation. (granted, that is good, but not unless you look at and compare the pre-and-post SMART reports.) I only need to look at this part correct? So "no", it is not all that you need to look at. It is only part of it. Quote Link to comment
Joe L. Posted December 4, 2012 Share Posted December 4, 2012 Hi, i have a question: if i put new disk into NAS, and connect to NAS through telnet (or SSH terminal) and start preclearing and then exit telnet...will the preclear process stop or no? And if it won't, how can I connect again and see the progress status? Thanks unless you invoked the preclear process under "screen", it stopped. There is no way to see its progress if you log in again, since it stopped. All you can do is start it again from the beginning. If you did use "screen" you can log back in and type screen -r to resume your screen session. Quote Link to comment
Razor444 Posted December 4, 2012 Share Posted December 4, 2012 And how do I use 'screen'? Is this the feature of telnet program? like putty or bitwise? Thanks Quote Link to comment
squirrellydw Posted December 4, 2012 Share Posted December 4, 2012 Thanks Joe, any chance you could post a report of excatly what I should be look for each time and what they mean? Quote Link to comment
sureguy Posted December 4, 2012 Share Posted December 4, 2012 And how do I use 'screen'? Is this the feature of telnet program? like putty or bitwise? Thanks A tutorial/HOW-to for screen can be found here: http://www.rackaid.com/resources/linux-screen-tutorial-and-how-to/ Quote Link to comment
maddog808 Posted December 5, 2012 Share Posted December 5, 2012 Hey everyone. I just did my first ever preclear, and was wondering if someone might have a couple minutes to verify that this drive is good to go. It looks good to me, but I could easily be missing something. I've attached the preclear_results.txt file. I would be quite grateful for any help at all. Thank you, Matt preclear_results.txt Quote Link to comment
Razor444 Posted December 5, 2012 Share Posted December 5, 2012 And how do I use 'screen'? Is this the feature of telnet program? like putty or bitwise? Thanks A tutorial/HOW-to for screen can be found here: http://www.rackaid.com/resources/linux-screen-tutorial-and-how-to/ Yes, thanks. Regarding unRaid, you should install "screen" addon from unMenu, and then use it with telnet. Quote Link to comment
garycase Posted December 5, 2012 Share Posted December 5, 2012 Joe, As you know, the "preclear_reports" folder on the UnRAID flash drive contain 3 files for each preclear that's been done: (1) preclear_start_<drive serial number>; preclear_rpt_<drive serial number>; and preclear_finish_<drive serial number> Am I missing anything if I simply look at the "preclear_rpt_<drive serial number>" file? For example, this is the contents of a recent one for one of my 3TB drives -- which shows only the temperature attribute changing (obviously a normal change), and all zeroes for the other items discussed above: ========================================================================1.13 == invoked as: ./preclear_disk.sh /dev/sde == WDC WD30EFRX-68AX9N0 WD-WMC1T0900350 == Disk /dev/sde has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 8:25:34 (98 MB/s) == Last Cycle's Zeroing time : 7:38:20 (109 MB/s) == Last Cycle's Post Read Time : 21:02:15 (39 MB/s) == Last Cycle's Total Time : 37:07:11 == == Total Elapsed Time 37:07:11 == == Disk Start Temperature: 29C == == Current Disk Temperature: 32C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sde /tmp/smart_finish_sde ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 118 121 0 ok 32 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. ============================================================================ Quote Link to comment
Joe L. Posted December 5, 2012 Share Posted December 5, 2012 Hey everyone. I just did my first ever preclear, and was wondering if someone might have a couple minutes to verify that this drive is good to go. It looks good to me, but I could easily be missing something. I've attached the preclear_results.txt file. I would be quite grateful for any help at all. Thank you, Matt Other than you used a version of the preclear script that is 4 versions old, all looks fine. Current version is 1.13, you used 1.9. Your older version does not work properly on disks > 2TB. Quote Link to comment
Helmonder Posted December 8, 2012 Share Posted December 8, 2012 Mmm... my telnetdaemon just died on me, preclear is running in SCREEN but I cannot get to it without telnet.. I started it up wit the parameter that prevents writing of info in the preclear results directory (also no email alerts), is there any way now for me to know if preclear is still running and what the results are when it is finished ? If not I will hook up a monitor and keyboard and check on console, but it is kind of a hassle, so if there is another way ? Maybe the end result will get written to the preclear results directory anyway ? EDIT: Just hooked up a monitor, seems like there is no SCREEN to reattach, therefor I will assume that preclear has terminated.. Can someone confirm that SCREEN is tied to the running telnetdaemon process and that therefor a SCREEN session will be lost when the telnetdaemon dies ? Quote Link to comment
Joe L. Posted December 8, 2012 Share Posted December 8, 2012 Mmm... my telnetdaemon just died on me, preclear is running in SCREEN but I cannot get to it without telnet.. I started it up wit the parameter that prevents writing of info in the preclear results directory (also no email alerts), is there any way now for me to know if preclear is still running and what the results are when it is finished ? If not I will hook up a monitor and keyboard and check on console, but it is kind of a hassle, so if there is another way ? Maybe the end result will get written to the preclear results directory anyway ? EDIT: Just hooked up a monitor, seems like there is no SCREEN to reattach, therefor I will assume that preclear has terminated.. Can someone confirm that SCREEN is tied to the running telnetdaemon process and that therefor a SCREEN session will be lost when the telnetdaemon dies ? screen is not connected to the telnet session. (or rather, does not die when telnet disconnected) Did you try running screen -r to see the existing "screen" sessions so you can re-connect to it? About the only other thing you can do is type top and see if the screen and preclear process is still running. (you would see "dd" constantly being invoked) or you can look in the /tmp directory. The preclear process writes its status files there. Quote Link to comment
Helmonder Posted December 8, 2012 Share Posted December 8, 2012 screen -r did not bring anything... weird... I'll have to try again, had to reboot. Quote Link to comment
Joe L. Posted December 8, 2012 Share Posted December 8, 2012 screen -r did not bring anything... weird... I'll have to try again, had to reboot. Did invoking that command at least say something like There is no screen to be resumed. (that is what it does on my server if there is no screen session running.) Quote Link to comment
Helmonder Posted December 8, 2012 Share Posted December 8, 2012 Thats exactly what it said... Human error is the easiest reason, maybe I have forgotten to set screen or I did it wrong... I'll test it out when I restart the preclear. Quote Link to comment
eknee1417 Posted December 27, 2012 Share Posted December 27, 2012 Hey guys, Of the 3 files that preclear logs which one do I need to look at to determine if the disk passed? start, finish or rpt Quote Link to comment
Questhate Posted December 28, 2012 Share Posted December 28, 2012 Was hoping you could help me with these. I just built an UNRAID a few weeks ago, I was able to get three HDD drives in there that all passed the preclear. I finally upgraded to the Pro license so that I could use this 128GB SSD that a friend had lying around as my cache drive. This is the first time a preclear has failed. It says the failing SMART attribute is 4 Start_Stop_Count. Can someone help me interpret this? Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ========================================================================1.13 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: == invoked as: ./preclear_disk.sh /dev/sdd Dec 28 02:06:19 Tower preclear_disk-diff[21437]: == ST9160823AS 5NK1HH0Z Dec 28 02:06:19 Tower preclear_disk-diff[21437]: == Disk /dev/sdd has been successfully precleared Dec 28 02:06:19 Tower preclear_disk-diff[21437]: == with a starting sector of 63 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: == Ran 1 cycle Dec 28 02:06:19 Tower preclear_disk-diff[21437]: == Dec 28 02:06:19 Tower preclear_disk-diff[21437]: == Using :Read block size = 8225280 Bytes Dec 28 02:06:19 Tower preclear_disk-diff[21437]: == Last Cycle's Pre Read Time : 1:05:19 (40 MB/s) Dec 28 02:06:19 Tower preclear_disk-diff[21437]: == Last Cycle's Zeroing time : 1:02:03 (42 MB/s) Dec 28 02:06:19 Tower preclear_disk-diff[21437]: == Last Cycle's Post Read Time : 2:15:38 (19 MB/s) Dec 28 02:06:19 Tower preclear_disk-diff[21437]: == Last Cycle's Total Time : 4:24:05 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: == Dec 28 02:06:19 Tower preclear_disk-diff[21437]: == Total Elapsed Time 4:24:05 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: == Dec 28 02:06:19 Tower preclear_disk-diff[21437]: == Disk Start Temperature: 31C Dec 28 02:06:19 Tower preclear_disk-diff[21437]: == Dec 28 02:06:19 Tower preclear_disk-diff[21437]: == Current Disk Temperature: -->41<--C, Dec 28 02:06:19 Tower preclear_disk-diff[21437]: == Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ============================================================================ Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Raw_Read_Error_Rate = 114 117 34 ok 124478417 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Start_Stop_Count = 1 1 20 FAILING_NOW 351456 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Airflow_Temperature_Cel = 59 69 0 ok 41 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Load_Cycle_Count = 1 1 0 near_thresh 375007 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Temperature_Celsius = 41 31 0 ok 41 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Hardware_ECC_Recovered = 64 96 0 ok 124478417 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Dec 28 02:06:19 Tower preclear_disk-diff[21437]: *** Failing SMART Attributes in /tmp/smart_finish_sdd *** Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 4 Start_Stop_Count 0x0032 001 001 020 Old_age Always FAILING_NOW 351456 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 0 sectors were pending re-allocation before the start of the preclear. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 0 sectors are pending re-allocation at the end of the preclear, Dec 28 02:06:19 Tower preclear_disk-diff[21437]: the number of sectors pending re-allocation did not change. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 0 sectors had been re-allocated before the start of the preclear. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 0 sectors are re-allocated at the end of the preclear, Dec 28 02:06:19 Tower preclear_disk-diff[21437]: the number of sectors re-allocated did not change. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ============================================================================ Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ============================================================================ Dec 28 02:06:19 Tower preclear_disk-diff[21437]: == Dec 28 02:06:19 Tower preclear_disk-diff[21437]: == S.M.A.R.T Initial Report for /dev/sdd Dec 28 02:06:19 Tower preclear_disk-diff[21437]: == Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Disk: /dev/sdd Dec 28 02:06:19 Tower preclear_disk-diff[21437]: smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Dec 28 02:06:19 Tower preclear_disk-diff[21437]: === START OF INFORMATION SECTION === Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Model Family: Seagate Momentus 7200.2 series Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Device Model: ST9160823AS Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Serial Number: 5NK1HH0Z Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Firmware Version: 3.CME Dec 28 02:06:19 Tower preclear_disk-diff[21437]: User Capacity: 160,041,885,696 bytes Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Device is: In smartctl database [for details use: -P show] Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ATA Version is: 7 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ATA Standard is: Exact ATA specification draft version not indicated Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Local Time is: Thu Dec 27 21:42:11 2012 PST Dec 28 02:06:19 Tower preclear_disk-diff[21437]: SMART support is: Available - device has SMART capability. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: SMART support is: Enabled Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Dec 28 02:06:19 Tower preclear_disk-diff[21437]: === START OF READ SMART DATA SECTION === Dec 28 02:06:19 Tower preclear_disk-diff[21437]: SMART overall-health self-assessment test result: PASSED Dec 28 02:06:19 Tower preclear_disk-diff[21437]: See vendor-specific Attribute list for marginal Attributes. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Dec 28 02:06:19 Tower preclear_disk-diff[21437]: General SMART Values: Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Offline data collection status: (0x00)^IOffline data collection activity Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ^I^I^I^I^Iwas never started. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ^I^I^I^I^IAuto Offline Data Collection: Disabled. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Self-test execution status: ( 0)^IThe previous self-test routine completed Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ^I^I^I^I^Iwithout error or no self-test has ever Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ^I^I^I^I^Ibeen run. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Total time to complete Offline Dec 28 02:06:19 Tower preclear_disk-diff[21437]: data collection: ^I^I ( 426) seconds. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Offline data collection Dec 28 02:06:19 Tower preclear_disk-diff[21437]: capabilities: ^I^I^I (0x53) SMART execute Offline immediate. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ^I^I^I^I^IAuto Offline data collection on/off support. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ^I^I^I^I^ISuspend Offline collection upon new Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ^I^I^I^I^Icommand. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ^I^I^I^I^INo Offline surface scan supported. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ^I^I^I^I^ISelf-test supported. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ^I^I^I^I^INo Conveyance Self-test supported. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ^I^I^I^I^ISelective Self-test supported. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: SMART capabilities: (0x0003)^ISaves SMART data before entering Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ^I^I^I^I^Ipower-saving mode. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ^I^I^I^I^ISupports SMART auto save timer. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Error logging capability: (0x01)^IError logging supported. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ^I^I^I^I^IGeneral Purpose Logging supported. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Short self-test routine Dec 28 02:06:19 Tower preclear_disk-diff[21437]: recommended polling time: ^I ( 1) minutes. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Extended self-test routine Dec 28 02:06:19 Tower preclear_disk-diff[21437]: recommended polling time: ^I ( 58) minutes. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: SCT capabilities: ^I (0x0001)^ISCT Status supported. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Dec 28 02:06:19 Tower preclear_disk-diff[21437]: SMART Attributes Data Structure revision number: 10 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Vendor Specific SMART Attributes with Thresholds: Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 1 Raw_Read_Error_Rate 0x000f 117 066 034 Pre-fail Always - 147964576 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 3 Spin_Up_Time 0x0003 100 099 000 Pre-fail Always - 0 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 4 Start_Stop_Count 0x0032 001 001 020 Old_age Always FAILING_NOW 351454 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 7 Seek_Error_Rate 0x000f 076 060 030 Pre-fail Always - 13036889429 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 9 Power_On_Hours 0x0032 091 091 000 Old_age Always - 133719511801603 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 10 Spin_Retry_Count 0x0013 100 100 034 Pre-fail Always - 0 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 12 Power_Cycle_Count 0x0032 099 099 020 Old_age Always - 1730 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 184 End-to-End_Error 0x0032 100 253 000 Old_age Always - 0 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 187 Reported_Uncorrect 0x003a 100 100 000 Old_age Always - 0 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 189 High_Fly_Writes 0x0022 100 100 045 Old_age Always - 0 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 190 Airflow_Temperature_Cel 0x0032 069 050 000 Old_age Always - 31 (Min/Max 31/31) Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 3 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 192 Power-Off_Retract_Count 0x0022 087 087 000 Old_age Always - 26933 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 193 Load_Cycle_Count 0x001a 001 001 000 Old_age Always - 375005 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 194 Temperature_Celsius 0x0012 031 050 000 Old_age Always - 31 (0 11 0 0) Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 195 Hardware_ECC_Recovered 0x0010 096 061 000 Old_age Offline - 147964576 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 196 Reallocated_Event_Count 0x003e 095 095 000 Old_age Always - 5181 (41479, 0) Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 197 Current_Pending_Sector 0x0000 100 100 000 Old_age Offline - 0 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 198 Offline_Uncorrectable 0x0032 100 100 000 Old_age Always - 0 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 199 UDMA_CRC_Error_Count 0x0000 200 200 000 Old_age Offline - 0 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 202 Data_Address_Mark_Errs 0x0000 100 253 000 Old_age Offline - 0 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 254 Free_Fall_Sensor 0x0000 100 253 000 Old_age Offline - 0 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Dec 28 02:06:19 Tower preclear_disk-diff[21437]: SMART Error Log Version: 1 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: No Errors Logged Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Dec 28 02:06:19 Tower preclear_disk-diff[21437]: SMART Self-test log structure revision number 1 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Dec 28 02:06:19 Tower preclear_disk-diff[21437]: SMART Selective self-test log data structure revision number 1 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 1 0 0 Not_testing Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 2 0 0 Not_testing Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 3 0 0 Not_testing Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 4 0 0 Not_testing Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 5 0 0 Not_testing Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Selective self-test flags (0x0): Dec 28 02:06:19 Tower preclear_disk-diff[21437]: After scanning selected spans, do NOT read-scan remainder of disk. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: If Selective self-test is pending on power-up, resume after 0 minute delay. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: == Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ============================================================================ Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Dec 28 02:06:19 Tower last message repeated 2 times Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ============================================================================ Dec 28 02:06:19 Tower preclear_disk-diff[21437]: == Dec 28 02:06:19 Tower preclear_disk-diff[21437]: == S.M.A.R.T Final Report for /dev/sdd Dec 28 02:06:19 Tower preclear_disk-diff[21437]: == Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Disk: /dev/sdd Dec 28 02:06:19 Tower preclear_disk-diff[21437]: smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Dec 28 02:06:19 Tower preclear_disk-diff[21437]: === START OF INFORMATION SECTION === Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Model Family: Seagate Momentus 7200.2 series Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Device Model: ST9160823AS Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Serial Number: 5NK1HH0Z Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Firmware Version: 3.CME Dec 28 02:06:19 Tower preclear_disk-diff[21437]: User Capacity: 160,041,885,696 bytes Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Device is: In smartctl database [for details use: -P show] Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ATA Version is: 7 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ATA Standard is: Exact ATA specification draft version not indicated Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Local Time is: Fri Dec 28 02:06:16 2012 PST Dec 28 02:06:19 Tower preclear_disk-diff[21437]: SMART support is: Available - device has SMART capability. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: SMART support is: Enabled Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Quote Link to comment
Questhate Posted December 28, 2012 Share Posted December 28, 2012 Here is the rest of it: Dec 28 02:06:19 Tower preclear_disk-diff[21437]: === START OF READ SMART DATA SECTION === Dec 28 02:06:19 Tower preclear_disk-diff[21437]: SMART overall-health self-assessment test result: PASSED Dec 28 02:06:19 Tower preclear_disk-diff[21437]: See vendor-specific Attribute list for marginal Attributes. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Dec 28 02:06:19 Tower preclear_disk-diff[21437]: General SMART Values: Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Offline data collection status: (0x00)^IOffline data collection activity Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ^I^I^I^I^Iwas never started. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ^I^I^I^I^IAuto Offline Data Collection: Disabled. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Self-test execution status: ( 0)^IThe previous self-test routine completed Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ^I^I^I^I^Iwithout error or no self-test has ever Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ^I^I^I^I^Ibeen run. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Total time to complete Offline Dec 28 02:06:19 Tower preclear_disk-diff[21437]: data collection: ^I^I ( 426) seconds. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Offline data collection Dec 28 02:06:19 Tower preclear_disk-diff[21437]: capabilities: ^I^I^I (0x53) SMART execute Offline immediate. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ^I^I^I^I^IAuto Offline data collection on/off support. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ^I^I^I^I^ISuspend Offline collection upon new Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ^I^I^I^I^Icommand. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ^I^I^I^I^INo Offline surface scan supported. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ^I^I^I^I^ISelf-test supported. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ^I^I^I^I^INo Conveyance Self-test supported. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ^I^I^I^I^ISelective Self-test supported. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: SMART capabilities: (0x0003)^ISaves SMART data before entering Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ^I^I^I^I^Ipower-saving mode. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ^I^I^I^I^ISupports SMART auto save timer. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Error logging capability: (0x01)^IError logging supported. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ^I^I^I^I^IGeneral Purpose Logging supported. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Short self-test routine Dec 28 02:06:19 Tower preclear_disk-diff[21437]: recommended polling time: ^I ( 1) minutes. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Extended self-test routine Dec 28 02:06:19 Tower preclear_disk-diff[21437]: recommended polling time: ^I ( 58) minutes. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: SCT capabilities: ^I (0x0001)^ISCT Status supported. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Dec 28 02:06:19 Tower preclear_disk-diff[21437]: SMART Attributes Data Structure revision number: 10 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Vendor Specific SMART Attributes with Thresholds: Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 1 Raw_Read_Error_Rate 0x000f 114 066 034 Pre-fail Always - 124478417 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 3 Spin_Up_Time 0x0003 100 099 000 Pre-fail Always - 0 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 4 Start_Stop_Count 0x0032 001 001 020 Old_age Always FAILING_NOW 351456 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 7 Seek_Error_Rate 0x000f 076 060 030 Pre-fail Always - 13038434889 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 9 Power_On_Hours 0x0032 091 091 000 Old_age Always - 166996918411016 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 10 Spin_Retry_Count 0x0013 100 100 034 Pre-fail Always - 0 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 12 Power_Cycle_Count 0x0032 099 099 020 Old_age Always - 1730 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 184 End-to-End_Error 0x0032 100 253 000 Old_age Always - 0 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 187 Reported_Uncorrect 0x003a 100 100 000 Old_age Always - 0 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 189 High_Fly_Writes 0x0022 100 100 045 Old_age Always - 0 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 190 Airflow_Temperature_Cel 0x0032 059 050 000 Old_age Always - 41 (Min/Max 41/43) Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 3 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 192 Power-Off_Retract_Count 0x0022 087 087 000 Old_age Always - 26933 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 193 Load_Cycle_Count 0x001a 001 001 000 Old_age Always - 375007 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 194 Temperature_Celsius 0x0012 041 050 000 Old_age Always - 41 (0 11 0 0) Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 195 Hardware_ECC_Recovered 0x0010 064 061 000 Old_age Offline - 124478417 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 196 Reallocated_Event_Count 0x003e 095 095 000 Old_age Always - 5185 (62594, 0) Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 197 Current_Pending_Sector 0x0000 100 100 000 Old_age Offline - 0 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 198 Offline_Uncorrectable 0x0032 100 100 000 Old_age Always - 0 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 199 UDMA_CRC_Error_Count 0x0000 200 200 000 Old_age Offline - 0 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 200 Multi_Zone_Error_Rate 0x0000 100 253 000 Old_age Offline - 0 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 202 Data_Address_Mark_Errs 0x0000 100 253 000 Old_age Offline - 0 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 254 Free_Fall_Sensor 0x0000 100 253 000 Old_age Offline - 0 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Dec 28 02:06:19 Tower preclear_disk-diff[21437]: SMART Error Log Version: 1 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: No Errors Logged Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Dec 28 02:06:19 Tower preclear_disk-diff[21437]: SMART Self-test log structure revision number 1 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Dec 28 02:06:19 Tower preclear_disk-diff[21437]: SMART Selective self-test log data structure revision number 1 Dec 28 02:06:19 Tower preclear_disk-diff[21437]: SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 1 0 0 Not_testing Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 2 0 0 Not_testing Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 3 0 0 Not_testing Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 4 0 0 Not_testing Dec 28 02:06:19 Tower preclear_disk-diff[21437]: 5 0 0 Not_testing Dec 28 02:06:19 Tower preclear_disk-diff[21437]: Selective self-test flags (0x0): Dec 28 02:06:19 Tower preclear_disk-diff[21437]: After scanning selected spans, do NOT read-scan remainder of disk. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: If Selective self-test is pending on power-up, resume after 0 minute delay. Dec 28 02:06:19 Tower preclear_disk-diff[21437]: == Dec 28 02:06:19 Tower preclear_disk-diff[21437]: ============================================================================ BTW -- I love my unRAID so far! Thanks in advance. 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.