Jump to content

Re: preclear_disk.sh - a new utility to burn-in and pre-clear disks for quick add


Recommended Posts

I haven't precleared a disk in over a year and I received a 2TB WD Red drive from my brother as a Xmas gift. Has anything changed that I should be aware of since then? It's been so long that I've forgotten all the commands and steps to doing a preclear too.

Always make sure you have the latest preclear version. 

Type:

preclear_disk.sh -v

to verify.  (as of this post, it is version 1.13)

Link to comment

I haven't precleared a disk in over a year and I received a 2TB WD Red drive from my brother as a Xmas gift. Has anything changed that I should be aware of since then? It's been so long that I've forgotten all the commands and steps to doing a preclear too.

Always make sure you have the latest preclear version. 

Type:

preclear_disk.sh -v

to verify.  (as of this post, it is version 1.13)

 

Hi Joe. I forgot all about this post from 5 months ago. I looked up the commands and everything was good to go :)

Link to comment
  • 3 weeks later...

Joe -

 

First, my many thanks!

 

Second, if a preclear writes all zeroes - why do we do additional preclears without first writing all ones?  I understand it can find sectors that are going bad or kick off a failing smart param - but can this not hide write issues?

 

Thanks

Link to comment

I am about to do a test build of an esxi system with 3 pass through M1015 on a X9SCM-F board with a E-1230V2 which is supposed to not work.  I suspect that the new firmware may and I stress may have fixed the issue.  I have got myself some 20 odd 2tb sata drives to play with for the test but I don't have the time to preclear them.  Basically what I want to do is add 20 to 22 of the disks to my build add them to an array without a cache drive and there will be no data as it is a test.  Once I add the drives prove that it works copy some data up and down then add another drive as cache and let it start to do a parity creation to stress reading and writing over all the disks. 

 

Now because this is only a test and the information of the drives is irrelevant is there a way to write the preclear signature with enough of the system erased without having to do a full preclear on all 20 odd drives??  It appears as tho I can skip pre and post reads and zero the mbr but this option says nothing else so I don't know if that means it does nothing else or will write a signature with only the mbr being zeroed.  Any help appreciated.  Found plenty of posts saying your data will be unprotected by adding a non zeroed drive but I have no data and don't care it is a fresh no data test build.

 

:) 

Link to comment

Until you assign a parity drive, unRAID will not clear additional drives added to the array to maintain parity.

When adding all drives initially (with or without a parity drive) none f the drives are cleared before formatting.

Parity creation READS the data disks and WRITES the parity disk.  It does nothing to determine if the data WRITTEN to the parity disk is READABLE

(You must perform a subsequent parity "check" to verify if the parity disk is readable.)

 

You can at any time set a new disk configuration (immediately invalidating parity), and when you next start the array parity will be calculated again, and no assigned disk will be cleared.

 

Enjoy your testing.

Link to comment
  • 3 weeks later...

Joe can you help on this one...

 

I precleared one of the disks and this was the output. Does not even look like it finished properly.

I see some syntax errors. This is with version 1.13 preclear script. Looks like an issue with the script maybe.

 

================================================================== 1.13

=                unRAID server Pre-Clear disk /dev/sdh

=              cycle 1 of 1, partition start on sector 64

= 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

=  **** This will take a while... you can follow progress below:

=

=

=

=

=

=

=

=

Elapsed Time:  6:24:25

0+0 records in

0+0 records out

0 bytes (0 B) copied, 0.0125323 s, 0.0 kB/s

./preclear_disk.sh: line 642: let: percent_wrote=(0 / ): syntax error: operand expected (error token is ")")

Wrote  0  bytes out of    bytes (% Done)

./preclear_disk.sh: line 1849: / (1373192449 - 1373192422) / 1000000 : syntax error: operand expected (error token is "/ (1373192449 - 1373192422) / 1000000 ")

========================================================================1.13

==  WDC WD20EARS-00MVWB0    WD-WMAZA3775121

== Disk /dev/sdh has been successfully precleared

== with a starting sector of 64

============================================================================

./preclear_disk.sh: line 817: [: : integer expression expected

./preclear_disk.sh: line 817: [: : integer expression expected

./preclear_disk.sh: line 817: [: : integer expression expected

./preclear_disk.sh: line 817: [: : integer expression expected

./preclear_disk.sh: line 817: [: : integer expression expected

./preclear_disk.sh: line 817: [: : integer expression expected

./preclear_disk.sh: line 817: [: : integer expression expected

./preclear_disk.sh: line 817: [: : integer expression expected

./preclear_disk.sh: line 817: [: : integer expression expected

./preclear_disk.sh: line 817: [: : integer expression expected

./preclear_disk.sh: line 817: [: : integer expression expected

./preclear_disk.sh: line 817: [: : integer expression expected

./preclear_disk.sh: line 817: [: : integer expression expected

./preclear_disk.sh: line 817: [: : integer expression expected

./preclear_disk.sh: line 817: [: : integer expression expected

./preclear_disk.sh: line 817: [: : integer expression expected

./preclear_disk.sh: line 817: [: : integer expression expected

** Changed attributes in files: /tmp/smart_start_sdh  /tmp/smart_finish_sdh

                ATTRIBUTE  NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE

      Raw_Read_Error_Rate =  200      ok

            Spin_Up_Time =  205      ok

        Start_Stop_Count =  100      ok

    Reallocated_Sector_Ct =  200      ok

          Seek_Error_Rate =  200      ok

          Power_On_Hours =    77      ok

        Spin_Retry_Count =  100      ok

  Calibration_Retry_Count =  100      ok

        Power_Cycle_Count =  100      ok

  Power-Off_Retract_Count =  200      ok

        Load_Cycle_Count =  199      ok

      Temperature_Celsius =  123      ok

  Reallocated_Event_Count =  200      ok

  Current_Pending_Sector =  200      ok

    Offline_Uncorrectable =  200      ok

    UDMA_CRC_Error_Count =  200      ok

    Multi_Zone_Error_Rate =  200      ok

No SMART attributes are FAILING_NOW

 

3 sectors were pending re-allocation before the start of the preclear.

 

    a change of -3 in the number of sectors pending re-allocation.

0 sectors had been re-allocated before the start of the preclear.

    a change of 0 in the number of sectors re-allocated.

SMART overall-health status =

root@Tower3:/boot/scripts#

 

Link to comment

When I run the following command on the drive:

 

smartctl  -a  -d  ata  /dev/sdh | todos >/boot/data/smart_report_disk6.txt

 

I get this:

 

smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build)

Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

 

Smartctl: Device Read Identity Failed (not an ATA/ATAPI device)

 

A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

 

Link to comment

When I run the following command on the drive:

 

smartctl  -a  -d  ata  /dev/sdh | todos >/boot/data/smart_report_disk6.txt

 

I get this:

 

smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build)

Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

 

Smartctl: Device Read Identity Failed (not an ATA/ATAPI device)

 

A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

Either change the "-d ata" to "-d sat" or "-A" instead.
Link to comment

I am wondering if this Supermicro AOC-SASLP-MVL8 is causing me issues. They are supposed to be great SATA controllers.

 

I tried this:

 

smartctl  -a  -d  sat  /dev/sdh | todos >/boot/data/smart_report_disk6.txt

 

Gave me this:

 

smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build)

Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

 

=== START OF INFORMATION SECTION ===

Device Model:    [No Information Found]

Serial Number:    [No Information Found]

Firmware Version: [No Information Found]

Device is:        Not in smartctl database [for details use: -P showall]

ATA Version is:  [No Information Found]

ATA Standard is:  [No Information Found]

Local Time is:    Tue Jul  9 20:56:20 2013 EDT

SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported.

SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled.

A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

 

Link to comment

I am wondering if this Supermicro AOC-SASLP-MVL8 is causing me issues. They are supposed to be great SATA controllers.

 

I tried this:

 

smartctl  -a  -d  sat  /dev/sdh | todos >/boot/data/smart_report_disk6.txt

 

Gave me this:

 

smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build)

Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net

 

=== START OF INFORMATION SECTION ===

Device Model:    [No Information Found]

Serial Number:    [No Information Found]

Firmware Version: [No Information Found]

Device is:        Not in smartctl database [for details use: -P showall]

ATA Version is:  [No Information Found]

ATA Standard is:  [No Information Found]

Local Time is:    Tue Jul  9 20:56:20 2013 EDT

SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if SMART supported.

SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 85-87 don't show if SMART is enabled.

A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

looks to me like the drive is not responding at all.

 

Have you tried

hdparm -i /dev/sdh

Link to comment

here is the output

 

root@Tower3:/boot/scripts# hdparm -i /dev/sdh

 

/dev/sdh:

HDIO_DRIVE_CMD(identify) failed: Input/output error

HDIO_GET_IDENTITY failed: No message of desired type

 

I think UNRAID has an issue with the Supermicro AOC-SASLP-MVL8. Is this SATA addon card supported? I thought it was or I would not have spent over $100 on it.

 

Can anyone confirm that the Supermicro AOC-SASLP-MVL8 is supported in UNRAID?

 

I posted a syslog of startup with the SATA board installed. Can someone confirm it is ok?

 

http://lime-technology.com/forum/index.php?topic=28406.0

 

Link to comment

I think UNRAID has an issue with the Supermicro AOC-SASLP-MVL8. Is this SATA addon card supported? I thought it was or I would not have spent over $100 on it.

 

Can anyone confirm that the Supermicro AOC-SASLP-MVL8 is supported in UNRAID?

This card is definitely supported.  I have two of them in my system and they work just fine.  I think it may well be one of the most commonly used expansion cards with unRAID.

 

My guess is that the drive is having problems.  Whether it is the drive itself, or something like cabling or power is not clear.

Link to comment

here is the output

 

root@Tower3:/boot/scripts# hdparm -i /dev/sdh

 

/dev/sdh:

HDIO_DRIVE_CMD(identify) failed: Input/output error

HDIO_GET_IDENTITY failed: No message of desired type

 

I think UNRAID has an issue with the Supermicro AOC-SASLP-MVL8. Is this SATA addon card supported? I thought it was or I would not have spent over $100 on it.

 

Can anyone confirm that the Supermicro AOC-SASLP-MVL8 is supported in UNRAID?

 

I posted a syslog of startup with the SATA board installed. Can someone confirm it is ok?

 

http://lime-technology.com/forum/index.php?topic=28406.0

The errors you are getting are consistent with a drive that has stopped responding to commands.

It could be the disk itself, or a cable to it, or a disk controller port.  It may even start responding again if power cycled. (it is locked up by buggy firmware on the disk)

 

In any case, you can isolate the issue by re-seating/replacing the cables to the drive, trying a different disk controller port, etc.

 

 

Link to comment

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.

×
×
  • Create New...