Jump to content
jbuszkie

Preclear.sh results - Questions about your results? Post them here.

2840 posts in this topic Last Reply

Recommended Posts

Hm... that's interesting that your speeds are that low.  I have precleared several 2 TB drives, from 7200 rpm down to 5400 rpm, and the lowest I've seen was 45 Mb/s.  The 7200 scales roughly 40 - 50% faster as a whole, which is what one might expect.  Never had one take 52 hours for a preclear cycle.  They usually finish @ 35 - 38 hours.  That's running off the motherboard ports.  My system has 2 GB ram in it, but if I remember correctly, when memory becomes an issue, the script either hangs or exits.

Share this post


Link to post

Yeah, that does seem slow.  My latest preclear results were from 2 TB WD EARS Greens (w/ jumpers), and they each took 35 hours.  I precleared 4 simultaneously (using a mixture of onboard and PCIe slots), and the speed didn't change.  Server had only 1 GB of RAM.

Share this post


Link to post

Yeah, that does seem slow.  My latest preclear results were from 2 TB WD EARS Greens (w/ jumpers), and they each took 35 hours.  I precleared 4 simultaneously (using a mixture of onboard and PCIe slots), and the speed didn't change.  Server had only 1 GB of RAM.

Was your unraid array on the same system and was it up?  Mine's on the same system (but most of the time wasn't doing anything!)  So if you have 1GB and I have 1GB, then maybe it's the processor speed?  I think mine's at 900MHz....  Maybe I'll try to bump it up and see what I get for speeds.  

Maybe I'll just hack the script to do the post read...  I'd hate to wait another two days just for a speed experiment! :D

 

Jim

 

And I have the jumper installed...

Share this post


Link to post

The server has to be booted into unRAID to run preclear, so I know unRAID was up, however I don't remember if the array was started or not.  I'm guessing not, since it wouldn't have had any disks assigned anyway, since I was preclearing all of them (this was a brand new server I was building for guiri, another member here).  The CPU was the Sempron 140, which is a single core 2.7 GHz.  900 MHz is pretty slow, maybe that's the reason.

 

Also, no need to 'hack' the script.  Joe L. included many commands that you can append to the initial preclear command that will change what the script does:

-n = Do NOT perform preread and postread of entire disk to allow
            SMART firmware to reallocate bad blocks in the clearing process

       -N = Do not perform read validation during postread. (skip this step)
            (basic test to check if values read are all zero as expected.
             Skipping this test will save a few miniutes, but possibly not detect
             a drive that returns non-zero values when zeros were expected as bad.)

       -c count  =  perform count preread/clear/postread cycles
            where count is a number from 1 through 20
            If not specified, default is 1 cycle.  For large disks, 1 cycle
            can take 10 or more hours

       -t = Test if disk has pre-clear signature.  This option may NOT be
            combined with the -c or -n options.  The test does not write to
            the disk.  It makes no changes to a disk at all. It only reads
            the first 512 bytes of the disk to verify a pre-clear signature
            exists.  Note: "-t" does not read the entire disk to verify it
            it pre-cleared as that could take hours for a large disk. since
            the pre-clear-signature is written *after* a disk is entirely
            filled with zeros, if it exists, we assume the disk is cleared.

       -w size  = write block size in bytes

       -r size  = read block size in bytes

       -b count = number of blocks to read at a time

       -v = print version of ./preclear_disk.sh

       -m email@somedomain.com = optional recipient address.  If blank and -M
            option is used, it will default to default e-mail address of "root"

       -M 1 = Will send an e-mail message at the end of the final results
              (default if -m is used, but no other -M option given)

       -M 2 = Will send an e-mail same as 1 plus at the end of a cycle (if multiple
            cycles are specified)

       -M 3 = Will send an e-mail same as 2 plus at the start and end of the pre-read,
            zeroing, post-read

       -M 4 = Will send an e-mail same as 3 plus also at intervals of 25%
            during the long tests

       The -m, -M options requires that a valid working mail command is installed.
       One version that has worked (bashmail) is affilaited with the unraid_notify script.
       There are others that also will work.

       Any of these need to be configured to work with your mail server.
       The unraid_notify script will have instructions on how to
       configure this. See http://lime-technology.com/forum/index.php?topic=2470.0
       for unraid_notify and http://lime-technology.com/forum/index.php?topic=2961.0
       for the mail script.  NOTE:  The lastest verion of mail has to be used. earlier versions of
       the mail script affiliated with unraid_notify do not support
       the standard mail syntax needed.

       Unless the -n option is specified the disk will first have its entire
       set of blocks read, then, the entire disk will be cleared by writing
       zeros to it.  Once that is done the disk will be partitioned with a
       special signature that the unRAID software will recognize when the
       drive is added to the array.  This special signature will allow the
       unraid software to recognize the disk has been pre-cleared and to skip
       an initial "clearing" step while the server remains off-line.

       The pre-read and post-read phases try their best to exercise the
       disk in a way to identify a drive prone to early failure.  It performs
       reads of random blocks of data interspersed with reads of sequential
       blocks on the disk in turn.  This program also uses non-buffered reads
       of the first and last cylinders on the disk, the goal is to perform
       those reads in between the others, and to keep the disk head
       moving much more than if it just read each linear block in turn.

Take from here.

 

Though reading through the above there doesn't seem to be a command that runs just the post read.  I'm sure Joe could help you with that if needed.

Share this post


Link to post

Was your unraid array on the same system and was it up?

Yes, my unraid was on the same system and was up during the preclear cycles.  In fact, I was writing over 100 GB of data to the array at one point, and only using the onboard SATA ports for all of it.  This is all on a D510 Atom system.  I would venture a guess that processor speed has little to do with preclearing the drive, and that it is most likely RAM and bus related.

Share this post


Link to post

Attached are my preclear_disk logs.

2x new WD20EARS drives.

 

I ran both drives simultaneously with 2 telnet sessions.

 

Don't mind the pre_read speed and time because I changed the system clock during the process - you should add ~4.5-5 hours for the pre-read step.

 

Please see if there is any problem with the drives.

WD20EARS_WCAYY0011814.txt

WD20EARS_WCAVY3082296.txt

Share this post


Link to post

Attached are my preclear_disk logs.

2x new WD20EARS drives.

 

I ran both drives simultaneously with 2 telnet sessions.

 

Don't mind the pre_read speed and time because I changed the system clock during the process - you should add ~4.5-5 hours for the pre-read step.

 

Please see if there is any problem with the drives.

 

they both look perfectly fine.

Share this post


Link to post

I posted a syslog back at the preclear utility thread by mistake, so here it is in the right place.Here are attached two syslogs from preclearing the same drive. I believe some values changed from one preclear to another, so maybe something is wrong with the drive? RMA? What would you do guys? Thanks in advance.

disco_falhou.txt

disco_falhou_2.txt

Share this post


Link to post

The two files you posted seem to be identical...???

 

Both have the same disclaimer at the top of the final output of the pre-clear results:

note, some 'raw' values may change, but not be an indication of a problem

Only a handful of "raw" values mean anything to anyone but the manufacturer.  They intend for us to look only at the "normalized" values.  There is one line in the resulting report where a "raw" count changed that we can interpret directly, the line for Re-Allocated Sectors:

 

The pre preclear values were:

5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 61

The current normalized value is 100

The worst normalized value is 100

The failure threshold for this parameter is 10. 

( If the current value drops below the threshold, the manufacturer will consider the drive to have failed.)

The number of re-allocated sectors is 61. 

(This is one of the few parameters where the "raw' value is meaningful to anyone other than the manufacturer)

 

The post preclear values are:

5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 62

 

The current normalized value is 100    (it is unchanged from the pre test)

The worst normalized value is 100

The failure threshold for this parameter is 10. 

( If the current value drops below the threshold, the manufacturer will consider the drive to have failed.)

The number of re-allocated sectors is 62.    It increased by 1 during the pre-clear process.

(This is one of the few parameters where the "raw' value is meaningful to anyone other than the manufacturer)

 

So.. the clearing process found one sector that it could not read in the pre-read phase and was subsequently re-allocated in the clearing of the drive.  Typically, in a large drive, there are several thousand spare sectors.  The normalized value is unchanged in the post report, and the manufacturer could potentially reject an RMA as the "worst" value is unchanged from its starting value of 100 and nowhere near the failure threshold.

 

If you have time, run another pre-clear cycle or two.  If the re-allocated sector count continues to increase, RMA the drive.  If it stays stable, just keep an eye on it over the next few months as you use it in your array.  Remember that every time you write to the drive the sector will first be read and then written.  It makes it easy for the drive to re-allocate an un-readable sector so your data is pretty safe.  The pre-clear script has read every sector on the disk at least twice, so you can have some faith in the drive as workable.

 

Joe L.

Share this post


Link to post

Can some just verify this is OK, pretty sure it is

=== START OF INFORMATION SECTION ===
Jul 19 09:26:14 Tower preclear_disk-start[6071]: Device Model:     Hitachi HDS721010CLA332
Jul 19 09:26:14 Tower preclear_disk-start[6071]: Serial Number:    JP2930HQ1MWAWH
Jul 19 09:26:14 Tower preclear_disk-start[6071]: Firmware Version: JP4OA39C
Jul 19 09:26:14 Tower preclear_disk-start[6071]: User Capacity:    1,000,204,886,016 bytes
Jul 19 09:26:14 Tower preclear_disk-start[6071]: Device is:        Not in smartctl database [for details use: -P showall]
Jul 19 09:26:14 Tower preclear_disk-start[6071]: ATA Version is:   8
Jul 19 09:26:14 Tower preclear_disk-start[6071]: ATA Standard is:  ATA-8-ACS revision 4
Jul 19 09:26:14 Tower preclear_disk-start[6071]: Local Time is:    Mon Jul 19 09:26:13 2010 EDT
Jul 19 09:26:14 Tower preclear_disk-start[6071]: SMART support is: Available - device has SMART capability.
Jul 19 09:26:14 Tower preclear_disk-start[6071]: SMART support is: Enabled
Jul 19 09:26:14 Tower preclear_disk-start[6071]: 
Jul 19 09:26:14 Tower preclear_disk-start[6071]: === START OF READ SMART DATA SECTION ===
Jul 19 09:26:14 Tower preclear_disk-start[6071]: SMART overall-health self-assessment test result: PASSED
Jul 19 09:26:14 Tower preclear_disk-start[6071]: 
Jul 19 09:26:14 Tower preclear_disk-start[6071]: General SMART Values:
Jul 19 09:26:14 Tower preclear_disk-start[6071]: Offline data collection status:  (0x80)^IOffline data collection activity
Jul 19 09:26:14 Tower preclear_disk-start[6071]: ^I^I^I^I^Iwas never started.
Jul 19 09:26:14 Tower preclear_disk-start[6071]: ^I^I^I^I^IAuto Offline Data Collection: Enabled.
Jul 19 09:26:14 Tower preclear_disk-start[6071]: Self-test execution status:      (   0)^IThe previous self-test routine completed
Jul 19 09:26:14 Tower preclear_disk-start[6071]: ^I^I^I^I^Iwithout error or no self-test has ever 
Jul 19 09:26:14 Tower preclear_disk-start[6071]: ^I^I^I^I^Ibeen run.
Jul 19 09:26:14 Tower preclear_disk-start[6071]: Total time to complete Offline 
Jul 19 09:26:14 Tower preclear_disk-start[6071]: data collection: ^I^I (9988) seconds.
Jul 19 09:26:14 Tower preclear_disk-start[6071]: Offline data collection
Jul 19 09:26:14 Tower preclear_disk-start[6071]: capabilities: ^I^I^I (0x5b) SMART execute Offline immediate.
Jul 19 09:26:14 Tower preclear_disk-start[6071]: ^I^I^I^I^IAuto Offline data collection on/off support.
Jul 19 09:26:14 Tower preclear_disk-start[6071]: ^I^I^I^I^ISuspend Offline collection upon new
Jul 19 09:26:14 Tower preclear_disk-start[6071]: ^I^I^I^I^Icommand.
Jul 19 09:26:14 Tower preclear_disk-start[6071]: ^I^I^I^I^IOffline surface scan supported.
Jul 19 09:26:14 Tower preclear_disk-start[6071]: ^I^I^I^I^ISelf-test supported.
Jul 19 09:26:14 Tower preclear_disk-start[6071]: ^I^I^I^I^INo Conveyance Self-test supported.
Jul 19 09:26:14 Tower preclear_disk-start[6071]: ^I^I^I^I^ISelective Self-test supported.
Jul 19 09:26:14 Tower preclear_disk-start[6071]: SMART capabilities:            (0x0003)^ISaves SMART data before entering
Jul 19 09:26:14 Tower preclear_disk-start[6071]: ^I^I^I^I^Ipower-saving mode.
Jul 19 09:26:14 Tower preclear_disk-start[6071]: ^I^I^I^I^ISupports SMART auto save timer.
Jul 19 09:26:14 Tower preclear_disk-start[6071]: Error logging capability:        (0x01)^IError logging supported.
Jul 19 09:26:14 Tower preclear_disk-start[6071]: ^I^I^I^I^IGeneral Purpose Logging supported.
Jul 19 09:26:14 Tower preclear_disk-start[6071]: Short self-test routine 
Jul 19 09:26:14 Tower preclear_disk-start[6071]: recommended polling time: ^I (   1) minutes.
Jul 19 09:26:14 Tower preclear_disk-start[6071]: Extended self-test routine
Jul 19 09:26:14 Tower preclear_disk-start[6071]: recommended polling time: ^I ( 167) minutes.
Jul 19 09:26:14 Tower preclear_disk-start[6071]: SCT capabilities: ^I       (0x003d)^ISCT Status supported.
Jul 19 09:26:14 Tower preclear_disk-start[6071]: ^I^I^I^I^ISCT Feature Control supported.
Jul 19 09:26:14 Tower preclear_disk-start[6071]: ^I^I^I^I^ISCT Data Table supported.
Jul 19 09:26:14 Tower preclear_disk-start[6071]: 
Jul 19 09:26:14 Tower preclear_disk-start[6071]: SMART Attributes Data Structure revision number: 16
Jul 19 09:26:14 Tower preclear_disk-start[6071]: Vendor Specific SMART Attributes with Thresholds:
Jul 19 09:26:14 Tower preclear_disk-start[6071]: ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
Jul 19 09:26:14 Tower preclear_disk-start[6071]:   1 Raw_Read_Error_Rate     0x000b   100   100   016    Pre-fail  Always       -       0
Jul 19 09:26:14 Tower preclear_disk-start[6071]:   2 Throughput_Performance  0x0005   100   100   054    Pre-fail  Offline      -       0
Jul 19 09:26:14 Tower preclear_disk-start[6071]:   3 Spin_Up_Time            0x0007   118   118   024    Pre-fail  Always       -       320 (Average 321)
Jul 19 09:26:14 Tower preclear_disk-start[6071]:   4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       18
Jul 19 09:26:14 Tower preclear_disk-start[6071]:   5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
Jul 19 09:26:14 Tower preclear_disk-start[6071]:   7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
Jul 19 09:26:14 Tower preclear_disk-start[6071]:   8 Seek_Time_Performance   0x0005   100   100   020    Pre-fail  Offline      -       0
Jul 19 09:26:14 Tower preclear_disk-start[6071]:   9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       7
Jul 19 09:26:14 Tower preclear_disk-start[6071]:  10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
Jul 19 09:26:14 Tower preclear_disk-start[6071]:  12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       15
Jul 19 09:26:14 Tower preclear_disk-start[6071]: 192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       18
Jul 19 09:26:14 Tower preclear_disk-start[6071]: 193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       18
Jul 19 09:26:14 Tower preclear_disk-start[6071]: 196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
Jul 19 09:26:14 Tower preclear_disk-start[6071]: 197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
Jul 19 09:26:14 Tower preclear_disk-start[6071]: 198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
Jul 19 09:26:14 Tower preclear_disk-start[6071]: 199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0
Jul 19 09:26:14 Tower preclear_disk-start[6071]: 
Jul 19 09:26:14 Tower preclear_disk-start[6071]: SMART Error Log Version: 0
Jul 19 09:26:14 Tower preclear_disk-start[6071]: No Errors Logged
Jul 19 09:26:14 Tower preclear_disk-start[6071]: 
Jul 19 09:26:14 Tower preclear_disk-start[6071]: SMART Self-test log structure revision number 1
Jul 19 09:26:14 Tower preclear_disk-start[6071]: No self-tests have been logged.  [To run self-tests, use: smartctl -t]
Jul 19 09:26:14 Tower preclear_disk-start[6071]: 
Jul 19 09:26:14 Tower preclear_disk-start[6071]: 
Jul 19 09:26:14 Tower preclear_disk-start[6071]: SMART Selective self-test log data structure revision number 1
Jul 19 09:26:14 Tower preclear_disk-start[6071]:  SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
Jul 19 09:26:14 Tower preclear_disk-start[6071]:     1        0        0  Not_testing
Jul 19 09:26:14 Tower preclear_disk-start[6071]:     2        0        0  Not_testing
Jul 19 09:26:14 Tower preclear_disk-start[6071]:     3        0        0  Not_testing
Jul 19 09:26:14 Tower preclear_disk-start[6071]:     4        0        0  Not_testing
Jul 19 09:26:14 Tower preclear_disk-start[6071]:     5        0        0  Not_testing
Jul 19 09:26:14 Tower preclear_disk-start[6071]: Selective self-test flags (0x0):
Jul 19 09:26:14 Tower preclear_disk-start[6071]:   After scanning selected spans, do NOT read-scan remainder of disk.
Jul 19 09:26:14 Tower preclear_disk-start[6071]: If Selective self-test is pending on power-up, resume after 0 minute delay.
Jul 19 09:26:14 Tower preclear_disk-start[6071]: 
Jul 19 15:44:19 Tower kernel:  sda: sda1
Jul 19 15:44:29 Tower kernel: udev: starting version 141
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: Home page is http://smartmontools.sourceforge.net/
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: 
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: === START OF INFORMATION SECTION ===
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: Device Model:     Hitachi HDS721010CLA332
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: Serial Number:    JP2930HQ1MWAWH
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: Firmware Version: JP4OA39C
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: User Capacity:    1,000,204,886,016 bytes
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: Device is:        Not in smartctl database [for details use: -P showall]
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: ATA Version is:   8
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: ATA Standard is:  ATA-8-ACS revision 4
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: Local Time is:    Mon Jul 19 22:04:39 2010 EDT
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: SMART support is: Available - device has SMART capability.
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: SMART support is: Enabled
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: 
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: === START OF READ SMART DATA SECTION ===
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: SMART overall-health self-assessment test result: PASSED
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: 
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: General SMART Values:
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: Offline data collection status:  (0x84)^IOffline data collection activity
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: ^I^I^I^I^Iwas suspended by an interrupting command from host.
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: ^I^I^I^I^IAuto Offline Data Collection: Enabled.
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: Self-test execution status:      (   0)^IThe previous self-test routine completed
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: ^I^I^I^I^Iwithout error or no self-test has ever 
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: ^I^I^I^I^Ibeen run.
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: Total time to complete Offline 
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: data collection: ^I^I (9988) seconds.
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: Offline data collection
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: capabilities: ^I^I^I (0x5b) SMART execute Offline immediate.
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: ^I^I^I^I^IAuto Offline data collection on/off support.
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: ^I^I^I^I^ISuspend Offline collection upon new
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: ^I^I^I^I^Icommand.
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: ^I^I^I^I^IOffline surface scan supported.
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: ^I^I^I^I^ISelf-test supported.
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: ^I^I^I^I^INo Conveyance Self-test supported.
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: ^I^I^I^I^ISelective Self-test supported.
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: SMART capabilities:            (0x0003)^ISaves SMART data before entering
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: ^I^I^I^I^Ipower-saving mode.
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: ^I^I^I^I^ISupports SMART auto save timer.
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: Error logging capability:        (0x01)^IError logging supported.
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: ^I^I^I^I^IGeneral Purpose Logging supported.
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: Short self-test routine 
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: recommended polling time: ^I (   1) minutes.
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: Extended self-test routine
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: recommended polling time: ^I ( 167) minutes.
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: SCT capabilities: ^I       (0x003d)^ISCT Status supported.
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: ^I^I^I^I^ISCT Feature Control supported.
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: ^I^I^I^I^ISCT Data Table supported.
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: 
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: SMART Attributes Data Structure revision number: 16
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: Vendor Specific SMART Attributes with Thresholds:
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
Jul 19 22:04:40 Tower preclear_disk-finish[1110]:   1 Raw_Read_Error_Rate     0x000b   100   100   016    Pre-fail  Always       -       0
Jul 19 22:04:40 Tower preclear_disk-finish[1110]:   2 Throughput_Performance  0x0005   100   100   054    Pre-fail  Offline      -       0
Jul 19 22:04:40 Tower preclear_disk-finish[1110]:   3 Spin_Up_Time            0x0007   118   118   024    Pre-fail  Always       -       320 (Average 321)
Jul 19 22:04:40 Tower preclear_disk-finish[1110]:   4 Start_Stop_Count        0x0012   100   100   000    Old_age   Always       -       18
Jul 19 22:04:40 Tower preclear_disk-finish[1110]:   5 Reallocated_Sector_Ct   0x0033   100   100   005    Pre-fail  Always       -       0
Jul 19 22:04:40 Tower preclear_disk-finish[1110]:   7 Seek_Error_Rate         0x000b   100   100   067    Pre-fail  Always       -       0
Jul 19 22:04:40 Tower preclear_disk-finish[1110]:   8 Seek_Time_Performance   0x0005   100   100   020    Pre-fail  Offline      -       0
Jul 19 22:04:40 Tower preclear_disk-finish[1110]:   9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       19
Jul 19 22:04:40 Tower preclear_disk-finish[1110]:  10 Spin_Retry_Count        0x0013   100   100   060    Pre-fail  Always       -       0
Jul 19 22:04:40 Tower preclear_disk-finish[1110]:  12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       15
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: 192 Power-Off_Retract_Count 0x0032   100   100   000    Old_age   Always       -       18
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: 193 Load_Cycle_Count        0x0012   100   100   000    Old_age   Always       -       18
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: 196 Reallocated_Event_Count 0x0032   100   100   000    Old_age   Always       -       0
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: 197 Current_Pending_Sector  0x0022   100   100   000    Old_age   Always       -       0
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: 198 Offline_Uncorrectable   0x0008   100   100   000    Old_age   Offline      -       0
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: 199 UDMA_CRC_Error_Count    0x000a   200   200   000    Old_age   Always       -       0
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: 
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: SMART Error Log Version: 0
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: No Errors Logged
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: 
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: SMART Self-test log structure revision number 1
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: No self-tests have been logged.  [To run self-tests, use: smartctl -t]
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: 
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: 
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: SMART Selective self-test log data structure revision number 1
Jul 19 22:04:40 Tower preclear_disk-finish[1110]:  SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
Jul 19 22:04:40 Tower preclear_disk-finish[1110]:     1        0        0  Not_testing
Jul 19 22:04:40 Tower preclear_disk-finish[1110]:     2        0        0  Not_testing
Jul 19 22:04:40 Tower preclear_disk-finish[1110]:     3        0        0  Not_testing
Jul 19 22:04:40 Tower preclear_disk-finish[1110]:     4        0        0  Not_testing
Jul 19 22:04:40 Tower preclear_disk-finish[1110]:     5        0        0  Not_testing
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: Selective self-test flags (0x0):
Jul 19 22:04:40 Tower preclear_disk-finish[1110]:   After scanning selected spans, do NOT read-scan remainder of disk.
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: If Selective self-test is pending on power-up, resume after 0 minute delay.
Jul 19 22:04:40 Tower preclear_disk-finish[1110]: 
Jul 19 22:04:40 Tower preclear_disk-diff[1123]: ============================================================================
Jul 19 22:04:40 Tower preclear_disk-diff[1123]: ==
Jul 19 22:04:40 Tower preclear_disk-diff[1123]: == Disk /dev/sda has been successfully precleared
Jul 19 22:04:40 Tower preclear_disk-diff[1123]: ==
Jul 19 22:04:40 Tower preclear_disk-diff[1123]: == Ran 1 preclear-disk cycle
Jul 19 22:04:40 Tower preclear_disk-diff[1123]: ==
Jul 19 22:04:40 Tower preclear_disk-diff[1123]: == Using :Read block size = 8225280 Bytes
Jul 19 22:04:40 Tower preclear_disk-diff[1123]: == Last Cycle's Pre Read Time  : 3:36:28 (77 MB/s)
Jul 19 22:04:40 Tower preclear_disk-diff[1123]: == Last Cycle's Zeroing time   : 2:40:50 (103 MB/s)
Jul 19 22:04:40 Tower preclear_disk-diff[1123]: == Last Cycle's Post Read Time : 6:19:57 (43 MB/s)
Jul 19 22:04:40 Tower preclear_disk-diff[1123]: == Last Cycle's Total Time     : 12:38:26
Jul 19 22:04:40 Tower preclear_disk-diff[1123]: ==
Jul 19 22:04:40 Tower preclear_disk-diff[1123]: == Total Elapsed Time 12:38:26
Jul 19 22:04:40 Tower preclear_disk-diff[1123]: ==
Jul 19 22:04:40 Tower preclear_disk-diff[1123]: == Disk Start Temperature: 28C
Jul 19 22:04:40 Tower preclear_disk-diff[1123]: ==
Jul 19 22:04:40 Tower preclear_disk-diff[1123]: == Current Disk Temperature: 30C, 
Jul 19 22:04:40 Tower preclear_disk-diff[1123]: ==
Jul 19 22:04:40 Tower preclear_disk-diff[1123]: ============================================================================
Jul 19 22:04:40 Tower preclear_disk-diff[1123]: S.M.A.R.T. error count differences detected after pre-clear 
Jul 19 22:04:40 Tower preclear_disk-diff[1123]: note, some 'raw' values may change, but not be an indication of a problem
Jul 19 22:04:40 Tower preclear_disk-diff[1123]: 19,20c19,20
Jul 19 22:04:40 Tower preclear_disk-diff[1123]: < Offline data collection status:  (0x80)^IOffline data collection activity
Jul 19 22:04:40 Tower preclear_disk-diff[1123]: < ^I^I^I^I^Iwas never started.
Jul 19 22:04:40 Tower preclear_disk-diff[1123]: ---
Jul 19 22:04:40 Tower preclear_disk-diff[1123]: > Offline data collection status:  (0x84)^IOffline data collection activity
Jul 19 22:04:40 Tower preclear_disk-diff[1123]: > ^I^I^I^I^Iwas suspended by an interrupting command from host. 
Jul 19 22:04:40 Tower preclear_disk-diff[1123]: ============================================================================
Jul 19 22:04:40 Tower preclear_disk-diff[1123]:  

 

Share this post


Link to post

Ran the script on my new build, got this weird error message:

 

http://pastebin.com/u0Uk1KuD

 

It also killed unmenu, but the regular webserver kept running.

 

Any idea?

Kernel Oops are usually memory related.

Have you run a memory test?  Did you specifically set the memory voltage, timing, and clock speed, or did you let the BIOS do it for you.

Some BIOS get it right, others get it very wrong.  It must be set for your specific model/brand of RAM.

 

How much RAM do you have?  Is it less than 512 Meg?

 

Joe L.

 

Share this post


Link to post

Ah yes, it's 2 sticks of 2GB of DDR3 ram... didn't set it up in the BIOS... or run a memtest yet either...

 

D'oh! And now it's located far from any monitors... time to go lug the beast back to a screen.

 

Thanks Joe!

 

 

Share this post


Link to post

Okay, I have this RAM: http://www.tigerdirect.com/applications/searchtools/item-details.asp?EdpNo=4837614&csid=ITD&body=MAIN#detailspecs

 

I set the 9-9-9-24 timings in my BIOS, running memtest now... but it reports it as 6-6-6-15.

 

Does memtest read wrong? Or is my BIOS fighting me?

 

Are there any parameters I should set besides the basic timings?

Timing, voltage, and clock speed.

 

I would be inclined to believe memtest.  And 6-6-6-15 might be too aggressive if the strips are designed for 9-9-9-24

 

Joe L.

Share this post


Link to post

Just built my first unRAID box.  Decided better safe than sorry.  Here are my pre-clear results for my 2 WD 15EARs with jumpers installed.

 

 

HD1

: smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen
: Home page is http://smartmontools.sourceforge.net/
: 
: === START OF INFORMATION SECTION ===
: Device Model:     WDC WD15EARS-00Z5B1
: Serial Number:    WD-WMAVU2866034
: Firmware Version: 80.00A80
: User Capacity:    1,500,301,910,016 bytes
: Device is:        Not in smartctl database [for details use: -P showall]
: ATA Version is:   8
: ATA Standard is:  Exact ATA specification draft version not indicated
: Local Time is:    Mon Jul 26 22:33:11 2010 CDT
: SMART support is: Available - device has SMART capability.
: SMART support is: Enabled
: 

: SMART Attributes Data Structure revision number: 16
: Vendor Specific SMART Attributes with Thresholds:
: ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
:   1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
:   3 Spin_Up_Time            0x0027   190   189   021    Pre-fail  Always       -       5458
:   4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       17
:   5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
:   7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
:   9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       26
:  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       -       15
: 192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       11
: 193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       35
: 196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
: 197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
: 198 Offline_Uncorrectable   0x0030   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
: No Errors Logged
: 
: SMART Self-test log structure revision number 1
: Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
: # 1  Short offline       Completed without error       00%         0         -
: 
: 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.
: 
: ============================================================================
: ==
: == Disk /dev/sda has been successfully precleared
: ==
: == Ran 1 preclear-disk cycle
: ==
: == Using :Read block size = 8225280 Bytes
: == Last Cycle's Pre Read Time  : 6:23:20 (65 MB/s)
: == Last Cycle's Zeroing time   : 6:56:01 (60 MB/s)
: == Last Cycle's Post Read Time : 11:39:50 (35 MB/s)
: == Last Cycle's Total Time     : 25:00:20
: ==
: == Total Elapsed Time 25:00:20
: ==
: == Disk Start Temperature: 28C
: ==
: == Current Disk Temperature: 34C, 
: ==
: ============================================================================
: S.M.A.R.T. error count differences detected after pre-clear 
: note, some 'raw' values may change, but not be an indication of a problem
: 19,20c19,20
: < Offline data collection status:  (0x80)^IOffline data collection activity
: < ^I^I^I^I^Iwas never started.
: ---
: > Offline data collection status:  (0x84)^IOffline data collection activity
: > ^I^I^I^I^Iwas suspended by an interrupting command from host.
: 54c54
: <   1 Raw_Read_Error_Rate     0x002f   100   253   051    Pre-fail  Always       -       0
: ---
: >   1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
: 58c58
: <   7 Seek_Error_Rate         0x002e   100   253   000    Old_age   Always       -       0
: ---
: >   7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
: 63c63
: < 193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       34
: ---
: > 193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       35 
: ============================================================================
:  

 

HD2

: smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen
: Home page is http://smartmontools.sourceforge.net/
: 
: === START OF INFORMATION SECTION ===
: Device Model:     WDC WD15EARS-00Z5B1
: Serial Number:    WD-WMAVU2807772
: Firmware Version: 80.00A80
: User Capacity:    1,500,301,910,016 bytes
: Device is:        Not in smartctl database [for details use: -P showall]
: ATA Version is:   8
: ATA Standard is:  Exact ATA specification draft version not indicated
: Local Time is:    Mon Jul 26 22:45:02 2010 CDT
: 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
: 

: SMART Attributes Data Structure revision number: 16
: Vendor Specific SMART Attributes with Thresholds:
: ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
:   1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
:   3 Spin_Up_Time            0x0027   189   187   021    Pre-fail  Always       -       5550
:   4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       17
:   5 Reallocated_Sector_Ct   0x0033   200   200   140    Pre-fail  Always       -       0
:   7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
:   9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       26
:  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       -       15
: 192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       11
: 193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       41
: 196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
: 197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
: 198 Offline_Uncorrectable   0x0030   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
: 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.
: 
: ============================================================================
: ==
: == Disk /dev/sdb has been successfully precleared
: ==
: == Ran 1 preclear-disk cycle
: ==
: == Using :Read block size = 8225280 Bytes
: == Last Cycle's Pre Read Time  : 6:25:07 (64 MB/s)
: == Last Cycle's Zeroing time   : 6:56:40 (60 MB/s)
: == Last Cycle's Post Read Time : 11:47:39 (35 MB/s)
: == Last Cycle's Total Time     : 25:10:33
: ==
: == Total Elapsed Time 25:10:33
: ==
: == Disk Start Temperature: 27C
: ==
: == Current Disk Temperature: 33C, 
: ==
: ============================================================================
: S.M.A.R.T. error count differences detected after pre-clear 
: note, some 'raw' values may change, but not be an indication of a problem
: 19,20c19,20
: < Offline data collection status:  (0x80)^IOffline data collection activity
: < ^I^I^I^I^Iwas never started.
: ---
: > Offline data collection status:  (0x84)^IOffline data collection activity
: > ^I^I^I^I^Iwas suspended by an interrupting command from host.
: 54c54
: <   1 Raw_Read_Error_Rate     0x002f   100   253   051    Pre-fail  Always       -       0
: ---
: >   1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
: 58c58
: <   7 Seek_Error_Rate         0x002e   100   253   000    Old_age   Always       -       0
: ---
: >   7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
: 63c63
: < 193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       40
: ---
: > 193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       41 
: ============================================================================
:  

 

I think it all looks good (but I've been known to wrong).  Please take a look and let me know.

 

Thanks.

Share this post


Link to post

Hi, just finnished a pre clear of my new 1.5TB WD disk, is this disk OK?

 

=                unRAID server Pre-Clear disk /dev/sdd
=                       cycle 1 of 1
= Disk Pre-Clear-Read completed                                 DONE
= Step 1 of 10 - Copying zeros to first 2048k bytes             DONE
= Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE
= Step 3 of 10 - Disk is now cleared from MBR onward.           DONE
= Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4       DONE
= Step 5 of 10 - Clearing MBR code area                         DONE
= Step 6 of 10 - Setting MBR signature bytes                    DONE
= Step 7 of 10 - Setting partition 1 to precleared state        DONE
= Step 8 of 10 - Notifying kernel we changed the partitioning   DONE
= Step 9 of 10 - Creating the /dev/disk/by* entries             DONE
= Step 10 of 10 - Testing if the clear has been successful.     DONE
= Disk Post-Clear-Read completed                                DONE
Disk Temperature: 24C, Elapsed Time:  24:58:49
============================================================================
==
== Disk /dev/sdd has been successfully precleared
==
============================================================================
S.M.A.R.T. error count differences detected after pre-clear
note, some 'raw' values may change, but not be an indication of a problem
19,20c19,20
< Offline data collection status:  (0x80)       Offline data collection activity
<                                       was never started.
---
> Offline data collection status:  (0x84)       Offline data collection activity
>                                       was suspended by an interrupting command from host.
54c54
<   1 Raw_Read_Error_Rate     0x002f   100   253   051    Pre-fail  Always       -       0
---
>   1 Raw_Read_Error_Rate     0x002f   200   200   051    Pre-fail  Always       -       0
58c58
<   7 Seek_Error_Rate         0x002e   100   253   000    Old_age   Always       -       0
---
>   7 Seek_Error_Rate         0x002e   200   200   000    Old_age   Always       -       0
63c63
< 193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       12
---
> 193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       14
============================================================================

 

 

Smart results

 

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD15EARS-00Z5B1
Serial Number:    WD-WMAVU2990125
Firmware Version: 80.00A80
User Capacity:    1,500,301,910,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Tue Jul 27 13:12:02 2010 CEST
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:  (0x84)	Offline data collection activity
				was suspended by an interrupting command from host.
				Auto Offline Data Collection: Enabled.
Self-test execution status:      (   0)	The previous self-test routine completed
				without error or no self-test has ever 
				been run.
Total time to complete Offline 
data collection: 		 (34800) 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: 	       (0x3031)	SCT Status 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   200   200   051    Pre-fail  Always       -       0
  3 Spin_Up_Time            0x0027   188   188   021    Pre-fail  Always       -       5558
  4 Start_Stop_Count        0x0032   100   100   000    Old_age   Always       -       10
  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       -       24
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       -       8
192 Power-Off_Retract_Count 0x0032   200   200   000    Old_age   Always       -       7
193 Load_Cycle_Count        0x0032   200   200   000    Old_age   Always       -       29
194 Temperature_Celsius     0x0022   126   120   000    Old_age   Always       -       24
196 Reallocated_Event_Count 0x0032   200   200   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0032   200   200   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0030   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
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.

Share this post


Link to post
I think it all looks good (but I've been known to wrong).  Please take a look and let me know.

As you said, both disks look good.

 

Good luck with your server.

 

Joe L.

Share this post


Link to post

Hi, just finnished a pre clear of my new 1.5TB WD disk, is this disk OK?

Other than you spelled "finished" with a double "n", yes. ;D

Share this post


Link to post

Sweet! Thanks Joe!!

 

Time to move all those loud, heat generating, clicking and whirring movies off my HTPC into the unraid closet!  ;D

Share this post


Link to post

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.