hi i have hitachi 500gb SATA drive, it was working fine few days ago and suddenly my system cannot detect it and takes lot of time while booting up but still can not detect the drive i have another same drive and same capacity i tried to changed the board of both the drives so that i can recover data from the faulty drive, however still there was no luck with the change of board i be really thankful if some one can helo me out to recover the data from it

Use the search function for "nv-ram". It will help you understand why the PCB swap is not enough as a fix, given it is a PCB issue.

In order to get a little more helpful advice, you need to provide more details about the drive's behavior after power-on.

Does it spin? If yes, does it click? Etc.

For comparison, you can listen to other drive you have to hear what a good drive should run like.

_________________
Hard Disk Drive (HDD), Solid State Drive (SSD, SATA, NVMe, etc), USB Flash Drive and RAID Data Recovery Specialist in Massachusetts

yeah which board i conned the orignal one or the one from the other drive the drive spins normally there are no click at all i tried the board of faulty drive on the good one and the good drive doesnot works with that as well

1) put PCBs back to their own drives
2) power-on the healthy drive and listen to how it operates (ex: begins to spin, then hear two-three quick clicks, still spinning, then drive shows up in device manager)
3) Do the same with failed drive. Then post here the drive's behavior by referencing the example above.

_________________
Hard Disk Drive (HDD), Solid State Drive (SSD, SATA, NVMe, etc), USB Flash Drive and RAID Data Recovery Specialist in Massachusetts

When having on original PCB does the drive show up in your BIOS. You say it takes a long time to boot with this HDD on it.

BTW board swap like you try will not work. Hitachi has adaptive parameters in the NVRAM that have to be moved over to work. You can not simply swap out a board and it will work. You either need to move the NVRAM to the donor drive board or have special tools to write the NVRAM to the donor board to make it work

_________________
Iorana Haraharaini

@ labtech i am at work right now and will check it once i be home and post it here

@ poehere yeah it takes longer to boot up and the drive doesnot show up in BIOS so how can i get those special tools to write NVRAM to donor drive board and another thing is will i be able to write back the NVRAM of the donor drive to donor board.

@labtech i have checked the sound of the hard drive they sound almost the same.

"Almost" means there is a difference. What is that difference?
Last last time I will try to help in this case if you refuse to be descriptive.

_________________
Hard Disk Drive (HDD), Solid State Drive (SSD, SATA, NVMe, etc), USB Flash Drive and RAID Data Recovery Specialist in Massachusetts

i have listened to them again both of them click exactly the same and then spin off smoothly

Search on MHDD and see if it detects the drive

_________________
Hard Disk Drive (HDD), Solid State Drive (SSD, SATA, NVMe, etc), USB Flash Drive and RAID Data Recovery Specialist in Massachusetts

i have used MHDD and pressed F2 on every port but no luck with detection of hard drive

The have more severe problems. Sending to a pro is the best course of action if data is important.
If not, try RMA.

_________________
Hard Disk Drive (HDD), Solid State Drive (SSD, SATA, NVMe, etc), USB Flash Drive and RAID Data Recovery Specialist in Massachusetts

That can mean one of two things. Either:

a) Your "problem" drive has a serious issue; or/and
b) Your motherboard & BIOS is not configured (or not able to be configured) and being used by you, in a way that makes it compatible with MHDD - so even a good drive wouldn't be detected by MHDD in that case, and that can mislead any attempt at diagnosing the "problem" drive too.

I've replied to several similar situations in the past. Search for MHDD in my previous postings using the forum search feature, to read those discussions (e.g. SATA controller setting, SATA port used etc.).

To distinguish between options (a) & (b) above, it can be simplest to attach a known-working drive to the same SATA port where you plan to attach your "problem" drive, and check whether that known-working drive can be detected by MHDD. If that known-working drive can be detected and responds to EID correctly, then point (a) above is likely; if not then point (b) above is likely and you need to resolve that first, before you can then use MHDD as previously suggested by labtech, with your "problem" drive.