I buy branded external HDDs when they go on sale and use cloud backup. A spinning disk is going to die some day. Cheap ones have lasted me years. Remember that for the most part, its reads vs. writes.
Apart from the fact that they may not work in the role for which they are specifically touted (resilvering a RAID). WD were the first to offer this kind of product that claimed to be optimized for particular roles and that could well come back to bite them.there's nothing actually wrong with the drives
Yes. If the drives are in the listening room it can be annoying, if you are weird about this like me, if they are elsewhere it's not an issue.You mean the actual hdd spinning noise ?
Look at BackBlaze HDD reports for their quarterly reliability statistics.
Those figures should be taken with a pinch of salt. They use cheap consumer drives well outside their intended parameters. It's like measuring how many bricks you can throw at a car before the windows break.
The problem comes when one drive fails, you replace it and try to rebuild the array. People have been reporting that the rebuild with the shingled drives at best takes orders of magnitude longer than usual, and at at worst fails entirely as the drive hits an error condition during rebuild.I'm aware of that. I have 2 mirrored Red drives in my Synology NAS. What you should care about is this: "SMR hard drives are best used in workloads where the majority of the drive's duty cycle consists of reads rather than writes. "
With my NAS I do exactly that - I write the music files once and listen to them many times.
The problem comes when one drive fails, you replace it and try to rebuild the array. People have been reporting that the rebuild with the shingled drives at best takes orders of magnitude longer than usual, and at at worst fails entirely as the drive hits an error condition during rebuild.
SMR drives perform _very_ badly if writes are not done properly. Maybe your OS knows what to do.I replaced a drive a year ago, it was a Seagate mirrored with WD Red. I put in another WD Red and rebuild it without any issues. IIRC it took 3-4 hours to rebuild a 2TB drive. I see no reason why it would have difficulties rebuilding it.
SMR drives perform _very_ badly if writes are not done properly. Maybe your OS knows what to do.
If you did it a year ago there's a good chance the new drive wasn't shingled. If you check Synology's compatibility list the shingled WD Red models are notable by their absence.I replaced a drive a year ago, it was a Seagate mirrored with WD Red. I put in another WD Red and rebuild it without any issues. IIRC it took 3-4 hours to rebuild a 2TB drive. I see no reason why it would have difficulties rebuilding it.
Which is sadly ironic given that WD Red was the first drive range marketed to the public-at-large as specifically for RAID use.If you check Synology's compatibility list the shingled WD Red models are notable by their absence
I don't see what RAID has to do with anything. It doesn't alter the overall access pattern seen by the drive.Which is sadly ironic given that WD Red was the first drive range marketed to the public-at-large as specifically for RAID use.
Try with WD Purple or some other NAS/surveillance one's. Now days price sweat spot is on 4TB side.
If you did it a year ago there's a good chance the new drive wasn't shingled. If you check Synology's compatibility list the shingled WD Red models are notable by their absence.
MTBF numbers are mostly meaningless. The relevant parameter for SSDs is write endurance, which I can't find anywhere on the Sabrent website. Not a good sign.After my 1 tb Samsung 850 Evo died on me I got a Sabrient 2tb because of its huge MTBF.
Don't think I see your point. Have you read the entire story over at The Register? The problem concerns the WD Red range, which is specifically sold as the drive of choice for RAID use. When used outside a RAID environment* the worst case is that writing will be a lot slower than reading. If that suits you, fine. However, if you use a new low capacity “Red” (I believe <8TB) as a theoretically identical replacement for a failed drive within a RAID (“resilvering”), the process of reconstructing the RAID may fail as the write performance of the new drive is far worse than that of its older RAID partners.I don't see what RAID has to do with anything. It doesn't alter the overall access pattern seen by the drive.