Seagate Skyhawk drive for unRaid?


Recommended Posts

Any opinions on whether Seagates latest drives in 10TB form would be of any use for unRaid. The Ironwolf drives are specced for nas use but the Skyhawks for surveillance and are equally specced to power down when not in use and power up quickly which would seem just what unRaid needs. Problem is that they're both 7200rpm heat generators! Any thoughts anyone cos my array needs an upgrade from 8TBs soon.

 

Sent from my LxG-D855 using Tapatalk

 

 

 

 

 

 

Link to comment

I haven't used SkyHawks but I have some of WD's Purple surveillance drives and they are fine. I bought them because at the time I could get four of them significantly cheaper than four Reds. They have different firmware but I wouldn't be surprised if mechanically they had a lot in common.

Link to comment
I haven't used SkyHawks but I have some of WD's Purple surveillance drives and they are fine. I bought them because at the time I could get four of them significantly cheaper than four Reds. They have different firmware but I wouldn't be surprised if mechanically they had a lot in common.

I'm gonna take a punt on two skyhawks and keep fingers x'd

 

Sent from my LG-D855 using Tapatalk

 

 

 

Link to comment

Depends. Got a good deal on a pair of oem drives. Bit risky but ... Ironwolf at 7200rpm seem comparable yet skyhawk drives seem the better choice although maybe being powered down a lot of the time might not be ideal givem that theyre designed as surveillance drives. I'm going to free up a couple of 8TB drives by putting them in as 1 of a parity pair across a couple of microservers. So my parity will be a mix of 10TB / 8TB (data drives are 8TB) rather than throw two into one server which may not be a wise idea. If there's any failures i can return the 8TB freed up.

 

Sent from my LG-D855 using Tapatalk

 

 

 

 

 

 

 

 

Link to comment

Surveillance drives are optimised not to drop frames when recording a steady stream of video data. NAS drives are optimised not to be thrown out of a RAID array by retrying failed reads. Otherwise they're pretty similar. Both are designed to spin 24/7 but both can be spun down to save power. What neither likes is repeated spinning up and spinning down.

Link to comment
Surveillance drives are optimised not to drop frames when recording a steady stream of video data. NAS drives are optimised not to be thrown out of a RAID array by retrying failed reads. Otherwise they're pretty similar. Both are designed to spin 24/7 but both can be spun down to save power. What neither likes is repeated spinning up and spinning down.
So ... maybe leave parity drives spinning and not power down?

Sent from my LG-D855 using Tapatalk

Link to comment
1 hour ago, superloopy1 said:

But if they're optimised for constant spinning?
 

That's nonsence marketing jibber-jabber.  Almost all drives share the same mechanism.

 

An IronWolf has the same mechanicals as a SkyHawk, a WD Red has the same mechanicals as a Purple, etc, etc.  Heck, my WD White-labels, WD Reds and WD Purple (all 8TB drives) all even have the same firmware revision on them, just different features turned on/off depending on the drive.  Physically they're identical.

Link to comment
On 2018-04-03 at 12:24 PM, John_M said:

Surveillance drives are optimised not to drop frames when recording a steady stream of video data

Doesn't that also imply that non-surveillance drives will drop frames (ie: data) on a continual stream of writes?  If that's the case, then I'm switching over to be 100% surveillance drives if they're the only ones that won't lose data when I'm writing to them....

Link to comment
4 minutes ago, Squid said:

Doesn't that also imply that non-surveillance drives will drop frames (ie: data) on a continual stream of writes?  If that's the case, then I'm switching over to be 100% surveillance drives if they're the only ones that won't lose data when I'm writing to them....

 

Short delays while copying files just cause the copy process to slow down for a while. When you record live video streams there isn't much scope for pausing for long. Once the DRAM cache is full frames will get dropped.

Link to comment
17 minutes ago, nuhll said:

Its just like throwing money out of window.


I don't agree with you - it's more complicated than that. I have had quite a number of different blue desktop drives fail on me (Seagate and WD), because they didn't like 24/7/365 use.

 

What the Backblaze statistics shows is that you don't need to buy the really expensive enterprise disks for server use - at least as long as you don't use them as database disks where there will be really huge amounts of disk seeks.

 

The Backblaze statistics doesn't cover how disks handles the wear from database use. And it doesn't cover the differences because of firmware optimizations, such as max latency.

 

Cloud storage companies are using more complex redundancy methods which means individual data blocks are stored in multiple pools which makes it easy to rewrite data that gives read errors by making use of alternative storage clusters.

 

In the end, the Backblaze statistics gives some form of indication about expected failure rate for the specific models used in their disk pools. Nothing can be deduced about other drive models, or newer production batches or other model sizes.

 

It isn't obvious if anyone needs surveillance disks in their unRAID server, but that doesn't mean that all disks are equally suitable for the task.

Link to comment
6 hours ago, nuhll said:

If backblaze is not database use, then i dont know.

 

Thats probably the worst case for hdds.

 

You believe this marketing sh1t and or working for them, idc. 

 

Backblaze sells backup storage. It's a huge difference between backup storage and database use.

 

Backup servers focus on storage volume and bandwidth - database servers focuses on transactions/second. So very big difference in the type of workload for the disks.

Link to comment
16 minutes ago, John_M said:

One thing I noticed about the Seagate IronWolf and SkyHawk  is that (for the higher capacity drives, at least) the uncorrectable read error rate is an order of magnitude better than the WD Red (10e-15 vs. 10e-14).

 

It's necessary for large disks to improve the probability of uncorrectable read errors because of the huge amount of data they handle. So they have had to improve the detection of vibrations so they can pause writing new data if vibrations might knock the write head off alignment.

 

When the drive prepares to write it uses the read head to locate the correct track and pick up which sector of the track that is currently passing under the read head. Then the drive performs a blind realign to move the write head on top of the track (how much realign that is needed depends on how far off-center the track is) and then the drive blindly counts time until the expected sector rotates in under the write head so the write operation can be started. Any bump after the read-align would send the write head off-track, and the required tolerances are so small that vibrations from other disks can be enough. And with higher track density, it's also more important to handle that the tracks aren't perfectly round circles - both because of the servo-track mastering and because of mechanical tolerances.

 

After the blind write, the drive does not return back to the just written sectors to verify that the writes did go well - at best it does a read-align to check how well it follows the track. So it isn't until the drive gets a read request for the sectors or the user issues a long SMART test that it will know if the new data is readable. So lots of care is needed to minimize the danger that the writes ended up misaligned. This is a reason why Seagate writes "Drive balance with Rotational Vibration (RV) sensors manage multi-bay vibration for long-term consistent performance and reliability".

Link to comment

It's astonishing they work at all, but I thought that 30 years ago and they still keep squeezing more and more into the same space. While capacities have increased almost by a factor of a million (my first hard disk had a capacity of 20 MB) the chance of reading the whole disk without getting an unrecoverable read error has not kept pace. If I remember correctly the figure was typically 1 in 10^12 back then.

Link to comment
2 hours ago, John_M said:

It's astonishing they work at all, but I thought that 30 years ago and they still keep squeezing more and more into the same space. While capacities have increased almost by a factor of a million (my first hard disk had a capacity of 20 MB) the chance of reading the whole disk without getting an unrecoverable read error has not kept pace. If I remember correctly the figure was typically 1 in 10^12 back then.


WD and Seagate have R&D budgets like small countries - it was many years since normal, simple, physics could improve a HDD. And they get into big troubles if one of them gets too much ahead of the other with the research into new technology. A huge number of HDD manufacturers have already had to close shop because they couldn't keep up. Bye Maxtor, Connor, Micropolis, MiniScribe, ...

 

Right now, we are quite vulnerable. The big R&D budgets - and the progress - depends on competition.

Link to comment
  • 2 years later...
  • 1 month later...

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.