Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

WD30EZRX

Featured Replies

About to put two of these in my Newegg cart.  WD30EZRX 

 

One will be parity and one will be data.  This will be the start of my array until I copy data over and add some of the drives I already have laying around.  Will run WD's utils on both, followed by several preclear passes, before copying data.

 

I've read a bit about these drives, and some posts here as well.  Just want to make one final post asking about any potential issues before I commit.

 

Thanks.

I have one as my parity drive now. It passed 2 pre clear cycles without issue and has been running great for a month. You could always get a bad one (as with any drive), but my experience has been good so far.

  • Author

I have one as my parity drive now. It passed 2 pre clear cycles without issue and has been running great for a month. You could always get a bad one (as with any drive), but my experience has been good so far.

 

 

Just ordered one, thanks.  This doesn't have that 4096 byte format issue thing I've seen mentioned does it?  Not need to jumper it?

I have 5 of these, no issues so far but only 3 are in an array at this time.

 

Don't forget to change/disable the idle3 timer using wdidle3. If you don't you can and will get excessive head parking under linux.

I have one as my parity drive now. It passed 2 pre clear cycles without issue and has been running great for a month. You could always get a bad one (as with any drive), but my experience has been good so far.

 

 

Just ordered one, thanks.  This doesn't have that 4096 byte format issue thing I've seen mentioned does it?  Not need to jumper it?

 

No, no need for a jumper and it's >2.2gb, so no special options needed when you preclear.

 

distracted: I didn't do this with mine. How can I check for the excessive head parking and what could it cause down the road? Thanks.

  • Author

http://support.wdc.com/product/download.asp?groupid=609&sid=113

 

????

 

Is there one for each specific drive or series of drives?  Do I have to do this to ALL the WD drives I buy?

 

Fine, but I guess there really aren't any drives that "just work."  Hrmph.  In the last 25 years, I have never had to do anything with a hard disk other than plug it in and go, unless it was a SCSI ID or termination change.

  • Author

I ended up using the -A option when I precleared based on other posts... Will this break something?  I plan on preclearing a second and possibly a third time just to beat the drive up before I put data on it... Should I continue with the -A option or not?

From what I've read the -A option is not needed on a drive >2.2gb. I ran 2 cycles on mine without the -A option and it is running just fine as my parity drive now.

  • Author

Should I run the next two preclears without it?  Have I done anything to mess up the drive (and if so, is it correctable)?

 

Also, I used a tool to change the spindown delay to 300 seconds. 

http://support.wdc.com/product/download.asp?groupid=609&sid=113

 

????

 

Is there one for each specific drive or series of drives?  Do I have to do this to ALL the WD drives I buy?

 

Fine, but I guess there really aren't any drives that "just work."  Hrmph.  In the last 25 years, I have never had to do anything with a hard disk other than plug it in and go, unless it was a SCSI ID or termination change.

 

Just the green drives, AFAIK. That same utility should work for all green drives.

  • 1 month later...

Anyone remember how long it took to preclear a WD30EZRX? I have 3 of these and planning on running 3 passes on them. So just wondering if the below results look normal.

 

================================================================== 1.13
=                unRAID server Pre-Clear disk /dev/sda
=               cycle 1 of 3, partition start on sector 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 - Verifying if the MBR is cleared.              DONE
= Post-Read in progress: 36% complete. 
(  1,097,252,352,000  of  3,000,592,982,016  bytes read ) 97.9 MB/s
Disk Temperature: 30C, Elapsed Time:  28:22:56

 

================================================================== 1.13
=                unRAID server Pre-Clear disk /dev/sdb
=               cycle 1 of 3, partition start on sector 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 - Verifying if the MBR is cleared.              DONE
= Post-Read in progress: 38% complete. 
(  1,153,184,256,000  of  3,000,592,982,016  bytes read ) 96.7 MB/s
Disk Temperature: 29C, Elapsed Time:  28:20:58

  • Author

Those times and speeds are consistent with my preclears on the same model drive.

Those times and speeds are consistent with my preclears on the same model drive.

 

So 48h or so for 1 pass?

 

Console shows:

 

================================================================== 1.13
=                unRAID server Pre-Clear disk /dev/sda
=               cycle 1 of 3, partition start on sector 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 - Verifying if the MBR is cleared.              DONE
= Post-Read in progress: 91% complete. 
(  2,737,373,184,000  of  3,000,592,982,016  bytes read ) 65.1 MB/s
Disk Temperature: 31C, Elapsed Time:  45:35:06

 

But unMenu shows:

 

Post-Read (1 of 3). 91% @ 28 MB/s (45:32:45)

 

Note the difference in speed.

For comparison sake only, here is the report of the last one of these I precleared...

 

== invoked as: /boot/preclear_disk.sh /dev/sdu

==  WDC WD30EZRX-00MMMB0    WD-WCAWZ1992269

== Disk /dev/sdu has been successfully precleared

== with a starting sector of 1

== Ran 1 cycle

==

== Using :Read block size = 8225280 Bytes

== Last Cycle's Pre Read Time  : 8:45:22 (95 MB/s)

== Last Cycle's Zeroing time  : 8:12:05 (101 MB/s)

== Last Cycle's Post Read Time : 18:46:29 (44 MB/s)

== Last Cycle's Total Time    : 35:44:56

==

== Total Elapsed Time 35:44:56

==

== Disk Start Temperature: 24C

==

== Current Disk Temperature: 30C,

For comparison sake only, here is the report of the last one of these I precleared...

 

== invoked as: /boot/preclear_disk.sh /dev/sdu

==  WDC WD30EZRX-00MMMB0    WD-WCAWZ1992269

== Disk /dev/sdu has been successfully precleared

== with a starting sector of 1

== Ran 1 cycle

==

== Using :Read block size = 8225280 Bytes

== Last Cycle's Pre Read Time  : 8:45:22 (95 MB/s)

== Last Cycle's Zeroing time  : 8:12:05 (101 MB/s)

== Last Cycle's Post Read Time : 18:46:29 (44 MB/s)

== Last Cycle's Total Time    : 35:44:56

==

== Total Elapsed Time 35:44:56

==

== Disk Start Temperature: 24C

==

== Current Disk Temperature: 30C,

 

What unRAID version and were you simultaneously preclearing multiple drives? I found a thread where other people are having a similar issue to me. The issue appears to be simultaneously preclearing multiple drives on RC8

 

http://lime-technology.com/forum/index.php?topic=23573.msg207804#msg207804

It was running at the same time as this one on RC8a

 

== invoked as: /boot/preclear_disk.sh /dev/sdt

==  WDC WD30EZRX-00MMMB0    WD-WCAWZ1974146

== Disk /dev/sdt has been successfully precleared

== with a starting sector of 1

== Ran 1 cycle

==

== Using :Read block size = 8225280 Bytes

== Last Cycle's Pre Read Time  : 8:52:08 (93 MB/s)

== Last Cycle's Zeroing time  : 8:37:29 (96 MB/s)

== Last Cycle's Post Read Time : 18:59:17 (43 MB/s)

== Last Cycle's Total Time    : 36:29:54

==

== Total Elapsed Time 36:29:54

==

== Disk Start Temperature: 25C

==

== Current Disk Temperature: 28C

  • Author

Hmmm... No.  Mine were right around 38 hours and I was getting 70-80MB/s

 

I just did a single preclear @ 45h. Looks like the post read is what's slow. So is this necessarily an issue?

 

========================================================================1.13
== invoked as: ./preclear_disk.sh /dev/sda
==  WDC WD30EZRX-00MMMB0    WD-WMAWZ0333927
== Disk /dev/sda has been successfully precleared
== with a starting sector of 1 
== Ran 1 cycle
==
== Using :Read block size = 8225280 Bytes
== Last Cycle's Pre Read Time  : 9:20:54 (89 MB/s)
== Last Cycle's Zeroing time   : 8:27:11 (98 MB/s)
== Last Cycle's Post Read Time : 27:30:18 (30 MB/s)
== Last Cycle's Total Time     : 45:19:25
==
== Total Elapsed Time 45:19:25
==
== Disk Start Temperature: 31C
==
== Current Disk Temperature: 30C, 
==
============================================================================
** Changed attributes in files: /tmp/smart_start_sda  /tmp/smart_finish_sda
                ATTRIBUTE   NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS      RAW_VALUE
      Temperature_Celsius =   122     121            0        ok          30
No SMART attributes are FAILING_NOW

0 sectors were pending re-allocation before the start of the preclear.
0 sectors were pending re-allocation after pre-read in cycle 1 of 1.
0 sectors were pending re-allocation after zero of disk in cycle 1 of 1.
0 sectors are pending re-allocation at the end of the preclear,
    the number of sectors pending re-allocation did not change.
0 sectors had been re-allocated before the start of the preclear.
0 sectors are re-allocated at the end of the preclear,
    the number of sectors re-allocated did not change. 
============================================================================

 

EDIT: Results from a 3 cycle run are faster..?

 

========================================================================1.13
== invoked as: /boot/preclear_disk.sh -c 3 /dev/sdd
==  WDC WD30EZRX-00MMMB0    WD-WCAWZ2350602
== Disk /dev/sdd has been successfully precleared
== with a starting sector of 1 
== Ran 3 cycles
==
== Using :Read block size = 8225280 Bytes
== Last Cycle's Pre Read Time  : 9:19:38 (89 MB/s)
== Last Cycle's Zeroing time   : 8:39:37 (96 MB/s)
== Last Cycle's Post Read Time : 28:37:00 (29 MB/s)
== Last Cycle's Total Time     : 37:17:39
==
== Total Elapsed Time 123:17:21

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.