02-01-2009 01:05 PM
I have been searching in vain (it seems) for a solution from my favorite HD manufacturer: Seagate.
My 1TB drive (as mentioned in the title) most certainly IS affected by the same problem or a variant of it.
When I power on sometimes, the POST screen shows no HDs connected on the controller.
Other times, when in XP working an a program, the systems will quickly reboot with no warning, no lag, no hangs, nothing. Just powers down and reboots and when it scans for drives, you guessed it: there are none to be found.
1) I have a support case open since 1/27 with no activity or notes.
2) I have downloaded the Brinks-3D6H-SD1B.ISO and burned to a CDr to try the firmware update, but it says found ST31000333AS, expected ST31000333AS. HUH?!?
I am told that CC1F is not affected, and that stupid serial number confirmation page with its rediculous inane verification (of old texts???) never accepts the codes I enter, even though they are separated by a space and case-duplicates of the originals.
Obviously, my drive is not supposed to reboot my system by itself and disappear from the BIOS detection.
I have been a supporter of Seagate since the early nineties, when my WD drives kept losing data and forming bad sectors. This is the first problem I have ever had with them. EVER.
I don't want to rake anyone over any coals, but there isn't much communication on the issues, and it seems as though they don't want to say anything for liability sake.
In the meantime, my whole collection of data is being backed up daily to avoid loss, but one of these times it will reboot in the middle of a backup and I will be finished.
Does anyone have anything to lend to this? Am I doing something wrong with the firmware? Do I need to be in AHCI mode instead of N-IDE?
02-01-2009 04:00 PM
Gcracker, I don't think your problem is the same that is causing bricked drives and related to the recent firmware releases from seagate for the 7200.11s. It *may* be a new firmware bug or something else, but the recently discovered firmware problem has one characteristic : bricked drives do not 'wake up' sometimes. Your error seems to me more likely that your system is in the limit of allowance when giving time to speed up drives at boot, and some times just it 'checks' for drives when the 7200.11 is not yet ready (up to speed), thus not finding it in Bios.
To prove that you need to delay bios check a bit.. you can look for some kind of 'hard disk delay' or 'staggered hd startup' option in BIOS, or just make the boot sequence slower by adding a floppy, or the memory check, or something similar.
Now regarding the reboots, they could be related or not but they seem more like some kind of power or voltage issue.
02-01-2009 04:10 PM
I agree that my problem isn't the same one affecting the drives with SD## revisions of firmware, but it is being affected by some problem.
The rebooting is taking place with no user-demand on the HD, and indexing is turned off. I realize that these days, Windows can decide to write something at anytime, but my system has been stable until now.
As for the spinup issue, my POST takes forever and a day anyway, and doesn't bother giving me a display until after all drives have been polled. I understand that on reboot, I may have an issue because the drive hasn't sent a ready signal or some other confusion, but on boot from power-off state, I still am having two to three failed detections a day.
My random reboot stats are in the range of once every other day. (twice today tho)
Finally, on my firmware issue: the firmware CD didn't read all the info from the drive until I was in AHCI mode, when it told be the update was for the SD## series and not to perform the flash.
Thanks for the reply, FTC. I hope this is a random unrepeatable problem, but it has odors of similarity to the other problems I've been reading about here.
02-04-2009 10:28 AM