rapperwith1p
Gawd
- Joined
- Oct 23, 2005
- Messages
- 670
Unless your drive is failing, it's a firmware update. Nothing to replace.
But the problem on that end that still isn't resolved is the OS-related nonsense.
FWIW - someone on the forums contacted Seagate for this supposed firmware for Linux users.
They were told "we do not support Linux."
This is the absolute retarded nonsense from Seagate that needs to f-ing stop.
You now have a potential fix, but getting the updated firmware is put on hold due to incorrectly answering a "what OS are you using?" question.
Personally, if I owned one, I would just call, and tell them the situation, and the firmware update, and refuse to answer any OS-related question.
Frankly, why doesn't Seagate just put this firmware up as a download? I would suppose it's a beta firmware.
If that's the case, they need to educate their staff on the issue pronto, so those affected can get their hands on the beta firmware without being screwed with.
Look, Seagate announces there's a new firmware for Linux users, and to call to get it. You call, and are told Linux isn't supported, and basically are told to go screw yourself. I don't even own one of these drives yet, and that treatment pisses me off. So I can imagine the owners are feeling pretty hot...
A Seagate mod is suggesting someone didn't get the memo... I work for a company that operates world-wide, and we're all aware that a single e-mail is enough to clarify a situation. And my company (dare I say) isn't exactly necessarily the most efficient company communication-wise, either...
This all just smells of the issue I had with Seagate a few years ago, where I had a drive that failed SMART, I determined the drive was going bad, Seagate agreed the drive was going bad, but since the drive would still pass a surface scan, an RMA was refused. My RAID controller refused the drive due to the SMART failure, so I was forced to just put it in a spare machine and let it spin until it actually failed. (I should have just lied and said it stopped working already, but I couldn't get myself to re-call and just lie...)
Five-year warranties are nothing if they're going to have retards at the wheel...
Eh, before you say it, yeah, I agree, if I'm this upset, I should just go with another manufacturer. WD/Samsung/Hitachi will probably have a 1.5TB+ drive here soon enough... Or by the time I run out of storage space...
Rants aside, I'd like to know what makes this 1.5TB so special that this issue never cropped up in a previous drive? Although I hear the 1TB drives had issues, too, but I think that's just a reliability issue. Wonder also, as others have wondered, if this issue is why other manufs haven't issued a 1.5TB drive yet...?
Pretty bad that storage demands are so high that we desire these huge drives so bad. (I still like my four-750GB-drive 2TB raid-5 arrays, but the 1.5TB drives would be cheaper...)
Dude you saved me from giving my own rant on the issue. I'm totally ticked off about how Seagate is handling this fiasco. FWIW I've been running without freezes on Vista32 with the temporary fix someone else suggested by disabling write caching. Faggate needs to fully acknowledge the issue and take responsibility for this crap and make a sincere effort in resolving this issue.