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.

Warning purchasing USB hard drives

Featured Replies

There was an interesting article by Mr. Antman (England) checking a Seagate Archive drive in a Drobo which failed d/t the SMS type file structure being used.  In summary the Write Head is larger than the Read Head, thus multiple writes to the HD means the data must be read (d/t size) then re-written.  Not sure how that might affect Parity ????

 

I have not seen that article, but it is not so much that the head is larger, the required track on media is larger. The track needed to write is wider than needed to read, so smr (shingled) overlap the writes, removing some the "extra" area written, since it is not needed to read. This relationship between write and read requirements is unlikely to change in future generations.

 

This article covers in depth many of the characteristics of the SMR drives.

https://www.usenix.org/system/files/conference/fast15/fast15-paper-aghayev.pdf

 

In summary, sustained random writes will not perform well. Random writes up within the capacity of the persistent cache, followed by lengthy (hours) idle time (no reads or writes) will achieve good performance.

 

  • Replies 55
  • Views 45.4k
  • Created
  • Last Reply

Top Posters In This Topic

Posted Images

Remember these are called "shingled" drives => the name is derived from the fact that the writes overlap each other, as c3 noted above -- think of the shingles on a roof (this is why they named the technique "shingled").    The drives perform very well for reads (no different than standard PMR drives); but to write anything on a specific track requires re-writing the entire track as well as every track after it up until the next "buffer" track (where there's no shingling).    This could result in TERRIBLE write performance, except there is an area reserved for "buffering" all of these random writes, known as the "persistent cache", which buffers writes to a non-shingled area, and then moves them to the shingled sections later (during idle time).  Seagate has done a very good job of mitigating these issues, as I've outlined in this thread: http://lime-technology.com/forum/index.php?topic=39526.0

 

Hi garycase/C3,

 

Many thanks for the responses and the detailed information.  Gary I read through your analysis per the post and tried to read danioj analysis as well (a bit over my head), but bottom line, I'll go ahead an preclear one of the disks at a time and see how they stack up. 

 

I really appreciate your responses to my questions.  Is there any advantage to taking the drive out of the case vs using USB3 to preclear?

 

Regards and Kudos!

 

Dave

I haven't done any USB-based pre-clearing; but my understanding is the newest version supports USB v3, so as long as your computer has USB3 ports, pre-clearing via USB should be just about as fast as a direct SATA connection -- and has the advantage that you'll know the drive is good before opening the case to remove it (thus voiding the warranty).

 

Hi Gary,

 

It's currently in the Pre-read phase at ~ 2 hours @ an average of 198 mb/sec so I guess it  works! ;D

 

Dave

 

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...

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.