- Jul 27, 2020
- 24,056
- 16,810
- 146
Every Seagate drive I bought in the past failed on me. Never again. I lost faith in the brand completely.which is why i never buy seagate)
Same here. I used some spinners and their SSHD options and they all died very quickly when OEM drives lasted years. Some give them praises but when you have multiple failures across different types it's just bad to keep using them.Every Seagate drive I bought in the past failed on me. Never again. I lost faith in the brand completely.
I remember very well buying a 4TB HDD back when 4TB HDDs were non-existent. Basically, it was a Seagate dual 2TB HDD in RAID 0. After spending hours copying all my data, the drive dies literally the next day! That's just one bad storySame here. I used some spinners and their SSHD options and they all died very quickly when OEM drives lasted years. Some give them praises but when you have multiple failures across different types it's just bad to keep using them.
On the flip side I've bene running WD Red's ~5 years w/o any issues 24/7. If there's an issue it's self induced at this point.
They're junk unless you go enterprise some say. Others have them last a decade. Trust that it's not going to die and make you waste time is the bigger issue.
The SAS models must have a special sauce altogether (pardon the punI hear the EXOS SAS versions are OK too.
I bet the 2nd one would fail before you replaced the 1st failure though.but not at the same time.
That's the thing though. Witnessed several SATA failures at my workplace. No SAS failure that I know of in my 12+ years on the job (I'm not the techie though, but I do come to know of failures one way or the other).SAS vs SATA though shouldn't make a difference
18.18 formatted capacity if the online calculator is right. Sure you still want them?I've got an eye on potentially 20TB WD Red's for $400/ea though. Still hitting that $20/TB mark.
I know there's overhead and I calculate prices based on sticker not formatted results. Keeps things consistent.18.18 formatted capacity if the online calculator is right. Sure you still want them?
SAS vs SATA though shouldn't make a difference if the guts are the same. It's just their loss on the consumer side.
I can't tell you how many Seagate drives I RMA'd. I was such a fanboy. People couldn't convince me that it wasn't normal. I've had failures of all brands. But it was happening so fast. I stopped caring how I shipped the drives back to them. I think I sent a pair back in a manila envelope only wrapped in newspaper. I was determined to spend as little as possible sending them back. I saved all sorts of HDD packaging for shipment it was so often. I still have at least 8-10 HDD shipping boxes. Guess what? I never us them any longer. Why is that? About ten years ago I made the switch to HGST. I built a new machine last year and got three new HGST 2TB spinners for my thrash (download) drives. The previous ones lasted 10 years. One failed so I just got three new ones. I figure if they can last 10 years running 24/7 then it's stupid to get anything else. They were old stock, as they don't make HGST 2TB drives any longer. Who cares. I like reliability. I've also got 4 HGST 8-10TB He enterprise drives. I still don't trust WDC to keep the same quality standards as HGST. I do have a lone 74TB 2nd gen WD Raptor drive from 2006 that is still going strong. I really don't use it any longer due to the small size. But the quality is definitely there on that model.Every Seagate drive I bought in the past failed on me. Never again. I lost faith in the brand completely.
Well, both are true if you use Raid 10. You can have 3 drives fail and still have copy of your data if the R0's fail you still have a mirror copy on the R1 set. Obviously replacing them sooner than later would be a priority or having a hot standby in the array to take over immediately. Hedging your bets is better than a single disk any day. While not proper "backup" it's still a copy that can be accessed if removed from the PC.Note: RAID is NOT backup. It's for uptime.
It's my understanding that if data gets corrupted, then that corruption gets copied to the mirrored drive.Well, both are true if you use Raid 10. You can have 3 drives fail and still have copy of your data if the R0's fail you still have a mirror copy on the R1 set. Obviously replacing them sooner than later would be a priority or having a hot standby in the array to take over immediately. Hedging your bets is better than a single disk any day. While not proper "backup" it's still a copy that can be accessed if removed from the PC.
It's my understanding that if data gets corrupted, then that corruption gets copied to the mirrored drive.
Another option is just upload vital items using Google Drive and that satisfies 2 of your methods offsite / cold.Besides file corruption, if a user deletes a file, that deletion is copied across the array.
Another option is just upload vital items using Google Drive and that satisfies 2 of your methods offsite / cold.
When it comes down to the things we all really need to save vs hoard it's not that big of a capacity requirement. If you strip out all of the media usually you're not left with a whole lot that needs a backup.
Note: RAID is NOT backup. It's for uptime.
It's my understanding that if data gets corrupted, then that corruption gets copied to the mirrored drive.
You are lucky than most to have critical stuff at that quite manageable capacity.Pictures, home videos, media files, expensive programs, game install files, etc. are sitting at 1.41 TB currently though, and I consider those pretty critical files for quality of life.
WINRARing stuff with "store" zero compression is my preferred way of knowing if data got corrupted somehow when transferring files. Of course, if it got corrupted WHILE making that archive, I'm screwed. Guess ECC would be useful to have to prevent that. By the way, I create SHA files on a daily basis to transfer financial messages. In over 10 years, I encountered my first SHA error only a few days ago where the remote server complained that the file I transferred with the accompanying SHA file didn't match the hash. The PC was a Dell 3rd gen i5 with a Samsung 860 EVO drive. I'm guessing it was the SSD that dropped the ball.But honestly if data is copied from a personal PC without ECC onto the NAS, its pointless to have ECC in the server almost, as the DATA could of started corrupted to begin with, and the ECC on the server wont save you from that.
WINRARing stuff with "store" zero compression is my preferred way of knowing if data got corrupted somehow when transferring files. Of course, if it got corrupted WHILE making that archive, I'm screwed. Guess ECC would be useful to have to prevent that. By the way, I create SHA files on a daily basis to transfer financial messages. In over 10 years, I encountered my first SHA error only a few days ago where the remote server complained that the file I transferred with the accompanying SHA file didn't match the hash. The PC was a Dell 3rd gen i5 with a Samsung 860 EVO drive. I'm guessing it was the SSD that dropped the ball.