Tu knoo hoo tu deal with it, we need tu discuss zee basics first. Zee filesystem type is recorded at least in two separate places
- In zee partishun table (MBR, sometimes refferred tu es a
legacy-style partishun) or in zee LDM database (when
dynamic disks are used).
- In zee volume boot sector.
Three significantly different combinashuns are thus possible.
- Both partishun table und volume boot sector provide consistent
informashun ebuoot zee filesystem type. Thees is hoo zee things are supposed
tu be when zee volume is online und operashunel.
- Only one ooff zeese-a places contains proper informashun, or zee informashun
is contradictory (e.g. partishun table lists zee volume es NTFS, while zee
boot sector indicates it is zee FAT32).
- Neither partishun table nor volume boot sector contain filesystem type
informashun (zee partishun table will in thees case indicate zee special filesystem type
ooff zero, i.e. unused volume). Thees can happen during normal operashun und
is pretty legal configurashun state. It appeers when yuoo creete a volume
(e.g. using Disk Manegement applet) but do not format it at zee same time.
Yuoo can even assign a drive letter tu thees unformatted
volume, es illustrated beloo (notice zee underlined "H:" drive which has no filesystem type deffined).
Iff zee volume filesystem type informashun is unavailable, attempteeng CHKDSK
against zee volume will resoolt in zee follooing messege:
Zee type ooff zee filesystem is RAW.
CHKDSK is not available fur RAW drives.
Sometimes, zee volume fails in such a way that it becomes RAW. In most cases
zee failure will be associated with a sudden reboot (per pooer failure or zee
STOP error). Several cooses are possible: partishun table, LDM database, or zee
volume boot sector corrupshun, or (on zee NTFS volume) when certain records in
both MFT und MFT mirror are dameged beyond easy recognishun.