I have seagate Barracuda 7200.11 SATA recognized in bios but showing 0 bytes capacity, any idea opinion ?

_________________
RAID/Server Recovery

_________________
Flash Killer - everyday new resources (pinout, XOR, ECC,config) for flash devices

data will be safe with this method ? i am afraid not, plz advise some one any otherway ?

_________________
RAID/Server Recovery

The only other way is to take it to a professional where it will be safe.

_________________
Zero Alpha: zeroalpha.com.au
Find Cheap Donor Drives App: https://www.zeroalpha.com.au/donor-drive-app Updated February 2026

Toatally agree. Otherwise your mistakes in DIY attempts will cost you higher and the recovery chances will be lower.

FINAL WARNING: Please do NOT try this if you have valuable data on your drive. Do not blame anyone if something goes wrong. You do it at your own risk. Remember that if something goes wrong, it is extremely unlikely that anyone will be able to help you remotely. One wrong command via terminal could easily result in a completely bricked HDD (I really do mean bricked = no one will be able to recover it, even Seagate).


This disclamer says it all. U can do it urself. But if u are not confident - find a shop. Its not an expensive issue.

can any one please explain the expected problem in brief ? is it because of FW or what ?

_________________
RAID/Server Recovery

FW issue.

Description
An issue exists that may cause some Seagate hard drives to become inoperable immediately after a power-on operation. Once this condition has occurred, the drive cannot be restored to normal operation without intervention from an expert. Data on the drive will be unaffected and can be accessed once normal drive operation has been restored. This is caused by a firmware issue coupled with a specific manufacturing test process.

Root Cause
This condition was introduced by a firmware issue that sets the drive event log to an invalid location causing the drive to become inaccessible.
The firmware issue is that the end boundary of the event log circular buffer (320) was set incorrectly. During Event Log initialization, the boundary condition that defines the end of the Event Log is off by one. During power up, if the Event Log counter is at entry 320, or a multiple of (320 + x*256), and if a particular data pattern (dependent on the type of tester used during the drive manufacturing test process) had been present in the reserved-area system tracks when the drive's reserved-area file system was created during manufacturing, firmware will increment the Event Log pointer past the end of the event log data structure. This error is detected and results in an "Assert Failure", which causes the drive to hang as a failsafe measure. When the drive enters failsafe further update s to the counter become impossible and the condition will remain through subsequent power cycles. The problem only arises if a power cycle initialization occurs when the Event Log is at 320 or some multiple of 256 thereafter. Once a drive is in this state, there is no path to resolve/recover existing failed drives without expert intervention. For a drive to be susceptible to this issue, it must have both the firmware that contains the issue and have been tested through the specific manufacturing process.

This applies if there is no additional problem in the drive. And this explain why there is no "one solution fits all" problem and why people apply unconditionally what they have read on the internet to every situation, bricking drives

For a DIY fix, and an explanation of the bug, see this thread:
http://forums.seagate.com/t5/ATA-and-Se ... 036#M19464

Contact Seagate Tech Support and ask if your drive qualifies for free data recovery.

BTW, Seagate's terminal commands are Case Sensitive. Don't get it wrong.

Finally i got the drive back with all of the data, thanks a lot of the help.. great work.. gurus

_________________
RAID/Server Recovery