Bad NTFS Boot Partition?
Posted: 24 Sep 2014, 01:31
Hi,
I have something stange going on and I can't figure out what happened, but now my *new* external usb3 4TB drive won't mount.
I am running a dual boot system with windows 7 and xubuntu. My main OS is xubuntu. I am getting ready to update my Linux OS and have had to boot into Windows a few times to sync the time and such, and in the process Windows of course made a bunch of updates. I had my USB drive connected as the reason I was upgrading my OS was that my Nix filesystem seemed to be damamged and so I used Gnu ddrescure to back everything up to img files on the big USB drive. All was fine until one last boot into Windows sparked a chkdsk on my USB drive and I wasn't around when it started. When I came back to my computer I noticed that chkdsk was "Fixing" all my files on the USB drive by deleting them. As I was watching my life and data go down the tubes, my only option was to do a hard shutdown.
So..
after removing the drive and booting into Windows, I immediately went to check the logs to see if I could find a record of this heinous action. The logs I found showed a bunch of errors but said it was unable to fix the errors as the disk was in read-only mode. (I am not in Windows right now but I can hunt down and attach those logs if needed.)
Problem is, that I clearly saw when chkdsk was running that it was deleting the files.
Now I attached the drive in linux and of course it was unmountable so I moved to try testdisk. I analysed the disk,
then did the Deeper Search which took most of the day bad came back with zero errors.
I looked over this page, http://www.cgsecurity.org/wiki/Advanced ... MFT_Repair
but wasn't confident enough to go any further. From what I can tell, the disk seems structuraly sound, but something got fubar'd along the way before chkdsk started, or from the hard rebbot to stop chkdsk.
Here's my log
Could anyone please advise how I should proceed? The data on this is already a backup of possibly corrupted data and I feel I keep burrowing further down the rabbit hole. The TestDisk program is still open in my terminal and won't do anything until I hopefully hear back.
Many Thanks,
akovia
I have something stange going on and I can't figure out what happened, but now my *new* external usb3 4TB drive won't mount.
I am running a dual boot system with windows 7 and xubuntu. My main OS is xubuntu. I am getting ready to update my Linux OS and have had to boot into Windows a few times to sync the time and such, and in the process Windows of course made a bunch of updates. I had my USB drive connected as the reason I was upgrading my OS was that my Nix filesystem seemed to be damamged and so I used Gnu ddrescure to back everything up to img files on the big USB drive. All was fine until one last boot into Windows sparked a chkdsk on my USB drive and I wasn't around when it started. When I came back to my computer I noticed that chkdsk was "Fixing" all my files on the USB drive by deleting them. As I was watching my life and data go down the tubes, my only option was to do a hard shutdown.
So..
after removing the drive and booting into Windows, I immediately went to check the logs to see if I could find a record of this heinous action. The logs I found showed a bunch of errors but said it was unable to fix the errors as the disk was in read-only mode. (I am not in Windows right now but I can hunt down and attach those logs if needed.)
Problem is, that I clearly saw when chkdsk was running that it was deleting the files.
Now I attached the drive in linux and of course it was unmountable so I moved to try testdisk. I analysed the disk,
then did the Deeper Search which took most of the day bad came back with zero errors.
I looked over this page, http://www.cgsecurity.org/wiki/Advanced ... MFT_Repair
but wasn't confident enough to go any further. From what I can tell, the disk seems structuraly sound, but something got fubar'd along the way before chkdsk started, or from the hard rebbot to stop chkdsk.
Here's my log
Could anyone please advise how I should proceed? The data on this is already a backup of possibly corrupted data and I feel I keep burrowing further down the rabbit hole. The TestDisk program is still open in my terminal and won't do anything until I hopefully hear back.
Many Thanks,
akovia