A Western Digital spokesperson said, "We do not comment on pending litigation."
Western Digital knows there is an unreasonably high failure rate for these drives, and they even offered a firmware update that was supposed to fix the problem. But drives continue to fail. And Western Digital continues to sell them.
Ideally any professional photographer should be dumping their photos as they take them to two separate external drives from two separate manufacturers.Doing a wedding shoot and having one of these die on you would give "fucked" a whole new meaning.
As the linked article by Jeremy Reimer points out the "proper" definition was very much up for debate then. Since that time the matter has been settled with a definition which happened to favour storage manufacturers' view, but that doesn't erase the history of controversy.Not simping for WD here, and it's tangental to the SSD problem but since it's referenced at the end of the article I'll consider it fair game - the whole drive size terminology fiasco is stupid. ALL HDD manufacturers I've ever dealt with use the same terms - megabyte, gigabyte, and terabyte - and use them properly. Just because most normal humans don't understand what a TB is vs. a TiB doesn't mean WD (or Seagate, or any other manufacturer over the years) was misleading people.
/rant
What a ridiculous idea! Who would ever want a redundant array of independent disks?So there would be a market for portable dual drives - two identical drives in a case which perform all operations in sync. So you need two f-ed up drives for your wedding shoot to disappear.
This comment finally made me see the light. Honestly, I've known about the difference for so long, I stopped caring about it. But if you'd asked me yesterday, I would have said that the HD makers were gaming the system. Not now.Not simping for WD here, and it's tangental to the SSD problem but since it's referenced at the end of the article I'll consider it fair game - the whole drive size terminology fiasco is stupid. ALL HDD manufacturers I've ever dealt with use the same terms - megabyte, gigabyte, and terabyte - and use them properly. Just because most normal humans don't understand what a TB is vs. a TiB doesn't mean WD (or Seagate, or any other manufacturer over the years) was misleading people.
/rant
It's called a mirrored RAID1 array — and been around for a few decades.So there would be a market for portable dual drives - two identical drives in a case which perform all operations in sync. So you need two f-ed up drives for your wedding shoot to disappear.
The IEC standard was tabled in the beginning of 1999. The linked article is in 2006. Granted, things like class action lawsuits take their time winding through the legal system, but by the time that article was written, there wasn't a whole lot of controversy.As the linked article by Jeremy Reimer points out the "proper" definition was very much up for debate then. Since that time the matter has been settled with a definition which happened to favour storage manufacturers' view, but that doesn't erase the history of controversy.
I know, right? No one else believes me when I tell them about the secret RAM conspiracy.This comment finally made me see the light. Honestly, I've known about the difference for so long, I stopped caring about it. But if you'd asked me yesterday, I would have said that the HD makers were gaming the system. Not now.
Now I understand who really deserves the blame for this confusion about disk capacity: RAM vendors. Those bastards have used incorrect units for decades, giving their customers more bytes than they expected, and all for free.
So there would be a market for portable dual drives - two identical drives in a case which perform all operations in sync. So you need two f-ed up drives for your wedding shoot to disappear.
I guess those memories weren't stored on WD drives, then ...Well, doesn't that just bring back memories (of reporting on Western Digital stories)...
At some point, and after a few years of courtroom wrangling, that’ll undoubtedly be $100,000,000.00 for the law firm that filed the suit, and a generous $7.46 for each customer who bought one of those defective PoSs.Doing a wedding shoot and having one of these die on you would give "fucked" a whole new meaning.
They deserve whats coming to them via the legal system.
I mean... have we met? Doesn't much matter whose drives they were stored on, because the array is redundant, fully backed up, and 24/7 automatically monitored.I guess those memories weren't stored on WD drives, then ...
I'm going to go out on a limb and guess you've never professionally sold computing devices to end users.Not simping for WD here, and it's tangental to the SSD problem but since it's referenced at the end of the article I'll consider it fair game - the whole drive size terminology fiasco is stupid. ALL HDD manufacturers I've ever dealt with use the same terms - megabyte, gigabyte, and terabyte - and use them properly. Just because most normal humans don't understand what a TB is vs. a TiB doesn't mean WD (or Seagate, or any other manufacturer over the years) was misleading people.
/rant
Pretty sure the reason we have two separate sets of units in the first place is because the storage vendors dug their heels in on the short changing practice and we still needed binary aligned units elsewhere. Though, admittedly, I could be misinformed.Not simping for WD here, and it's tangental to the SSD problem but since it's referenced at the end of the article I'll consider it fair game - the whole drive size terminology fiasco is stupid. ALL HDD manufacturers I've ever dealt with use the same terms - megabyte, gigabyte, and terabyte - and use them properly. Just because most normal humans don't understand what a TB is vs. a TiB doesn't mean WD (or Seagate, or any other manufacturer over the years) was misleading people.
/rant
The fix is obviously to add a mandatory arbitration clause to their end-user license agreement.Good. This is exactly what the class-action system is for.
Unfortunately, that's the take away Western Digital is going to get from this.The fix is obviously to add a mandatory arbitration clause to their end-user license agreement.
/s
Besides the point with regards to the WD shenanigans: If you're doing a wedding shoot and you are not using a camera capable of writing to two SD/CF/XQD cards simultaneously, you deserve whatever wrath you get from your customers. Damn near every modern professional mirrorless system offers this capability and if you're shooting events, you cant afford not to.Doing a wedding shoot and having one of these die on you would give "fucked" a whole new meaning.
You are not misinformed.Pretty sure the reason we have two separate sets of units in the first place is because the storage vendors dug their heels in on the short changing practice and we still needed binary aligned units elsewhere. Though, admittedly, I could be misinformed.
Depends what you call selling, and who you call and end user. I do solution design for IT departments. My customers (nearly all, at least) know the actual capacity they are getting, so this isn't normally a conversation I need to have. That said, I built a spreadsheet that I've used for years that allows me to take exactly the hard drive capacity and RPM they are buying, the RAID level they are using, and give them a realistic expectation of actual usable capacity and IOPS, inclusive of the TB to TiB conversion.I'm going to go out on a limb and guess you've never professionally sold computing devices to end users.
Because let me tell you, end users get extremely confused about that, and extremely angry about it when their invoice says they got a "2TB" drive, but their operating system tells them it's only a "1.8TB" drive. I have spent probably a literal 24/7 week of my lifespan explaining those issues to very, very angry people certain that not only were they getting screwed, but that I was the one screwing them.
And if you think "a literal 24/7 week" sounds like it's dramatically overstated, well, I've been having to have those explanation/arguments with people since it was "they bought a 120GB drive, but their OS says it's only 111GB."
In totally unrelated news, Newegg has the SanDisk 2TB Extreme Portable and SanDisk 4TB Extreme Portable SSDs on sale for LESS THAN HALF PRICE!
https://www.newegg.com/sandisk-extr...s-_-N82E16820173504&ignorebbr=1&cvtc=19237559
https://www.newegg.com/sandisk-extr...s-_-N82E16820173505&ignorebbr=1&cvtc=19237559
Would be nice if my data meant nothing to me.
Purely Microsoft's fault for misusing kB shorthand when they meant KiB. Here is a good article:I'm going to go out on a limb and guess you've never professionally sold computing devices to end users.
Because let me tell you, end users get extremely confused about that, and extremely angry about it when their invoice says they got a "2TB" drive, but their operating system tells them it's only a "1.8TB" drive. I have spent probably a literal 24/7 week of my lifespan explaining those issues to very, very angry people certain that not only were they getting screwed, but that I was the one screwing them.
And if you think "a literal 24/7 week" sounds like it's dramatically overstated, well, I've been having to have those explanation/arguments with people since it was "they bought a 120GB drive, but their OS says it's only 111GB."
Units matter. Ask NASA!Purely Microsoft's fault for misusing kB shorthand when they meant KiB. Here is a good article:
https://en.wikipedia.org/wiki/Binary_prefix
It's situations like this which make some engineers so anal.
If it's a Mac, tell them it's the "Apple tax" (ducks and hides).I'm going to go out on a limb and guess you've never professionally sold computing devices to end users.
Because let me tell you, end users get extremely confused about that, and extremely angry about it when their invoice says they got a "2TB" drive, but their operating system tells them it's only a "1.8TB" drive. I have spent probably a literal 24/7 week of my lifespan explaining those issues to very, very angry people certain that not only were they getting screwed, but that I was the one screwing them.
And if you think "a literal 24/7 week" sounds like it's dramatically overstated, well, I've been having to have those explanation/arguments with people since it was "they bought a 120GB drive, but their OS says it's only 111GB."
Are you seriously floating the idea that "solution design for IT departments" is the same thing as "selling computing devices to end users?"Depends what you call selling, and who you call and end user. I do solution design for IT departments.
If it's a Mac, they'll get (last time I checked) an answer in GB/TB in Finder, but an answer in GiB/TiB in most (but not all!) Terminal applications.If it's a Mac, tell them it's the "Apple tax" (ducks and hides).
Now seriously, just checked on my Mac. Selected a hard drive in the Finder, Cmd-I = Info, it says 2TB, and then it says an exact number of bytes used, say 123,456,789,012 bytes and in brackets (123.456 GB).
No not at all ... my point was that end user compute is not what I do. Mostly. Sometimes it comes up. But the math is still important when I do some low-level design.Are you seriously floating the idea that "solution design for IT departments" is the same thing as "selling computing devices to end users?"
Yes, pretty much everybody in any given IT department is aware that they shouldn't expect to see 1TB capacity out of a "1TB" drive... although quite a lot of them probably don't know why (I find that many assume it's all "system overhead" that simply isn't reported as part of the capacity), they're at least aware that they shouldn't expect the numbers to match up.
End users, on the other hand...