EclipseWebJS2 Posted February 7, 2006 Share Posted February 7, 2006 (edited) OK, somebody tell me something: Does a bad cluster in a file mean there's physically bad sectors on my hard drive ... again?!? Event Type: Information Event Source: Winlogon Event Category: None Event ID: 1001 Date: 2/7/2006 Time: 11:03:39 AM User: N/A Computer: LUNAR-ONE Description: Checking file system on C: The type of the file system is NTFS. A disk check has been scheduled. Windows will now check the disk. Attribute record of type 0x80 and instance tag 0x0 is cross linked starting at 0x1fc27e for possibly 0x35 clusters. Attribute record of type 0x80 and instance tag 0x0 is cross linked starting at 0x1fc27e for possibly 0x35 clusters. Some clusters occupied by attribute of type 0x80 and instance tag 0x0 in file 0x4183 is already in use. The attribute of type 0x80 and instance tag 0x0 in file 0x4183 has allocated length of 0x3590000 instead of 0x30d0000. Deleted corrupt attribute list entry with type code 128 in file 16771. Unable to locate attribute with instance tag 0x0 and segment reference 0x3000000004a8d. The expected attribute type is 0x80. Deleting corrupt attribute record (128, $J) from file record segment 19085. Unable to locate attribute with instance tag 0x0 and segment reference 0x100000000a8ab. The expected attribute type is 0x80. Deleting corrupt attribute record (128, $J) from file record segment 43179. Cleaning up sparse flag for file 0x4183. Cleaning up minor inconsistencies on the drive. The file attributes flag 0x26 in file 0x4183 is incorrect. The expected value is 0x226. Correcting a minor error in file 16771. Inserting an index entry into index $I30 of file 11. Cleaning up 6 unused index entries from index $SII of file 0x9. Cleaning up 6 unused index entries from index $SDH of file 0x9. Cleaning up 6 unused security descriptors. CHKDSK is verifying Usn Journal... Creating Usn Journal $J data stream Usn Journal verification completed. CHKDSK is verifying file data (stage 4 of 5)... Windows replaced bad clusters in file 8622 of name \Ontrack\MXCYCLE\00000120. Windows replaced bad clusters in file 8804 of name \Ontrack\MXCYCLE\00000252. Windows replaced bad clusters in file 8835 of name \Ontrack\MXCYCLE\00000260. Windows replaced bad clusters in file 8865 of name \Ontrack\MXCYCLE\00000262. Windows replaced bad clusters in file 8870 of name \Ontrack\MXCYCLE\00000263. Windows replaced bad clusters in file 8883 of name \Ontrack\MXCYCLE\00000274. Windows replaced bad clusters in file 8974 of name \Ontrack\MXCYCLE\00000114. Windows replaced bad clusters in file 9015 of name \Ontrack\MXCYCLE\00000117. Windows replaced bad clusters in file 16504 of name \Ontrack\MXCYCLE\00000251. Windows replaced bad clusters in file 18910 of name \Ontrack\MXCYCLE\00000256. Windows replaced bad clusters in file 18942 of name \Ontrack\MXCYCLE\00000266. Windows replaced bad clusters in file 18956 of name \Ontrack\MXCYCLE\00000268. Windows replaced bad clusters in file 19000 of name \Ontrack\MXCYCLE\00000273. Windows replaced bad clusters in file 19003 of name \Ontrack\MXCYCLE\00000275. Windows replaced bad clusters in file 19014 of name \Ontrack\MXCYCLE\00000283. Windows replaced bad clusters in file 19786 of name \Ontrack\MXCYCLE\00000146. Windows replaced bad clusters in file 20182 of name \Ontrack\MXCYCLE\00000152. Windows replaced bad clusters in file 20218 of name \Ontrack\MXCYCLE\00000154. Windows replaced bad clusters in file 20243 of name \Ontrack\MXCYCLE\00000160. Windows replaced bad clusters in file 20246 of name \Ontrack\MXCYCLE\00000163. Windows replaced bad clusters in file 20269 of name \Ontrack\MXCYCLE\00000169. Windows replaced bad clusters in file 20271 of name \Ontrack\MXCYCLE\00000171. Windows replaced bad clusters in file 20272 of name \Ontrack\MXCYCLE\00000172. Windows replaced bad clusters in file 20274 of name \Ontrack\MXCYCLE\00000174. Windows replaced bad clusters in file 20275 of name \Ontrack\MXCYCLE\00000175. Windows replaced bad clusters in file 20277 of name \Ontrack\MXCYCLE\00000177. Windows replaced bad clusters in file 20278 of name \Ontrack\MXCYCLE\00000178. Windows replaced bad clusters in file 20279 of name \Ontrack\MXCYCLE\00000179. Windows replaced bad clusters in file 20291 of name \Ontrack\MXCYCLE\00000180. Windows replaced bad clusters in file 20293 of name \Ontrack\MXCYCLE\00000182. Windows replaced bad clusters in file 20294 of name \Ontrack\MXCYCLE\00000183. Windows replaced bad clusters in file 20296 of name \Ontrack\MXCYCLE\00000186. Windows replaced bad clusters in file 20298 of name \Ontrack\MXCYCLE\00000188. Windows replaced bad clusters in file 20396 of name \Ontrack\MXCYCLE\00000197. Windows replaced bad clusters in file 20399 of name \Ontrack\MXCYCLE\00000198. Windows replaced bad clusters in file 20402 of name \Ontrack\MXCYCLE\00000199. Windows replaced bad clusters in file 20405 of name \Ontrack\MXCYCLE\00000200. Windows replaced bad clusters in file 20408 of name \Ontrack\MXCYCLE\00000201. Windows replaced bad clusters in file 20411 of name \Ontrack\MXCYCLE\00000202. Windows replaced bad clusters in file 20414 of name \Ontrack\MXCYCLE\00000203. Windows replaced bad clusters in file 20506 of name \Ontrack\MXCYCLE\00000216. Windows replaced bad clusters in file 20613 of name \Ontrack\MXCYCLE\00000220. Windows replaced bad clusters in file 20614 of name \Ontrack\MXCYCLE\00000221. Windows replaced bad clusters in file 20619 of name \Ontrack\MXCYCLE\00000225. Windows replaced bad clusters in file 20620 of name \Ontrack\MXCYCLE\00000226. Windows replaced bad clusters in file 20625 of name \Ontrack\MXCYCLE\00000230. Windows replaced bad clusters in file 20626 of name \Ontrack\MXCYCLE\00000231. Windows replaced bad clusters in file 20627 of name \Ontrack\MXCYCLE\00000232. Windows replaced bad clusters in file 20631 of name \Ontrack\MXCYCLE\00000233. Windows replaced bad clusters in file 20636 of name \Ontrack\MXCYCLE\00000234. Windows replaced bad clusters in file 20641 of name \Ontrack\MXCYCLE\00000235. Windows replaced bad clusters in file 20642 of name \Ontrack\MXCYCLE\00000236. Windows replaced bad clusters in file 20643 of name \Ontrack\MXCYCLE\00000237. Windows replaced bad clusters in file 20644 of name \Ontrack\MXCYCLE\00000238. Windows replaced bad clusters in file 20645 of name \Ontrack\MXCYCLE\00000239. Windows replaced bad clusters in file 20646 of name \Ontrack\MXCYCLE\00000240. Windows replaced bad clusters in file 20649 of name \Ontrack\MXCYCLE\00000241. Windows replaced bad clusters in file 20661 of name \Ontrack\MXCYCLE\00000247. Windows replaced bad clusters in file 20662 of name \Ontrack\MXCYCLE\00000248. Windows replaced bad clusters in file 20663 of name \Ontrack\MXCYCLE\00000249. Windows replaced bad clusters in file 20664 of name \Ontrack\MXCYCLE\00000250. Windows replaced bad clusters in file 46694 of name \Ontrack\MXCYCLE\00000332. Windows replaced bad clusters in file 46697 of name \Ontrack\MXCYCLE\00000333. Windows replaced bad clusters in file 46703 of name \Ontrack\MXCYCLE\00000337. Windows replaced bad clusters in file 46710 of name \Ontrack\MXCYCLE\00000336. Windows replaced bad clusters in file 46719 of name \Ontrack\MXCYCLE\00000295. Windows replaced bad clusters in file 46722 of name \Ontrack\MXCYCLE\00000296. Windows replaced bad clusters in file 46725 of name \Ontrack\MXCYCLE\00000297. Windows replaced bad clusters in file 46749 of name \Ontrack\MXCYCLE\00000330. Windows replaced bad clusters in file 46772 of name \Ontrack\MXCYCLE\00000311. Windows replaced bad clusters in file 46787 of name \Ontrack\MXCYCLE\00000322. Windows replaced bad clusters in file 46790 of name \Ontrack\MXCYCLE\00000323. Windows replaced bad clusters in file 46791 of name \Ontrack\MXCYCLE\00000324. Windows replaced bad clusters in file 46796 of name \Ontrack\MXCYCLE\00000325. File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... Free space verification is complete. CHKDSK discovered free space marked as allocated in the master file table (MFT) bitmap. CHKDSK discovered free space marked as allocated in the volume bitmap. Windows has made corrections to the file system. 40136008 KB total disk space. 13634048 KB in 38464 files. 12428 KB in 3886 indexes. 0 KB in bad sectors. 114776 KB in use by the system. 65536 KB occupied by the log file. 26374756 KB available on disk. 4096 bytes in each allocation unit. 10034002 total allocation units on disk. 6593689 allocation units available on disk. Internal Info: a0 ba 00 00 79 a5 00 00 2f e5 00 00 00 00 00 00 ....y.../....... c9 00 00 00 01 00 00 00 47 01 00 00 00 00 00 00 ........G....... 08 dc 60 01 00 00 00 00 a4 9e 41 1c 00 00 00 00 ..`.......A..... a0 52 57 01 00 00 00 00 16 f7 a4 83 01 00 00 00 .RW............. 8e f7 9f a6 01 00 00 00 e2 cf 8f 51 03 00 00 00 ...........Q.... 99 9e 36 00 00 00 00 00 a0 39 07 00 40 96 00 00 [email protected] 00 00 00 00 00 00 28 40 03 00 00 00 2e 0f 00 00 ......(@........ Windows has finished checking your disk. Please wait while your computer restarts. Edited February 7, 2006 by EclipseWebJS2 Link to post Share on other sites
EclipseWebJS2 Posted February 7, 2006 Author Share Posted February 7, 2006 0 KB in bad sectors.But the test result didn't reveal any bad sectors Link to post Share on other sites
mouse Posted February 7, 2006 Share Posted February 7, 2006 Crosslinked files are part of the problem. All drives have bad clusters from time to time and might even have bad sectors. Usually chkdsk will move them out of service and replace them with good clusters and usually move files if a whole sector is bad. Drives are built with extra cluster for cluster replacement. Link to post Share on other sites
EclipseWebJS2 Posted February 7, 2006 Author Share Posted February 7, 2006 (edited) Crosslinked files are part of the problem. All drives have bad clusters from time to time and might even have bad sectors. Usually chkdsk will move them out of service and replace them with good clusters and usually move files if a whole sector is bad. Drives are built with extra cluster for cluster replacement. And just where are those extra clusters? In that 7 megs of unallocated space on my HD? Here's something else-- I was just running my hard drive tools, and the tool says I had 15 heads for the disk instead of 16... ?? Another question -- does the boot-time CHKDSK make copies of the crosslinked clusters? Edited February 7, 2006 by EclipseWebJS2 Link to post Share on other sites
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now