after writing these correctly-detected values in, Windows 7 still does not recognise it as a valid NTFS drive - it still reports RAW.įindandmount also detects these 2 partitions upon deep scanning (not normal scanning). The problem lies now still in the first partition - it is detected as NTFS and testdisk is able to “write” the detected partition data in, as well as “write” the MBR in. the second partition however is recognised easily and is active, NTFS. the BIOS recognised it easily but again, the first partition is still RAW. Testdisk only allows me to “A” add my own partition information, or “L” load some information, but does not detect anything to help me.Īnyone has any further thoughts what might be happening? most suggestions I am receiving are last-ditch methods, am I down to that?Īn update: i removed the HDD from the case and connected it directly to the SATA port on my motherboard.
I didn’t accidentally format my drive either, nor damage it.
Not sure what happened in my situation, seems that everyone’s managed to testdisk a solution way earlier than me. Since it detects Drive J: as the first partition, I tried to calculate how many heads this partition will take, and enter geometry as:Ĩ9730.5228822 so I have to enter 89731 cylinders, heads 255, sectors 63, size 512 The analysis was very very fast, within a few minutes, but partition detected was nothing. I used the numbers derived, as recommended on the net, to re-Analyze testdisk.Ĭylinders 121601 heads 255 sectors 63 size 512 it seems that others on the internet have a similar strange geometry as well, see link: LBA: 1953525168 does not fit exactly into 255 heads 63 sectors, there is a decimal place. So it seems that sectors = 1953525168 x 512 sector size = 1 terabyte, that seems to fit. Western Digital Caviar Black, 64 mb cache, model: WD1001FAES-00W7A0 I got some further geometry information after consulting Western Digital support centre, as It did not detect the second partition.ĭisk Management also reads two “drives”, both RAW, in the correct sizes 687.37 gig & 244.14 gig. however, the reported geometry is (probably) wrong. So what happened was, it managed to detect the first partition as “Drive J:” with the correct size. One day the whole hard disk became undetectable.Īfter testdisk Analyze taking 72 hours, it was detected asĭrive J: - 738 GB / 687 GiB - WD My Book 3.0 1123 Original FAT table was unchanged from purchase, i’m not sure if it’s FAT32 or NTFS Hi, anyone has any thoughts about my case? here’s a summary:ġ terabyte My Book 3.0 partitioned into 687.37 gig & 244.14 gig
0 kommentar(er)
