The Argumentalizer
2010-06-13 20:36:32
I don't know if anyone has heard of this, but there is firmware debacle concerning unknown numbers of Seagate Internal Drives. What happens is defective firmware, during a power down phase, locks the drive complete, or BRICKS it. Failure rate is huge 30 to 40 % of recent 500 and 1T drives.
I lost a 1T Seagate with 400 gigs of music and 500 gigs of movies and some backed up Docs. One day, the BIOS wouldn't recognize it. Not only that, but having it connected wreaked havoc on POST and BOOT times.
I had it all backed up to another 1T drive, so no problem, right. Well, we had a power out and wouldn't you know, NOT DETECTED.
Its a massive mess, with a Serial Number checker that denies some drives are effected and disinformation regarding Data Recovery reimbursement.
The worst part is that their firmware fix cannot be used on a bricked drive. They require some electronic hacking to fix.
And if you can get the drive unlocked, you still have to apply the right update and here, Seagate is screwing that up.
If you have any problems losing a Seagate drive, not being seen in the BIOS, consider this cause before replacing MBs, and PSUs and such.
While it could be a cable, bricking is more likely.
Here is a link to a geek hack that works:
http://www.msfn.org/board/topic/128807- ... 0011-hdds/
I lost a 1T Seagate with 400 gigs of music and 500 gigs of movies and some backed up Docs. One day, the BIOS wouldn't recognize it. Not only that, but having it connected wreaked havoc on POST and BOOT times.
I had it all backed up to another 1T drive, so no problem, right. Well, we had a power out and wouldn't you know, NOT DETECTED.
Its a massive mess, with a Serial Number checker that denies some drives are effected and disinformation regarding Data Recovery reimbursement.
The worst part is that their firmware fix cannot be used on a bricked drive. They require some electronic hacking to fix.
And if you can get the drive unlocked, you still have to apply the right update and here, Seagate is screwing that up.
If you have any problems losing a Seagate drive, not being seen in the BIOS, consider this cause before replacing MBs, and PSUs and such.
While it could be a cable, bricking is more likely.
Here is a link to a geek hack that works:
http://www.msfn.org/board/topic/128807- ... 0011-hdds/