M
mattrix3
Hi,
A couple of times a day I am getting this error in the event viewer:
The device, \Device\Harddisk0\D, has a bad block
I'm not sure what this means,
a) I have a couple of new bad blocks each day, or
b) NTFS keeps hitting the SAME bad block a couple of times a day
I'm assuming the second. I would have thought that if the bad block was unallocated, NTFS would mark it as unusable. So its probably in a file.
So, is there any way to work out which file(s) is affected?
Is there a way to find out how many bad blocks NTFS thinks there is?
I am reluctant to let chkdsk fix the drive before I know what is likely to be affected.
Chkdsk in Read-Only mode finds a single error in the index and wont complete.
Is there a way to repair the index, (without doing the security repair) so that chkdsk can complete and tell me about bad blocks?
Thanks,
Continue reading...
A couple of times a day I am getting this error in the event viewer:
The device, \Device\Harddisk0\D, has a bad block
I'm not sure what this means,
a) I have a couple of new bad blocks each day, or
b) NTFS keeps hitting the SAME bad block a couple of times a day
I'm assuming the second. I would have thought that if the bad block was unallocated, NTFS would mark it as unusable. So its probably in a file.
So, is there any way to work out which file(s) is affected?
Is there a way to find out how many bad blocks NTFS thinks there is?
I am reluctant to let chkdsk fix the drive before I know what is likely to be affected.
Chkdsk in Read-Only mode finds a single error in the index and wont complete.
Is there a way to repair the index, (without doing the security repair) so that chkdsk can complete and tell me about bad blocks?
Thanks,
Continue reading...