HaQue wrote:
-Performing commands you don't know is one mistake.
-Not Documenting each step so you actually know which changed your drive is another.
-Spending hundreds of hours reading all over the web, while obviously exaggerated, is another. Reading is one part, experience is key.
-reading tons and tons about this trap is overkill. Almost every tutorial on the 7200.11 fixes start with "Do Not try this on a 7200.12", yet you still did it.
-Wanting to "fix" a drive no one in their right mind would ever use for data is another.
-not listening to Pro's is another.
If I drain the oil out of my car and run the engine until the con rods smash out the engine block, I can flatten the battery trying to start it. So I ask a Pro and he says my engine is dead. get a new one. Do I say, no, I bought new battery and now the engine turns over so it must be nearly fixed?
just because you hammered commands into the drive, and now terminal says something different does not mean you have got it on the way to being "fixed".
What criteria are you using to decide the Pro's don't know what they are talking about?
I would be interested to know what, specifically, you have actually learnt so far. Aside from don't apply 7200.11 fixes to 7200.12 of course.
Anyway what evs
To HaQue, well, it's easy to criticize and being sarcastic when others do a mistake. All i see is that nobody can share any knowledge and information on this topic. It's just worthless posts. Beginning by the first one. Some here like to waste their time to criticize and discourage the amateurs, It's well known. That said, i suspect that the culprit step of my part (after the partial LBA problem resulted of the bad translator format command) is that "one key fix command" in F3 menu of STR-3000 (this program is not working at all). As i said in the first topic, i dont care at all about this drive. That's why i just tried random things. As we say, sometimes we learn by mistakes. That can be applied here.
To thatdellguy, in my case i really dont care about the data, there's nothing inside this drive, it was just used to do desktop cloning with norton ghost image on it. And when i say random commands, it's a imaging expression.
Meanwhile, i've learnt how to read the modules for F3, and i'm investigating on the possibility to restore them, maybe by using the second platter SA copy. So if i can read the modules, doesn't that mean there is not "severe physical damages"? or maybe partially at worst.
FAQ
Search
Login
Register
HDDGURU FILES
