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


Recommended Posts

This is a brand new WD20EARS. The report looks good, but I'd like to have another set of experienced eyes look it over, please.

 

Disk: /dev/sdc
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 WD20EARS-00MVWB0
Serial Number:    WD-WMAZA3212657
Firmware Version: 51.0AB51
User Capacity:    2,000,398,934,016 bytes
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   8
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Fri Feb  4 20:19:37 2011 PST
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: 		 (38100) 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: 	       (0x3035)	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   253   253   021    Pre-fail  Always       -       1125
  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   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       -       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       -       15
194 Temperature_Celsius     0x0022   119   116   000    Old_age   Always       -       31
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.

First, that is a smartctl report, not a preclear_disk.sh report.

 

Second, we really cannot tell much from that report other than it cannot be from the end of a preclear cycle since it only shows 26 hours of operation.  From what I been hearing from other unRAID users, it takes between 33 and 35 hours to run a full cycle on a 2TB drive.

 

26 hours seems a bit too little time.  I suspect that might be a report from the start of a preclear cycle.

Link to comment
========================================================================1.3
== invoked as: ./preclear_disk.sh -A /dev/sdc
==
== Disk /dev/sdc has been successfully precleared
== with a starting sector of 64 
== Ran 1 cycle
==
== Using :Read block size = 8225280 Bytes
== Last Cycle's Pre Read Time  : 6:32:44 (84 MB/s)
== Last Cycle's Zeroing time   : 6:25:28 (86 MB/s)
== Last Cycle's Post Read Time : 13:13:50 (41 MB/s)
== Last Cycle's Total Time     : 26:13:08
==
== Total Elapsed Time 26:13:08
==
== Disk Start Temperature: 28C
==
== Current Disk Temperature: 31C, 
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdc  /tmp/smart_finish_sdc
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Temperature_Celsius =   119     122            0        ok          31
No SMART attributes are FAILING_NOW

0 sectors were pending re-allocation before the start of the preclear.
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. 
============================================================================

Link to comment

========================================================================1.3
== invoked as: ./preclear_disk.sh -A /dev/sdc
==
== Disk /dev/sdc has been successfully precleared
== with a starting sector of 64 
== Ran 1 cycle
==
== Using :Read block size = 8225280 Bytes
== Last Cycle's Pre Read Time  : 6:32:44 (84 MB/s)
== Last Cycle's Zeroing time   : 6:25:28 (86 MB/s)
== Last Cycle's Post Read Time : 13:13:50 (41 MB/s)
== Last Cycle's Total Time     : 26:13:08
==
== Total Elapsed Time 26:13:08
==
== Disk Start Temperature: 28C
==
== Current Disk Temperature: 31C, 
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sdc  /tmp/smart_finish_sdc
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Temperature_Celsius =   119     122            0        ok          31
No SMART attributes are FAILING_NOW

0 sectors were pending re-allocation before the start of the preclear.
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. 
============================================================================

You must have a very fast (and very nice) disk controller in that server of yours.  I was wrong, as the preclear did run in 26 hours.

 

The report says it all.  The only attribute that changes in any way you might care about was the drive temperature. It went from 28C to 31C.  (You must have good fans too.)

 

Joe L.

PS.

You are also running the slightly older version of preclear. I posted version 1.4 this morning.  It has a few new features, but none that changed the output report.

 

Joe L.

Link to comment

First, that is a smartctl report, not a preclear_disk.sh report.

 

Second, we really cannot tell much from that report other than it cannot be from the end of a preclear cycle since it only shows 26 hours of operation.  From what I been hearing from other unRAID users, it takes between 33 and 35 hours to run a full cycle on a 2TB drive.

 

26 hours seems a bit too little time.  I suspect that might be a report from the start of a preclear cycle.

 

None of my four pre-clears have taken over 27 hours. Now I'm concerned.

Link to comment

You must have a very fast (and very nice) disk controller in that server of yours.  I was wrong, as the preclear did run in 26 hours.

The report says it all.  The only attribute that changes in any way you might care about was the drive temperature. It went from 28C to 31C.  (You must have good fans too.)

 

Joe L.

PS.

You are also running the slightly older version of preclear. I posted version 1.4 this morning.  It has a few new features, but none that changed the output report.

 

Joe L.

 

Thanks Joe!

 

I saw the v1.4 released today, but I was 10 hours into the pre-clear already.

Link to comment

First, that is a smartctl report, not a preclear_disk.sh report.

 

Second, we really cannot tell much from that report other than it cannot be from the end of a preclear cycle since it only shows 26 hours of operation.  From what I been hearing from other unRAID users, it takes between 33 and 35 hours to run a full cycle on a 2TB drive.

 

26 hours seems a bit too little time.  I suspect that might be a report from the start of a preclear cycle.

 

None of my four pre-clears have taken over 27 hours. Now I'm concerned.

It just indicates you have fast disks and a fast disk controller.
Link to comment

First, that is a smartctl report, not a preclear_disk.sh report.

 

Second, we really cannot tell much from that report other than it cannot be from the end of a preclear cycle since it only shows 26 hours of operation.  From what I been hearing from other unRAID users, it takes between 33 and 35 hours to run a full cycle on a 2TB drive.

 

26 hours seems a bit too little time.  I suspect that might be a report from the start of a preclear cycle.

 

None of my four pre-clears have taken over 27 hours. Now I'm concerned.

It just indicates you have fast disks and a fast disk controller.

 

All of my WD 2TB EARS have taken 26+ hours. I was originally a little worried that it was taking too long. Glad to hear this is all normal.

Link to comment

Hi my putty telnet software time out overnight the system went into sleep mode is there a way to reset putty to see what the present status is of the preclear?

thanks Lou

Unless you started the preclear using "screen" it is easy to know the status. The preclear was terminated when the telnet session terminated.

 

If you are using the 1.3 or 1.4 version of preclear you will find a preclear_reports directory on your flash drive if it completed. In that directory will be the final reports.

 

Otherwise, you can get an idea of how far it might have gotten by looking in the /tmp directory.

If there is a file named /tmp/zerosdX, where sdX = the three letter drive designation, you can type

tail /tmp/zerosdX

to get an idea how far it got.  

To see when it quit you might be able to look at its time-stamp on the file with

ls -l /tmp/zero*

 

That file is only used when actually zeroing the disk.  If the preclear terminated before it got to the "write" phase, it will not be present.

You will need to start it as if it had never performed the process at all.

 

If the last line in /tmp/zero* does not have the full number of bytes on your disk, it would have terminated in the write phase.

 

You can re-start the process using the -W option if the "/tmp/zero*" file is present.  It will then do only the "write" phase and post-read-verify phases.

preclear_disk.sh -W /dev/sdX

If the "write" phase was completed, or you suspect it was, you can test if the pre-clear signature is present by using

preclear_disk.sh -t /dev/sdX

If it is you can use the new

"-V" option to perform only the post-read-verify phase.

 

preclear_disk.sh -V /dev/sdX

 

You can use the -A option on any of the above preclear_disk.sh commands to specify a 4k-aligned sector 64 start.

You should download and use the latest version of the preclear script.    I've been constantly improving the output report.

The last version as of this post is version 1.4

You can see the version by typing

preclear_disk.sh -v

Joe L.

Link to comment

Hi my putty telnet software time out overnight the system went into sleep mode is there a way to reset putty to see what the present status is of the preclear?

thanks Lou

Unless you started the preclear using "screen" it is easy to know the status. The preclear was terminated when the telnet session terminated.

 

If you are using the 1.3 or 1.4 version of preclear you will find a preclear_reports directory on your flash drive if it completed. In that directory will be the final reports.

 

Otherwise, you can get an idea of how far it might have gotten by looking in the /tmp directory.

If there is a file named /tmp/zerosdX, where sdX = the three letter drive designation, you can type

tail /tmp/zerosdX

to get an idea how far it got.  

To see when it quit you might be able to look at its time-stamp on the file with

ls -l /tmp/zero*

 

That file is only used when actually zeroing the disk.  If the preclear terminated before it got to the "write" phase, it will not be present.

You will need to start it as if it had never performed the process at all.

 

If the last line in /tmp/zero* does not have the full number of bytes on your disk, it would have terminated in the write phase.

 

You can re-start the process using the -W option if the "/tmp/zero*" file is present.  It will then do only the "write" phase and post-read-verify phases.

preclear_disk.sh -W /dev/sdX

If the "write" phase was completed, or you suspect it was, you can test if the pre-clear signature is present by using

preclear_disk.sh -t /dev/sdX

If it is you can use the new

"-V" option to perform only the post-read-verify phase.

 

preclear_disk.sh -V /dev/sdX

 

You can use the -A option on any of the above preclear_disk.sh commands to specify a 4k-aligned sector 64 start.

You should download and use the latest version of the preclear script.    I've been constantly improving the output report.

The last version as of this post is version 1.4

You can see the version by typing

preclear_disk.sh -v

Joe L.

 

Thanks very much Joe for the detailed info I had made two errors I had downloaded 1.2 by mistake now corrected to 1.4, also started fresh preclear with sleep mode disabled on the main system great stuff small learning curve ;D thanks

Lou

Link to comment

hello everyone,

 

JoeL, your new script is really sweet

running 1.3 I got this result... should I worry ?

 

================================================================== 1.3
=                unRAID server Pre-Clear disk /dev/sdj
=               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 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 10 of 10 - Verifying if the MBR is cleared.     DONE
= Step 10 of 10 - Verifying the clear has been successful.
= Disk Post-Clear-Read completed                                DONE
Disk Temperature: 31C, Elapsed Time:  27:35:50
========================================================================1.3
==
== Disk /dev/sdj has been successfully precleared
== with a starting sector of 64
============================================================================
** Changed attributes in files: /tmp/smart_start_sdj  /tmp/smart_finish_sdj
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =   119     120            6        ok          220222410
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
  Airflow_Temperature_Cel =    69      71           45        near_thresh 31
      Temperature_Celsius =    31      29            0        ok          31
   Hardware_ECC_Recovered =    52      50            0        ok          220222410
No SMART attributes are FAILING_NOW

0 sectors were pending re-allocation before the start of the preclear.
0 sectors are pending re-allocation at the end of the preclear,
    the number of sectors pending re-allocation did not change.
0 sectors had been re-allocated before the start of the preclear.
0 sectors are re-allocated at the end of the preclear,
    the number of sectors re-allocated did not change.

 

I don't know these attributes and can't seem to find conclusive information.

 

thanks for your help,

R

Link to comment

hello everyone,

 

JoeL, your new script is really sweet

running 1.3 I got this result... should I worry ?

 

================================================================== 1.3
=                unRAID server Pre-Clear disk /dev/sdj
=               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 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 10 of 10 - Verifying if the MBR is cleared.     DONE
= Step 10 of 10 - Verifying the clear has been successful.
= Disk Post-Clear-Read completed                                DONE
Disk Temperature: 31C, Elapsed Time:  27:35:50
========================================================================1.3
==
== Disk /dev/sdj has been successfully precleared
== with a starting sector of 64
============================================================================
** Changed attributes in files: /tmp/smart_start_sdj  /tmp/smart_finish_sdj
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Raw_Read_Error_Rate =   119     120            6        ok          220222410
         Spin_Retry_Count =   100     100           97        near_thresh 0
         End-to-End_Error =   100     100           99        near_thresh 0
  Airflow_Temperature_Cel =    69      71           45        near_thresh 31
      Temperature_Celsius =    31      29            0        ok          31
   Hardware_ECC_Recovered =    52      50            0        ok          220222410
No SMART attributes are FAILING_NOW

0 sectors were pending re-allocation before the start of the preclear.
0 sectors are pending re-allocation at the end of the preclear,
    the number of sectors pending re-allocation did not change.
0 sectors had been re-allocated before the start of the preclear.
0 sectors are re-allocated at the end of the preclear,
    the number of sectors re-allocated did not change.

 

I don't know these attributes and can't seem to find conclusive information.

 

thanks for your help,

R

Best info ins in the wiki: http://en.wikipedia.org/wiki/S.M.A.R.T.

 

Good luck finding conclusive information.  (Other than the disk has not failed SMART of the VALUE is above the FAILURE_THRESHOLD)

 

The status column in my final report will show the status from the SMART report if there was one, or "near_thresh" if the value is within 25 of its affiliated failure_threshold, and "ok" if the SMART report showed nothing else..  (I chose to put "near_thresh" as the status if a value was within 25 of its affiliated failure threshold.  The idea was to bring it to your attention.  I did not think I'd ever seen a failure threshold of 99 with a starting value of 100 as your manufacturer has done.

 

You have two values where the manufacturer decided to put the failure threshold only a few counts higher than their failure_threshold.  Their raw values have no counts, so odds are high the disk is perfectly healthy even though the failure threshold is near.

 

Other that that, enjoy your new disk.  (Oh yes, there is already a newer version 1.4 of the preclear script, but it just adds a few new features for special purposes and fixed the "Step 10 of 10" cosmetic bug where I displayed the "DONE" line one too high on the screen overwriting the "Step 9 of 10" line.  Your version would have worked perfectly)

 

Joe L.

Link to comment

I'm concerned about the section I've bolded. It would appear that something fixed the 11 bad sectors. Is that even possible?

 

========================================================================1.4

== invoked as: ./preclear_disk.sh -A /dev/sdc

==

== Disk /dev/sdc has been successfully precleared

== with a starting sector of 64

== Ran 1 cycle

==

== Using :Read block size = 8225280 Bytes

== Last Cycle's Pre Read Time  : 7:23:44 (75 MB/s)

== Last Cycle's Zeroing time   : 6:47:41 (81 MB/s)

== Last Cycle's Post Read Time : 15:00:12 (37 MB/s)

== Last Cycle's Total Time     : 29:12:44

==

== Total Elapsed Time 29:12:44

==

== Disk Start Temperature: 34C

==

== Current Disk Temperature: 29C,

==

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

** Changed attributes in files: /tmp/smart_start_sdc  /tmp/smart_finish_sdc

               ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE

     Temperature_Celsius =   123     118            0        ok          29

No SMART attributes are FAILING_NOW

 

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

2 sectors are pending re-allocation at the end of the preclear,

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

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.

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

Link to comment

Usually the fix is they are actually reallocated. It's a little odd that they were removed from the pending reallocation list but were not actually reallocated. Perhaps they were able to be properly read during the preclear and thus removed from the pending list.

 

I would run another preclear cycle on the drive to see how it behaves.

 

Maybe Joe L or someone else would know better.

Link to comment

Usually the fix is they are actually reallocated. It's a little odd that they were removed from the pending reallocation list but were not actually reallocated. Perhaps they were able to be properly read during the preclear and thus removed from the pending list.

 

I would run another preclear cycle on the drive to see how it behaves.

 

Maybe Joe L or someone else would know better.

 

Thanks.

Link to comment

I'm concerned about the section I've bolded. It would appear that something fixed the 11 bad sectors. Is that even possible?

 

========================================================================1.4

== invoked as: ./preclear_disk.sh -A /dev/sdc

==

== Disk /dev/sdc has been successfully precleared

== with a starting sector of 64

== Ran 1 cycle

==

== Using :Read block size = 8225280 Bytes

== Last Cycle's Pre Read Time  : 7:23:44 (75 MB/s)

== Last Cycle's Zeroing time   : 6:47:41 (81 MB/s)

== Last Cycle's Post Read Time : 15:00:12 (37 MB/s)

== Last Cycle's Total Time     : 29:12:44

==

== Total Elapsed Time 29:12:44

==

== Disk Start Temperature: 34C

==

== Current Disk Temperature: 29C,

==

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

** Changed attributes in files: /tmp/smart_start_sdc  /tmp/smart_finish_sdc

               ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE

     Temperature_Celsius =   123     118            0        ok          29

No SMART attributes are FAILING_NOW

 

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

2 sectors are pending re-allocation at the end of the preclear,

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

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.

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

Absolutely it is possible.

 

Before re-allocating a sector it is first attempted to be re-written in its original location.  If successful there is no need to re-allocate it.

 

It does possibly indicate the original "write" was not successful.  It is good the sectors did not need to be re-allocated.  It could be an indication of a noisy power supply or a vibration issue that would make it tough for the disk to be written.

 

The remaining two that are pending re-allocation are an issue though, since all detected in the pre-read should have been re-allocated in the write phase. Therefore I suspect the two remaining were detected in the post-read phase.

 

As mentioned, I see another pre-clear cycle is in your future, and if the disk still has more pending sectors, a possible RMA.

 

Joe L.

Link to comment

I'm having a cascade of problems today. Besides realizing I have a 2TB seagate drive that requires a critical update to CC35 (don't know why though) and a Gigabyte board that has added HPA sectors to one of my hard drives... I also have a funny WD 2TB EARS drive. The topic of this post will pertain to the EARS drive:

 

I originally installed the 2TB EARS drive with NO jumper. I precleared using an older version of preclear (<< 0.9.9) and didn't take the Advanced Format aspect of the EARS drive into consideration (sector 63, not 64). Everything went fine and I added the drive to my array (I believe Unraid 4.6 at the time). Fast forward to the other day, when a red dot and a message "disk invalid" appeared next to the drive in the unraid menu. I happened to be preclearing another 2 TB EARS drive (again, NO jumper, sector 63). This drive precleared OK and I swapped the disks in the array.

 

Attempting to discover whether the first 2 TB EARS disk was bad or not, I attempted to preclear (NO jumper, sector 63) and the preclear failed with the following error messages (sorry I didn't copy the whole log at the time, just the errors and they are not in order):

 

dd: reading `/dev/sdb': Input/output error

> 0+0 records in

> 0+0 records out

> 0000000

> 0 bytes (0 B) copied, 0.00222053 s, 0.0 kB/s

> dd: writing `/dev/sdb': Input/output error

 

Restarting udevd

 

BLKRRPART: Input/output error

 

Following this error, I attempted to run preclear again, but the disk no longer reported and all that was returned was two rows of asterisks with nothing between them.

 

Afterward I went searching for similar problems in the forums and I happened upon the whole Advanced Format discussions. I updated my preclear script, updated to Unraid 4.7, and attempted to preclear the dodgy 2TB EARS drive again. Under these conditions, with or without the -A option, I get the attached output saying my drive is not recognized (in both smartctl 5.38 and 5.39). If I run the old preclear script, I do not get this error.

 

Is this drive broken? Why does the old preclear script not return the same smartctl error? How can I identify what version the old preclear script is?

 

Thanks in advance!

preclear-output.txt

Link to comment

I'm having a cascade of problems today. Besides realizing I have a 2TB seagate drive that requires a critical update to CC35 (don't know why though) and a Gigabyte board that has added HPA sectors to one of my hard drives... I also have a funny WD 2TB EARS drive. The topic of this post will pertain to the EARS drive:

 

I originally installed the 2TB EARS drive with NO jumper. I precleared using an older version of preclear (<< 0.9.9) and didn't take the Advanced Format aspect of the EARS drive into consideration (sector 63, not 64). Everything went fine and I added the drive to my array (I believe Unraid 4.6 at the time). Fast forward to the other day, when a red dot and a message "disk invalid" appeared next to the drive in the unraid menu. I happened to be preclearing another 2 TB EARS drive (again, NO jumper, sector 63). This drive precleared OK and I swapped the disks in the array.

 

Attempting to discover whether the first 2 TB EARS disk was bad or not, I attempted to preclear (NO jumper, sector 63) and the preclear failed with the following error messages (sorry I didn't copy the whole log at the time, just the errors and they are not in order):

 

dd: reading `/dev/sdb': Input/output error

> 0+0 records in

> 0+0 records out

> 0000000

> 0 bytes (0 B) copied, 0.00222053 s, 0.0 kB/s

> dd: writing `/dev/sdb': Input/output error

 

Restarting udevd

 

BLKRRPART: Input/output error

 

Following this error, I attempted to run preclear again, but the disk no longer reported and all that was returned was two rows of asterisks with nothing between them.

 

Afterward I went searching for similar problems in the forums and I happened upon the whole Advanced Format discussions. I updated my preclear script, updated to Unraid 4.7, and attempted to preclear the dodgy 2TB EARS drive again. Under these conditions, with or without the -A option, I get the attached output saying my drive is not recognized (in both smartctl 5.38 and 5.39). If I run the old preclear script, I do not get this error.

 

Is this drive broken? Why does the old preclear script not return the same smartctl error? How can I identify what version the old preclear script is?

 

Thanks in advance!

 

preclear_disk.sh -v

will give you the version.   If it does not recognize that option it is a very early version indeed.

Basically your disk has stopped responding to any command.

 

Type

fdisk -l /dev/sdX

or

hdparm /dev/sdX

 

and see if it responds at all.  If it is like every other EARS drive, once it locks up it will take a power cycle to get it to respond again.

 

So... stop your array, power down, power back up, and then try to see if the disk will respond to any command.

 

Joe L.

 

 

Link to comment

Thanks for your quick response Joe L.!

 

preclear_disk.sh -v

will give you the version.  If it does not recognize that option it is a very early version indeed.

 

It appears the version of preclear was very old... before the -v command was implemented. Only the -n, -t, and -c commands are available in that version.

 

If it is like every other EARS drive, once it locks up it will take a power cycle to get it to respond again.

 

I should have mentioned that by rebooting I regained access to the EARS drive and that the following problems occur while the disk is responsive.

 

I have attached a log of performing fdisk -l, hdparm, preclear_disk.sh -t, then preclear_disk.sh -A. From this log you will see that using the -A command results in the above mentioned smartctl error. Calling the preclear script without -A works fine. Should I preclear without the -A and then use the -C 64 command to convert the disk?

 

*EDIT* By using the command "preaclear_disk.sh -D -A /dev/sdX" I was able to circumvent the smartctl error. Immediately I said "No" to a preclear and tried "preaclear_disk.sh -A /dev/sdX", which also miraculously worked, despite it previously not working (see the attached logs). Thanks for your help Joe L., if anything funny was going on I hope I supplied you with enough information for you to understand what it was.

2TB-EARS-Preclear-Trouble.txt

Link to comment

Calling the preclear script without -A works fine. Should I preclear without the -A and then use the -C 64 command to convert the disk?

Yes, that will certainly work.  it will give me some time to figure out what is going on.

 

Converting a precleared disk only takes seconds.

 

What version of unRAID are you running?

 

Joe L.

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.