Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
November 28th, 2010, 18:11
Hi All,
I got a strange and interesting case with a Seagate 2.5 drive Momentus 7200.4 SATA 3Gb/s 250-GB Hard Drive
Exactly the model ass can be seen here:
http://www.seagate.com/ww/v/index.jsp?v ... cale=en-USThe drive is detected as capacity 0.
This drive has only one head.
How can I bypass the firmware issue on the drive even I don't have PC3000?
The symptom is exactly as the known seagate busy bug (7200.11 LBA 0).
Any suggestions for help?

Best Regards,
November 28th, 2010, 19:06
Scorpion wrote:This drive has only one head.
Not that it helps, but according to section 2.4 of the following document, your drive (ST9250410AS or ST9250410ASG) has 2 heads and 1 platter.
Momentus 7200.4 SATA Product Manual, Rev. A:
http://www.seagate.com/staticfiles/supp ... 0(Holliday)/100534376a.pdf
November 28th, 2010, 19:13
where's the beef ?
November 28th, 2010, 19:24
fzabkar wrote:Scorpion wrote:This drive has only one head.
Not that it helps, but according to section 2.4 of the following document, your drive (ST9250410AS or ST9250410ASG) has 2 heads and 1 platter.
Momentus 7200.4 SATA Product Manual, Rev. A:
http://www.seagate.com/staticfiles/supp ... 0(Holliday)/100534376a.pdf
So Atola did a mistake with the identify..
BlackST what do you mean by "where's the beef ?"?
Any creative way to bypass the firmware issue?
The solution for the busy bug of 7200.11 (LBA 0) would kill the drive permanently? or would fix it?
November 28th, 2010, 19:42
Scorpion wrote:The symptom is exactly as the known seagate busy bug (7200.11 LBA 0).
1. busy bug and LBA 0 are two different symptoms
2. LBA 0 as you mentioned is not a problem but a symptom
3. And it can represent many problems
4. Finding the exact problem is the key
November 28th, 2010, 19:54
Doomer wrote:Scorpion wrote:The symptom is exactly as the known seagate busy bug (7200.11 LBA 0).
1. busy bug and LBA 0 are two different symptoms
2. LBA 0 as you mentioned is not a problem but a symptom
3. And it can represent many problems
4. Finding the exact problem is the key
Tnx for the info
Still I don't have any idea how do I break this case.
I thought about terminal codes but as everybody knows, the wrong sequence impot of the codes will kill the drive, or I mistaken?
November 28th, 2010, 21:45
Scorpion wrote:Still I don't have any idea how do I break this case.
Maybe it is time to outsource
November 28th, 2010, 21:49
Doomer wrote:Scorpion wrote:Still I don't have any idea how do I break this case.
Maybe it is time to outsource
Good idea, but specific this case would not be a worthwhile to do that..
Beside of that, PM me with your regular prices for heads swap..
November 28th, 2010, 22:33
you have to find somebody who interested in this
Powered by phpBB © phpBB Group.