Hello,
One HDD, lets call it "A", was accidentally hit and started beeping, i tried to open the case but couldnt open it fully, just moved the reader a bit and closed the case again, it just keep beeping and is not recognized by the BIOS. This drive was the one who make the windows booting so i had to format a SSD to make it the boot again with a clean windows. Can i fix it myself somehow or i should send it to a repair expert? dont know how to open even the case, it just had glue all around and even though all screws sere removed i still could not remove the plate

When i start the new windows, i see i have I/O errors in other hard drive "B" when try to copy the folders, i try Repair-Volume command in powershell but doesnt repair anything, i restart and Windows start checking the drive and was like a day repairing, but just ended worse, the drive sometimes showed the folders and other times said it was RAW. I could copy some files with robocopy to another HDD "C"

Then i use ubuntu and mount the partition of "B" tells me it cannot be access, i use ntfsfix command and let me access to the files even though i cannot copy anything due to I/O errors. Also mount a partition for "C" where i wanted to copy the files, but says me cannot create a directory and the "C" drive starts to beep, even though i dont find any reason for that

I restart he computer with windows again and now "C" drives beeps when start the loading, stops and then i see "C" drive now is also missing, and "B" drive doesnt show the folders randomly as before, now is always RAW or just doesnt show anything but the drive to initialize in disk manager, same happens with "C" drive just shows the option to initialize. I tried to initialize "B" as recommends a scam page like aeseus (even though later i read from microsoft initialize actually wipe your files), i tried to initialize as GPT as "B" drive has 4GB, but seems it didnt initialize successfuly "B" cause appears as RAW and unknown, today i rescanned again and appears not as RAW but as unallocated and the drive says it is not initialized. "C" never let you initialize anything, shows an error and never shows any partition.

I ran TestDisk for "B" and seems my data is still there, shows as EFI GPT even though windows disk manager showed me the disk as Basic RAW after trying the initialization and then changed to unknown unallocated for no reason, so Basic doest mean MBR Intel? even though TestDisk tells me is EFI GPT, but it was not a bootable disk, it was just a disk to store data, so should not be EFI. Also i am confused as i though MBR disk had just a limit of 2GB capacity and this one has 4GB, should i choose EFI GPT or Intel/PC option in TestDisk?

I opened Disk Manager in windows and tells me the partition type is "not applicable" instead telling me if it is MBR or GPT and unassigned space seems almost the whole space of the disk

- opening disk A wasn't a smart idea, especially if it has valuable data. If it does, seek professional help , otherwise bin it.
- same applies if disk B has valuable data,
- generally, it seems like all 3 drives had a bad day and got physically damaged. Trying various software may cause further damage (not the SW of course but running the drive at all)


The MBR is probably corrupt, the GPT might be intact after the corrupt MBR which is why TestDisk might see it (i never used TestDisk, so just guessing).

pepe

_________________
Adatmentés - Data recovery

In this other forum Gorf did not bother telling the whole story:

https://forum.cgsecurity.org/phpBB3/vie ... hp?t=11989

Interestingly, Gorf has probably learnt that a certain minimum effort is necessary to receive an answer at all.
Therefore he has obviously put much more energy in his initial posting here.