Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows VistaWindows XPWindows MeWindows 98Windows 95Virtual PCInternet ExplorerOutlook ExpressWindows MediaSecurity
Related Topics
MS Server ProductsMS OfficePC HardwareMore Topics ...

Windows Forum / Windows 98 / Disks / File System / June 2004

Tip: Looking for answers? Try searching our database.

Consequences of "error in FSInfoSector" reported by Scandisk?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Chris Spencer - 09 Jun 2004 19:09 GMT
When I run Scandisk on my Win98SE system, I often see a message that a
FSInfoSector error was found and repaired.  I suspect this is due to
occassional power failures (out of my control) that result in an
uncontrolled PC shutdown.  My question is, what are the WORST possible
consequences of this situation?

Is it technically possible to lose data from file(s) that were NOT
being written to at the time of shutdown?  Such as Windows system
files?

Is it technically possible that files created after this error occurs
would be cross-linked, resulting in unrecoverable data loss?

I know that skipping the Windows shutdown is not recommended, but
please no hyperbolic "your computer will explode" answers.  Thanks,

- Chris
Jeff Richards - 10 Jun 2004 00:46 GMT
It is quite possible for a power failure to create an error in any part of
the disk. For instance, if the FAT is being updated at the moment of
shutdown then a whole sector of FAT data, involving many files, can be
corrupted. In the wort case, power failures can damage hardware, as they are
often accompanied by spikes or brownouts. The typical PC power supply is
actually very good at filtering these effects, but it can happen that
components are damaged.

It is unlikely that anything other than open files (or such items as the
FSInfoSector) will be affected by switching the machine off, provided there
is no active disk process occurring at the time. Note that any open file,
not just a file currently being written to, is at risk.  Note also that
different file types have different risks - a simple text file being
processed in a text editor is probably unaffected by an illegal shutdown,
while a database file can be corrupted beyond repair.

A cross-linked file is usually a symptom of data loss, not a cause - data
from one file has been written over the top of another file. The error
becomes visible when the FAT checking reveals the cross linking.  It occurs
because of an error in the FAT, where a sector that is in use is processed
as if it were free, and is allocated to a new file. The data from the latest
file to use the sector is usually recoverable, while the previous data has
been overwritten and lost.  Cross linking should not occur if the FAT is
repaired on the next start-up following an illegal shutdown, but of course
the data may have already been lost..
Signature

Jeff Richards
MS MVP (DTS)

> When I run Scandisk on my Win98SE system, I often see a message that a
> FSInfoSector error was found and repaired.  I suspect this is due to
[quoted text clipped - 13 lines]
>
> - Chris
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.