|
Hi, I have Windows XP Pro SP3.
My hard drive developed bad sectors, and windows couldn't load (including safe mode). I used chkdsk /f on the drive which marked 8kb of bad sectors. After reading a bit here I found that running chkdsk /f was not a good idea...
Now I'm trying to figure out which files were damaged. I opened the drive in WinHex and I located the bad sectors (used the info from the windows Application log in Event Viewer to find the sector numbers reported by chkdsk). According to WinHex, the bad sectors are all in a file called $LogFile. Or to be more precise: they are in a file called $BadClus:$Bad , but I if I guess correctly (?) this file is simply the bad cluster mark created by chkdsk, while dozens of clusters before and after this specific sector contain the file $LogFile (this is what WinHex says). Using the "List Clusters" function in WinHex, I saw that the $LogFile file is fragmented exactly on the cluster with the bad sectors (for example, let's say $LogFile is in clusters 1,2,3,4,5,800,7,8,9,10... while cluster 6 has bad sectors and the file $BadClus:$Bad).
So my question is this: if I understand all of the above correctly, is it logical to assume that the location of the bad sector in the middle of a continuous stream of clusters that contain the file $LogFile, means that the file damaged by the bad sector is in fact $LogFile and not some other file? And if this $LogFile thing was damaged, could that explain why windows could not load?
Thank you very much.
|