07-14-2011 02:59 PM
Those of you that have trouble after a new MB is fiited I assume have done fresh installs of Windows? and even if you have a full format might be the best thing sl that old drivers aren't still detected, because as I'm sure you know unless you do a full prefferably destructive format you will simply be moving old data to another area rather than destroying it.
For those returning drives I recommend you use Discwizard first to do an FBI grade format before you return it, as some drives are re-issued as replacement refurbs and all your details will still be recoverable unless the company is prepared to leave returned drives formatting for days on end, which I assume they don't, so beware if the drive still functions, fully clean it before you send it in, or you might just find someone else who is a bit knowledgeable now has your bank account numbers, and believe me it can be done.
07-14-2011 09:49 PM
Cantbecanit wrote:
For those returning drives I recommend you use Discwizard first to do an FBI grade format before you return it, as some drives are re-issued as replacement refurbs and all your details will still be recoverable unless the company is prepared to leave returned drives formatting for days on end, which I assume they don't, so beware if the drive still functions, fully clean it before you send it in, or you might just find someone else who is a bit knowledgeable now has your bank account numbers, and believe me it can be done.
I don't think that there are ATA commands that let the computer get at the error sectors that have been replaced by spares. So I don't imagine that any program, including Discwizard, can wipe those sectors.
A determined foe might well be able to get those sectors. This would involve undocumented access: through the disk firmware console, through undocumented ATA commands, or though mounting a different controller on the platters.
Summary: for the truly concerned, RMAing is not a choice.
Some drives are encrypting. If you use them, and don't disclose the key, then RMAing ought to be OK. Assuming you think that there is no "key recovery" backdoor implemented by Seagate.
In the good old days (before SCSI and IDE) more direct access to the raw data was provided. A "low level format" would probably do the job. But even then, some claimed that there would be residual signal left untouched unless you wrote multiple patterns multiple times.
Things are even worse with SSDs: wear-leveling can hide your old sectors in more complicated ways.
07-24-2011 08:03 AM
When I returned my sick disk I wiped it so clean the NSA would be annoyed.
Even wiped it stll present SMART errors
I now have a 7200.12 disk and its dramaitic the difference. This one runs rings around the old disk which suggests the old disk had serious problems indeed.
10-27-2011 11:32 AM
Hi. I'm in trouble with an st3500320as drive.
The drive have the same problem discussed in this thread: bios won't recognise disk and data are not readable.
The firmware on this unit is SD1A so it shouldn't be affected by this firmware bug.
Anybody had same trouble with this unit with that firmware ?
Thanks in advance.
10-17-2012 05:24 AM
Just had three (yes 3 - there was a good deal on) of these ST3500320AS drives go bad on me - all upgraded in the past to SDA1 firmware, one by i365/Seagate in the Netherlands, and the other two at home by myself.
Two of the drives now report as SMART 'BAD' during POST and the other Vista detects but was it needs to be marked 'Active' which from what I understand means the MBR is corrupt (?)
Had a data recovery specialist look at them, all he can find is a dual partition on one of the drives (and a few bad sectors) but NO files!
I'm going to be contacting Seagate to explore my options on data recovery and replacement drives under warranty...
So you're not alone in having issues :-(
05-17-2013 12:15 AM
Hello, I had a ST3500320AS 500GB barracuda with SD15 firmware which suddenly stopped working. I managed to solve the problem by using a Nokia cable and following some instructions I found in a web site. The disk worked fine again.
Then, unfortunately, I decided to update the firmware, as Seagate recommends. I downloaded the SD1A version from their website and installed it. Everything was ok until the syste rebooted. Since then, there has been no way to read the disk.
Both BIOS and Windows detect the correct model and capacity, but windows says that it is a non-initialized disk, and suggests initializing it. I've trid with a couple of data recovery programs, but none of them could read a sector.
I've read through this thread, and it seems to be a firmware version issue. I guess that there is no way to get back to SD15 version but, Is there a solution to this issue? I am reluctant to send the disk to a date recovery company as they could gain access to my personal data.
Thanks in advance.
©2012 Seagate Technology LLC