Went back to diskdrill, smart errors all over the place and ever since. Testdisk detected the NTFS partition but the filesystem was damaged Used DiskDrill to detect the files, could not recover because of data limit from the software The FAT32 Partition got unallocated by windows (oops, forgot to mention before)
One FAT32 partition of about 40 gig got inserted on the drive (By that point i gave up saving any data.) The disk would not initialise because of physical failure.ĤTb external hard drive used for moderate dudty storage (WD Mybook 24EE, about 3.9k hours use) I found out about the MBR vs GPT thing, used windows to convert back to GPT and then tried to format the disk into NTFS. Once back on disk drill i am getting smart warnings that my drive is failing, read times are abysmall, the whole ordeall. That plan would have worked fine from the get go because out of the 3Tb of data i had only a very tiny portion was important. At that point i realised i was in way over my head with that and choose to go back to diskdrill, save whatever most important data and wipe the rest. Once the process returned testdisk could not detect the ntfs partition anymore. I read somewhere that trying to use Testdisk's mbr rebuild could help you in that case so i went for it. So i decided to go for Testdisk, the software detected the ntfs partition but could not rebuild the filesystem. I first tried disk drill, it was working fine and detecting every file with no issue but i found out about the 500mb limit for the free version. Once the backup was complete i created a instalation disk for windows but i mistakenly selected the external hard drive instead of the usb key i just connected to the computer.Īnyways, once i realised the mistake i started looking for solutions. Up to this point the external hard drive had been used to a normal level for a external storage device and was clocking in about 3.9k hours online. I recently had to reinstall windows on my main computer so i used my external hard drive to store the data meanwhile. I know it is kind of a far fetch but i feel like the timing of the error to be at least suspicious. The smart fail started right after i mistakenly tried to rebuild the MBR using Testdisk (i know now that MBR cant handle more than 2tb and i should have gone for GPT). The disk in question is a 4TB Wd external hard drive (my book 25ee). TLDR: Is it possible for a disk to fail its smart self-health test for software issues.
0 kommentar(er)
