[bloodraveb27]

i got my ca-42 cable today its made in china and there is 3 cable at there(blue-orange-red) i tried all probability for gnd-tx-rx for 2.3. and 4 socked on hdd but never got a reply from terminal when i typied ctrl+Z...
I am sure about paper what i put in hdd for stopping motor when i tried without paper i am hearing some noises from hdd like cızzz cızzz and this is like a little bit vibration this is happening without paper anyways about ca-42 driver i already have cd fro ca-42 and i installed what driver include at there but i never got reply from terminal and when i put cable or take out i dont have any message from windows, isnt it a little bit weird? i thouht i would have "safe remove device" anyways and i am alittle bit nervous about my cable as well, Can it be not working?
this is what i am getting when i put the cable to usb,is that mean : driver installed correctly?

edit
this is what i am getting from terminal when i use -orange-blue-red cable as socket 2.3.4.

This post has been edited by bloodraveb27: 03 April 2009 - 04:03 PM

[australis]

I had the same cable with the same colors and orange is for ground you can be sure of that. But I forgot what was blue or red for. You have 2 possibilities in this case Just give it a try. Oh by the way I used a driver named "ark3116_Drive.rar" that I googled. Use this one in case the driver that comes with it does not work.

This post has been edited by australis: 04 April 2009 - 12:11 AM

[bloodraveb27]

looking my case is a driver problem i looked for google and ark3116_Drive.rar(http://www.citronid....k3116_Drive.rar) i dont know i installed right but i got same name(http://img231.images...1/3605/ca42.png) under device manager is it right file for driver ?which i downloaded, if not please upload this file on something other host firm(rapidshare) and give us a little more explain how to install(i unrared and show target file as \ark3116_Drive\data
edit
is there any special setting for terminal? ASCII or something different? i am workin on it nearly 13 hours and this is drive me crazy i would nearly throw hdd to wall...

This post has been edited by bloodraveb27: 04 April 2009 - 03:47 AM

[australis]

well the driver I found was on rapidshare. I'm not at home right now but I'll upload it asap. but I guess you have the right driver now. I used hyperterminal with the default settings. Just select the right com port that is assigned to your usb cable.

[stony1999]

Can I ask a question to those guys who used USB-TTL converter, do you have to connect the board to a battery or PC power? as I can read from the product description, it can get power from the USB port.

Thanks.

[bloodraveb27]

stony1999, on Apr 5 2009, 06:34 AM, said:

Can I ask a question to those guys who used USB-TTL converter, do you have to connect the board to a battery or PC power? as I can read from the product description, it can get power from the USB port.

Thanks.

if you're using USB A / USB B writer cable(this will be connect with usb and converter)you dont need any battery and ofc you will need your own pc sata power cable afaik...
otherwise
look 101. post http://www.msfn.org/board/index.php?showto...8807&st=100

This post has been edited by bloodraveb27: 05 April 2009 - 02:33 AM

[bloodraveb27]

mkinderwater, on Mar 27 2009, 05:37 AM, said:

I was having a hell of a time getting any response from the drive in terminal using an original Nokia CA-42 cable; but I thought I would share some of my research.

If you bought an original Nokia CA-42 (and not a cheaper eBay type) adapter a few things are needed to make things work.

1. Download drivers from: http://europe.nokia.com/A4144937
2. Splice wire.

BLACK -> GROUND
WHITE -> RX
BLUE -> TX
YELLOW -> (TO 3.3V BATTERY NEGITIVE)
RED -> (TO 3.3V BATTERY POSITIVE)

3. Ground needs to be connected to the PCB in order to get a response from terminal. No ground, no go.

BTW:

I also purchased:

FM232RQ (which is the really cool small thing) and a FM242RL. They do not work; do not waste your time.

what does this mean exactly? i thouht gnd to 2. pin at hdd is enough what do you mean with PCB and what you puchased? about FM232RQ and FM242RL i didnt understand what you mean about these 2 item?
and about my cable is ca-42 made in china i got with nearly 5 $ and you are saying orginal ca-42 cable and i thout it's nearly 60-70$ nearly one of new HDD ...
my problem is looking like gnd this is why i am curious about your post

[MikeT31]

I followed the guide and encountered the "Unknown Diag Cmd Failure 12CC4" error after step "F3 1>N1 (enter)." Do you know what it means?

[pichi]

MikeT31, on Apr 5 2009, 01:42 PM, said:

I followed the guide and encountered the "Unknown Diag Cmd Failure 12CC4" error after step "F3 1>N1 (enter)." Do you know what it means?

Have you unmounted the PCB?
Have you reseted or powered off the PCB before N1 command?

[MikeT31]

pichi, on Apr 5 2009, 08:51 AM, said:

Have you reseted or powered off the PCB before N1 command?

No. I used TTL-232R-3V3 cable. Very simple to use. The connection to the drive works. I was able to spin it up and down. The spin up is very smooth, so the problem is probably no physical.
My drive is 1TB ST31000340AS, firmware SD15. So the extra fix used for 500 GB drives does not apply.

I did the following three times.

Quote

Use 2 pieces of paper card to isolate both the Motor connector and HDMA contacts.
Turn on power to the RS232-to-TTL adapter and the hard drive.
Press CTRL+z.
F3 T>
F3 T>/2 (enter)
F3 2>
F3 2>Z (enter)
Spin Down Complete
Elapsed Time 0.147 msecs
F3 2>
Very carefully, remove the cardstock and tighten the screws.
F3 2>U (enter)
Spin Up Complete
Elapsed Time 7.093 secs
F3 2>
F3 2>/1 (enter)
F3 1>N1 (enter)
Unknown Diag Cmd Failure 12CC4 appeared.

The connection with the drive remained. I was able to physically spin it down using Z command.
12CC4 must mean something. Converted to binary it is a 20 bit code, but I don't know what it means.

[ElectroGeeza]

Hi everyone!

First of all, thanks a lot for this useful information! Even if I personally may not be able to or know how to follow this procedure in the end, I'm sure it will be sueful to a lot of people out there and that alone is a good reason for appreciation.

Last year I assembled a new PC which uses two Barracuda 7200.11 ST3500320A disk drives, both with SD15 firmware. One is a primary drive used as system disk, and the other is a secondary storage only drive. The primary drive has serial 9QM04FVK, and the secondary has serial 9QM5MAAN. I've taken the serials off the label on the drive itself, since I can't access them both from within the PC.

The most complete story of the Barracuda 7200.11 - with serial 9QM5MAAN
The secondary drive has stopped working properly on 31 March 2009. I bought it on 11 September 2008, so it has served me for about 191 days (or 5 months and 12 days) since installation. I've had some trouble with this drive before, like once when one or two partitions disappeard. They were not visible in Windows Explorer, but the drive was detected in BIOS as usual and one of the partition was even visible but not the remaining two if I can remember. If I can remember those errors were a result of my own mess, because I once experienced difficulties expanding one of the partitions from 20 GB to like 25 GB in Windows Logical Disk Manager utility, it said something about not being able to expand the chosen volume/partition because the version of Windows Vista I was using doesn't support dynamic disks. I am using Vista Home Premium and it's true that it doesn't feature the "dynamic disk" thing, but that's OK, I don't need that. I have been using this Windows disk manager ever since Windows XP, at least, and I have been using it several times without an issue in my Vista to both expanded and reduce disk volumes/partitions. I did nothing unusual this time, just right-clicked on the disk volume and chose the option to expand it, and I ofcourse made sure there was disk space available and un-allocated to grab space from. But it attempted to make it a dynamic disk for some wierd reason, obviously, since it returned that error talking about "dynamic disks" and s*** which I didn't even ask for or chose to do. I think it was trying to convert a "standard" disk to a "dynamic" one. Vista Home Premium doesn't support that, so naturally it failed. But the most stupid thing about it is that I didn't even ask to convert it to a dynamic disk!!!...

So I heard that Partition Magic could do the job and I downloaded a copy to try it because I was recommended to use that one instead. Well, if I knew it wasn't supported by Vista I wouldn't, but now it was too late. At start-up it said it had found some error and asked me if I should let it try to fix it. Having in mind the problems I experienced with Vistas own disk utility I though it may have found something wrong, so I said yes.

The message would look something like this.

Quote

PowerQuest PartitionMagic has detected an error 110 on the partition starting at sector 2048 on disk 2.

The length of the partition in the partition table is incorrect.
The CHS length is 488390017, the LBA length is 488384496, and the File System length is 488384495.
PowerQuest PartitionMagic has determined that the length can be changed to the correct value of 488390017.

Would you like PowerQuest PartitionMagic to fix this error?

It asked the same question several times, at least 8 times, and I started to feel uncomfortable but I kept saying yes on all of them. At last the PartitionMagic interface showed up. I think it was version 8.

I can't remember if it was immidiately after this that the partitions disappeared or later or after a system restart. But I strongly believe that they disappeared after these "corrections". I think it was after a restart I didn't find the two partitions, only the third. When I then started PartitionMagic again it didn't show those same messages, but instead it indicated the two partitions that were now invisible to Windows Explorer as "BAD". So they were visible in PartitionMagic but not in Windows Explorer. What a stupid peace of software, first it says it can fix an errorous disk drive, and then it says the same disk or partition on it is BAD!! PARTITION MAGIC SCREWED ME OVER!!! AND THEN IT LAUGHT IN MY FACE!!! Then I researched a little bit and found out that others have had the same or similar experience and that it wasn't even officially supported by Vista.

The same guy who recommended me PartitionMagic then recommended me Acronis Disk Director, and I have been using that one instead ever since, without any issues.

How did I fix the missing partitions? I heard from another guy about a open-source project called Testdisk, so downloaded it, and used it to rebuild the partition tables. That solved the whole problem with missing partitions.

Now to expand the partition I wanted to from the beginning I used Acronis Disk Director and expanded it sucessfully.

All was working well since that, but after installing what later turned out to be a bad, too old or non-compatible driver for the newly purchased and installed SATA RAID controller card with the VIA VT6421 controller chip, I have been facing some serious issues with this very same disk drive that was connected to it. It was still visible but unaccessible in Windows Explorer. After several days of researching and experimenting I found a way around to access the partitions on it. It turned out that inactivating UAC in Vista allowed me to access the partitions on the drive without any issues, and once UAC was active again it got unaccessible again. Weird! Also, when UAC was inactive and I logged on to my user account, I was getting a warning message saying something about the Recycle-bin on one of the partitions being damaged and asked me if I wanted to empty it. Once I chose to empty it I think I got rid of that message for good. But it's interesting, you will never be confronted with a message like that for a very long time, perhaps never ever if you're lucky.

I let the UAC be off temporarily and was planning to backup the files from this disk drive and then re-format it, but it got totally unaccessible before I could do that. At the moment it hapened i was just viewing a PDF file in Adobe Acrobat Pro and I noticed a slow performance almost hanging the software, so I shut down Acrobat. Then I re-opened it again with no problem and countinued to read my PDF document. Later I noticed the partitions on that drive were missing, AGAIN! I re-started the PC in order for the BIOS to recognize it again, but that didn't happen. I was still able to log on to Windows thou since the system disk seemed OK. I was confused and didn't know what to do. Then I remembered reading about the firmware problems with Seagate Barracuda 7200.11. I started to read more about it and found out that the problem affected other models in this disk drive family and not only the 1 Terrabyte or 1.5 Terrabyte models like I thought it did. Jeeezzz!! :/ I checked the serials above against Seagates serial check utility and it showed that the system disk was not affected but the storage drive was among the affected ones.

It was too late for me to upgrade the firmware on it since it was already locked in the BSY state. I have concluded that this is the case with my drive, because when it's connected the HDD LED stays lit all the time and BIOS doesn't recognize it. The BIOS does seem to be able to feel the presence of the drive on that IDE channel but it lists it as "None" on that second line at POST where it should say "ST3500320AS". It doesn't halt the system start time mutch, but it does take a bit longer for the BIOS than usual, like 10 seconds more than usual to go through the POST.

I could have just read those first reports on Barracuda 7200.11 more throughly and found out that my disk drive was one of the affected models, I could almost feel this coming. But I chose to stick with the motto "don't fix it if it's not broken" and now I have to deal with it the hard way. I've learned that prevention is just as important if not even more important than fixing problems.

About this thread
I have read the WHOLE thread of 19 pages at Seagate forum started by user Inviste. And I have read very much of the second thread here at MSFN forum which picks up where the first thread at Seagate forum left off. Since the Mods there have closed the thread it took me a while to find the solution that Fatlip was on to. I believe that this is it, rigth? Is it the official one? Or did he post the solution at some other place first, like at HDD Guru? I won't even bother commenting on Seagates behaviour towards their customers, and the Mods deleting and editing and finally closing the thread at the forum over there on their website.

I see that this one is not started by Fatlip, but it's a good one. It could have been written better thou, and by that I don't mean the somewhat bad english, I mean the disposition of the text, the linking to the adapters and other parts needed for this project. I find it all a bit confusing. I appreciate the effort and all that, and thank you Gradius2 for that! I'm just being honest. If you would like to get any suggestions on how it could be improved, I'll be glad to help out.

When or if I manage to bring my disk back to life, I'll understand better how this tutorial could be improved. I think Fatlip has suggested that he or his friend would be filming the whole procedure, but I haven't seen it yet. That could be a way to deal with it, but I personally prefer textual tutorials with lots of graphics and pictures for guidance. Pictures is something I've been missing in this tutorial, I see that Gradius2 has added more pictures when he got his parts delivered, but I'm still missing the step by step kind of instructions accompanied with i.e. screenshots of the actual terminal window.

About this firmware problem
I've chatted with Thomas M. at Seagate tech support about this problem few days ago and he told me to call Seagate company i365 at their facility in UK and make some arrangements, he said they would help me. He said they won't help with free data recovery, but with free firmware update on their expense, I would only pay the postage fee. I don't know exactly what he meant, but it sounded like he was saying that the guys there would unlock the drive if it's already in locked in the BSY state and then upgrade the firmware. What do you guys know about this?

About this recovery method

The hardware
Do I need to have access to two computers at the same time? If I understand it correctly I need to supply the HDD with power from the PSU of one PC (12V Molex connector) and I need another PC to interface with the HDD. Is that correct?

I have replaced the Nokia CA-53 data cable that followed with my Nokia N73 with a new one because the old one didn't work properly after some time of use (glitchy Pop-Port connector). Could I use that old CA-53 cable for this purpose? I see some users mentioning the use of a CA-42, but could I use CA-53 as well? Does that one also include the RS232/TTL transceiver in it like the CA-42?

My PC doesn't have any Serial Port, only USB ports. Do I have to use strictly a USB-RS232-TTL adapter or can I use a USB-RS232 adapter cable in combination with a RS232-TTL adapter?

Since I was unable to find the most important thing - the TTL adapter - in local stores, I visited two online stores in Sweden - Electrokit, and ELFA - the second one being one of northern Europe's leading supplier of electronics.

Here are my findings. I have posted them all so that other users from Sweden can find the stuff faster. I think Electrokit is the best equiped online store in Sweden for this kind of small scale electronics projects, otherwise for larger projects ELFA is probably the best store to go with.

@ Electrokit

Arduino USB extension (USB to TTL??)

LilyPad USB link(USB to TTL??)

RS232/TTL nivåomvandlare (level shifter, "Spark Fun" branded)

USB-seriell omvandlare FT232RL

USB-RS232 omvandlare för PC

Kopplingstråd

Mät och test kablage

Kontakt PCB 2.54mm 4-pol

Kontakt med kabel 4-pol 20 cm

CR2032 batteri lithium 3V

Batterihållare CR2016/2025/2032 plast

@ ELFA

The website is utilizing Javascripts for the product web pages, so I can't directlink to these. You need to visit their website for international customers at https://www1.elfa.se...en/b2b/start.do and make a search for the stock number below to see the products.

73-206-58
FT232BL USB - Serial interface LQFP32

73-206-59
FT232RL USB - Serial interface SSOP28

73-206-60
FT232RQ USB - Serial interface QFN32

73-206-73
TTL-232R USB-TTL cable 5V I/O

73-206-74
TTL-232R-3V3 USB-TTL cable 3.3V I/O

25-164-09
USB-RS232 adaptor DB9m

ELFA also has mounting wires, jumpers or similar testing or lab kind of products, button-cell batteries and sockets and even batteries for PCB mounting. So they basically have all the stuff found at Electrokit, but they don't seem to have any RS232 to TTL adapter modules like the one from Sprk Fun, they seem to have only kits which you have to build on your own.

I would really appreciate some help with finding the parts. At least one of the online stores above (ELFA or Electrokit) should have most of the stuff, but I'm not absolutely sure what to look for and I rather not do any soldering work, especially not on the drive itself so I would prefer any method that doesn't involve soldering. So I'll appreciated any help finding the parts I need.

The terminal software
Do I have to use HyperTerminal or could I use some other terminal software? if I could use others as well, do you have any suggestions of which one? I am running Windows Vista. The HyperTerminal software that Microsoft licensed from Hilgraeve Software for Windows 2000 through XP is not included anymore in Windows Vista. I have visited the Hilgraeve website, but there it says that "HyperTerminal Private Edition version 7.0 is available for Windows Vista" but it also says that it's a "free 30 day trial". So it's not mutch of a free software after all, is it?!

Have you guys been using the trial version for this project? I'm not so willing to use a trial version of a software for such an important and crucial operations. I can't imagine that you all have Windows XP with this software included, at least someone must have met this difficulty with Vista and perhaps used another software. Any free or free and open-source suggestions are welcome. I know there are plenty open-source projects of this type out there, but none that I've used before and have any knowledge from. This is surely something that could be mentioned in the tutorial, what other alternative software could be used instead of HyperTerminal, instead of just stating that you could use your favorite terminal software besides the HyperTerminal.

The device driver
What about the device driver for the USB-RS232 adaptor? Does Windows have any such drivers built in to it, or do I have to build my own, or find one on the Internet? Will this be an issue?

I won't go into the details about the instructions for using the terminal software right now, this reply of mine has already gone wild and become a more lenghty one then I oricinally planned. So I'll just put a period here so you can catch up on what I've already written.

Thanks in adance! And I want to specially thank Fatlip and Gradius2 for their efforts on this problem!

This post has been edited by ElectroGeeza: 05 April 2009 - 08:55 AM

[jaclaz]

@ElectroGeeza

Not an answer to all your questions, but only to a few of your doubts:
Rest assured that not Partition Magic nor Acronis Disk Director caused the firmware of the HD to fail.

FYI:
http://everything2.c...?node_id=935597

Quote

The greatest trick the Devil ever pulled was convincing the world he didn't exist

to which I may add:

Quote

The second greatest trick the Devil ever pulled was convincing the world that partition manipulating utilities are foolproof.

the problem was not due to the programs, but to the way they were used, but still it has no relation to the firmware problem that is originated by Seagate.

A single PC is enough, as you can power the interface with a couple batteries or even, as well as the HD from the same Power Supply of the PC on which you are running Hyperterminal.

Easier would be to borrow a PC, possibly a laptop, with XP (and Hyperterminal) to perform the reviviving.

jaclaz

[pichi]

MikeT31, on Apr 5 2009, 04:12 PM, said:

pichi, on Apr 5 2009, 08:51 AM, said:

Have you reseted or powered off the PCB before N1 command?

No. I used TTL-232R-3V3 cable. Very simple to use. The connection to the drive works. I was able to spin it up and down. The spin up is very smooth, so the problem is probably no physical.
My drive is 1TB ST31000340AS, firmware SD15. So the extra fix used for 500 GB drives does not apply.

I did the following three times.

Quote

Use 2 pieces of paper card to isolate both the Motor connector and HDMA contacts.
Turn on power to the RS232-to-TTL adapter and the hard drive.
Press CTRL+z.
F3 T>
F3 T>/2 (enter)
F3 2>
F3 2>Z (enter)
Spin Down Complete
Elapsed Time 0.147 msecs
F3 2>
Very carefully, remove the cardstock and tighten the screws.
F3 2>U (enter)
Spin Up Complete
Elapsed Time 7.093 secs
F3 2>
F3 2>/1 (enter)
F3 1>N1 (enter)
Unknown Diag Cmd Failure 12CC4 appeared.

The connection with the drive remained. I was able to physically spin it down using Z command.
12CC4 must mean something. Converted to binary it is a 20 bit code, but I don't know what it means.

Ctrl+z
F3 T>/C
F3 C>Q
(List all commands of your hdd)

[bloodraveb27]

I want to say one important point...
is there anyone who had this problems https://apps1.seagat...rms_af_srl_chk/ when this chech say "Drive is not affected." "No action required."
cuz i think i do what can i do, nearly 3 days i am working on my hdd and seagate saying you didnt affected from firmware but my case is much similar like BSY error...
so could i have another problems?

[Dolic]

Possible use the cable DCA-540 instead of cable for A-35? http://pinouts.ru/Ce...emens_c55.shtml
Scheme please

[ElectroGeeza]

jaclaz, on Apr 5 2009, 05:19 PM, said:

@ElectroGeeza

Not an answer to all your questions, but only to a few of your doubts:
Rest assured that not Partition Magic nor Acronis Disk Director caused the firmware of the HD to fail.

FYI:
http://everything2.c...?node_id=935597

Quote

The greatest trick the Devil ever pulled was convincing the world he didn't exist

to which I may add:

Quote

The second greatest trick the Devil ever pulled was convincing the world that partition manipulating utilities are foolproof.

the problem was not due to the programs, but to the way they were used, but still it has no relation to the firmware problem that is originated by Seagate.

A single PC is enough, as you can power the interface with a couple batteries or even, as well as the HD from the same Power Supply of the PC on which you are running Hyperterminal.

Easier would be to borrow a PC, possibly a laptop, with XP (and Hyperterminal) to perform the reviviving.

jaclaz

I must admit, that's an interesting rhetorical device (metaphor or analogy?)! As I understand it you actually suggest that my firmware problem could be caused by the partition manipulation utilities like Acronis and PartitionMagic, rather then by the firmware bug originating from Seagate? I am not sure, but I sure have my doubts, but in that case I think that using the above mentioned utilities only speeded up the time before failure (MTBF=191 days???).

So the CR2032 battery is for powering the SR232-TTL module/adaptor? I didn't completely understand the powering instructions, like when to power on, when to power off, and what to power by what power source. I understand that I can chose to either power the SR232-TTL module from the PSU of the PC, OR from the CR2032 battery. But when do I power the HDD with the 12V Molex connector?

And what was that warning about practicing the step of removing the PCB before even attempting to do it?

Quote

Now the tricky part. Pratice a lot without any power before even trying this. You need to make sure that the screws don't touch the PCB board where they aren't suppose to or you will fry your PCB board. If you have been practicing and the power is not connected, start at STEP ONE.

With the POWER CONNECTED to the PCB board, as well as your TX/RX terminal wires, mount the board back on the HDA case. You must have the power connected when you do this.

I don't get this part at all. Is he suggesting to interface with the drive BEFORE even powering it on? What is there to practice? Experimenting with sending different commands perhaps? Or is he talking about connecting the power to the PCB and then just being careful with putting it back to the HDA housing with the power connected? Why is it important to be careful? What do I have to avoid? Is he saying that I shouldn't power on the HDD with the PCB connected to the HDA?

He was also saying something about seeing the LED errors in the terminal. Is that what the warning is about? That I can connect the drive with the PCB attached in order to see those LED errors in the terminal repeating, but if I do connect the HDD with the PCB attached that the LED errors would eventually stop repeating and the HDD would be permanently blocked? Then why do it? Just to see the LED errors?...

Quote

Keep in mind those are direct from Seagate sides, so you'll need to connect in this way

What's a "Seagate side"? Does he mean to inverse the connection where RX from first device goes to TX on the other and TX of the first goes to RX? If that's what he means, then I understand it, but I'm curious if he means something else as well.

Like I said, I don't understand this very good. I am hoping to understand it by the time I get all the parts.

bloodraveb27, on Apr 5 2009, 05:58 PM, said:

I want to say one important point...
is there anyone who had this problems https://apps1.seagat...rms_af_srl_chk/ when this chech say "Drive is not affected." "No action required."
cuz i think i do what can i do, nearly 3 days i am working on my hdd and seagate saying you didnt affected from firmware but my case is much similar like BSY error...
so could i have another problems?

When I check the two of my ST3500320AS disk drives against Seagates serial check utility, it says that the system disk isn't affected and doesn't need any actions just like it says for your disk drive. I'm not sure whether or not I should upgrade the firmware on that drive anyway. I think there were some users at the Seagate forum reporting that their drives got locked even thou they were listed as not affected.

Here you can see a screenshot: http://img4.imagesha...erialcheck2.jpg

Does anyone here know if we should uppgrade the SD15 firmware even for the drives that are listed as not affected?

This post has been edited by ElectroGeeza: 05 April 2009 - 12:11 PM

[jaclaz]

ElectroGeeza, on Apr 5 2009, 07:47 PM, said:

I must admit, that's an interesting rhetorical device (metaphor or analogy?)! As I understand it you actually suggest that my firmware problem could be caused by the partition manipulation utilities like Acronis and PartitionMagic, rather then by the firmware bug originating from Seagate? I am not sure, but I sure have my doubts, but in that case I think that using the above mentioned utilities only speeded up the time before failure (MTBF=191 days???).

NO , what I was trying to say is that YOU used IMPROPERLY Partition Magic (or Acronis) and thus messed up your partition:

• not a fault of the programs but of the use that was made of them
  AND
  
• not your fault as most people think that using such programs is easy (IT IS NOT, and can lead to partitioning corruption), and you were misled by the apparent easyness of use of them

BUT
the problem with the hard disk firmware is COMPLETELY UNRELATED to messing with partitions:

• not a fault of the programs
  AND
  
• not your fault
  BUT
  
• ONLY and EXCLUSIVELY by Seagate's fault by having a badly written firmware/test procedure/test machine in factory

I was trying to reassure you that Partition Magic, Acronis and your misuse of them are absolutely NOT guilty of having damaged the hard disk, what you did at software level carries NO CONSEQUENCES whatever at firmware one.

You are COMPLETELY innocent!



jaclaz

[bloodraveb27]

Quote

I want to say one important point...
is there anyone who had this problems https://apps1.seagat...rms_af_srl_chk/ when this chech say "Drive is not affected." "No action required."
cuz i think i do what can i do, nearly 3 days i am working on my hdd and seagate saying you didnt affected from firmware but my case is much similar like BSY error...
so could i have another problems?

When I check the two of my ST3500320AS disk drives against Seagates serial check utility, it says that the system disk isn't affected and doesn't need any actions just like it says for your disk drive. I'm not sure whether or not I should upgrade the firmware on that drive anyway. I think there were some users at the Seagate forum reporting that their drives got locked even thou they were listed as not affected.

Here you can see a screenshot: http://img4.imagesha...erialcheck2.jpg

Does anyone here know if we should uppgrade the SD15 firmware even for the drives that are listed as not affected?

At your case is second driver look like affected i want to say if also second driver got BSY error this will effect the whole system(pc will not open)
for me this seagate is my second driver and i was only usage for storage...
try to open pc only with primary(which driver installed windows)(take out second drivers power and sata data cable before open pc ...
so you can understand maybe the first driver is OK

[ElectroGeeza]

jaclaz, on Apr 5 2009, 08:45 PM, said:

ElectroGeeza, on Apr 5 2009, 07:47 PM, said:

I must admit, that's an interesting rhetorical device (metaphor or analogy?)! As I understand it you actually suggest that my firmware problem could be caused by the partition manipulation utilities like Acronis and PartitionMagic, rather then by the firmware bug originating from Seagate? I am not sure, but I sure have my doubts, but in that case I think that using the above mentioned utilities only speeded up the time before failure (MTBF=191 days???).

NO , what I was trying to say is that YOU used IMPROPERLY Partition Magic (or Acronis) and thus messed up your partition:

• not a fault of the programs but of the use that was made of them
  AND
  
• not your fault as most people think that using such programs is easy (IT IS NOT, and can lead to partitioning corruption), and you were misled by the apparent easyness of use of them

BUT
the problem with the hard disk firmware is COMPLETELY UNRELATED to messing with partitions:

• not a fault of the programs
  AND
  
• not your fault
  BUT
  
• ONLY and EXCLUSIVELY by Seagate's fault by having a badly written firmware/test procedure/test machine in factory

I was trying to reassure you that Partition Magic, Acronis and your misuse of them are absolutely NOT guilty of having damaged the hard disk, what you did at software level carries NO CONSEQUENCES whatever at firmware one.

You are COMPLETELY innocent!



jaclaz

Well, thanks for clearing that out for me. I wouldn't either expect this kind of manipulations on software layer to have any impact on the firmware. But then I'm pretty sure that software is able to communicate with the firmware, and then the firmware can communicate with the hardware. So anything is possible, even the impossible. The possible is already done, it's the impossible that's interesting.

I have only positive thoughts about the Acronis Disk Director, so I don't think it could have destroyed anything. If it can't fix something it won't destroy it either. It's the PartitionMagic that's the bad guy here. Magic???... haha, yeah, sure!! If you want to put it that way.

If you by easiness of use mean the message I was getting when starting PartitionMagic for the first time, then I'm sure a smart software shouldn't behave this way prompting the user to take action on this matter if it's something critical by which the partition table may be destroyed. Instead of that, the software should let the more advanced user be able to perform these tasks by starting the operation manually once they enter the software. Or perhaps if the advanced user wants to be prompted with this kind of thing when starting the software like this, then he should be able to set that up in the settings, where the default setting is NOT to prompt these questions. That's the way I would have designed it at least. From my experience I know that the less settings and things you mess with in a software the least are the chances you destroy or mess up something badly, and some software are too intrusive (don't know a better word for it) by both having too many options available as default and asking too many questions and things like that. I'm sure it's appreciated by advanced users or users familiar with the particular software, but for a novice it's just too much.

[ElectroGeeza]

bloodraveb27, on Apr 5 2009, 09:36 PM, said:

At your case is second driver look like affected i want to say if also second driver got BSY error this will effect the whole system(pc will not open)
for me this seagate is my second driver and i was only usage for storage...
try to open pc only with primary(which driver installed windows)(take out second drivers power and sata data cable before open pc ...
so you can understand maybe the first driver is OK

• The 9QM04FVK is the system disk on this PC system, and according to Seagate's serial check utility it's not one of the affected drives even thou it does have the SD15 firmware. What this means is that on this disk drive resides the SD15 which is the bad firmware, but this drive has probably not gone through the bad testing process which in turn means that the bug in the SD15 firmware won't ever be exhibited thanks to the correct testing process. But this still doesn't change the fact that the bad firmware resides on this drive.
  
  
  
• Since 9QM04FVK is the system disk, I am still able to load Windows with no problem.
  
  
  
• The 9QM5MAAN is the faulty disk here, and it's used only for storage, not for Windows.
  
  
  
• I have been using the 9QM04FVK as system disk for a long time now, and I'm sure it's OK. I have never had any difficulties with it ever, it works perfectly, and I think the Seagate serial check confirms that. But since I have had this bad experience with the 9QM5MAAN I am afraid that the system disk will give up on me as well. I must say that I didn't purchase these two disks at the same time, or even from the same store, so that would explain why one works perfectly and one is faulty. The probability for both of them working perfectly would seem very high if I had purchased them both from the same store. So I'm sure they both didn't came with the same shipment from the manufacturer, where one came from the healthy production line, while the other didn't have the same luck.