Startup Chkdsk

[Seekermeister]

Frequently, when I have a BSOD, when Windows reboots, it wants to run chkdsk on some partition on another drive from where the OS is, which is formatted FAT32. But none of my programs are located on these, and when the crash happens, I'm not doing anything to access them. I wouldn't be surprised if it wanted to check the OS partition, but why would one such as I described even come into play? This is not simply an installation issue, because it has happened repeatedly on different installations.

 

[Canterwood]

FAT32 gets corrupted much more easily than NTFS, so the OS thinks it needs to check the FAT32 partition after a BSOD even if its not being used.

If you convert it to NTFS, (assuming your using XP or 2K) then the issue would go away, but I'd be more concerned as to why I was getting frequent BSOD tbh.

 

[Seekermeister]

I'm still working on the BSOD aspect. I appreciate the insight into FAT32 though, but I don't want to change it, because I use those partitions for both Windows and Linux, and Linux doesn't like NTFS too much.

 

[Nothinman]

The reason NTFS doesn't need chkdsk run is because it's journaled. All I/O on the filesystem is first commited to the journal and then done later, after the operation is completed successfully the journal entry is removed. This means that no matter what happens the filesystem is left in a consistent state, when the driver mounts the filesystem it can look in the journal and either finish or rollback any operations that weren't completed. FAT has no journal so if the filesystem is unmounted uncleanly the only way to know if anything is wrong to scan the whole filesystem and see if it looks ok.