I have a question about Prevent 
file corruption problems:


I have tried running the "new" CHKDSK under Windows XP using both the Error Checking 
tool in "My Computer/File/Properties" and from the command line.

When I used the Error Checking tool (without selecting the Automatic fix of file 
system errors or the scan for bad sectors) XP displayed a dialogue with a sequence 
of messages, telling me that the Error Checker was performing phase 1 of its check, 
then phases 2 and 3 and finally a new dialogue appeared telling me that the check 
had been completed - and nothing more.

When I ran CHKDSK from the command prompt, using the command "CHKDSK C: /V" the output 
was more informative:

"The type of the file system is NTFS.

WARNING!  F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
File verification completed.
CHKDSK is verifying indexes (stage 2 of 3)...
Index verification completed.
Detected minor inconsistencies on the drive.
CHKDSK is verifying security descriptors (stage 3 of 3)
Cleaning up 33 unused index entries from index
Cleaning up 33 unused index entries from index
Cleaning up 33 unused security descriptors.
Security descriptor verification completed.
CHKDSK is verifying Usn Journal...
Usn Journal verification completed.
Correcting errors in the Volume Bitmap.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct"

My question is, which should I trust - the Error Checking tool (which I assume invokes 
CHKDSK in the background) or the command line? Or perhaps a third party program?

Tip: Run a free scan for common Windows errors ad

re: Question about 'Prevent file corruption problems' Tuesday, October 22, 2002 at 8:10 am Posted by Mike (1 messages posted) Paul: I'm amazed that I have not seen more messages like yours on the Web! For the last several months on both of my machines I have experienced problems similar to yours with my Windows XP Pro boot drives that are formatted with the NTFS file system. If you're interested I suggest you read Microsoft Knowledge Base Article Q315688. I'm not endorsing the article per se, however you may want to note their brief paragraph toward the end of the article, which is titled "NTFS File System Corruption". It is indicative of the kind of problems I have experienced running Chkdsk from the command prompt. I could go on and on, but I will make only a couple of more points. One, if you call Microsoft, the techs will probably tell you to load Recovery Console (if you haven't already; it is not installed by default) in order to correct the Chkdsk reporting errors. My experience is that as soon as you think you accomplished something with it (using Chkdsk with the "p" and "r" switches), the problem comes right back. This is not to suggest that Recovery Console in and of itself is not a good thing. In fact as I write this I am seriously comtemplating using it to reformat my boot drives with FAT32. The last comment I want to make is that I have recently discovered that in excess of 20% of my boot drive usage (as reported by various disk utilities) cannot be accounted for (yes, after making adjustments for page and hibernation files). And, in contradistinction to the KB article referred to above (note the references to "misreporting of disk space allocation"), my folder/file sizes compared to "size on disk" is relatively tight. So who knows what's going on? Thanks for providing an outlet for my frustration. Later, Mike On Friday, October 4, 2002 at 10:02 pm, Paul wrote: >I have a question about Prevent >file corruption problems: > >I have tried running the "new" CHKDSK under Windows XP using both the Error Checking >tool in "My Computer/File/Properties" and from the command line. > >When I used the Error Checking tool (without selecting the Automatic fix of file >system errors or the scan for bad sectors) XP displayed a dialogue with a sequence >of messages, telling me that the Error Checker was performing phase 1 of its check, >then phases 2 and 3 and finally a new dialogue appeared telling me that the check >had been completed - and nothing more. > >When I ran CHKDSK from the command prompt, using the command "CHKDSK C: /V" the output >was more informative: > >"The type of the file system is NTFS. > >WARNING! F parameter not specified. >Running CHKDSK in read-only mode. > >CHKDSK is verifying files (stage 1 of 3)... >File verification completed. >CHKDSK is verifying indexes (stage 2 of 3)... >Index verification completed. >Detected minor inconsistencies on the drive. >CHKDSK is verifying security descriptors (stage 3 of 3) >Cleaning up 33 unused index entries from index >Cleaning up 33 unused index entries from index >Cleaning up 33 unused security descriptors. >Security descriptor verification completed. >CHKDSK is verifying Usn Journal... >Usn Journal verification completed. >Correcting errors in the Volume Bitmap. >Windows found problems with the file system. >Run CHKDSK with the /F (fix) option to correct" > >My question is, which should I trust - the Error Checking tool (which I assume invokes >CHKDSK in the background) or the command line? Or perhaps a third party program? [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Thursday, October 24, 2002 at 3:43 am Posted by Paul (6 messages posted) Mike, Thanks for the tip on Recovery Console. Glad that I could be of help in providing an outlet for your frustration ;). Paul [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Friday, November 15, 2002 at 2:06 am Posted by Tom (38 messages posted) huhuhu... AFAIK... in Windows 2000 occurs the same problem :'( On Friday, October 4, 2002 at 10:02 pm, Paul wrote: >I have a question about Prevent >file corruption problems: > >I have tried running the "new" CHKDSK under Windows XP using both the Error Checking >tool in "My Computer/File/Properties" and from the command line. > >When I used the Error Checking tool (without selecting the Automatic fix of file >system errors or the scan for bad sectors) XP displayed a dialogue with a sequence >of messages, telling me that the Error Checker was performing phase 1 of its check, >then phases 2 and 3 and finally a new dialogue appeared telling me that the check >had been completed - and nothing more. > >When I ran CHKDSK from the command prompt, using the command "CHKDSK C: /V" the output >was more informative: > >"The type of the file system is NTFS. > >WARNING! F parameter not specified. >Running CHKDSK in read-only mode. > >CHKDSK is verifying files (stage 1 of 3)... >File verification completed. >CHKDSK is verifying indexes (stage 2 of 3)... >Index verification completed. >Detected minor inconsistencies on the drive. >CHKDSK is verifying security descriptors (stage 3 of 3) >Cleaning up 33 unused index entries from index >Cleaning up 33 unused index entries from index >Cleaning up 33 unused security descriptors. >Security descriptor verification completed. >CHKDSK is verifying Usn Journal... >Usn Journal verification completed. >Correcting errors in the Volume Bitmap. >Windows found problems with the file system. >Run CHKDSK with the /F (fix) option to correct" > >My question is, which should I trust - the Error Checking tool (which I assume invokes >CHKDSK in the background) or the command line? Or perhaps a third party program? [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Wednesday, November 27, 2002 at 9:53 am Posted by rainmanp7 (2 messages posted) I got the best one of all and i do know what is going on...... but will they ever fix it who knows? First off it has somthing to do with not cleaning up after itself and it does have to do with windows such as shutting down and other file movement Explorer.exe has some serious problems the faster you computer is the qicker you see these problems and the faster you use it the MORE Problems you will see...... i push my system to the limit 24/7 and see all kinds of errors left and right even with all the updates installed like all of a sudden a folder is in use because somthing in windows forgot to release it "It's lock on the folder and when you reboot while the folder is locked it will do somthing to the volume bitmap" index curruption Etc. that is just one of the things amongst many others But here is the wild thing run chkdsk and then wait a bit work on the system doing stuff give it about 1/2 hour of doing stuff and or 15 minutes and Wham it's back again with errors it has to do with file movement but the worst is you have poc health running all the time and when stuff doesn't work right and you see no errors give it another 15 minutews of working on it and you run chkdsk at the cmd prompt and WHAM back again.............. and yes over time it does degrade! but when you reboot you see no errors getting fixed because of NTFS saved it self when it booted up by going to another somthing that does not have the error present. sorry i can't help any further but yup i did test .Net and i did see the same problem with it but it corrects it self WICKED FAST and it does cure itself of stupid ass errors...... [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Thursday, November 28, 2002 at 10:24 am Posted by John Blackmore (3 messages posted) Paul Did you ever get a solution ? I have exactly the same expereince. If I install Xp using FAT 32 then there is no problem. If I install Xp as NTFS then XHDSK reports errors. If I convert from FAT32 to NTFS then the problem goes away . Microsoft say that a Disk converted to NTFS from FAT is not the same as a drive formated as NTFS. On Friday, October 4, 2002 at 10:02 pm, Paul wrote: >I have a question about Prevent >file corruption problems: > >I have tried running the "new" CHKDSK under Windows XP using both the Error Checking >tool in "My Computer/File/Properties" and from the command line. > >When I used the Error Checking tool (without selecting the Automatic fix of file >system errors or the scan for bad sectors) XP displayed a dialogue with a sequence >of messages, telling me that the Error Checker was performing phase 1 of its check, >then phases 2 and 3 and finally a new dialogue appeared telling me that the check >had been completed - and nothing more. > >When I ran CHKDSK from the command prompt, using the command "CHKDSK C: /V" the output >was more informative: > >"The type of the file system is NTFS. > >WARNING! F parameter not specified. >Running CHKDSK in read-only mode. > >CHKDSK is verifying files (stage 1 of 3)... >File verification completed. >CHKDSK is verifying indexes (stage 2 of 3)... >Index verification completed. >Detected minor inconsistencies on the drive. >CHKDSK is verifying security descriptors (stage 3 of 3) >Cleaning up 33 unused index entries from index >Cleaning up 33 unused index entries from index >Cleaning up 33 unused security descriptors. >Security descriptor verification completed. >CHKDSK is verifying Usn Journal... >Usn Journal verification completed. >Correcting errors in the Volume Bitmap. >Windows found problems with the file system. >Run CHKDSK with the /F (fix) option to correct" > >My question is, which should I trust - the Error Checking tool (which I assume invokes >CHKDSK in the background) or the command line? Or perhaps a third party program? [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Thursday, November 28, 2002 at 11:45 pm Posted by Paul (6 messages posted) No solution yet John. On Thursday, November 28, 2002 at 10:24 am, John Blackmore wrote: >Paul > >Did you ever get a solution ? I have exactly the same expereince. > >If I install Xp using FAT 32 then there is no problem. >If I install Xp as NTFS then XHDSK reports errors. > >If I convert from FAT32 to NTFS then the problem goes away . Microsoft say that >a Disk converted to NTFS from FAT is not the same as a drive formated as NTFS. > > > > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Saturday, November 30, 2002 at 10:25 am Posted by John Blackmore (3 messages posted) Paul How are you running CHKDSK ? In windows 2000 if you go to the C prompt you get C:\ > and you then type CHKDSK -- no errors reported unless you type CHKDSK /v when minor issues are reported - which are not a problem. With Windows Xp pro whn I go to the C prompt it starts C:\> Documents and settings\John> if I type CHKDSK I get errors. If, howeber, I type CD\ first and go back to just C:\> and type CHKDSK I get no errors (so far). I have set up a second partition for data ( E:) and this has shown no errors at all. I looks like CHKDSK is somewhat suspect. Also of you type CHKNTFS C: what answer do you get. If there are no problems you should get C: is not dirty John On Thursday, November 28, 2002 at 11:45 pm, Paul wrote: > >No solution yet John. > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Tuesday, December 10, 2002 at 2:44 am Posted by Ken (4 messages posted) Oh my god! I knew it! The constant corruption wasn't just my computer! What suprise me most of all is why isn't there more news about this over the internet. After running chkdsk /f, then doing some task, the same error would report again! My computer doesn't crash often or at all and I usually shut it down through XP. Can someone tell me if it truly corrupts my files or just a reporting error? I have lots of important files on my computer and I rather not take the chance of it being corrupted. [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Monday, December 16, 2002 at 9:15 am Posted by Michael Lees (2 messages posted) Hi all, Phew am I glad I found this thread! My problems started a few weeks back after buying a new computer with new HD. I installed XP and everything seemed to be okay. That was until one day, while XP was booting I switched my USB (music) keyboard on. All of a sudden UNMOUNTABLE_VOLUME was displayed and XP wouldn't load. So I used the CD to load the recovery console and ran chkdsk, XP booted and I thought everything was okay. Once XP loaded I ran chkdsk and it was reporting bad sectors on the drive! I assumed I'd been given a bad HD by maxtor so I went to their website to return the drive. Maxtor have a piece of software called powermax which you can download. They use it to certify their drives and remove bad sectors after construction. I downloaded this and performed a low-level format and certified the drive. It was coming up okay? So I re-installed XP, while XP was formating the drive (NTFS) it complained saying the partition was too small. When I looked XP had partitioned my drive in two, an 8Meg partition and a 40Gig partition? I have no idea why this happened but I installed XP on the 40 Gig partition and everything seemed okay. Now ultra-paranoid of my drive I found myself running chkdsk every 10 minutes. I grew even more concerned when the drive was constantly indicating minor errors, I assumed it was some indication that a major error was about to happen? However upon further inspection I realised the error reporting was completely inconsistent! I'd run chkdsk in the command prompt window (read-only mode) and it would report errors suggesting I re-run chkdsk with /f option. However if I then ran chkdsk again immediately afterwards (without the /f option) still in the command prompt, chkdsk would report no problems? Obviously the error can't have been fixed if chkdsk was in read-only mode so obviously the error wasn't ever there? After further investigation I've realised chkdsk seems to report spurious errors about the volume bitmap? What the hell is going on?? Perhaps the reason there isn't more news on this is people never run chkdsk manually, they rely on XP to check for drive inconsistencies on booting? On Tuesday, December 10, 2002 at 2:44 am, Ken Do wrote: >Oh my god! I knew it! The constant corruption wasn't just my computer! What suprise >me most of all is why isn't there more news about this over the internet. After running >chkdsk /f, then doing some task, the same error would report again! My computer doesn't >crash often or at all and I usually shut it down through XP. > >Can someone tell me if it truly corrupts my files or just a reporting error? I have >lots of important files on my computer and I rather not take the chance of it being >corrupted. [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Monday, December 16, 2002 at 9:41 am Posted by Michael Lees (2 messages posted) Just found this, :) http://www.webspiffy.com/archives/2002/08/ntfs_file_system_glitch.php On Monday, December 16, 2002 at 9:15 am, Michael Lees wrote: > >Hi all, > >Phew am I glad I found this thread! My problems started a few weeks back after buying >a new computer with new HD. I installed XP and everything seemed to be okay. That >was until one day, while XP was booting I switched my USB (music) keyboard on. All >of a sudden UNMOUNTABLE_VOLUME was displayed and XP wouldn't load. So I used the >CD to load the recovery console and ran chkdsk, XP booted and I thought everything >was okay. Once XP loaded I ran chkdsk and it was reporting bad sectors on the drive! >I assumed I'd been given a bad HD by maxtor so I went to their website to return >the drive. Maxtor have a piece of software called powermax which you can download. >They use it to certify their drives and remove bad sectors after construction. >I downloaded this and performed a low-level format and certified the drive. It was >coming up okay? So I re-installed XP, while XP was formating the drive (NTFS) it >complained saying the partition was too small. When I looked XP had partitioned my >drive in two, an 8Meg partition and a 40Gig partition? I have no idea why this happened >but I installed XP on the 40 Gig partition and everything seemed okay. Now ultra-paranoid >of my drive I found myself running chkdsk every 10 minutes. I grew even more concerned >when the drive was constantly indicating minor errors, I assumed it was some indication >that a major error was about to happen? However upon further inspection I realised >the error reporting was completely inconsistent! I'd run chkdsk in the command prompt >window (read-only mode) and it would report errors suggesting I re-run chkdsk with >/f option. However if I then ran chkdsk again immediately afterwards (without the >/f option) still in the command prompt, chkdsk would report no problems? Obviously >the error can't have been fixed if chkdsk was in read-only mode so obviously the >error wasn't ever there? > >After further investigation I've realised chkdsk seems to report spurious errors >about the volume bitmap? What the hell is going on?? Perhaps the reason there isn't >more news on this is people never run chkdsk manually, they rely on XP to check for >drive inconsistencies on booting? > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Monday, December 16, 2002 at 1:43 pm Posted by Ken (4 messages posted) Yeah, I get paranoid too and run check a lot. This solution might not be solve your problem, but it helped me a bit. So far I did not notice any file corruption when I move files between drive or while downloading. In the bios, disable IDE Block Mode and IDE Prefetch (if you have any). It disable 32bit access since XP probably has problem with it. It is a MS documented bug in Windows NT NTFS which apparently was *supposed* to be fix, but it seems that it still exist in XP as well. I hope that helps you, it helped me somewhat. [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Tuesday, December 24, 2002 at 5:31 am Posted by Dan (1 messages posted) I see this as well (the problem)....It's quite annoying and I actually bought a new a drive, thinking my drive was at fault (glad I saw this thread, as I was GOING to buy a new motherboard....I HATE this problem...seems to me like my hard drive slows down and starts *clicking*....).....But anyway...thanks for the info, now I'll start bitching at Microdunces.....err...soft.. Dan On Monday, December 16, 2002 at 1:43 pm, Ken wrote: >Yeah, I get paranoid too and run check a lot. This solution might not be solve your >problem, but it helped me a bit. So far I did not notice any file corruption when >I move files between drive or while downloading. In the bios, disable IDE Block Mode >and IDE Prefetch (if you have any). It disable 32bit access since XP probably has >problem with it. It is a MS documented bug in Windows NT NTFS which apparently was >*supposed* to be fix, but it seems that it still exist in XP as well. I hope that >helps you, it helped me somewhat. [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Saturday, January 4, 2003 at 9:47 am Posted by Peter Shkabara (6 messages posted) I just found this thread and I too am glad to hear that I am not alone. My new system uses an Intel motherboard with SATA RAID - I thought that the problem was due to the RAID controller, but your descriptions match mine too well. The answer as to corruption, unfortunately, is YES - I expereienced actual corruption of the disk and had to fix it before the comptuer would boot. Fotunately, CHKDSK seems to be enough to fix it. I seem to have isolated true corruption as occuring only during shutdown. To avoid this corruption, I started to turn off the power without doing a Windows shutdown - I know that this is exactly opposite of what Microsoft tells us to do, but it seems to work for me. Any comments and experiences from other folks would be appreciated. For reference, I am running XP Pro with SP1. The hard disk is SATA RAID (Silicon Image 3112r) with two WD800JB drives partitioned as a stripe set (RAID 0) and a single NTFS partition of 149GB. On Tuesday, December 10, 2002 at 2:44 am, Ken Do wrote: >Oh my god! I knew it! The constant corruption wasn't just my computer! What suprise >me most of all is why isn't there more news about this over the internet. After running >chkdsk /f, then doing some task, the same error would report again! My computer doesn't >crash often or at all and I usually shut it down through XP. > >Can someone tell me if it truly corrupts my files or just a reporting error? I have >lots of important files on my computer and I rather not take the chance of it being >corrupted. [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Sunday, January 5, 2003 at 5:18 pm Posted by Robot (1 messages posted) I've been watching strains in several places about this topic. The one thing that I have noticed, that it is always NTFS that is the problem. That is the only common factor in many cases. This leads me to believe that NTFS IS SCREWED UP!!! Go for FAT32 every time you get the chance. If XP won't format FAT32, then get a win98 boot disk and do it yourself. The win98 boot disk is the only piece of software that microsoft ever wrote without errors. fdisk and format.com are the only partition/format programs that I ever use, because they are the only ones that ever work. Anything else that tries to format FAT32 always screws it up and I have to go back and do it again with format.com. sigh. On Saturday, January 4, 2003 at 9:47 am, Peter Shkabara wrote: >I just found this thread and I too am glad to hear that I am not alone. My new system >uses an Intel motherboard with SATA RAID - I thought that the problem was due to >the RAID controller, but your descriptions match mine too well. The answer as to >corruption, unfortunately, is YES - I expereienced actual corruption of the disk >and had to fix it before the comptuer would boot. Fotunately, CHKDSK seems to be >enough to fix it. I seem to have isolated true corruption as occuring only during >shutdown. To avoid this corruption, I started to turn off the power without doing >a Windows shutdown - I know that this is exactly opposite of what Microsoft tells >us to do, but it seems to work for me. Any comments and experiences from other folks >would be appreciated. For reference, I am running XP Pro with SP1. The hard disk >is SATA RAID (Silicon Image 3112r) with two WD800JB drives partitioned as a stripe >set (RAID 0) and a single NTFS partition of 149GB. > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Sunday, January 5, 2003 at 7:33 pm Posted by Peter Shkabara (6 messages posted) I don't think that NTFS per se is to blame. I ran it on NT 3.1 through NT 3.51 and never had any problems. From other forums I have been to, it seems that Win2k and XP have introduced a change in NTFS that indeed has a problem. Some users say that if you format to FAT32 and then convert to NTFS the problem goes away - but the NTFS done that way is different from formatting using XP directly. I have not tried it yet, but am tempted to do so since my computer keeps getting corrupted - unless I don't use shutdown! On Sunday, January 5, 2003 at 5:18 pm, Robot wrote: >I've been watching strains in several places about this topic. The one thing that >I have noticed, that it is always NTFS that is the problem. That is the only common >factor in many cases. This leads me to believe that NTFS IS SCREWED UP!!! Go for >FAT32 every time you get the chance. If XP won't format FAT32, then get a win98 >boot disk and do it yourself. The win98 boot disk is the only piece of software >that microsoft ever wrote without errors. fdisk and format.com are the only partition/format >programs that I ever use, because they are the only ones that ever work. Anything >else that tries to format FAT32 always screws it up and I have to go back and do >it again with format.com. sigh. > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Monday, January 6, 2003 at 12:44 pm Posted by Randy J. Anderson (1 messages posted) Warning, Chkdsk errors are occuring high chances are because you are running Chkdsk with open files. The accurate reporting can only be done when running Chkdsk during bootup mode (when not using Windows and Chkdsk runs *before* the Windows desktop loads). Chkdsk often *will* report an error if the hard disk drive has open files. On Sunday, January 5, 2003 at 7:33 pm, Peter Shkabara wrote: >I don't think that NTFS per se is to blame. I ran it on NT 3.1 through NT 3.51 and >never had any problems. From other forums I have been to, it seems that Win2k and >XP have introduced a change in NTFS that indeed has a problem. Some users say that >if you format to FAT32 and then convert to NTFS the problem goes away - but the NTFS >done that way is different from formatting using XP directly. I have not tried it >yet, but am tempted to do so since my computer keeps getting corrupted - unless I >don't use shutdown! > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Tuesday, January 7, 2003 at 10:23 am Posted by Michael Kraft (1 messages posted) Randy is correct. See http://support.microsoft.com/?kbid=109524 Even though it doesn't say so it also applies to XP. Also if any program writes to the drive while Chkdsk is running, chkdsk mayl report more severe errors as it will think the index has become corrupted. There was an old MSKB article about this, but its been removed: Microsoft Knowledge Base Article: 246882 - If you run the Chkdsk.exe tool with no command-line switches against a Windows NT file system (NTFS) volume, Chkdsk.exe may report that problems were found, and suggest that you run the Chkdsk command with the /f switch to fix the volume. This is why you can run chkdsk multiple times and sometimes it will report errors and sometimes it will not. If you run chkdsk /v /f and it comes back with no errors than your disk is fine. You can also run chkntfs to see if Windows believes there is a problem with the drive. On Monday, January 6, 2003 at 12:44 pm, Randy J. Anderson wrote: >Warning, Chkdsk errors are occuring high chances are because you are running Chkdsk >with open files. The accurate reporting can only be done when running Chkdsk during >bootup mode (when not using Windows and Chkdsk runs *before* the Windows desktop >loads). Chkdsk often *will* report an error if the >hard disk drive has open files. > > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Monday, January 27, 2003 at 9:26 pm Posted by Kass (2 messages posted) I just want to say that I am in the same boat as Peter. I apparently made the mistake of installing XP Pro on a NTFS formatted partition. My XP Pro SP1 runs fine, but corrupts files regularly *only* upon shutdown or reboots. I am running an AMD XP 2100+, gigabyte motherboard, maxtor 60 GB, samsung PC2700 256 MB, latest bios, chipset drivers etc. I am now afraid to shutdown or reboot, good tip peter to shut down by powering off!! ;-) I'll have to try that as I am sick of having to enter the recovery console to salvage the registry and then using system restore in safe mode. I can't believe MS isn't aware of this problem with their shutdowns.. FWIW, I am convinced this is a software issue as I have checked my hard drive for surface errors using a Maxtor utility and I have also checked my RAM. On Saturday, January 4, 2003 at 9:47 am, Peter Shkabara wrote: >I just found this thread and I too am glad to hear that I am not alone. My new system >uses an Intel motherboard with SATA RAID - I thought that the problem was due to >the RAID controller, but your descriptions match mine too well. The answer as to >corruption, unfortunately, is YES - I expereienced actual corruption of the disk >and had to fix it before the comptuer would boot. Fotunately, CHKDSK seems to be >enough to fix it. I seem to have isolated true corruption as occuring only during >shutdown. To avoid this corruption, I started to turn off the power without doing >a Windows shutdown - I know that this is exactly opposite of what Microsoft tells >us to do, but it seems to work for me. Any comments and experiences from other folks >would be appreciated. For reference, I am running XP Pro with SP1. The hard disk >is SATA RAID (Silicon Image 3112r) with two WD800JB drives partitioned as a stripe >set (RAID 0) and a single NTFS partition of 149GB. > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Monday, January 27, 2003 at 9:46 pm Posted by Kass (2 messages posted) Still trying to resolve this issue...I recently came across Q315403 Could this be related to our problem??? Known problem with NTFS with IDE drive cache...supposed to be fixed in SP1, but maybe they didn't properly patch it. I noticed that I have always had my write cache enabled of course for performance...I've tried disabling it and so far 2 for 2 on shutdowns...but who knows if this is the issue..time will tell.. [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Tuesday, January 28, 2003 at 8:09 am Posted by Peter Shkabara (6 messages posted) I now have my system under control and can share some of what I learned with this forum. To prevent corruption on my system, I changed my computer type form ACPI to Standard PC. When I shut down, XP stops and tells me "It is safe ...". No more corruptions! Regarding CHKDSK - if CHKDSK is run agains the boot drive, it will report errors because some files are open. Need to run it with /f so it is done at startup. Also - very strange - certain $I30 errors are "normal" according to Microsoft and only indicate "housekeeping" tasks that CHKDSK does. Apparently there is no real corruption in the directory. The corruption I expereienced on shutdown, however, was not limited to these "expected" errors and actually damaged directory structure entries. Microsoft needs to add more delay before turning power off on ACPI systems - there was such a problem with Win98 I believe. On my own system, the RAID driver on the SATA drives does not allow me to turn off write cache, so that is not an option for me. I there a way to send such bug reports to Microsoft? There are a number of us that are seeing this problem, but I know of no way to report it to the big company. [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Thursday, February 27, 2003 at 8:26 am Posted by fran (5 messages posted) Just so you know, I went to my hard drive manufacturer site and most of them have a download that you put on a floppy and boot with it and IT will put your hard drive through 5 or 6 checks of integrity and fix errors OR tell you if your drive is really bad..... Found errors that MS did NOT find and fixed them.....and does it all in dos so doesn't screw up your windows..... On Friday, October 4, 2002 at 10:02 pm, Paul wrote: >I have a question about Prevent >file corruption problems: > >I have tried running the "new" CHKDSK under Windows XP using both the Error Checking >tool in "My Computer/File/Properties" and from the command line. > >When I used the Error Checking tool (without selecting the Automatic fix of file >system errors or the scan for bad sectors) XP displayed a dialogue with a sequence >of messages, telling me that the Error Checker was performing phase 1 of its check, >then phases 2 and 3 and finally a new dialogue appeared telling me that the check >had been completed - and nothing more. > >When I ran CHKDSK from the command prompt, using the command "CHKDSK C: /V" the output >was more informative: > >"The type of the file system is NTFS. > >WARNING! F parameter not specified. >Running CHKDSK in read-only mode. > >CHKDSK is verifying files (stage 1 of 3)... >File verification completed. >CHKDSK is verifying indexes (stage 2 of 3)... >Index verification completed. >Detected minor inconsistencies on the drive. >CHKDSK is verifying security descriptors (stage 3 of 3) >Cleaning up 33 unused index entries from index >Cleaning up 33 unused index entries from index >Cleaning up 33 unused security descriptors. >Security descriptor verification completed. >CHKDSK is verifying Usn Journal... >Usn Journal verification completed. >Correcting errors in the Volume Bitmap. >Windows found problems with the file system. >Run CHKDSK with the /F (fix) option to correct" > >My question is, which should I trust - the Error Checking tool (which I assume invokes >CHKDSK in the background) or the command line? Or perhaps a third party program? [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Sunday, March 16, 2003 at 9:29 pm Posted by Allan (1 messages posted) I don't remember where I read this but Winblows XP O/S doesn't like to be run on NTFS because ithat format makes it too difficult to handle files the way it was meant to, which is to say chaotically rather than nice and organized. I run XP pro on my FAT32 drive and other drives are NTFS formatted and I have no problems other than what's normal for Winblows. - allan On Thursday, February 27, 2003 at 8:26 am, fran wrote: >Just so you know, I went to my hard drive manufacturer site and most of them have >a download that you put on a floppy and boot with it and IT will put your hard drive >through 5 or 6 checks of integrity and fix errors OR tell you if your drive is really >bad..... Found errors that MS did NOT find and fixed them.....and does it all in >dos so doesn't screw up your windows..... > > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Monday, March 17, 2003 at 6:43 am Posted by fran (5 messages posted) Alan, that's interesting because all the 'geeks' say just the opposite.... that XP is basically a bloated windows 2000 which loves NTFS. All the literature I've read says that it runs best on NTFS - that's why I did it that way. I'd like to know where you saw that article. I have 2 hard drives... the other is FAT32 which holds my files and for ghosting. Interesting response though..... On Sunday, March 16, 2003 at 9:29 pm, Allan wrote: >I don't remember where I read this but Winblows XP O/S doesn't like to be run on >NTFS because ithat format makes it too difficult to handle files the way it was meant >to, which is to say chaotically rather than nice and organized. I run XP pro on >my FAT32 drive and other drives are NTFS formatted and I have no problems other than >what's normal for Winblows. > >- allan > > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Tuesday, March 25, 2003 at 10:12 am Posted by esmithz (1 messages posted) I'm assuming you only need to change the driver in system setup. If that is so then what driver file are you using for Standard PC? On Tuesday, January 28, 2003 at 8:09 am, Peter Shkabara wrote: >I now have my system under control and can share some of what I learned with this >forum. To prevent corruption on my system, I changed my computer type form ACPI to >Standard PC. When I shut down, XP stops and tells me "It is safe ...". No more corruptions! > >Regarding CHKDSK - if CHKDSK is run agains the boot drive, it will report errors >because some files are open. Need to run it with /f so it is done at startup. Also >- very strange - certain $I30 errors are "normal" according to Microsoft and only >indicate "housekeeping" tasks that CHKDSK does. Apparently there is no real corruption >in the directory. > >The corruption I expereienced on shutdown, however, was not limited to these "expected" >errors and actually damaged directory structure entries. Microsoft needs to add more >delay before turning power off on ACPI systems - there was such a problem with Win98 >I believe. On my own system, the RAID driver on the SATA drives does not allow me >to turn off write cache, so that is not an option for me. > >I there a way to send such bug reports to Microsoft? There are a number of us that >are seeing this problem, but I know of no way to report it to the big company. [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Tuesday, March 25, 2003 at 1:06 pm Posted by Peter Shkabara (6 messages posted) I solved the corruption on shutdown problem by setting my system to not use ACPI - that is, I told XP that I have a standard PC without power management (a lie!). What I would like to see, however, is to have Microsoft add a delay before turning power off when using ACPI. On Tuesday, March 25, 2003 at 10:12 am, esmithz wrote: >I'm assuming you only need to change the driver in system setup. If that is so then >what driver file are you using for Standard PC? > > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Wednesday, March 26, 2003 at 9:46 am Posted by ML (3 messages posted) One of the side effects I have found from this is that the file system systematically consumes the available harddrive space to the point where WindowsXP no longer functions. On my system it takes about 24-36 hours for Windows to report 4.5GB of free space as being in use, when in fact it is really not. A reboot will free up all the space again and then the process starts over. I did find this article at MS: How to Locate and Correct Disk Space Problems on NTFS Volumes in Windows XP, but it hasn't provided any viable solutions. http://support.microsoft.com/?kbid=315688 If anyone has a solution to these problems, please please post it! -Fred On Friday, October 4, 2002 at 10:02 pm, Paul wrote: >I have a question about Prevent >file corruption problems: > >I have tried running the "new" CHKDSK under Windows XP using both the Error Checking >tool in "My Computer/File/Properties" and from the command line. > >When I used the Error Checking tool (without selecting the Automatic fix of file >system errors or the scan for bad sectors) XP displayed a dialogue with a sequence >of messages, telling me that the Error Checker was performing phase 1 of its check, >then phases 2 and 3 and finally a new dialogue appeared telling me that the check >had been completed - and nothing more. > >When I ran CHKDSK from the command prompt, using the command "CHKDSK C: /V" the output >was more informative: > >"The type of the file system is NTFS. > >WARNING! F parameter not specified. >Running CHKDSK in read-only mode. > >CHKDSK is verifying files (stage 1 of 3)... >File verification completed. >CHKDSK is verifying indexes (stage 2 of 3)... >Index verification completed. >Detected minor inconsistencies on the drive. >CHKDSK is verifying security descriptors (stage 3 of 3) >Cleaning up 33 unused index entries from index >Cleaning up 33 unused index entries from index >Cleaning up 33 unused security descriptors. >Security descriptor verification completed. >CHKDSK is verifying Usn Journal... >Usn Journal verification completed. >Correcting errors in the Volume Bitmap. >Windows found problems with the file system. >Run CHKDSK with the /F (fix) option to correct" > >My question is, which should I trust - the Error Checking tool (which I assume invokes >CHKDSK in the background) or the command line? Or perhaps a third party program? [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Tuesday, April 1, 2003 at 6:48 am Posted by JJstecchino (1 messages posted) Very interesting thread. I also have a sil3112 sata raid controller with two wdigital 120gb 8mb cache in raid 0 with ntfs. I use a SATA to Parallel ATA converter for these drives. My boot drive is a wd 100gb 2 mb cache also witn ntfs connected as a master drive to the primary IDE controller. What is interesting is that I am not experiencing any file corruption on the boot drives but lots of errors on the SATA Raid. Fairly frequently I find corrupted and unusable files. This setup is almost unusable. The RAID setup worked well on initial setup so I was thinking the problem was with the raid controller or with the disks gone bad. The disks support SMART and smart reports them as healthy, so I was blaming the motherboard and the sil sata controller. I was about to return it. The problem is not on shutdown, it is file write, randomly some files are corrupted. From the initial setup I installed sp1 and the MS suggested patches. I am going to try FAT32 if it supports a large (240gb) drive or I am going to try to use XP software raid and see if it works better. Also the raid disks are 70% full and who knows if that matter (poor handling of large drives?) Any sugestion on the problem appreciated. On Sunday, January 5, 2003 at 7:33 pm, Peter Shkabara wrote: >I don't think that NTFS per se is to blame. I ran it on NT 3.1 through NT 3.51 and >never had any problems. From other forums I have been to, it seems that Win2k and >XP have introduced a change in NTFS that indeed has a problem. Some users say that >if you format to FAT32 and then convert to NTFS the problem goes away - but the NTFS >done that way is different from formatting using XP directly. I have not tried it >yet, but am tempted to do so since my computer keeps getting corrupted - unless I >don't use shutdown! > > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Tuesday, April 1, 2003 at 7:31 am Posted by Peter Shkabara (6 messages posted) I had tried NT RAID before with poor results - would be curious to see your experience if you try it. What adaptors are you useing for your drives? Mine are Iwill I2S, and the controller is built-in on my Intel D845PEBT2 motherboard. Since I disabled the ACPI shutdown, I have had no more corruption. Are you certain that your corruption is not occuring at shutdown? On Tuesday, April 1, 2003 at 6:48 am, JJstecchino wrote: >Very interesting thread. I also have a sil3112 sata raid controller with two wdigital >120gb 8mb cache in raid 0 with ntfs. I use a SATA to Parallel ATA converter for these >drives. My boot drive is a wd 100gb 2 mb cache also witn ntfs connected as a master >drive to the primary IDE controller. What is interesting is that I am not experiencing >any file corruption on the boot drives but lots of errors on the SATA Raid. Fairly >frequently I find corrupted and unusable files. This setup is almost unusable. The >RAID setup worked well on initial setup so I was thinking the problem was with the >raid controller or with the disks gone bad. The disks support SMART and smart reports >them as healthy, so I was blaming the motherboard and the sil sata controller. I >was about to return it. The problem is not on shutdown, it is file write, randomly >some files are corrupted. From the initial setup I installed sp1 and the MS suggested >patches. I am going to try FAT32 if it supports a large (240gb) drive or I am going >to try to use XP software raid and see if it works better. Also the raid disks are >70% full and who knows if that matter (poor handling of large drives?) Any sugestion >on the problem appreciated. > > > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Tuesday, April 1, 2003 at 4:23 pm Posted by bagtagsell (1 messages posted) I got this error that told me that I needed to run chkdsk on my hard drive. I tried to run the command but it wouldnt work the prompt immediately closed w/o any action. So I rebooted thinking I could do it on the command prompt mode, but when I restarted my computer the drive was nowhere to be found. It is however recognized in the bios, but XP doesnt see it. It has some great data that I dont want to lose. If anyone could help I would appreciate it [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Sunday, April 6, 2003 at 7:55 am Posted by Marcus (1 messages posted) I am no expert and don't know the answer to your problem speciifically but I am pretty certain (that is is SOUNDS like but might not be), based on your brief description, that your data is probably there but your boot.ini is missing or corrupted. If you can find a thread on how to repair/replace your boot.ini you should be OK. This happend to me once and ever since I keep a copy of my boot.ini file. Screwing around with boot.ini can make your HD unbootable but since it already is ... Good luck. On Tuesday, April 1, 2003 at 4:23 pm, bagtagsell wrote: >I got this error that told me that I needed to run chkdsk on my hard drive. I tried >to run the command but it wouldnt work the prompt immediately closed w/o any action. > So I rebooted thinking I could do it on the command prompt mode, but when I restarted >my computer the drive was nowhere to be found. It is however recognized in the bios, >but XP doesnt see it. It has some great data that I dont want to lose. If anyone >could help I would appreciate it [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Thursday, April 10, 2003 at 2:42 pm Posted by Antonio Giner (1 messages posted) It's incredible to find this thread! I was experiencing the same problems in Windows 2000, even worse cause the ntfs corruption often caused BSOD in my system. At first it's was difficult to find a relation among constant blue screens and ntfs corruption till I noticed that chkdsk eliminated them for the next 3-4 reboots. After that, ntfs went sick again with the sympthoms you described. I started to think about shutdown problems when I noticed that the hd red led was always still on when Windows performed the powerdown (seems it didn't wait for the hd to stop). Yesterday I found this holy thread that has confirmed my suspicions. Now I wish there was an easy way to disable the auto-powerdown feature and return to the old "It's safe to turn off your computer" screen. It's annoying to search the net to see that everyone has exactly the opposite problem (their auto-powerdown feature doesn't work and they want to enable it). I know I could possibly disable the ACPI from the BIOS setup and reinstall Windows 2000 to get a non-ACPI hal... but this method sucks. Hope that Microsoft adds that delay in SP4, will they? Thanks a lot, you have saved me from a horrible headache. Antonio On Tuesday, March 25, 2003 at 1:06 pm, Peter Shkabara wrote: >I solved the corruption on shutdown problem by setting my system to not use ACPI >- that is, I told XP that I have a standard PC without power management (a lie!). >What I would like to see, however, is to have Microsoft add a delay before turning >power off when using ACPI. > > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Friday, April 18, 2003 at 11:59 am Posted by Martin Kaminer (1 messages posted) I have been struggling with this too (it's like a recovery group -- Microsoft Victims Anonymous) and here's the latest -- CHKDSK runs every time on bootup (the abbreviated 3-step version that it decides to do on its own, not the longer 5-step version you get when you run it from the disk tools menu) and doesn't complete. It bombs in the middle and goes straight into boot. And it's like Groundhog Day -- because it never completes it tries to do it again every time it reboots. Everything seems to work OK once it boots but it's making me nervous as I have had all the file corruption problems described earlier in the thread. I downloaded the diag tool from Maxtor and it says everything is clean but I don't know what it checks vis-a-vis the filesystem (if anything). Has anyone else had problems with CHKDSK not completing? I guess everyone keeps asking this but what's the best third-party substitute for checking file system integrity? On Monday, January 27, 2003 at 9:26 pm, Kass wrote: >I just want to say that I am in the same boat as Peter. I apparently made the mistake >of installing XP Pro on a NTFS formatted partition. My XP Pro SP1 runs fine, but >corrupts files regularly *only* upon shutdown or reboots. I am running an AMD XP >2100+, gigabyte motherboard, maxtor 60 GB, samsung PC2700 256 MB, latest bios, chipset >drivers etc. I am now afraid to shutdown or reboot, good tip peter to shut down by >powering off!! ;-) I'll have to try that as I am sick of having to enter the recovery >console to salvage the registry and then using system restore in safe mode. I can't >believe MS isn't aware of this problem with their shutdowns.. FWIW, I am convinced >this is a software issue as I have checked my hard drive for surface errors using >a Maxtor utility and I have also checked my RAM. > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Thursday, April 24, 2003 at 1:46 am Posted by Geoff (191 messages posted) "Microdunces" ... that is so funny! On Tuesday, December 24, 2002 at 5:31 am, Dan wrote: >I see this as well (the problem)....It's quite annoying and I actually bought a new >a drive, thinking my drive was at fault (glad I saw this thread, as I was GOING to >buy a new motherboard....I HATE this problem...seems to me like my hard drive slows >down and starts *clicking*....).....But anyway...thanks for the info, now I'll start >bitching at Microdunces.....err...soft.. > >Dan > > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Thursday, April 24, 2003 at 2:04 am Posted by Geoff (191 messages posted) I have discovered my Windows XP (home edition) starting to break down as well. I would like to summarize what I have learned from the posts above. Please comment if I am on the right/wrong track with these. === 1st Suggestion === 1. Use Windows 98se to FAT32 format larger hard drives 2. Install Windows XP onto the FAT32 formatted hard drive 3. Ask Windows XP to convert my FAT32 to NTFS - or - 1. Install Windows 98se using FAT32 format for larger hard drives 2. Ask Windows 98se to convert the file system from FAT32 to NTFS 3. Install Windows XP onto the "converted" NTFS Note: I have long heard that NTFS is the preferred file system for Windows XP; however, after reading several posts I am no longer convinced of the best Windows XP installation solution. Please help me select from the following: 1. Fresh install of NTFS 2. Converted FAT32 to NTFS (using one of the suggestions above) 3. FAT32 only 4. NTFS partition for the Windows XP operating system and a separate FAT32 partition for the data files 5. FAT32 partition for the Windows XP operating system and a separate NTFS partition for the data files === 2nd Suggestion === Just power the computer off without using the standard automated Windows XP shut-down feature ... because the automated Windows XP shutdown either saves the "corruption / corrupted files and folders" or Windows-controlled ACPI does not wait long enough for the computer to save all it's important settings (ie. the hard drive will still be spinning as Windows XP automatically powers off everything) not giving enough time for a proper shut-down. Question ... how do you ask Windows XP to display the "Your computer is now safe to shut down" dialog without shutting down the computer automatically? === 3rd Suggestion === In slight opposition to what was suggested in the "2nd Suggestion" ... unplug/turn-off your computer without using the standard automated Windows XP shutdown so that you do not give Windows XP a chance to save "corruption / corrupted files and folders" to the deteriorating file system/hard drive. === 4th Suggestion === Apparently, CHKDSK will report errors of different kinds with each running of the application when files are currently open and in use (this includes Windows XP operating system files which will always be open and in use … so you will continue to see errors of different kinds as new files/applications are being run by windows all the time in the background). The work-around for this is to run CHKDSK only when rebooting your computer system. From what I have heard this can be done by: Right-click on the drive in question > Select “Properties” from the menu > Select the “Tools” tab > Under the “Error-checking” area select “Check Now…” > Select both “Automatically fix file system errors” and “Scan for and attempt recovery of bad sectors”. During this process, I have been told, the computer might let you know that it will need to continue running the CHKDSK operation when the computer reboots. === 5th Suggestion === Check you system’s files and folders using third-party CHKDSK software. Question … what is the best third-party substitute for checking the integrity of your file system? [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Saturday, May 3, 2003 at 8:45 am Posted by James (1 messages posted) On Windows XP home edition I use norton systmworks 2003, Disk Doctor and get the same problem. If I try to fix it computer freezes after first reboot on second reboot still shows the Usn Journal has errors but doesn't freeze etc On Friday, October 4, 2002 at 10:02 pm, Paul wrote: >I have a question about Prevent >file corruption problems: > >I have tried running the "new" CHKDSK under Windows XP using both the Error Checking >tool in "My Computer/File/Properties" and from the command line. > >When I used the Error Checking tool (without selecting the Automatic fix of file >system errors or the scan for bad sectors) XP displayed a dialogue with a sequence >of messages, telling me that the Error Checker was performing phase 1 of its check, >then phases 2 and 3 and finally a new dialogue appeared telling me that the check >had been completed - and nothing more. > >When I ran CHKDSK from the command prompt, using the command "CHKDSK C: /V" the output >was more informative: > >"The type of the file system is NTFS. > >WARNING! F parameter not specified. >Running CHKDSK in read-only mode. > >CHKDSK is verifying files (stage 1 of 3)... >File verification completed. >CHKDSK is verifying indexes (stage 2 of 3)... >Index verification completed. >Detected minor inconsistencies on the drive. >CHKDSK is verifying security descriptors (stage 3 of 3) >Cleaning up 33 unused index entries from index >Cleaning up 33 unused index entries from index >Cleaning up 33 unused security descriptors. >Security descriptor verification completed. >CHKDSK is verifying Usn Journal... >Usn Journal verification completed. >Correcting errors in the Volume Bitmap. >Windows found problems with the file system. >Run CHKDSK with the /F (fix) option to correct" > >My question is, which should I trust - the Error Checking tool (which I assume invokes >CHKDSK in the background) or the command line? Or perhaps a third party program? [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Tuesday, May 20, 2003 at 11:16 am Posted by Yusuf Abrahams (1 messages posted) I had the same problem, but managed to create a work around. try the following: 1. start XP in safe mode, do this by pressing f8 just before xp loads and select safe mode. 2. goto device manager, right click My Computer select properties click hardware and then Device Manager. 3. open "IDE ATA/ATAPI controlers. 4. duble click "Primary IDE Channel" 5. select "Advance Settings" tab. 6. Change "Transfer Mode" from "DMA" to "POI" on the hard drive that XP is loaded on, e.g. on my PC XP is loaded on "Device 0". 7. click "Ok", close all windows and restart XP. i'm still looking for the reason and mybe an answer as 2 y XP is doing this. On Monday, December 16, 2002 at 9:15 am, Michael Lees wrote: > >Hi all, > >Phew am I glad I found this thread! My problems started a few weeks back after buying >a new computer with new HD. I installed XP and everything seemed to be okay. That >was until one day, while XP was booting I switched my USB (music) keyboard on. All >of a sudden UNMOUNTABLE_VOLUME was displayed and XP wouldn't load. So I used the >CD to load the recovery console and ran chkdsk, XP booted and I thought everything >was okay. Once XP loaded I ran chkdsk and it was reporting bad sectors on the drive! >I assumed I'd been given a bad HD by maxtor so I went to their website to return >the drive. Maxtor have a piece of software called powermax which you can download. >They use it to certify their drives and remove bad sectors after construction. >I downloaded this and performed a low-level format and certified the drive. It was >coming up okay? So I re-installed XP, while XP was formating the drive (NTFS) it >complained saying the partition was too small. When I looked XP had partitioned my >drive in two, an 8Meg partition and a 40Gig partition? I have no idea why this happened >but I installed XP on the 40 Gig partition and everything seemed okay. Now ultra-paranoid >of my drive I found myself running chkdsk every 10 minutes. I grew even more concerned >when the drive was constantly indicating minor errors, I assumed it was some indication >that a major error was about to happen? However upon further inspection I realised >the error reporting was completely inconsistent! I'd run chkdsk in the command prompt >window (read-only mode) and it would report errors suggesting I re-run chkdsk with >/f option. However if I then ran chkdsk again immediately afterwards (without the >/f option) still in the command prompt, chkdsk would report no problems? Obviously >the error can't have been fixed if chkdsk was in read-only mode so obviously the >error wasn't ever there? > >After further investigation I've realised chkdsk seems to report spurious errors >about the volume bitmap? What the hell is going on?? Perhaps the reason there isn't >more news on this is people never run chkdsk manually, they rely on XP to check for >drive inconsistencies on booting? > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Tuesday, June 3, 2003 at 2:03 pm Posted by Paul (1 messages posted) Glad to know I'm not imagining it. Firstly - any way to recover the files. Secondly - any sign of a proper fix yet? Cheers Paul [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Friday, June 13, 2003 at 8:19 pm Posted by ChoGGi (809 messages posted) hehe i just found this thread too but the last message had been posted oct 2002 so it look like either fat32 or no acpi are the choices we have left :) On Tuesday, June 3, 2003 at 2:03 pm, Paul wrote: >Glad to know I'm not imagining it. > >Firstly - any way to recover the files. > >Secondly - any sign of a proper fix yet? > >Cheers > >Paul [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Wednesday, July 9, 2003 at 6:28 pm Posted by Keith (1 messages posted) Chkdsk errors – file system errors, problems with the volume bitmap, etc… Symptom: chkdsk /f will not fix the errors. My Solution: (It took me days to figure this out. HP could not provide a solution and I could not find one on the Windows website…. Use this solution at your own risk! Double click “My Computer” Right click on C: (local disk) and then select properties Uncheck the box at the bottom where it says allow indexing service to index this disk… Select apply or OK…if you have any errors while the drive is un-indexing select ignore all. Go back to “My Computer” and select C: (local disk) properties again, then select the tools tab. Select “Check Now” and the check the box that says automatically fix file system errors. The computer will prompt you to reboot. Reboot the computer…let the checkdisk run and then go back to “My computer” C: (local disk) properties and check the box (so it’s selected to re-index) to allow indexing service to index this disk…. Select ignore all errors Run chkdsk again and it should be clean! You may have to do this again after running widows updates or adding programs! On Friday, October 4, 2002 at 10:02 pm, Paul wrote: >I have a question about Prevent >file corruption problems: > >I have tried running the "new" CHKDSK under Windows XP using both the Error Checking >tool in "My Computer/File/Properties" and from the command line. > >When I used the Error Checking tool (without selecting the Automatic fix of file >system errors or the scan for bad sectors) XP displayed a dialogue with a sequence >of messages, telling me that the Error Checker was performing phase 1 of its check, >then phases 2 and 3 and finally a new dialogue appeared telling me that the check >had been completed - and nothing more. > >When I ran CHKDSK from the command prompt, using the command "CHKDSK C: /V" the output >was more informative: > >"The type of the file system is NTFS. > >WARNING! F parameter not specified. >Running CHKDSK in read-only mode. > >CHKDSK is verifying files (stage 1 of 3)... >File verification completed. >CHKDSK is verifying indexes (stage 2 of 3)... >Index verification completed. >Detected minor inconsistencies on the drive. >CHKDSK is verifying security descriptors (stage 3 of 3) >Cleaning up 33 unused index entries from index >Cleaning up 33 unused index entries from index >Cleaning up 33 unused security descriptors. >Security descriptor verification completed. >CHKDSK is verifying Usn Journal... >Usn Journal verification completed. >Correcting errors in the Volume Bitmap. >Windows found problems with the file system. >Run CHKDSK with the /F (fix) option to correct" > >My question is, which should I trust - the Error Checking tool (which I assume invokes >CHKDSK in the background) or the command line? Or perhaps a third party program? [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Thursday, July 10, 2003 at 6:36 pm Posted by Gordon (1 messages posted) You said: >Use this solution at your own risk! Well, I just discovered this forum. I, like many others, have had an XP for about a year now, Norton SoftWork (recently upgrading to 2003), etc etc and get those same errors showing up. What's the risk if I don't? On Wednesday, July 9, 2003 at 6:28 pm, Keith wrote: >Chkdsk errors – file system errors, problems with the volume bitmap, etc… > >Symptom: chkdsk /f will not fix the errors. > > >My Solution: (It took me days to figure this out. HP could not provide a solution >and I could not find one on the Windows website…. > >Use this solution at your own risk! > >Double click “My Computer” > >Right click on C: (local disk) and then select properties > >Uncheck the box at the bottom where it says allow indexing service to index this >disk… > >Select apply or OK…if you have any errors while the drive is un-indexing select ignore >all. > >Go back to “My Computer” and select C: (local disk) properties again, then select >the tools tab. > >Select “Check Now” and the check the box that says automatically fix file system >errors. > >The computer will prompt you to reboot. > >Reboot the computer…let the checkdisk run and then go back to “My computer” C: (local >disk) properties and check the box (so it’s selected to re-index) to allow indexing >service to index this disk…. > >Select ignore all errors > >Run chkdsk again and it should be clean! > > >You may have to do this again after running widows updates or adding programs! > > > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Thursday, July 17, 2003 at 11:55 am Posted by Cindi (1 messages posted) I also wonder what the risk is. I have been watching this thread for months while having this very same problem with a new Dell computer. Dell has had me reformat three times and they have replaced the hard drive twice due to these volume bitmap, MFT, and index errors. The only performance issue that I experience with these errors is that System Restore won't restore. I wish I could figure out how to prevent this? Cindi > > On Thursday, July 10, 2003 at 6:36 pm, Gordon wrote: >You said: > >Use this solution at your own risk! > . What's the risk if I don't? > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Saturday, July 26, 2003 at 9:48 pm Posted by Fernando Salas (2 messages posted) Hi, finally I see this problem in the net, I had it, in fact it made me go back to win2K, now I have a hunch after reading everithing I found about this, try disabling the indexing service(which what a coincidence runs only over NTFS filesystem) here a lik to how to do it, http://www.techaholic.net/support/xp-indexing.html I will get it a shot to see what happens, some of the posts was quite usefull and match my experience, for example I had XP installed in 2 machines, one of them was AT case with AT/ATX board, and the other ATX, the AT one never got corrupted(same XP on both) so seems that is consistency around the shutdown issue, I hope the indexing can get rid of the problem, if it does please post it, so we know it Fer On Thursday, July 17, 2003 at 11:55 am, Cindi wrote: >I also wonder what the risk is. > >I have been watching this thread for months while having this very same problem with >a new Dell computer. Dell has had me reformat three times and they have replaced >the hard drive twice due to these volume bitmap, MFT, and index errors. > >The only performance issue that I experience with these errors is that System Restore >won't restore. > >I wish I could figure out how to prevent this? > >Cindi > > > > > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Thursday, August 7, 2003 at 1:43 pm Posted by Bill (3 messages posted) Ahhh, I am yet another WinXP user realizing this problem. I've made posts at www.amdmb.com, www.mypcclinic.com, and in the MS Newsgroup. I'm glad to see I'm not alone. You can see the exact details I posted at: http://mypcclinic.com/forum/forum_posts.asp?TID=1301&PN=1&TPN=1 So far, not much in the way of responses. I'm seriously contemplating switching back to Fat32. I only did NTFS for the support of files > 4G. [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Thursday, August 7, 2003 at 2:26 pm Posted by Fernando Salas (2 messages posted) Well, Ive done what I said, disabling indexing, even deleted the index repository, and so far so good, no more strange behavior, so I think that is it, I recommend you should try it to confirm it Fernando On Thursday, August 7, 2003 at 1:43 pm, Bill wrote: >Ahhh, I am yet another WinXP user realizing this problem. I've made posts at www.amdmb.com, >www.mypcclinic.com, and in the MS Newsgroup. I'm glad to see I'm not alone. > >You can see the exact details I posted at: >http://mypcclinic.com/forum/forum_posts.asp?TID=1301&PN=1&TPN=1 > >So far, not much in the way of responses. I'm seriously contemplating switching >back to Fat32. I only did NTFS for the support of files > 4G. > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Tuesday, August 12, 2003 at 2:51 pm Posted by Bill (3 messages posted) So far so good. Fat32 is treating me like it should. [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Thursday, August 14, 2003 at 4:36 am Posted by Rui (1 messages posted) Hi, i recently bought a new pc (p4 2.8Ghz FSB 800Mhz) and since i installed winxp pro i've experienced lots of problems.i've got a S-ATA hdd (seagate barracuda 80Gb) connected on the 4th ide master.some times the system stops responding and a blue screen appears.Messages like: KERNEL_DATA_INPAGE_ERRROR atapi.sys address xxxxxx or Stop: xxxxx UNKNOWN HARD ERROR or UNMOUNTABLE_VOLUME or even KMODE_EXCEPTION_NOT_HANDLED were some of the blue screen errors i got. i've formated the disk "n" times, and i even installed win2000 to make sure it was winxp problem...no way of getting rid of this problem! when i used win2000 repair option and i got the following msg: "Setup has determined that drive c: is corrupted and cannot be repaired". I paid very attention to all these posts and i wonder if changing from NTFS to FAT32 will resolve this issue or if it's a hardware failure... i'd appreciate very much any help from you. Thank you very much, Rui Portugal [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Sunday, August 17, 2003 at 9:14 am Posted by VolTrdr (1 messages posted) Hi All, Thank you all for posting to this thread. I've been experiencing similar problems, though the corruption to my file system has been more fatal and has prevented me from using the system 95% of the time. I built the box in mid July. I'm running Win XP Pro on top of two Seagate 120GB SATA drives setup in a RAID-0 configuration with NTFS. I'm using the RAID controller built into the motherboard (A7N8X Deluxe), a Silicon Image Sil 3112A controller. RAM is a pair of Corsair TWINX1024-3200LL DIMMs. The box ran stable for the first three weeks after I completed the build. One day I booted up into the BSOD. After restoring the system, it would run fine for a few days then, BAM, file corruption errors and eventually the BSOD. I found a post to try memtest86 to test out my RAM. I did and found some errors on one of the two Corsair DIMMs. I removed the effected module and am running the box on one DIMM. So I'm thinking problem solved, and I repair my Windows installation for the 40th time. System runs stable for a couple of days then BAM, more file corruption problems and the BSOD. It got to the point where I would leave the system on for days at a time, running CHKDSK from the command prompt only to find new errors cropping up all the time. I tried to turned the box off without letting XP shutdown and still XP somehow gets corrupted. I'm going to throw in the towel on NTFS and try FAT32. I noticed some other posts here with people having problems with NTFS and RAID. I hope this fixes the problem. If this doesn't work, it's back to Windows ME. On Thursday, August 14, 2003 at 4:36 am, Rui wrote: >Hi, > >i recently bought a new pc (p4 2.8Ghz FSB 800Mhz) and since i installed winxp pro >i've experienced lots of problems.i've got a S-ATA hdd (seagate barracuda 80Gb) connected >on the 4th ide master.some times the system stops responding and a blue screen appears.Messages >like: > >KERNEL_DATA_INPAGE_ERRROR >atapi.sys address xxxxxx > >or > >Stop: xxxxx UNKNOWN HARD ERROR > >or > >UNMOUNTABLE_VOLUME > >or even > >KMODE_EXCEPTION_NOT_HANDLED > >were some of the blue screen errors i got. > >i've formated the disk "n" times, and i even installed win2000 to make sure it was >winxp problem...no way of getting rid of this problem! when i used win2000 repair >option and i got the following msg: >"Setup has determined that drive c: is corrupted and cannot be repaired". >I paid very attention to all these posts and i wonder if changing from NTFS to FAT32 >will resolve this issue or if it's a hardware failure... > >i'd appreciate very much any help from you. > >Thank you very much, > >Rui >Portugal [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Tuesday, August 26, 2003 at 2:22 pm Posted by Bill (3 messages posted) So far, no problems whatsoever. It wasn't a RAID issue, it was an NTFS issue. Since converting to Fat32, I've not had one problem. On Sunday, August 17, 2003 at 9:14 am, VolTrdr wrote: >Hi All, > >Thank you all for posting to this thread. I've been experiencing similar problems, >though the corruption to my file system has been more fatal and has prevented me >from using the system 95% of the time. > >I built the box in mid July. I'm running Win XP Pro on top of two Seagate 120GB >SATA drives setup in a RAID-0 configuration with NTFS. I'm using the RAID controller >built into the motherboard (A7N8X Deluxe), a Silicon Image Sil 3112A controller. > RAM is a pair of Corsair TWINX1024-3200LL DIMMs. The box ran stable for the first >three weeks after I completed the build. One day I booted up into the BSOD. After >restoring the system, it would run fine for a few days then, BAM, file corruption >errors and eventually the BSOD. I found a post to try memtest86 to test out my RAM. > I did and found some errors on one of the two Corsair DIMMs. I removed the effected >module and am running the box on one DIMM. > >So I'm thinking problem solved, and I repair my Windows installation for the 40th >time. System runs stable for a couple of days then BAM, more file corruption problems >and the BSOD. > >It got to the point where I would leave the system on for days at a time, running >CHKDSK from the command prompt only to find new errors cropping up all the time. > I tried to turned the box off without letting XP shutdown and still XP somehow gets >corrupted. I'm going to throw in the towel on NTFS and try FAT32. > >I noticed some other posts here with people having problems with NTFS and RAID. >I hope this fixes the problem. If this doesn't work, it's back to Windows ME. > > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Saturday, September 6, 2003 at 3:21 pm Posted by Zippy (1 messages posted) This is a copy of a post I made at another forum with a possible solution. Id already tried all the usual things that have been suggested here. Like most people my main suspicion was the early power off problem - so to eliminate this I hot wired the PSU to provide power all the time and ignore the power off signal from the motherboard - and I still got the same corruption on reboot. After searching and trying numerous vaguely related patches and fixes from MS I came across Q331958 - 137GB ATAPI driver limit in XP (in all versions of XP upto and including SP1). Id noticed this before but as it said it only applied to Hibernate and kernal dumps I hadn't bothered installing it. To quote from MS "The ATAPI driver for Windows XP Service Pack 1 (SP1) does not use 48-bit Logical Block Addressing (LBA) when it writes memory dump files or hibernation files. Additionally, the flush cache command is not issued to a large hard disk that has 48-bit LBA enabled when Windows XP enters standby or hibernation" However I thought I might as well install it - and so far after 10 reboots I havent had one chkdsk or any other sign of corruption. Either thats a 1 in a million coincidence or MS are being economical with the truth and the bug applies to ALL disk accesses. I was also under the impression that as most IDE Raid devices used virtual SCSI devices that these ATAPI problems shouldn't apply. For anyone thats interested in trying this - http://support.microsoft.com/default.aspx?scid=kb;[LN];331958 [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Tuesday, September 9, 2003 at 11:30 pm Posted by El Chino (1 messages posted) I got the same problem with XP. I agreed with you, it seems like HD is still writting / reading during powerdown, leaving open archives in the operation. That causes chkdsk starts on startup and, if you got bad luck, some important system file corrupted and no boot at all. The issue disappears if you restart instead shutdown, and shut it down manually after reboot. Anybody out there got or knows about any solution? Thanks in advance On Thursday, April 10, 2003 at 2:42 pm, Antonio Giner wrote: >It's incredible to find this thread! I was experiencing the same problems in Windows >2000, even worse cause the ntfs corruption often caused BSOD in my system. At first >it's was difficult to find a relation among constant blue screens and ntfs corruption >till I noticed that chkdsk eliminated them for the next 3-4 reboots. After that, >ntfs went sick again with the sympthoms you described. I started to think about shutdown >problems when I noticed that the hd red led was always still on when Windows performed >the powerdown (seems it didn't wait for the hd to stop). Yesterday I found this holy >thread that has confirmed my suspicions. Now I wish there was an easy way to disable >the auto-powerdown feature and return to the old "It's safe to turn off your computer" >screen. It's annoying to search the net to see that everyone has exactly the opposite >problem (their auto-powerdown feature doesn't work and they want to enable it). I >know I could possibly disable the ACPI from the BIOS setup and reinstall Windows >2000 to get a non-ACPI hal... but this method sucks. Hope that Microsoft adds that >delay in SP4, will they? > > >Thanks a lot, you have saved me from a horrible headache. > > >Antonio > > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Monday, September 15, 2003 at 2:23 am Posted by DeeGee (1 messages posted) I too have installed this patch on a twin-disk 160Gb XP system, and it seems to have cured my frequent startup corruptions. These corruptions were always in system or registry fies. There is now a noticeable 1 or 2 second delay on shutdown, which used to be instantaneous. So, as you say, the fix does appear to affect shutdown as well as standby and hibernate. Thanks On Saturday, September 6, 2003 at 3:21 pm, Zippy wrote: >This is a copy of a post I made at another forum with a possible solution. > >Id already tried all the usual things that have been suggested here. Like most people >my main suspicion was the early power off problem - so to eliminate this I hot wired >the PSU to provide power all the time and ignore the power off signal from the motherboard >- and I still got the same corruption on reboot. > >After searching and trying numerous vaguely related patches and fixes from MS I came >across Q331958 - 137GB ATAPI driver limit in XP (in all versions of XP upto and including >SP1). Id noticed this before but as it said it only applied to Hibernate and kernal >dumps I hadn't bothered installing it. > >To quote from MS "The ATAPI driver for Windows XP Service Pack 1 (SP1) does not use >48-bit Logical Block Addressing (LBA) when it writes memory dump files or hibernation >files. Additionally, the flush cache command is not issued to a large hard disk that >has 48-bit LBA enabled when Windows XP enters standby or hibernation" > >However I thought I might as well install it - and so far after 10 reboots I havent >had one chkdsk or any other sign of corruption. > >Either thats a 1 in a million coincidence or MS are being economical with the truth >and the bug applies to ALL disk accesses. I was also under the impression that as >most IDE Raid devices used virtual SCSI devices that these ATAPI problems shouldn't >apply. > >For anyone thats interested in trying this - >http://support.microsoft.com/default.aspx?scid=kb;[LN];331958 > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Monday, September 15, 2003 at 3:04 pm Posted by James S. (7 messages posted) I am having this same type problem. I run chkdsk from the command line prompt and consistently see the error, Correcting errors in the master file table's (MFT) BITMAP attribute. Correcting errors in the Volume Bitmap. -------------- I have this compaq presario, windows xp or prof., brand new pc since 11/02. Just recently, over the past 4 to 8 weeks, I am not able to correct the problem above. A couple of the newsgroups from yahoo suggest that the HDD is corrupt. Also, HP/Compaq say the same, corrupt. I was introduced to the 6 floppy disk set of xp boot disk setup. Was told to delete the partition and start over. Tried this several times. No success. Tried several FDISK's, no success. Early this morning, after doing a disk sanitizer, windows IS able to fix the errors above. AFTER I install most of the critical updates, I have the errors, again. Have tried both, c.l.i. or the 'c' drive icon, properties, tools, check now. Neither will fix the errors. I have tried 20 attempts. I have a LOW tolerance if a problem CANNOT fix a problem. Windows did crash due to a re-boot. I am getting the report, the HDD is not dirty. I will try the suggestion, format in fat32. If you have any comments, feel free to e-mail me, js8jim@msn.com Thank you, JIM ================================= On Friday, October 4, 2002 at 10:02 pm, Paul wrote: >I have a question about Prevent >file corruption problems: > >I have tried running the "new" CHKDSK under Windows XP using both the Error Checking >tool in "My Computer/File/Properties" and from the command line. > >When I used the Error Checking tool (without selecting the Automatic fix of file >system errors or the scan for bad sectors) XP displayed a dialogue with a sequence >of messages, telling me that the Error Checker was performing phase 1 of its check, >then phases 2 and 3 and finally a new dialogue appeared telling me that the check >had been completed - and nothing more. > >When I ran CHKDSK from the command prompt, using the command "CHKDSK C: /V" the output >was more informative: > >"The type of the file system is NTFS. > >WARNING! F parameter not specified. >Running CHKDSK in read-only mode. > >CHKDSK is verifying files (stage 1 of 3)... >File verification completed. >CHKDSK is verifying indexes (stage 2 of 3)... >Index verification completed. >Detected minor inconsistencies on the drive. >CHKDSK is verifying security descriptors (stage 3 of 3) >Cleaning up 33 unused index entries from index >Cleaning up 33 unused index entries from index >Cleaning up 33 unused security descriptors. >Security descriptor verification completed. >CHKDSK is verifying Usn Journal... >Usn Journal verification completed. >Correcting errors in the Volume Bitmap. >Windows found problems with the file system. >Run CHKDSK with the /F (fix) option to correct" > >My question is, which should I trust - the Error Checking tool (which I assume invokes >CHKDSK in the background) or the command line? Or perhaps a third party program? [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Tuesday, September 23, 2003 at 10:27 am Posted by Jim (7 messages posted) All these problems seem all too familiar. Had built my machine in March....ran great with XP home (NTFS). About a month ago my hard drive (120 GB Maxtor) crashed after a reboot. Just a simple reboot. Received message "disk read error" (or something like that). I had no problems till then. The only thing I had done was 2 weeks prior to this crash was installl extra memory. And 1 week prior install a sencond hard drive (120 GB Maxtor) to my RAID promise controler. I took the hard drive out and slaved it off another XP machine. Upon trying to gain excess to this drive I recieved the error "file or directory is corrupted and unreadable". Cost me $500.00 to have a recovery place retrieve all my lost pictures and imoprtant files (like a fool did not back-up on CD). Anyway, I purchased a new hard drive, another 120 GB maxtor hard drive, formated with NTFS WINXP, and loaded some of my programs, email, etc. Suddenly a few days later started getting file corruptions again. Messages told me to run check disk. When I went to run check disk (under tools and check now) nothing would happen. Almost like a dead function. I click the button and nothing would happen. I used the command window and typed in "CHKDSK" and I would recieve the messsage "file or directory is corrupted and unreadable". I could not even used the check disk to fix the disk. The diagnostics of winXP was corrupted. I rebooted with a continuous reboot happening over and over again. WinXP would not boot up. I slaved the drive off my working XP machine and gained access to the files in there, with a bunch missing (like outlook PST files). I used this second XP machine to do a CHKDSK on this screwed up drive......found problems and fixed them. But, it would still not function in my main computer, just keep rebooting by itself. Now my second machine running XP has been a dream. Not one problem. Both using an NTFS format. Only difference is my main machine uses a RAID controller with two 120 GB maxtor hard drives (one being the boot drive). I redid the hard drive with a fresh NTFS load and winXP, using the win XP disk for this. Ran great for a few days, then a file corruption came up. Quickly ran CHKDSK. Found problems, fixed them, and kept running fine. So whats the real sollution here? Run CHKDSK every chance you get?? Kill the power suddenly instead of letting winXP shut it down.....does that include a reboot??? Try some of the suggestions from above?? I have to use NTFS for my file system because I connect my DV camera to the computer and save my video to the hard drive for converting over to a DVD format to burn to a DVD. Most of these files are over 4 GB which a FAT32 does not support. So any more ideas would be great help. Thanks. On Monday, September 15, 2003 at 3:04 pm, James S. wrote: >I am having this same type problem. I run chkdsk from the command line prompt and >consistently see the error, >Correcting errors in the master file table's (MFT) BITMAP attribute. >Correcting errors in the Volume Bitmap. >-------------- >I have this compaq presario, windows xp or prof., brand new pc since 11/02. Just >recently, over the past 4 to 8 weeks, I am not able to correct the problem above. >A couple of the newsgroups from yahoo suggest that the HDD is corrupt. Also, HP/Compaq >say the same, corrupt. I was introduced to the 6 floppy disk set of xp boot disk >setup. Was told to delete the partition and start over. Tried this several times. >No success. Tried several FDISK's, no success. Early this morning, after doing a >disk sanitizer, windows IS able to fix the errors above. AFTER I install most of >the critical updates, I have the errors, again. Have tried both, c.l.i. or the 'c' >drive icon, properties, tools, check now. Neither will fix the errors. I have tried >20 attempts. I have a LOW tolerance if a problem CANNOT fix a problem. Windows did >crash due to a re-boot. I am getting the report, the HDD is not dirty. I will try >the suggestion, format in fat32. If you have any comments, feel free to e-mail me, >js8jim@msn.com Thank you, JIM >================================= > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Tuesday, September 23, 2003 at 9:34 pm Posted by James S. (7 messages posted) Hello; I think I may have found a way to fix my problem and yours, too. If I delete the partition the error messages are coming from when doing chkdsk, then format the HDD in fat32, c: /fs:fat32, then on re-boot, let the o.s. xp, start loading. My recovery cd's will auto. choose ntfs as the format to format my hdd. I have NO option of which format when the recovery cd's either format and recovery, or, do a recovery. ***Another point I would like to make, when installing all the updates from microsoft, do a SMALL amount at a time. Defragment. Run chkdsk. Install more updates, so on, so on.It was suggested from a microsoft rep. to install the updates, a few at a time..After I install i.e. 6.x s.p.1a, then I had problems trying to fix the errors, chkdsk found. Like to add, try this, chkdsk c: /v /f, or, chkdsk c: /f ,I used to type chkdsk c:/f (that is wrong). If you would like a little more help, contact me at:js8jim@msn.com =>P.S. I have obsessive/compulsive habits, despite that, I have a habit of doing chkdsk as often as I feel is necessary. Best wishes, JIM ================================ On Tuesday, September 23, 2003 at 10:27 am, Jim wrote: >All these problems seem all too familiar. Had built my machine in March....ran great with XP home (NTFS). About a month ago my hard drive (120 GB Maxtor) crashed after a reboot. Just a simple reboot. Received message "disk read error" (or something like that). I had no problems till then. The only thing I had done was 2 weeks prior to this crash was installl extra memory. And 1 week prior install a sencond hard drive (120 GB Maxtor) to my RAID promise controler. I took the hard drive out and slaved it off another XP machine. Upon trying to gain excess to this drive I recieved the error "file or directory is corrupted and unreadable". Cost me $500.00 to have a recovery place retrieve all my lost pictures and imoprtant files (like a fool did not back-up on CD). Anyway, I purchased a new hard drive, another 120 GB maxtor hard drive, formated with NTFS WINXP, and loaded some of my programs, email, etc. Suddenly a few days later started getting file corruptions again. Messages told me to run check disk. When I went to run check disk (under tools and check now) nothing would happen. Almost like a dead function. I click the button and nothing would happen. I used the command window and typed in "CHKDSK" and I would recieve the messsage "file or directory is corrupted and unreadable". I could not even used the check disk to fix the disk. The diagnostics of winXP was corrupted. I rebooted with a continuous reboot happening over and over again. WinXP would not boot up. I slaved the drive off my working XP machine and gained access to the files in there, with a bunch missing (like outlook PST files). I used this second XP machine to do a CHKDSK on this screwed up drive......found problems and fixed them. But, it would still not function in my main computer, just keep rebooting by itself. Now my second machine running XP has been a dream. Not one problem. Both using an NTFS format. Only difference is my main machine uses a RAID controller with two 120 GB maxtor hard drives (one being the boot drive). > >I redid the hard drive with a fresh NTFS load and winXP, using the win XP disk for this. Ran great for a few days, then a file corruption came up. Quickly ran CHKDSK. Found problems, fixed them, and kept running fine. So whats the real sollution here? Run CHKDSK every chance you get?? Kill the power suddenly instead of letting winXP shut it down.....does that include a reboot??? Try some of the suggestions from above?? > >I have to use NTFS for my file system because I connect my DV camera to the computer and save my video to the hard drive for converting over to a DVD format to burn to a DVD. Most of these files are over 4 GB which a FAT32 does not support. > >So any more ideas would be great help. Thanks. [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Wednesday, September 24, 2003 at 7:37 am Posted by Jim (7 messages posted) Not too sure about your fix. Your deleting the partition where the errors are coming from. Formating with a FAT32, then loading XP with a NTFS format? I thought the idea was to load XP on a FAT32 then convert to an NTFS? There was a post in here explaining this. Like I mentioned before, I do need to run NTFS because of the file sizes I work with. So really where is the problem? With NTFS? With XP itself? or with XP and NTFS used togther? Because there should be some fix out there for XP to be more compatible with the NTFS. Even though XP does not give you the ability to format with a FAT32 (have to use a third hand SW). I am comenting on a post about a MS update. Q331958 - do a search at MS knowledge base on this update. Still wondering if I should install this update. It mentions about hard drives larger then 137 GB. I have two 120 GB hard drives connected to a third IDE channel controlled by a RAID promise controller. I seem to have file corruptions with both hard drives. One of these 120 GB drives is my boot drive, the other for storage and back up. Both using an NTFS format. So my question is this, after reading about this update (Q331958) I am wondering if XP looks at these drives together for a total of 240 GB? Would it even hurt to add this update if it still does not apply to a certain problem? Currently, I am just defragin' and check diskin' as often as I can. Mostly after a few program installs or MS updates. Been almost a week with no real problem. From what I read in this thread. Some fixes that have seemed to cure these file corruption problem are: 1. Using a FAT32 for your XP install. 2. Use defrag and check disk more often then you use the restrooms. 3. Apply the MS update (Q331958) 4. Go buy a Mac. Have I missed any real helpful tips on this problem? On Tuesday, September 23, 2003 at 9:34 pm, James wrote: >Hello; I think I may have found a way to fix my problem and yours, too. If I delete >the partition the error messages are coming from when doing chkdsk, then format the >HDD in fat32, c: /fs:fat32, then on re-boot, let the o.s. xp, start loading. My recovery >cd's will auto. choose ntfs as the format to format my hdd. I have NO option of which >format when the recovery cd's either format and recovery, or, do a recovery. >***Another point I would like to make, when installing all the updates from microsoft, >do a SMALL amount at a time. Defragment. Run chkdsk. Install more updates, so on, >so on.It was suggested from a microsoft rep. to install the updates, a few at a time..After >I install i.e. 6.x s.p.1a, then I had problems trying to fix the errors, chkdsk found. >Like to add, try this, chkdsk c: /v /f, or, chkdsk c: /f ,I used to type chkdsk >c:/f (that is wrong). If you would like a little more help, contact me at:js8jim@msn.com >=>P.S. I have obsessive/compulsive habits, despite that, I have a habit of doing >chkdsk as often as I feel is necessary. Best wishes, JIM >================================ [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Wednesday, September 24, 2003 at 10:06 am Posted by James S. (7 messages posted) Hello; Have you tried posting this question to the following newsgroup, WinXPHelp@yahoogroups.com? There are other newsgroups from yahoo on computers. Have you tried posting that question to those, as well? I recently just found out about these yahoo newsgroups. There is, pc_computersolutions@yahoogroups.com, computersupport_2@yahoogroups.com There might be more, not sure of the names. Best wishes, JIM ========== On Wednesday, September 24, 2003 at 7:37 am, Jim wrote: >Not too sure about your fix. Your deleting the partition where the errors are coming from. Formating with a FAT32, then loading XP with a NTFS format? I thought the idea was to load XP on a FAT32 then convert to an NTFS? There was a post in here explaining this. Like I mentioned before, I do need to run NTFS because of the file sizes I work with. >So really where is the problem? With NTFS? With XP itself? or with XP and NTFS used togther? Because there should be some fix out there for XP to be more compatible with the NTFS. Even though XP does not give you the ability to format with a FAT32 (have to use a third hand SW). > >I am comenting on a post about a MS update. >Q331958 - do a search at MS knowledge base on this update. Still wondering if I should install this update. It mentions about hard drives larger then 137 GB. I have two 120 GB hard drives connected to a third IDE channel controlled by a RAID promise controller. I seem to have file corruptions with both hard drives. One of these 120 GB drives is my boot drive, the other for storage and back up. Both using an NTFS format. >So my question is this, after reading about this update (Q331958) I am wondering if XP looks at these drives together for a total of 240 GB? Would it even hurt to add this update if it still does not apply to a certain problem? > >Currently, I am just defragin' and check diskin' as often as I can. Mostly after a few program installs or MS updates. Been almost a week with no real problem. > >From what I read in this thread. Some fixes that have seemed to cure these file corruption problem are: > 1. Using a FAT32 for your XP install. > 2. Use defrag and check disk more often then you use the restrooms. > 3. Apply the MS update (Q331958) > 4. Go buy a Mac. > >Have I missed any real helpful tips on this problem? ============================= [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Thursday, September 25, 2003 at 7:29 am Posted by Jim (7 messages posted) This was the first place to come up in my search. Still looking around....although my system seems fairly stable. I'll check it out. Thanks!! On Wednesday, September 24, 2003 at 10:06 am, James wrote: >Hello; Have you tried posting this question to the following newsgroup, >WinXPHelp@yahoogroups.com? >There are other newsgroups from yahoo on computers. Have you tried posting that question >to those, as well? I recently just found out about these yahoo newsgroups. There >is, pc_computersolutions@yahoogroups.com, computersupport_2@yahoogroups.com >There might be more, not sure of the names. >Best wishes, JIM >========== [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Thursday, September 25, 2003 at 11:23 am Posted by James S. (7 messages posted) Hello; Jim, will you please inform me of new information that you find on this topic? I am studying about computers in college with a minor in computer technology. Always interested in trying to understand the why and how. Thanks, JIM ============================ On Thursday, September 25, 2003 at 7:29 am, Jim wrote: >This was the first place to come up in my search. Still looking around....although >my system seems fairly stable. I'll check it out. Thanks!! > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Monday, September 29, 2003 at 1:22 pm Posted by Jim (7 messages posted) I had shut my system down over the weekend (went out of town). Fired it up and received the message: NTLDR is missing Microshit has a few fixes for the NTLDR fix, none seem to be the cause of my problem....hoping the solution they post helps. Maybe the boot files became corrupted?? Who knows. Getting more pissed as time goes on. My computer was running stable until I decided to place my hard drive on the third IDE channel (which is controlled by a RAID promice controller) over a month ago. That is when all my trouble started. I'm starting to lean into the RAID controller as the problem. I am thinking about placing the hard drive back on IDE channel 1. I did not have these many problems before. I'd like to fix my boot problem (replace the NTLDR file) and install the MS update that I mentioned a few weeks ago. I can leave my second hard drive connected to the RAID controller and place the boot drive on the primary IDE connector. My computer has been running for over 4 months without incident. Primary channel (IDE 1) had the hard drive and zip drive attached. Secondary channel (IDE 2) had my CD burner and DVD burner. I had thought I could use the third channel (IDE 3) for a DVD rom drive, finding out that a RAID driver is intented for a hard drive, not a CD drive. I placed the hard drive on the RAID and rearanged the CD drives and zip drive on the IDE 1 and IDE 2. This configuration ran fine for a few weeks. I placed a 3rd memory stick (512) a week later. I then slaved a second 120 Gig hard drive off the RAID, ran fine for a few days. Then all the problems started to happen. Removed the memory stick, thinking that might be the problem, doesn't seem like it. Can't see the slaved drive causing these problems. This whole thread talk about file corruption. Not really thinking that the RAID device had anything to do with it, but focused on XP. If this makes sense to anyone...great. If not, ask to clarify and I will try. Thanks. On Thursday, September 25, 2003 at 11:23 am, James wrote: >Hello; >Jim, will you please inform me of new information that you find on this topic? >I am studying about computers in college with a minor in computer technology. Always >interested in trying to understand the why and how. Thanks, JIM >============================ [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Monday, September 29, 2003 at 5:28 pm Posted by James S. (7 messages posted) Hello; Did you try posting all these thoughts and problems with your pc at winxphelp@yahoogroups.com ? Or, the other yahoogroups I talked about? They have staff that MAY go out the person's home and help repair the problem. Send an e-mail to this address to get started, winxphelp-subscribe@yahoogroups.com Best of luck. (Why are using the RAID controller in the first place?) JIM =>P.S. With the NEW pc that supports, hibernate, I will always choose, hibernate, or, stand-by versus shut down. The pc WILL last LONGER.||| ++++++++++++++++++++++++ On Monday, September 29, 2003 at 1:22 pm, Jim wrote: >I had shut my system down over the weekend (went out of town). Fired it up and received >the message: NTLDR is missing > >Microshit has a few fixes for the NTLDR fix, none seem to be the cause of my problem....hoping the solution they post helps. Maybe the boot files became corrupted?? Who knows. >Getting more pissed as time goes on. My computer was running stable until I decided to place my hard drive on the third IDE channel (which is controlled by a RAID promice controller) over a month ago. That is when all my trouble started. I'm starting to lean into the RAID controller as the problem. I am thinking about placing the hard drive back on IDE channel 1. I did not have these many problems before. > >I'd like to fix my boot problem (replace the NTLDR file) and install the MS update that I mentioned a few weeks ago. I can leave my second hard drive connected to the RAID controller and place the boot drive on the primary IDE connector. > >My computer has been running for over 4 months without incident. Primary channel (IDE 1) had the hard drive and zip drive attached. Secondary channel (IDE 2) had my CD burner and DVD burner. I had thought I could use the third channel (IDE 3) for a DVD rom drive, finding out that a RAID driver is intented for a hard drive, not a CD drive. I placed the hard drive on the RAID and rearanged the CD drives and zip drive on the IDE 1 and IDE 2. This configuration ran fine for a few weeks. I placed a 3rd memory stick (512) a week later. I then slaved a second 120 Gig hard drive off the RAID, ran fine for a few days. Then all the problems started to happen. >Removed the memory stick, thinking that might be the problem, doesn't seem like it. >Can't see the slaved drive causing these problems. This whole thread talk about file corruption. Not really thinking that the RAID device had anything to do with it, but focused on XP. If this makes sense to anyone...great. If not, ask to clarify and I will try. >Thanks. [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Tuesday, September 30, 2003 at 8:53 am Posted by Jim (7 messages posted) I purchased an Aopen mother board that utilizes 3 IDE channels. The third using a RAID controller. I had a hard drive, zip drive, CD-burner, DVD-burner, and a DVD-ROM drive I wanted to install. Plus with having one more device which I used for a second back-up hard drive. I had no idea that the 3rd IDE channel was intended for hard drives only (not realizing at first this was setup for a RAID device). So that was the configuration I wanted to have............until the problems started after I placed the hard drive on IDE 3. As for the winxphelp yahoo group, which I am looking into, what group would be the best to post my question?? And for an update after the "NTLDR is Missing" problem that I had, I used the recovery console on the winxp CD-ROM and ran a "CHKDSK /R" which took over an hour to run. Errors were found and fixed. I rebooted the machine and XP loaded flawlessly. I'm guessing the file corruption problems hit some boot files and caused this problem, but CHKDSK fixed them. After I got my machine up and running, I installed the Q331958 update from microsoft (suggested update posted in this forum) thinking that having two 120 GB hard drive would make WINXP think that there was 240 total gigs of space for the computer......which would make that update relevent to install. I'll keep an update to see if this update helps anyting. On Monday, September 29, 2003 at 5:28 pm, James wrote: >Hello; Did you try posting all these thoughts and >problems with your pc at >winxphelp@yahoogroups.com ? Or, the other >yahoogroups I talked about? They have staff that MAY >go out the person's home and help repair the problem. >Send an e-mail to this address to get started, >winxphelp-subscribe@yahoogroups.com >Best of luck. (Why are using the RAID controller in the >first place?) JIM >=>P.S. With the NEW pc that supports, hibernate, I >will always choose, hibernate, or, stand-by versus >shut down. The pc WILL last LONGER.||| >++++++++++++++++++++++++ [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Tuesday, September 30, 2003 at 10:19 am Posted by James S. (7 messages posted) Hello; I see NO reason why it would not hurt to post these questions to all 3 groups? I would start with the winxhphelp group. You would send a blank e-mail to the group. In the recovery console, there is also, the fixmbr command. Or, fixboot, command. Sorry to hear of all the problems. Good luck, JIM ============================= On Tuesday, September 30, 2003 at 8:53 am, Jim wrote: >I purchased an Aopen mother board that utilizes 3 IDE channels. The third using a RAID controller. I had a hard drive, zip drive, CD-burner, DVD-burner, and a DVD-ROM drive I wanted to install. Plus with having one more device which I used for a second back-up hard drive. I had no idea that the 3rd IDE channel was intended for hard drives only (not realizing at first this was setup for a RAID device). So that was the configuration I wanted to have............until the problems started after I placed the hard drive on IDE 3. > >As for the winxphelp yahoo group, which I am looking into, what group would be the best to post my question?? > >And for an update after the "NTLDR is Missing" problem that I had, I used the recovery console on the winxp CD-ROM and ran a "CHKDSK /R" which took over an hour to run. >Errors were found and fixed. I rebooted the machine and XP loaded flawlessly. I'm guessing the file corruption problems hit some boot files and caused this problem, but CHKDSK fixed them. >After I got my machine up and running, I installed the Q331958 update from microsoft (suggested update posted in this forum) thinking that having two 120 GB hard drive would make WINXP think that there was 240 total gigs of space for the computer......which would make that update relevent to install. > >I'll keep an update to see if this update helps anyting. [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Thursday, October 2, 2003 at 4:23 am Posted by James Tuvix (1 messages posted) Well I think this update solved all my corruption-problems. After installing it I had no chkdsk at startup any more!! thy to zippy!! On Saturday, September 6, 2003 at 3:21 pm, Zippy wrote: >After searching and trying numerous vaguely related patches and fixes from MS I came >across Q331958 - 137GB ATAPI driver limit in XP (in all versions of XP upto and including >SP1). Id noticed this before but as it said it only applied to Hibernate and kernal >dumps I hadn't bothered installing it. > >To quote from MS "The ATAPI driver for Windows XP Service Pack 1 (SP1) does not use >48-bit Logical Block Addressing (LBA) when it writes memory dump files or hibernation >files. Additionally, the flush cache command is not issued to a large hard disk that >has 48-bit LBA enabled when Windows XP enters standby or hibernation" > >However I thought I might as well install it - and so far after 10 reboots I havent >had one chkdsk or any other sign of corruption. >For anyone thats interested in trying this - >http://support.microsoft.com/default.aspx?scid=kb;[LN];331958 [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Monday, October 13, 2003 at 10:45 am Posted by Jim (7 messages posted) I am concerned with this update. If you have two 120 gig hard drives (1 being slaved, other being master) attached to a single IDE connection, does this update apply? Does it hurt applying this update if not needed?? I am thinking having two 120 gig hard drives togther makes XP total the drives to 240 gig, even though they are seperate drives. I am also giving an update with this problem I have been having. The Aopen manufacture feels the IDE controller might be bad causing file corruption. Even the 80 wire ribbon cable could be bad as well. I decided to purchase a new motherboard......hoping for a fix. On Saturday, September 6, 2003 at 3:21 pm, Zippy wrote: >This is a copy of a post I made at another forum with a possible solution. > >Id already tried all the usual things that have been suggested here. Like most people >my main suspicion was the early power off problem - so to eliminate this I hot wired >the PSU to provide power all the time and ignore the power off signal from the motherboard >- and I still got the same corruption on reboot. > >After searching and trying numerous vaguely related patches and fixes from MS I came >across Q331958 - 137GB ATAPI driver limit in XP (in all versions of XP upto and including >SP1). Id noticed this before but as it said it only applied to Hibernate and kernal >dumps I hadn't bothered installing it. > >To quote from MS "The ATAPI driver for Windows XP Service Pack 1 (SP1) does not use >48-bit Logical Block Addressing (LBA) when it writes memory dump files or hibernation >files. Additionally, the flush cache command is not issued to a large hard disk that >has 48-bit LBA enabled when Windows XP enters standby or hibernation" > >However I thought I might as well install it - and so far after 10 reboots I havent >had one chkdsk or any other sign of corruption. > >Either thats a 1 in a million coincidence or MS are being economical with the truth >and the bug applies to ALL disk accesses. I was also under the impression that as >most IDE Raid devices used virtual SCSI devices that these ATAPI problems shouldn't >apply. > >For anyone thats interested in trying this - >http://support.microsoft.com/default.aspx?scid=kb;[LN];331958 > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Monday, October 20, 2003 at 7:55 am Posted by Peter Shkabara (6 messages posted) An update on my situation: A few days ago, I downloaded some Microsoft patches for XP while I was at work with a high-speed connection (2 T1 lines). I then brought home the patches and installed them. Something did not work properly because on rebooting, I got an error message saying that my XP registration could not be verified and I could not log in. (A new Microsoft annoyance) Microsoft's knowledge base says that this usually requires a re-install of XP - do so as an upgrade to preserve all my settings. After trying other means of getting around this, I finally did a re-install of the OS. While most of my settings remained ok, the HAL got replaced with an APCI compliant version. This means that the computer turns power off on shutdown. The amazing thing is that this time I did not get the disk corruption that I had previously experienced. Doing a CHKDSK showed only minor errors, and not always. No more index corruption showed up so far after at least 10 reboots! Unfortunately, I don't know which patch is responsible for this "fix", but it is a welcome result. Being somewhat skeptical, I still run CHKDSK after every other shutdown, but my confidence is starting to build up. [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Tuesday, November 4, 2003 at 11:24 pm Posted by Grant (1 messages posted) All I can say is "what better way for a man to alleviate a multi-billion dollar lawsuit than to make a crappy product that you will probably try to fix or replace with another of his crappy products?" It's like I have the worst case of schizophrenia in the world and I've been posting on this sight in my sleep for 2 yrs. I finally got tired of not being able to burn anything more than 15kb before my PC/RW spit out the cdr. This, I finally decided, was due to MS inability to supply a driver that supports all the features for a number of different makes/models of CD-DVDROM drives. Being one of the ecstatic millions of unlucky recipient's of the famed "oem scam" systems I didn't get a whole lot of help from the PC distributor or the company that made the CD-DVDROM drive either. By accident I found myself on Western Digital's website looking for an overhaul kit for what sounds like a 1975 shovel- head firing up where my hardrive used to reboot and came across the .ZIP file that is suppose to fix the problem with our pal Williams' XP drivers. So I nabbed it, unzipped it, read the install txt file and installed it along with the CONFIG.SYS\AUTOEXEC.BAT file edits they said had to be done to make 'em run and support UDMA. So, needless to say, if I've learned anything at all from using anything MS provides is to back it up 5 times and hide another copy under you mattress. I reverse edited the config/auto files to there original pristine disfunctional condition and rebooted. Got the chkdsk prompt and it went off without a hitch. In, fact I've never seen chkdsk works so fast. I tried to find what caused the chkdsk to even run as I didn't schedule it. Got another prompt from windows' "found hardware" program. Upon investigation a Sony memory stick got hooked up to my system and it was needing a driver and so was all of my removable media and storage devices. Well to make an epic saga into a low-buck paperback I back-peddalled a well executed restore point, ran another sector/recovery scan, ad-aware scan, virus scan, McCafee quickclean, thouroughly checked the MMC console and firewall logs and even did a completely unnecessary check back at Ole' at the Windows' up-chuck site, rebooted, called a psychiatrist, swore off chemical substance abuse (side effect Mr. G's technology), and went to bed. Next morning my pc still still needed some time to reboot, only 3 of 5 processes completed and a prompt "deleting index entry bootex.log in index $I30 of file 5/the file system was corrupt and unreadable. Another 2 hrs, later it finally started after it tried and did another chkdsk while I was gone. Now, upon 2clicking any file, search assistant starts up because Search has become the default action in all my sub-menus, half my background services won't run, my cable modem can't acquire an IP address, my sound-card is staticy even during windows default sound scheme's, but, you can hear a spider fart over my hard drive it's so quiet and evidently Western Digital makes the M1A1-ABRAHMS tank of HDD's after a diagnostic scan mine is rating good to healthy ratings in every test after 4 yrs. of family PC abuse and 4 OS. Just to put a twist on this broadway show. I switched to XP Pro after my 2000 Pro had reduced me to a slobbering idiot(again thank's to Bill's snake oil security patches). As if any of you people are still reading, here I sit watching my system lose it's hardware/software systems one at a time. I think when I get done printing these pdfs of MAC PC's and Redhat Linux 9.0 I'll do one more chkdsk on the ol' girl and skip to ma loo with my little plastic fortune to my local pc dealer. By the way NTFS here too and I think I remember reading something at western digital or rarlab about a DDO device driver for high volume harddrive's. Something about exceeding BIOS limits and instead just recognizing 80 GB when you have 139 GB. In fact, I remember a couple of you mention a 20% loss in accounting your HD space and according to them this appeared on harddrives over 138GB. Anyway, keep posting guys I need ideas on how to make this thing really run bad. Sorry for the 17 ton vent session. THANX! n Friday, October 4, 2002 at 10:02 pm, Paul wrote: >I have a question about Prevent >file corruption problems: > >I have tried running the "new" CHKDSK under Windows XP using both the Error Checking >tool in "My Computer/File/Properties" and from the command line. > >When I used the Error Checking tool (without selecting the Automatic fix of file >system errors or the scan for bad sectors) XP displayed a dialogue with a sequence >of messages, telling me that the Error Checker was performing phase 1 of its check, >then phases 2 and 3 and finally a new dialogue appeared telling me that the check >had been completed - and nothing more. > >When I ran CHKDSK from the command prompt, using the command "CHKDSK C: /V" the output >was more informative: > >"The type of the file system is NTFS. > >WARNING! F parameter not specified. >Running CHKDSK in read-only mode. > >CHKDSK is verifying files (stage 1 of 3)... >File verification completed. >CHKDSK is verifying indexes (stage 2 of 3)... >Index verification completed. >Detected minor inconsistencies on the drive. >CHKDSK is verifying security descriptors (stage 3 of 3) >Cleaning up 33 unused index entries from index >Cleaning up 33 unused index entries from index >Cleaning up 33 unused security descriptors. >Security descriptor verification completed. >CHKDSK is verifying Usn Journal... >Usn Journal verification completed. >Correcting errors in the Volume Bitmap. >Windows found problems with the file system. >Run CHKDSK with the /F (fix) option to correct" > >My question is, which should I trust - the Error Checking tool (which I assume invokes >CHKDSK in the background) or the command line? Or perhaps a third party program? [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Wednesday, November 12, 2003 at 9:42 am Posted by nonsence (4 messages posted) wow, sounds like me a year or more ago. i had the same kinda problems with windows 2000 pro, server and advanced server. i tried them all, all with no luck. my computer, which i custom built with the parts I WANTED, I CHOICE, I BOUGHT, gave me nothing but file corruptions, deleted files, and so much bullshit. my error messages were during boot up when the "all mighty" chkdsk "utility" would run and start deleting bad indexes. well those "bad indexes" happened to be many of my movies, mp3 and sometimes even text files or web server content. html, jpg, and other file i had on my IIS5 web server would be deleted. what i found strange was it would delete a 700mb movie file but leave the actual "visible" icon in the directory. however the file would only show up as 0k, thus it wouldn't work because as far as windows media player is concerned it's not a movie anymore. same thing would happen if i copied a dvd to the hard drive. eventually, chkdsk would come along and delete the indexes upon boot, screw me over, and that's that. i'm left tearing out my hair, yelling at my computer half expecting it to give me the finger and slap me in the face! but we all know that's not true, because microsoft does that all on their own. as for the indexing service, what if i need it? for lets say a web site search engine or just because i search for files alot? i mean, what the hell! microsoft wants to get into the enterprise server ring with UNIX and their workstation systems which are VERY much like their server systems can't run worth shit, corrupt files, and basically just FAIL. given, when Windows works, it works and i like it. hell, i've done some cool things with it, Active Directory, IIS5, System Management Server, etc. all cool software. but how come when it REALLY COUNTS it always fails?! well, to sum it up. has anyone figured a way out of this yet? i mean hell, it's already the end of 2003, i just got in on this forum now. but i got all the windows 2000 updates, and i still fear that one day chkdsk will come along and screw me over. and it's not like i can avoid it. whenever the partition is messed up or there are "performance" problems, i do need to run chkdsk to fix them. and it works. except it does my files with them. not windows files, but bigger files usually. and my hard drive is only an 80gb. my windows is on a different partition. can ANYONE help?! On Tuesday, November 4, 2003 at 11:24 pm, Grant wrote: >All I can say is "what better way for a man to alleviate a multi-billion dollar >lawsuit than to make a crappy product that you will probably try to fix or replace >with another of his crappy products?" It's like I have the worst case of schizophrenia >in the world and I've been posting on this sight in my sleep for 2 yrs. I finally >got tired of not being able to burn anything more than 15kb before my PC/RW spit >out the cdr. This, I finally decided, was due to MS inability to supply a driver >that supports all the features for a number of different makes/models of CD-DVDROM >drives. Being one of the ecstatic millions of unlucky recipient's of the famed "oem >scam" systems I didn't get a whole lot of help from the PC distributor or the company >that made the CD-DVDROM drive either. By accident I found myself on Western Digital's >website looking for an overhaul kit for what sounds like a 1975 shovel- head firing >up where my hardrive used to reboot and came across the .ZIP file that is suppose >to fix the problem with our pal Williams' XP drivers. So I nabbed it, unzipped it, >read the install txt file and installed it along with the CONFIG.SYS\AUTOEXEC.BAT >file edits they said had to be done to make 'em run and support UDMA. So, needless >to say, if I've learned anything at all from using anything MS provides is to back >it up 5 times and hide another copy under you mattress. I reverse edited the config/auto >files to there original pristine disfunctional condition and rebooted. Got the chkdsk >prompt and it went off without a hitch. In, fact I've never seen chkdsk works so >fast. I tried to find what caused the chkdsk to even run as I didn't schedule it. >Got another prompt from windows' "found hardware" program. Upon investigation a Sony >memory stick got hooked up to my system and it was needing a driver and so was all >of my removable media and storage devices. Well to make an epic saga into a low-buck >paperback I back-peddalled a well executed restore point, ran another sector/recovery >scan, ad-aware scan, virus scan, McCafee quickclean, thouroughly checked the MMC >console and firewall logs and even did a completely unnecessary check back at Ole' >at the Windows' up-chuck site, rebooted, called a psychiatrist, swore off chemical >substance abuse (side effect Mr. G's technology), and went to bed. Next morning my >pc still still needed some time to reboot, only 3 of 5 processes completed and a >prompt "deleting index entry bootex.log in index $I30 of file 5/the file system was >corrupt and unreadable. Another 2 hrs, later it finally started after it tried and >did another chkdsk while I was gone. Now, upon 2clicking any file, search assistant >starts up because Search has become the default action in all my sub-menus, half >my background services won't run, my cable modem can't acquire an IP address, my >sound-card is staticy even during windows default sound scheme's, but, you can hear >a spider fart over my hard drive it's so quiet and evidently Western Digital makes >the M1A1-ABRAHMS tank of HDD's after a diagnostic scan mine is rating good to healthy >ratings in every test after 4 yrs. of family PC abuse and 4 OS. Just to put a twist >on this broadway show. I switched to XP Pro after my 2000 Pro had reduced me to a >slobbering idiot(again thank's to Bill's snake oil security patches). As if any of >you people are still reading, here I sit watching my system lose it's hardware/software >systems one at a time. I think when I get done printing these pdfs of MAC PC's and >Redhat Linux 9.0 I'll do one more chkdsk on the ol' girl and skip to ma loo with >my little plastic fortune to my local pc dealer. By the way NTFS here too and I think >I remember reading something at western digital or rarlab about a DDO device driver >for high volume harddrive's. Something about exceeding BIOS limits and instead just >recognizing 80 GB when you have 139 GB. In fact, I remember a couple of you mention >a 20% loss in accounting your HD space and according to them this appeared on harddrives >over 138GB. Anyway, keep posting guys I need ideas on how to make this thing really >run bad. Sorry for the 17 ton vent session. THANX! > >n Friday, October 4, 2002 at 10:02 pm, Paul wrote: > >I have a question about Prevent >file corruption problems: > >I have tried running the "new" CHKDSK under Windows XP using both the Error Checking >tool in "My Computer/File/Properties" and from the command line. > >When I used the Error Checking tool (without selecting the Automatic fix of file >system errors or the scan for bad sectors) XP displayed a dialogue with a sequence >of messages, telling me that the Error Checker was performing phase 1 of its check, >then phases 2 and 3 and finally a new dialogue appeared telling me that the check >had been completed - and nothing more. > >When I ran CHKDSK from the command prompt, using the command "CHKDSK C: /V" the >output >was more informative: > >"The type of the file system is NTFS. > >WARNING! F parameter not specified. >Running CHKDSK in read-only mode. > >CHKDSK is verifying files (stage 1 of 3)... >File verification completed. >CHKDSK is verifying indexes (stage 2 of 3)... >Index verification completed. >Detected minor inconsistencies on the drive. >CHKDSK is verifying security descriptors (stage 3 of 3) >Cleaning up 33 unused index entries from index >Cleaning up 33 unused index entries from index >Cleaning up 33 unused security descriptors. >Security descriptor verification completed. >CHKDSK is verifying Usn Journal... >Usn Journal verification completed. >Correcting errors in the Volume Bitmap. >Windows found problems with the file system. >Run CHKDSK with the /F (fix) option to correct" > >My question is, which should I trust - the Error Checking tool (which I assume invokes >CHKDSK in the background) or the command line? Or perhaps a third party program? > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Wednesday, November 19, 2003 at 6:54 pm Posted by VM (1 messages posted) Same trouble with WinXP on NTFS 80 Gb Seagate SATA, Motherboard Abit NF7-S. On Wednesday, November 12, 2003 at 9:42 am, nonsence wrote: >wow, sounds like me a year or more ago. i had the same kinda problems with windows >2000 pro, server and advanced server. i tried them all, all with no luck. my computer, >which i custom built with the parts I WANTED, I CHOICE, I BOUGHT, gave me nothing >but file corruptions, deleted files, and so much bullshit. >my error messages were during boot up when the "all mighty" chkdsk "utility" would >run and start deleting bad indexes. well those "bad indexes" happened to be many >of my movies, mp3 and sometimes even text files or web server content. html, jpg, >and other file i had on my IIS5 web server would be deleted. >what i found strange was it would delete a 700mb movie file but leave the actual >"visible" icon in the directory. however the file would only show up as 0k, thus >it wouldn't work because as far as windows media player is concerned it's not a movie >anymore. >same thing would happen if i copied a dvd to the hard drive. eventually, chkdsk would >come along and delete the indexes upon boot, screw me over, and that's that. i'm >left tearing out my hair, yelling at my computer half expecting it to give me the >finger and slap me in the face! but we all know that's not true, because microsoft >does that all on their own. >as for the indexing service, what if i need it? for lets say a web site search engine >or just because i search for files alot? i mean, what the hell! microsoft wants to >get into the enterprise server ring with UNIX and their workstation systems which >are VERY much like their server systems can't run worth shit, corrupt files, and >basically just FAIL. >given, when Windows works, it works and i like it. hell, i've done some cool things >with it, Active Directory, IIS5, System Management Server, etc. all cool software. >but how come when it REALLY COUNTS it always fails?! > >well, to sum it up. has anyone figured a way out of this yet? i mean hell, it's already >the end of 2003, i just got in on this forum now. but i got all the windows 2000 >updates, and i still fear that one day chkdsk will come along and screw me over. >and it's not like i can avoid it. whenever the partition is messed up or there are >"performance" problems, i do need to run chkdsk to fix them. and it works. except >it does my files with them. not windows files, but bigger files usually. and my hard >drive is only an 80gb. my windows is on a different partition. can ANYONE help?! > > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Thursday, November 20, 2003 at 9:20 am Posted by rainmanp7 (2 messages posted) The One thing I have found out is this ! When ever a folder has permissions and or files of a directory tree then If somehow because the power fails or the partition gets screwed up........ Then somthing magical will happen The partition will see the directory as normal and a linked folder on the hard drive will have normal permissions but become a bad sector on the hard drive untill it is re partioned and formated. This has been going on since the days of the windows 95 error but on windows NT you can correct this by resetting the Permissions all the way down to nothing and re obtaining the folder and files as Administrator but on 95,98,winME your pretty much screwed unless you can hook that hard drive up to a machine with a bootable NT system to repair the file/folder Structure...... There is another way to easliy but painlessly correctly find this error on the hard drive being caused by a file or folder in a file ,and that's by Copying or Moving in windows the files and folders to another hard drive If this wierd error is present windows will not allow you even if you are administrator to move it ,until the permissions are corrected and or the file deleted or repaired by some other methode I can not mention here because of the complexity of the situation.... Good Luck. [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Friday, November 21, 2003 at 2:34 am Posted by ChoGGi (809 messages posted) anyone having this problem just change acpi to standard pc instructions goto the control panel then system then hardware then device manager expand the cross next to computer right click on advanced configuration and power interface (ACPI) PC and choose update driver then pick install from a list or specfic location press next choose dont search i will choose the driver to install press next click have disk next to browse type in c:\windows\inf press ok select standard PC press next now you need your winxp cd (point it to the i386 folder on the cdrom if it has any problems finding it) then when the driver is done installing you have to reboot and its time to reinstall all your drivers its mostly automagical you should only have to point it to c:\windows\system32 and c:\windows\system32\drivers after windows is all done it'll ask you for a reboot do it and your all done [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Sunday, November 23, 2003 at 7:25 am Posted by Jim (7 messages posted) Here is an update about my file corruption problem. I purchased a totally different motherboard and I have been running for over a month with no problems. Bad IDE controller on the motherboard seemed to be the problem. On Tuesday, September 30, 2003 at 10:19 am, James wrote: >Hello; I see NO reason why it would not hurt to post these questions to all 3 groups? >I would start with the >winxhphelp group. You would send a blank e-mail to the group. In the recovery console, >there is also, the >fixmbr command. Or, fixboot, command. Sorry to hear >of all the problems. Good luck, JIM >============================= [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Sunday, November 23, 2003 at 2:48 pm Posted by James S. (7 messages posted) Jim; Thank you on the update. Always good to hear great news. Continued success in the future. JIM ====================== On Sunday, November 23, 2003 at 7:25 am, Jim wrote: >Here is an update about my file corruption problem. I purchased a totally different motherboard and I have been running for over a month with no problems. > >Bad IDE controller on the motherboard seemed to be the problem. [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Tuesday, November 25, 2003 at 12:55 pm Posted by kiwibank (1 messages posted) i have the same problems with xp/NTFS(also does the same thing in fat32 and after i`ve installed new software with bitmap errors, misreported free space and the infamous partition magic "improperly dismounted volume" error message that started the whole damn thing. same problems with recovery console. seems i`ll have to bare with it. apparently xp volumes rebuild themselves over time and constant rebooting and chkdsk running anyway. [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Thursday, December 4, 2003 at 12:21 pm Posted by mike (358 messages posted) The same misreported freespace errors were in windows 98. microsoft was unable to resolve after spending hour after hour, day after day, week after week discussing it with them. Taking out 3rd party programs as they suggested resulted in no solution. They suggested the brand new hard drive's were failing. Yet if clear the cmos, reinstall the OS and 3rd party programs the problem was resolved until specific firewall hits occured. On Tuesday, November 25, 2003 at 12:55 pm, kiwibank wrote: >i have the same problems with xp/NTFS(also does the same thing in fat32 and after >i`ve installed new software with bitmap errors, misreported free space and the infamous >partition magic "improperly dismounted volume" error message that started the whole >damn thing. same problems with recovery console. seems i`ll have to bare with it. >apparently xp volumes rebuild themselves over time and constant rebooting and chkdsk >running anyway. > > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Sunday, December 28, 2003 at 5:51 pm Posted by poslek (1 messages posted) The solution really is FAT32! I just reformatted my drive 100 times and always the sam stuff happening - INDEX$30 errors everywhere... But then I divided my disk into 3 partitions (so that I can format it with FAT32 when installing xp) and now everythings working like a charm! Thanks for the tip!!! On Friday, October 4, 2002 at 10:02 pm, Paul wrote: >I have a question about Prevent >file corruption problems: > >I have tried running the "new" CHKDSK under Windows XP using both the Error Checking >tool in "My Computer/File/Properties" and from the command line. > >When I used the Error Checking tool (without selecting the Automatic fix of file >system errors or the scan for bad sectors) XP displayed a dialogue with a sequence >of messages, telling me that the Error Checker was performing phase 1 of its check, >then phases 2 and 3 and finally a new dialogue appeared telling me that the check >had been completed - and nothing more. > >When I ran CHKDSK from the command prompt, using the command "CHKDSK C: /V" the output >was more informative: > >"The type of the file system is NTFS. > >WARNING! F parameter not specified. >Running CHKDSK in read-only mode. > >CHKDSK is verifying files (stage 1 of 3)... >File verification completed. >CHKDSK is verifying indexes (stage 2 of 3)... >Index verification completed. >Detected minor inconsistencies on the drive. >CHKDSK is verifying security descriptors (stage 3 of 3) >Cleaning up 33 unused index entries from index >Cleaning up 33 unused index entries from index >Cleaning up 33 unused security descriptors. >Security descriptor verification completed. >CHKDSK is verifying Usn Journal... >Usn Journal verification completed. >Correcting errors in the Volume Bitmap. >Windows found problems with the file system. >Run CHKDSK with the /F (fix) option to correct" > >My question is, which should I trust - the Error Checking tool (which I assume invokes >CHKDSK in the background) or the command line? Or perhaps a third party program? [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Tuesday, January 13, 2004 at 3:14 pm Posted by William Smith (2 messages posted) To get your data back, use a copy of GetDataBack for FAT or GetDataBack for NTFS. This decent program does find all your data - long filenames and directory structures. If you download the shareware version for evaluation you won't be able to copy the files, BUT, it will make an image file for you that you can write to another drive or partition. I am also having this damn corrupt file problem. Numerous small files (all copied to another directory as backup for an XP re-install) report 'Access Denied' and you can't do diddly squat with them. I managed to delete some of them through the command prompt but, others won't work. I'm disecting the file permissions on these and I'm going to investigate the NTFS file system in hex. Bootex.log reports as being corrupt and can't be deleted or opened. Incidently, this is the cause of chkdsk running every time that the system is started from a shutdown. Checkntfs states the drive is 'dirty'. Now, I'm still investigating this but, I am absolutely certain it is in the XP OS software somewhere. I can guarantee that XP is writing invalid info to NTFS - whether it's on shutdown or not I can't be sure but, as others surmise in their posts it is a possibility. I'll post an update to this thread when I find out more. Regards to all, Bill On Tuesday, June 3, 2003 at 2:03 pm, Paul wrote: >Glad to know I'm not imagining it. > >Firstly - any way to recover the files. > >Secondly - any sign of a proper fix yet? > >Cheers > >Paul [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Monday, January 19, 2004 at 1:02 am Posted by Darren Brothers (2 messages posted) Got it! I figured it out! I kept getting the same errors on my second hard drive when running CHKDSK, but only when I had very large files (>4GB) on it. I figured out that WinXP's compression is the cause. I disabled hard drive compression, and CHKDSK ran without any problems. On Friday, October 4, 2002 at 10:02 pm, Paul wrote: >I have a question about Prevent >file corruption problems: > >I have tried running the "new" CHKDSK under Windows XP using both the Error Checking >tool in "My Computer/File/Properties" and from the command line. > >When I used the Error Checking tool (without selecting the Automatic fix of file >system errors or the scan for bad sectors) XP displayed a dialogue with a sequence >of messages, telling me that the Error Checker was performing phase 1 of its check, >then phases 2 and 3 and finally a new dialogue appeared telling me that the check >had been completed - and nothing more. > >When I ran CHKDSK from the command prompt, using the command "CHKDSK C: /V" the output >was more informative: > >"The type of the file system is NTFS. > >WARNING! F parameter not specified. >Running CHKDSK in read-only mode. > >CHKDSK is verifying files (stage 1 of 3)... >File verification completed. >CHKDSK is verifying indexes (stage 2 of 3)... >Index verification completed. >Detected minor inconsistencies on the drive. >CHKDSK is verifying security descriptors (stage 3 of 3) >Cleaning up 33 unused index entries from index >Cleaning up 33 unused index entries from index >Cleaning up 33 unused security descriptors. >Security descriptor verification completed. >CHKDSK is verifying Usn Journal... >Usn Journal verification completed. >Correcting errors in the Volume Bitmap. >Windows found problems with the file system. >Run CHKDSK with the /F (fix) option to correct" > >My question is, which should I trust - the Error Checking tool (which I assume invokes >CHKDSK in the background) or the command line? Or perhaps a third party program? [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Wednesday, January 21, 2004 at 8:58 pm Posted by Zatoichi (3 messages posted) First off... I'm glad I finally found this thread after 10 days of reinstalling windows 2000 on 3 different systems at least 3 times each. I was getting ready to throw all the hardware against the wall! Anyways, I've been experiencing very similar circumstances involving the chkdsk utility of win2k. Running chkdsk on the bootable drive thru the windows desktop almost always concludes in some kind of "file system" problem but, according to this thread it's because some files are open or running off this partition/drive. However, running chkdsk via windows desktop on data partitions/drives would sometimes end up with the same "file system" problems also. My problems started when I redid my system after installing a used motherboard. I had 2 hard drives attached to the board. Drive 1 had 2 partitions. Partition 1 was the boot drive, and partition 2 was the data drive. After reformatting both partitions of drive 1, I powered down and attached drive 2 as a slave. Drive 2 held all my saved data from my previous setup and other computer (drivers, files, programs, mp3's, divx movies, etc.). My plan was to copy all the saved files from drive 2 and create a duplicate set on partition 2 of drive 1. I attempted this by right-clicking the mouse and using "copy" & "paste" on directories I wanted to duplicate. The directories varied in size but could get as large as 40gigs for one directory. During the process some directories & files were corrupted and subsequently lost. This got me started on a chkdsk frenzy. I'd run chkdsk just to run chkdsk and found that I had these weird file system errors on one or all drives. If one partition or drive checked out ok/good one time, the next day it would check out bad with a file system error. "What's up with that?" I've been talking to people & searching the net and this thread is probably one of the best informational support groups on this problem. For the people with boot problems: a friend of mine said he experienced similar boot problems and his internet research resulted in information regarding using NTFS on hard drives which had previous installations of windows98se & FAT32 installed. Apparently, a NTFS installation will somehow detect the remnants of a fat32 boot sector resulting in the system not booting. Does this sound right? Is this possible? He then suggested to only use NTFS on brand new hard drives with no prior fat32 installations. He's followed this strategy and it's worked out for him. Unfortunately for me, I can't afford to buy a new hard drive every time I want to change an OS. I mentioned this situation to another friend that works in I.T. and he suggested using a utility that supposedly will totally wipe a drive clean called "kill fdisk" or something. At the place he works, he has dealt with FAT32 hard drives that were changed or converted to NTFS over time and, thus far they have suffered none of the problems mentioned in this thread. (NOTE: my drives had previous FAT32 installations before changing over to win2k & NTFS...coincidence?) In regards to my problem, I just found this article: Microsoft Knowledge Base Article - 327009 (This article was previously published under Q327009) Here's the link: http://support.microsoft.com/default.aspx?scid=kb;EN-US;327009 I'm hoping this is helpful to anyone as well as me. It involves similar messages/problems I'm receiving so I've posted it for people. It mentions something about transferring a large number of files which result in security descriptor errors & file system corruption that chkdsk will find. These are supposedly minor index problems that arise when the original files have certain security features enabled by a user and these files get copied or transferred over to another drive. For some reason when the files get moved over to another system, those security features that were enabled via the prior computer system, are by default not enabled on the new computer they were transplanted to. Subsequently, this results in these errors. Does this make sense to anyone? Hopefully someone can shed some more light on the subject. I'm only posting here so that people can build on this info and provide more insight. I really don't want to go back to FAT32. Hope This Helps Someone, Ed On Friday, October 4, 2002 at 10:02 pm, Paul wrote: >I have a question about Prevent >file corruption problems: > >I have tried running the "new" CHKDSK under Windows XP using both the Error Checking >tool in "My Computer/File/Properties" and from the command line. > >When I used the Error Checking tool (without selecting the Automatic fix of file >system errors or the scan for bad sectors) XP displayed a dialogue with a sequence >of messages, telling me that the Error Checker was performing phase 1 of its check, >then phases 2 and 3 and finally a new dialogue appeared telling me that the check >had been completed - and nothing more. > >When I ran CHKDSK from the command prompt, using the command "CHKDSK C: /V" the output >was more informative: > >"The type of the file system is NTFS. > >WARNING! F parameter not specified. >Running CHKDSK in read-only mode. > >CHKDSK is verifying files (stage 1 of 3)... >File verification completed. >CHKDSK is verifying indexes (stage 2 of 3)... >Index verification completed. >Detected minor inconsistencies on the drive. >CHKDSK is verifying security descriptors (stage 3 of 3) >Cleaning up 33 unused index entries from index >Cleaning up 33 unused index entries from index >Cleaning up 33 unused security descriptors. >Security descriptor verification completed. >CHKDSK is verifying Usn Journal... >Usn Journal verification completed. >Correcting errors in the Volume Bitmap. >Windows found problems with the file system. >Run CHKDSK with the /F (fix) option to correct" > >My question is, which should I trust - the Error Checking tool (which I assume invokes >CHKDSK in the background) or the command line? Or perhaps a third party program? [Reply or follow-up to this message] Sins of NTFS Thursday, January 22, 2004 at 8:22 pm Posted by Down For The Count (4 messages posted) I come here, frequently now. I find some comfort in knowing I am not alone. I am truly sad however that I along with so many others have lost our beloved systems. I know I probably shouldn’t but I keep asking: what have I done to my system to deserve this? I have read and reread the epitaphs looking for a reason for all this but I find none. Grasping for meaning to grab hold of. I find none except that we all fell prey to running after Microsoft. I feel punished as I recall my decision to abandon more open systems. Oh sure, they weren’t perfect but I can’t help but feel my files would still be here if I had not given in to the seduction of Microsoft. I am tormented, daily now, to recall the good times with little hope of seeing them again. Those times when I shared files and happily listened to MP3s and knew my personal data was safe. My files now are corrupt, dirty and unusable. I cannot bear to tell anyone about my failings for fear they will think I am not geek enough. Sadly, Microsoft is silent on this subject while perhaps thousands suffer. You know they know. And every day more and more files, entire folders of files disappear from the face of this Earth with barely a cryptic display from CHKDSK. Sometimes I think it would be better to just have it all go at once. And yet, I visit nearly daily. Hoping against hope that someone will emerge with an answer to answer everyone: why my system? [Reply or follow-up to this message] My Xperience ! Monday, January 26, 2004 at 12:17 am Posted by ZeVs (2 messages posted) I've read all the thread, and I tried to solve the problem by doing the following: - Revert my filesystem back to FAT32 - Disable ACPI in bios - Change "ACPI computer" to "standard computer" in windows - Disable Hard Drive cache ==> ON each shutdown I STILL HAVE REGISTRY CORRUPTION. I need to reinstall Windows on EACH BOOT ATTEMPT !! It doesn't seems to be a NTFS problem. Do u know how I should troubleshoot ? I've looked the windows eventviewer but no errors appears. any idea is really welcome. Thanks a lot [Reply or follow-up to this message] re: My Xperience ! Tuesday, January 27, 2004 at 9:10 pm Posted by Down For The Count (4 messages posted) Are you actually trying to use the computer? I have found that in not using the computer the problem seems to go away. It is very worrysome this issue manifests from so many perceived "poor settings". This sure makes it seems as though XP an 2K are quirky and fickle. I might suggest you go back to Windows 3.1 as nobody reports problems with that platform. (Can't beat logic like that can you.) But before you do that, take a look at these and see how it might apply to your situation (hint: don't think there is only one cause as there is likely multiple given the reports here) http://support.microsoft.com/default.aspx?scid=kb;en-us;310841 http://webspiffy.com/archives/2002/08/ntfs_file_system_glitch I myself have: *disabled write cache (property for the drive) *turned off indexing (how did that get turned back on) *adjusted my power setting although i did not see it as an issue *reloaded sp4 and ensuing hotfixes *dropped my controller and drives drivers to get a new plug and play take on the world *reset my bios to make it forget whatever it might want to remember *disabled block mode io for the drives *prayed One cannot seem to say with fidelity the problem is conclusively gone but one can certainly know when the problem is at hand. On Monday, January 26, 2004 at 12:17 am, ZeVs wrote: > >I've read all the thread, and I tried to solve the problem by doing the following: > >- Revert my filesystem back to FAT32 >- Disable ACPI in bios >- Change "ACPI computer" to "standard computer" in windows >- Disable Hard Drive cache > >==> ON each shutdown I STILL HAVE REGISTRY CORRUPTION. I need to reinstall Windows >on EACH BOOT ATTEMPT !! > >It doesn't seems to be a NTFS problem. Do u know how I should troubleshoot ? I've >looked the windows eventviewer but no errors appears. any idea is really welcome. >Thanks a lot [Reply or follow-up to this message] Win2000 BSOD on chkdsk Thursday, January 29, 2004 at 1:11 pm Posted by Philip Sargent (Klebos) (6 messages posted) Hmm. I have a Win2000 SP4 with a 40GB hard drive, partitioned as 2 x 20GB C: and D:, both NTFS. For months, since last July at least (certainly pre-SP4, probably pre-SP3) it has crashed with BSOD whenever I attemped chkdsk on C: (D: has always been fine). It does this on startup, and if I use /I. The BSOD is STOP 0x__44 MULTIPLE_IRP_COMPLETE_REQUESTS and it happens at about 73% of Stage 1 of chkdsk. It also happens when I try to use the disc defragmentor - it fails in the "analyse" step. Other than that the machine works fine, except that occasionally it crashes with BSOD when a large file is being copied on C:, or I use the treesize free utility, or if I try to virus-scan a large part of C: That BSOD is STOP0x__1D IRQL_NOT_EQUAL Checks with other utilites, I have tried Knoppix and Partition Magic 5.01 all say that C: is a nice clean NTFS with no problems. Does anyone have a clue? Philip [Reply or follow-up to this message] Missing file/ Run chkdsk Saturday, January 31, 2004 at 7:28 am Posted by Flywolf (1 messages posted) I am getting a diffrent problem with CHKDSK running itself everytime or once every 2 to 3 times I start windows XP, it mention recovering lost files, correcting error with $I30 file 8949, anyone else getting this problem?, any ideas?..thanks [Reply or follow-up to this message] I Think I Got It - Inner Peace Monday, February 2, 2004 at 10:04 am Posted by Down For The Count (4 messages posted) I have made one more adjustment. This one in the area of the IDE channel I/O method. I changed it to "PIO Only",was UDMA. In W2K this found System/Device Manager/IDE ATAPI Controllers/Channel/Advanced Settings It seems to me UDMA should have worked - but hey maybe there is a timing issue working at that speed. I personnally think this is a bug that came in over the last year or so and hasn't been fixed. Wasn't the cables...changed those 'bout a 1/2 year ago. And while this has negatively affected the overall disk throughput, when I factor in all of the work to recover things...I am still far ahead. Heck I could have used a pen and paper for read/write operations and stayed ahead with all this has cost me. I think I finally have inner system peace. [Reply or follow-up to this message] Inner System Peace Tuesday, February 3, 2004 at 9:25 am Posted by Down For The Count (4 messages posted) As I posted earlier I have been changing a thing or two at a time to shake this out. Last change made was to see if it was somewhere in the IDE settings. I had set the devices on both channels to PIO. The problem POOF ... disappeared. I then inched up from PIO to DMA to UDMA mode 4, 66MB. I think I am sitting good here. I actually think now there is an issue with this AWARD BIOS that has an issue running at UDMA mode 5 which the drive is capable of. I was a bit concerned working in this area as it is a bit of a black-art. I think I should be able to do mode 5 and I may look into a BIOS update. Or not. That could shake another bolt loose. So hopefully this helps someone. [Reply or follow-up to this message] If you have overclocked your system Saturday, February 7, 2004 at 12:23 am Posted by Jonathan (1 messages posted) Hi all, I did experince file corruption problem including corrupted files, loss of files, corrupted hibernation file... for years on my system. I thought it was Window's bug or it was aging problem of my pretty old system. I have download patches, latest drivers and changed registry but it don't solve the problem. I did backup my system registry files to restore my system in case there was system file corruption. I used to overclock by CPU (600@927), overclock my RAM (CL2=>CL3) and optimized my mainbroad. I do run through stability and burn in testes to ensure that my system is "stable", so I did not think it would any data corruption problem. Fortunately, I turned out to find this forum and some posts indicated that the problem may be caused by setting in mainbroad. So did the following change; 1. Restored all the default settings of my mainbroad 2. RAM changed back to CL3 The data corruption problem went away and I can now hibernate my computer (no hibernate file corruption anymore). I can now even overclock my CPU to 945MHz and the system still run stable without file corruption problem. That is my own experience and it may just happen to be good for my own computer configuration. Hope this would provide some hints for you guys to solve the problem. On Monday, January 26, 2004 at 12:17 am, ZeVs wrote: > >I've read all the thread, and I tried to solve the problem by doing the following: > >- Revert my filesystem back to FAT32 >- Disable ACPI in bios >- Change "ACPI computer" to "standard computer" in windows >- Disable Hard Drive cache > >==> ON each shutdown I STILL HAVE REGISTRY CORRUPTION. I need to reinstall Windows >on EACH BOOT ATTEMPT !! > >It doesn't seems to be a NTFS problem. Do u know how I should troubleshoot ? I've >looked the windows eventviewer but no errors appears. any idea is really welcome. >Thanks a lot [Reply or follow-up to this message] I found the problem :) Saturday, February 7, 2004 at 6:36 am Posted by ZeVs (2 messages posted) I've just found my problem, when I replaced my no-name DDR chip with a high end Corsair memory module, all problems were suddendly solved... But, all the tests I ran on noname memory chips (WMemtest86, Windows Memory Diagnostic, DocMem RAM Diagnostic) were all tellling me that the chips were perfect.... [Reply or follow-up to this message] re: I found the problem :) Monday, February 16, 2004 at 10:15 am Posted by Hopeless (1 messages posted) Mmmmm... I have the same problem with an Asus A7N8X. The problem in fact could be in DDR module because every so the MB send a warning message about ram but system work correctly... I'll try to change my ram module too. On Saturday, February 7, 2004 at 6:36 am, ZeVs wrote: >I've just found my problem, when I replaced my no-name DDR chip with a high end Corsair >memory module, all problems were suddendly solved... > >But, all the tests I ran on noname memory chips (WMemtest86, Windows Memory Diagnostic, >DocMem RAM Diagnostic) were all tellling me that the chips were perfect.... > [Reply or follow-up to this message] Zatoichi Update: The Solution To My Problems...Maybe? Tuesday, February 24, 2004 at 6:49 pm Posted by Zatoichi (3 messages posted) My solution is sort of a guess. But, bear in mind, I've never worked in I.T. and I have no professional computer training. This fix is only based on 8 years of building and troubleshooting computers. But so far, the problems I had seem to have disappeared. Anyways, I redid all my computers with Win2k...again! First, I made sure to remove/undo any windows user/security/password protected data I had. I did this because I thought it would solve the chkdsk utility errors I described in my original post. (My guess is, this was the source of my problems) Then, I transferred that backup data to a NTFS formatted storage drive. To format the backup storage drive I used a demo utility called KillDisk. Here's the link: http://www.killdisk.com/downloadfree.htm Using Killdisk, I did a secure erase (refer to downloadable Killdisk PDF manual). The MFT/partition table is destroyed and zeros are written to the whole drive. This process took 4hrs for a 120gb drive, and 2.5 hours each for two 80gb drives. Kind of long, but it basically returns the drive into a "fresh from the factory state." Using Killdisk was a solution to the "remnant win98se fat32 boot sector" I described in my original post. After my data was backed up. I used KillDisk on both boot/system drives (the two 80gig drives) and used the same secure erase feature. When all the drives were erased, I then used the Western Digital hard drive installation utility to partition and format all drives. Afterwards, I resetup both computers by installing Win2k and retransferred my backup data to each system. One computer has been on 24 hrs a day, the other computer gets used daily 12hrs a day. It's been 4 weeks, and so far, there haven’t been any problems. I can't pinpoint which part of my solution fixed the errors, but I'm glad that they seem to be gone. (Note: I had to use the Western Digital partition/format utility because the Win2k partition utility during OS installation would not work right. For some reason, Win2k could not resize the drives to smaller partitions. This might be due to using the KillDisk utility. If you have a different brand hard drive, download a similar partition/reformat utility from your manufacture's website and use that instead. This step might be unnecessary if you don't use multiple partitions on a single hard drive.) Hope This Helps, Ed Daly City, California On Wednesday, January 21, 2004 at 8:58 pm, Zatoichi wrote: >First off... I'm glad I finally found this thread after 10 days of reinstalling windows >2000 on 3 different systems at least 3 times each. I was getting ready to throw all >the hardware against the wall! > >Anyways, I've been experiencing very similar circumstances involving the chkdsk utility >of win2k. Running chkdsk on the bootable drive thru the windows desktop almost always >concludes in some kind of "file system" problem but, according to this thread it's >because some files are open or running off this partition/drive. However, running >chkdsk via windows desktop on data partitions/drives would sometimes end up with >the same "file system" problems also. >My problems started when I redid my system after installing a used motherboard. I >had 2 hard drives attached to the board. Drive 1 had 2 partitions. Partition 1 was >the boot drive, and partition 2 was the data drive. After reformatting both partitions >of drive 1, I powered down and attached drive 2 as a slave. Drive 2 held all my saved >data from my previous setup and other computer (drivers, files, programs, mp3's, >divx movies, etc.). My plan was to copy all the saved files from drive 2 and create >a duplicate set on partition 2 of drive 1. I attempted this by right-clicking the >mouse and using "copy" & "paste" on directories I wanted to duplicate. The directories >varied in size but could get as large as 40gigs for one directory. During the process >some directories & files were corrupted and subsequently lost. This got me started >on a chkdsk frenzy. I'd run chkdsk just to run chkdsk and found that I had these >weird file system errors on one or all drives. If one partition or drive checked >out ok/good one time, the next day it would check out bad with a file system error. >"What's up with that?" I've been talking to people & searching the net and this thread >is probably one of the best informational support groups on this problem. > >For the people with boot problems: a friend of mine said he experienced similar boot >problems and his internet research resulted in information regarding using NTFS on >hard drives which had previous installations of windows98se & FAT32 installed. Apparently, >a NTFS installation will somehow detect the remnants of a fat32 boot sector resulting >in the system not booting. Does this sound right? Is this possible? He then suggested >to only use NTFS on brand new hard drives with no prior fat32 installations. He's >followed this strategy and it's worked out for him. Unfortunately for me, I can't >afford to buy a new hard drive every time I want to change an OS. >I mentioned this situation to another friend that works in I.T. and he suggested >using a utility that supposedly will totally wipe a drive clean called "kill fdisk" >or something. At the place he works, he has dealt with FAT32 hard drives that were >changed or converted to NTFS over time and, thus far they have suffered none of the >problems mentioned in this thread. >(NOTE: my drives had previous FAT32 installations before changing over to win2k & >NTFS...coincidence?) > >In regards to my problem, I just found this article: Microsoft Knowledge Base Article >- 327009 (This article was previously published under Q327009) >Here's the link: http://support.microsoft.com/default.aspx?scid=kb;EN-US;327009 >I'm hoping this is helpful to anyone as well as me. It involves similar messages/problems >I'm receiving so I've posted it for people. It mentions something about transferring >a large number of files which result in security descriptor errors & file system >corruption that chkdsk will find. These are supposedly minor index problems that >arise when the original files have certain security features enabled by a user and >these files get copied or transferred over to another drive. For some reason when >the files get moved over to another system, those security features that were enabled >via the prior computer system, are by default not enabled on the new computer they >were transplanted to. Subsequently, this results in these errors. Does this make >sense to anyone? Hopefully someone can shed some more light on the subject. I'm only >posting here so that people can build on this info and provide more insight. I really >don't want to go back to FAT32. > >Hope This Helps Someone, > >Ed > > > [Reply or follow-up to this message] Zatoichi Update: The Solution To My Problems...Maybe? Tuesday, February 24, 2004 at 6:54 pm Posted by Zatoichi (3 messages posted) My solution is sort of a guess. But, bear in mind, I've never worked in I.T. and I have no professional computer training. This fix is only based on 8 years of building and troubleshooting computers. But so far, the problems I had seem to have disappeared. Anyways, I redid all my computers with Win2k...again! First, I made sure to remove/undo any windows user/security/password protected data I had. I did this because I thought it would solve the chkdsk utility errors I described in my original post. (My guess is, this was the source of my problems) Then, I transferred that backup data to a NTFS formatted storage drive. To format the backup storage drive I used a demo utility called KillDisk. Here's the link: http://www.killdisk.com/downloadfree.htm Using Killdisk, I did a secure erase (refer to downloadable Killdisk PDF manual). The MFT/partition table is destroyed and zeros are written to the whole drive. This process took 4hrs for a 120gb drive, and 2.5 hours each for two 80gb drives. Kind of long, but it basically returns the drive into a "fresh from the factory state." Using Killdisk was a solution to the "remnant win98se fat32 boot sector" I described in my original post. After my data was backed up. I used KillDisk on both boot/system drives (the two 80gig drives) and used the same secure erase feature. When all the drives were erased, I then used the Western Digital hard drive installation utility to partition and format all drives. Afterwards, I resetup both computers by installing Win2k and retransferred my backup data to each system. One computer has been on 24 hrs a day, the other computer gets used daily 12hrs a day. It's been 4 weeks, and so far, there haven’t been any problems. I can't pinpoint which part of my solution fixed the errors, but I'm glad that they seem to be gone. (Note: I had to use the Western Digital partition/format utility because the Win2k partition utility during OS installation would not work right. For some reason, Win2k could not resize the drives to smaller partitions. This might be due to using the KillDisk utility. If you have a different brand hard drive, download a similar partition/reformat utility from your manufacture's website and use that instead. This step might be unnecessary if you don't use multiple partitions on a single hard drive.) Hope This Helps, Ed Daly City, California On Friday, October 4, 2002 at 10:02 pm, Paul wrote: >I have a question about Prevent >file corruption problems: > >I have tried running the "new" CHKDSK under Windows XP using both the Error Checking >tool in "My Computer/File/Properties" and from the command line. > >When I used the Error Checking tool (without selecting the Automatic fix of file >system errors or the scan for bad sectors) XP displayed a dialogue with a sequence >of messages, telling me that the Error Checker was performing phase 1 of its check, >then phases 2 and 3 and finally a new dialogue appeared telling me that the check >had been completed - and nothing more. > >When I ran CHKDSK from the command prompt, using the command "CHKDSK C: /V" the output >was more informative: > >"The type of the file system is NTFS. > >WARNING! F parameter not specified. >Running CHKDSK in read-only mode. > >CHKDSK is verifying files (stage 1 of 3)... >File verification completed. >CHKDSK is verifying indexes (stage 2 of 3)... >Index verification completed. >Detected minor inconsistencies on the drive. >CHKDSK is verifying security descriptors (stage 3 of 3) >Cleaning up 33 unused index entries from index >Cleaning up 33 unused index entries from index >Cleaning up 33 unused security descriptors. >Security descriptor verification completed. >CHKDSK is verifying Usn Journal... >Usn Journal verification completed. >Correcting errors in the Volume Bitmap. >Windows found problems with the file system. >Run CHKDSK with the /F (fix) option to correct" > >My question is, which should I trust - the Error Checking tool (which I assume invokes >CHKDSK in the background) or the command line? Or perhaps a third party program? [Reply or follow-up to this message] re: Zatoichi Update: The Solution To My Problems...Maybe? Monday, March 8, 2004 at 4:22 am Posted by Ronald (2 messages posted) OK, so far the issue seems to crop up with both windows 2000 and XP. It seems mostly related to large hard drives, even though some have it only with 120GB or higher, others report it as well with 40 and 60 GB. Things that help some people: -applying windows xp patch -not applying all OS patches at the same time -switching to fat32 -switching to non-acpi system ("It is now safe to turn of..") -switching from UDMA to PIO mode Except the first one, all of these are workarounds that impair functionality some way or another. According to this thread, it seems there is some major issue with timings in the OS, involving write caches to the disk on shutdown. This grows bigger with both larger memory and larger and faster hard drives. (makes sense somehow, the bigger the memory, the bigger the chance something doesn't get flushed properly from it) The problem does not seem related to hardware failure, nor to one single OS. I've seen MS knowledge base articles relating this issue back to the good ol' days of NT 4, so it's certainly a longstanding issue that seems to return from time to time. This could mean two things: 1-fundamentally flawed file system 2-continuously flawed implementation I have a similar issue as many others here, my FS was OK until chkdsk decided to screw up about 3000 files which were OK before..mostly jpegs but some movies as well. I also ran virusscans, spyware scans, checkdisks, etc etc. This problem is just too weird. I'm in the process of reinstalling w2k. Understanding from this thread it's not usefull to upgrade to XP. My planning: -revert to previous mobo bios version -test memory extensively with memtest86 -recertify hard drive with factory software -thoroughly clean hard drive for any existing formatting, beofre formatting new -set harddisk to UDMA 5 instead of 6 in the bios -install w2k with sp4 integrated (works flawlessly with previous installs) -disable write caching in the OS for the harddisk -NOT install IE 6 including ie6sp1 -install Directx 9.0b without the TV-card patch -NOT install the latest 5 OS patches (I work with mozilla firefox behind a firewall anyway, so there criticality is less) -use a little tool called 'sync' that's ported from the Unix world to win32. It flushes disk writes to the disk. There is a similar tool from wininternals that flushes the page file. These can both be used in winNT to run automatically during shutdown by using a shutdown script. -not use chkdsk to run manual disk checks, instead I will rely on third-party software. BTW:I tried the getdataback software, but it failed miserably. The jpeg's seem to have all lost their jpeg headers in the process, and I can find no way whatsoever to restore them. There is a similar tool called CIA unerase, if someone wants to try. [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Wednesday, March 17, 2004 at 4:51 am Posted by Jason (1 messages posted) Was your disk larger than 137 GB? Are your corruption troubles definitely gone? On Thursday, October 2, 2003 at 4:23 am, James Tuvix wrote: >Well I think this update solved all my corruption-problems. After installing it I >had no chkdsk at startup any more!! thy to zippy!! > > >On Saturday, September 6, 2003 at 3:21 pm, Zippy wrote: > >>After searching and trying numerous vaguely related patches and fixes from MS I >came >>across Q331958 - 137GB ATAPI driver limit in XP (in all versions of XP upto and >including >>SP1). Id noticed this before but as it said it only applied to Hibernate and kernal >>dumps I hadn't bothered installing it. >> >>To quote from MS "The ATAPI driver for Windows XP Service Pack 1 (SP1) does not >use >>48-bit Logical Block Addressing (LBA) when it writes memory dump files or hibernation >>files. Additionally, the flush cache command is not issued to a large hard disk >that >>has 48-bit LBA enabled when Windows XP enters standby or hibernation" >> >>However I thought I might as well install it - and so far after 10 reboots I havent >>had one chkdsk or any other sign of corruption. >>For anyone thats interested in trying this - >>http://support.microsoft.com/default.aspx?scid=kb;[LN];331958 > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Sunday, March 21, 2004 at 7:29 pm Posted by Matthew (1 messages posted) Alright...I've only been able to read about halfway through these errors and I think I found a solution: http://www.microsoft.com/windowsxp/home/using/productdoc/en/default.asp?url=/windowsxp/home/using/productdoc/en/chkdsk.asp that link shows the various switches, etc. used with CHKDSK. the /x command switch is of special interest since it seems to have the functionality of the /f (fix) switch while still removing the lock on the Hard drive so chkdsk CAN fix the problems. hope it helps. -Matt On Friday, October 4, 2002 at 10:02 pm, Paul wrote: >I have a question about Prevent >file corruption problems: > >I have tried running the "new" CHKDSK under Windows XP using both the Error Checking >tool in "My Computer/File/Properties" and from the command line. > >When I used the Error Checking tool (without selecting the Automatic fix of file >system errors or the scan for bad sectors) XP displayed a dialogue with a sequence >of messages, telling me that the Error Checker was performing phase 1 of its check, >then phases 2 and 3 and finally a new dialogue appeared telling me that the check >had been completed - and nothing more. > >When I ran CHKDSK from the command prompt, using the command "CHKDSK C: /V" the output >was more informative: > >"The type of the file system is NTFS. > >WARNING! F parameter not specified. >Running CHKDSK in read-only mode. > >CHKDSK is verifying files (stage 1 of 3)... >File verification completed. >CHKDSK is verifying indexes (stage 2 of 3)... >Index verification completed. >Detected minor inconsistencies on the drive. >CHKDSK is verifying security descriptors (stage 3 of 3) >Cleaning up 33 unused index entries from index >Cleaning up 33 unused index entries from index >Cleaning up 33 unused security descriptors. >Security descriptor verification completed. >CHKDSK is verifying Usn Journal... >Usn Journal verification completed. >Correcting errors in the Volume Bitmap. >Windows found problems with the file system. >Run CHKDSK with the /F (fix) option to correct" > >My question is, which should I trust - the Error Checking tool (which I assume invokes >CHKDSK in the background) or the command line? Or perhaps a third party program? [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Monday, March 22, 2004 at 8:08 am Posted by voirin (1 messages posted) Im running windows 2003 server and have the same problems you guys are having. chkdsk goes through its usual routine 70% of reboots. Most problems are directed towards C: drive (20Gig) but also on my other drives (60Gig). A few months ago i remember running chkdsk from command line because i was getting all sorts of problems and this wiped out half my data on one of my other drives. Im not using ACPI , just standard PC. I feel sick in my gut using my system. I have got important data and I feel that it will all blow away one day :( Im thinking of doing a reinstall. Maybe reverting back to 2000 server as that was a little more stable. [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Monday, March 22, 2004 at 9:32 pm Posted by Bob Smith (1 messages posted) No. Bootex.log is a file created by chkdsk.exe when it is run; its results are rolled into the main log after the system finished booting. If chkdsk.exe is interrupted, bootex.log can become corrupted. When chkdsk.exe runs again, it tries to write to bootex.log, which is, unfortunately, now corrupt. It doesn't know this until after the check; so even though it was deleted by chkdsk.exe, it was written to in the mean time and is therefore still corrupt. The fix is to run under the Recovery console by either booting from the Windows XP CD or running \i386\winnt32.exe on the Windows XP CD with the argument /cmdcons. When in the console, run chkdsk.exe /p to fix the file. Then type del c:\bootex.log to remove the offending file. Reboot, and all is taken care of. [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Wednesday, March 31, 2004 at 8:23 pm Posted by bradley (1 messages posted) hello, I believe I got some error like this or same as everyone has been getting on this page. My Pc is configured for gaming and I do like to download stuff. My harddrive is split into 2 parts. 1 part is the C: and other is D:. The boot drive is on the C: which I made it separate and whatever else goes on the D:. For the past 2-3 times I have tried to Defrag my drives and on my D:, it says can not defragment drive, run chkdks /f or something along the lines of that. Anytime I boot my pc, chkdsk runs at startup all the time. I am getting really pissed off reinstalling XP just to fix this error. From what I read on some posts above, that this is not a real threat, If it is not, then how will this error go away automatically. Earlier today When I fully typed the error I received when Defragging into a search engine. I found that 1 person had same error that I had. The way he fixed it was formatting his drives and reinstalling XP. How the hell can that be the only way?? Question, what is the command/F Key to hit to get into the Bios Section in Dos. [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Saturday, May 15, 2004 at 8:31 pm Posted by wrenched (2 messages posted) just thought that i would agree with you about changing to fat 32, i did that same thing and everything worked just fine for me . goodluck. auhhhh, im runing an older intell w\ xp 700. On Tuesday, October 22, 2002 at 8:10 am, Mike wrote: >Paul: > >I'm amazed that I have not seen more messages like yours on the Web! > >For the last several months on both of my machines I have experienced problems similar >to yours with my Windows XP Pro boot drives that are formatted with the NTFS file >system. If you're interested I suggest you read Microsoft Knowledge Base Article >Q315688. I'm not endorsing the article per se, however you may want to note their >brief paragraph toward the end of the article, which is titled "NTFS File System >Corruption". It is indicative of the kind of problems I have experienced running >Chkdsk from the command prompt. > >I could go on and on, but I will make only a couple of more points. One, if you call >Microsoft, the techs will probably tell you to load Recovery Console (if you haven't >already; it is not installed by default) in order to correct the Chkdsk reporting >errors. My experience is that as soon as you think you accomplished something with >it (using Chkdsk with the "p" and "r" switches), the problem comes right back. This >is not to suggest that Recovery Console in and of itself is not a good thing. In >fact as I write this I am seriously comtemplating using it to reformat my boot drives >with FAT32. > >The last comment I want to make is that I have recently discovered that in excess >of 20% of my boot drive usage (as reported by various disk utilities) cannot be accounted >for (yes, after making adjustments for page and hibernation files). And, in contradistinction >to the KB article referred to above (note the references to "misreporting of disk >space allocation"), my folder/file sizes compared to "size on disk" is relatively >tight. So who knows what's going on? > >Thanks for providing an outlet for my frustration. Later, > >Mike > > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Tuesday, May 25, 2004 at 12:34 pm Posted by RYAN TOMLINSON (1 messages posted) you should trust what you got in DOS. Nortons' re-writes the code. sometimes, it's not a good thing On Friday, October 4, 2002 at 10:02 pm, Paul wrote: > >I have a question about Prevent >file corruption problems: > >I have tried running the "new" CHKDSK under Windows XP using both the Error Checking >tool in "My Computer/File/Properties" and from the command line. > >When I used the Error Checking tool (without selecting the Automatic fix of file >system errors or the scan for bad sectors) XP displayed a dialogue with a sequence >of messages, telling me that the Error Checker was performing phase 1 of its check, >then phases 2 and 3 and finally a new dialogue appeared telling me that the check >had been completed - and nothing more. > >When I ran CHKDSK from the command prompt, using the command "CHKDSK C: /V" the output >was more informative: > >"The type of the file system is NTFS. > >WARNING! F parameter not specified. >Running CHKDSK in read-only mode. > >CHKDSK is verifying files (stage 1 of 3)... >File verification completed. >CHKDSK is verifying indexes (stage 2 of 3)... >Index verification completed. >Detected minor inconsistencies on the drive. >CHKDSK is verifying security descriptors (stage 3 of 3) >Cleaning up 33 unused index entries from index >Cleaning up 33 unused index entries from index >Cleaning up 33 unused security descriptors. >Security descriptor verification completed. >CHKDSK is verifying Usn Journal... >Usn Journal verification completed. >Correcting errors in the Volume Bitmap. >Windows found problems with the file system. >Run CHKDSK with the /F (fix) option to correct" > >My question is, which should I trust - the Error Checking tool (which I assume invokes >CHKDSK in the background) or the command line? Or perhaps a third party program? [Reply or follow-up to this message] re: Missing file/ Run chkdsk Saturday, May 29, 2004 at 4:24 pm Posted by Chris Martin (1 messages posted) I have just bought a new pc and i am getting chkdsk running itself every 3rd or fourth boot up on xp. I took it back to the builder who said it was a dodgy hard drive. After replacing the hard drive the error still persists! It also puts all the files it corrects into the recycle bin! Its driving me nuts! any help please? On Saturday, January 31, 2004 at 7:28 am, Flywolf wrote: >I am getting a diffrent problem with CHKDSK running itself everytime or once every >2 to 3 times I start windows XP, it mention recovering lost files, correcting error >with $I30 file 8949, anyone else getting this problem?, any ideas?..thanks > > > [Reply or follow-up to this message] re: Missing file/ Run chkdsk Monday, May 31, 2004 at 9:03 am Posted by Jal (1 messages posted) I just found this thread - I see I'm not alone. Just installed XP on my older P3 - I've got two 120GB SATA's (Seagate - boot drive & WD - additional storage) going through a Promise SATA TX2 PCI card - and I cannot install ANY third party defragmenting tool - I've tried PerfectDisk, O&O & Diskeeper - my computer goes into an endless CHDSK loop - where it keeps rebooting and apparently fixing the same errors over and over - I have done 3 complete reinstalls of the OS, but everytime I install a defragmenter it repeats this behaviour - I don't even have to try and do a boot time defrag - just install the 3rd party defrag prog. No disk problems if I use the built in defrag. The HD passes the Powermax tests for Quick, Advanced and Burn-in (20 passes!) So it is not the drive. It's now also started to do funny things with Norton GoBack? It's the POS OS...I am so frustrated! [Reply or follow-up to this message] HD in External Case Experiencing Chkdsk Errors Wednesday, June 2, 2004 at 12:15 am Posted by Ed (3 messages posted) Hello all, I meant to put this on this thread but started another one by accident. Anyway below is what I wrote, plus some extra info since I posted it as a separate thread. Hello all, I've been reading several posts and similar threads. My problem is similar. I am using a Seagate 160 GB Harddrive in an external enclosure and connecting it to my laptop via firewire. I run chkdsk and I get the same errors as othre people have. Such as there being an error present.. and the I30% "filename" blah blah being fixed. It usually doesnt get fixed within XP but only when it's rebooted and runs chkdsk by itself before entering windows. But this again only happens 1 out of 10 times. Most of the time, the system hangs, and the hard drive plods along notoriously slow. Once I left it overnight, and it only increased its progress by 10%. Anyway, here are the solutions I've tried. I reformated with ntfs. Didn't work. I used partition magic to format into fat 32. Then used winxp to convert to ntfs. Didn't work. The only thing I've noticed is that when I turn off the external hard drive before shutting down, then I won't get any chkdsk errors. Also in a related note, I didn't have problems with this drive until I connected a usb mp3 player. I orginally had my harddrive connected via usb. I added the player and started transferring files from the harddrive to the player. After doing that, I noticed for file copies to or from the hard drive, it would sometimes pause midway for minutes at a time. I would play mp3s from my computer and they would stop midway for minutes at a time. Even worse, I noticed some noise was inserted into some of my files so there would be a short high pitched scratching sound in the middle of some songs... and some of my videos became pixelated. I removed the drivers and stuff for the mp3 player and the drive stopped pausing midway through music. However, my files retained the noise. Makes me think, that the usb connection of multiple mass storage units is not completely stable. Any thoughts on either subject appreciated. Extra Information, In the earlier threads, people have mentioned the microsoft article about the 48bit LBA addressing problems with 137 GB drive... I applied the patch.... rebooted, and ran chkdsk. Chkdsk still had to fix files... and it rebooted itself and ran itself and finally fixed everything. After that, I've shutdown three times and run chkdsk each time after I log into xp. So far no problems. I will post an update if the solution keeps working. here are is the windows website for the patch again http://support.microsoft.com/default.aspx?scid=kb;[LN];331958 (has the patch) http://support.microsoft.com/default.aspx?scid=kb;EN-US;303013 (talks about how check if u need the patch) [Reply or follow-up to this message] re: Win2000 BSOD on chkdsk Sunday, June 13, 2004 at 2:46 pm Posted by Philip Sargent (Klebos) (6 messages posted) Found it! The problem was one of several Recycle Bins that belonged to deleted users. These sit in the directories C:\RECYCLER and D:\RECYCLER with directory names which are SIDs i.e. like S-1-5-21-725345543-1993962763-839522115-1014 After I deleted all the ones that did not belong to existing users, I could Analyse and Defragment again on C: - for the first time since last July I think. Philip Sargent On Thursday, January 29, 2004 at 1:11 pm, Philip Sargent (Klebos) wrote: > >Hmm. > >I have a Win2000 SP4 with a 40GB hard drive, partitioned as 2 x 20GB C: and D:, both >NTFS. > >For months, since last July at least (certainly pre-SP4, probably pre-SP3) it has >crashed with BSOD whenever I attemped chkdsk on C: (D: has always been fine). It >does this on startup, and if I use /I. > >The BSOD is STOP 0x__44 MULTIPLE_IRP_COMPLETE_REQUESTS and it happens at about 73% >of Stage 1 of chkdsk. It also happens when I try to use the disc defragmentor - it >fails in the "analyse" step. [snip] [Reply or follow-up to this message] Persistant File ystem Corruption Sunday, June 20, 2004 at 7:49 pm Posted by garbage (1 messages posted) I purchased a Dell Dimension 8250 with XP Pro in February 2003. It has required reformatting & reinstalling dozens of times under XP Pro. I tried all of the suggestions in this thread. All of them seem to work for a short time whereupon the problem reccurs. I can reliably reproduce the fault by simply enabling the indexing service. But disabling it does prevent recurrunces again at some time e.g. doing a large file transfer. I have previously used Linux on this for 6 months using ReiserFS with ZERO file system problems. As soon as I returned it to Xp Pro/NTFS => problems. Dell support response : Wha? Microsoft support response : Wha? I cannot find a solution & must discontiue the use of Microsoft operating systems due to frequent & costly data loss. This is not a M$ bashing exercise, I simply cannot use their OS... [Reply or follow-up to this message] re: Win2000 BSOD on chkdsk Tuesday, October 19, 2004 at 4:13 am Posted by Philip Sargent (Klebos) (6 messages posted) Well, I spoke too soon. It still crashes at 73% Phase 1 on chkdsk. Further investigation using the Seagate disc utilities found some bad sectors: it said "replace your hard disc now". But only the DOS-booting copy, the Seagate Utilities that run under Win2000 don't show any problems. A Hard Disc Repair utility (Russian) also found the same first bad sector. So that seems to be part of the problem too. [Reply or follow-up to this message] re: Win2000 BSOD on chkdsk Thursday, October 21, 2004 at 4:13 pm Posted by Philip Sargent (Klebos) (6 messages posted) It was a hard disc bad sector problem all along. New hard disc (machine was still under warranty - thanks www.woc.co.uk ) so a free replacement. All fine now. [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Sunday, November 21, 2004 at 10:13 pm Posted by hanspeter (1 messages posted) Having experiencing these problems myself, I found a MS URL admitting that you will get spuratic CHKDSK results: "If you run chkdsk without the /f command-line option on an active partition, it might report spurious errors because it cannot lock the drive." I also found MS recommending to only run CHKDSK from the Recovery Console for reliable and consistent results with XP. This seemed to work for me. http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/chkdsk.mspx [Reply or follow-up to this message] Problem solved - System Restore causing false chkdsk errors! Wednesday, December 22, 2004 at 2:36 pm Posted by Jeet Sukumaran (1 messages posted) Hi all. I have been going through a nightmarish time with these chkdsk problems. chkdsk consistently reported errors as described here ... and nothing could fix it ... every time I ran chkdsk, the same errors would get reported. Till I figured it out. It's the System Restore Point files screwing it up, resulting in false alarms raised by chkdsk. Switch of the System Restore facility and run chkdsk ... VOILA! No more corrupted bitmaps or what-have-up. Whew! On Wednesday, July 9, 2003 at 6:28 pm, Keith wrote: >Chkdsk errors – file system errors, problems with the volume bitmap, etc… > >Symptom: chkdsk /f will not fix the errors. > > >My Solution: (It took me days to figure this out. HP could not provide a solution >and I could not find one on the Windows website…. > >Use this solution at your own risk! > >Double click “My Computer” > >Right click on C: (local disk) and then select properties > >Uncheck the box at the bottom where it says allow indexing service to index this >disk… > >Select apply or OK…if you have any errors while the drive is un-indexing select ignore >all. > >Go back to “My Computer” and select C: (local disk) properties again, then select >the tools tab. > >Select “Check Now” and the check the box that says automatically fix file system >errors. > >The computer will prompt you to reboot. > >Reboot the computer…let the checkdisk run and then go back to “My computer” C: (local >disk) properties and check the box (so it’s selected to re-index) to allow indexing >service to index this disk…. > >Select ignore all errors > >Run chkdsk again and it should be clean! > > >You may have to do this again after running widows updates or adding programs! > > > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Monday, January 3, 2005 at 7:58 am Posted by kmgv25a (1 messages posted) I’m running XP with SP2 with dual 250G SATA drives, a single 120G IDE boot drive and am having the same problem. I did not schedule a CHKDSK, but it runs at system boot, gets to the message “CHKDSK is verifying security descriptors (stage 3 of 3)”, then the system stops, leaving that message on the screen. I’ve tried each of the solutions posted in this thread that doesn’t require formatting because I’m trying to keep my data. While none have worked – this has still been a very helpful thread. What has worked is R-Studio NTFS (suggested in an earlier post), which allowed me to at least pull my data off of the drive before formatting it. I guess I’ll now format with FAT 32 and hope for the best. Sorry this isn’t a solution, but it at least helped me get my data back. Like others, I’m amazed that this bug exists and is not only unrepaired but also unadressed by Microsoft. If this were Linux . . . [Reply or follow-up to this message] Missing or corrupted FAT32 files? Saturday, January 15, 2005 at 2:13 pm Posted by lanegs1 (16 messages posted) I, too, have soaked up everything I can from this long thread, but my issue seems related but a bit different. Bootup gives me at least two File Not Found messages for DLL files from the FAT32. I know nothing about what this is or does, but am wondering if there is a way to "reinstall" or "repair" my FAT32? Or is this really a problem? If not, is there a way to eliminate the error messages? Thanks, Lane On Monday, January 3, 2005 at 7:58 am, kmgv25a wrote: >I’m running XP with SP2 with dual 250G SATA drives, a single 120G IDE boot drive >and am having the same problem. >I did not schedule a CHKDSK, but it runs at system boot, gets to the message “CHKDSK >is verifying security descriptors (stage 3 of 3)”, then the system stops, leaving >that message on the screen. I’ve tried each of the solutions posted in this thread >that doesn’t require formatting because I’m trying to keep my data. While none have >worked – this has still been a very helpful thread. > >What has worked is R-Studio NTFS (suggested in an earlier post), which allowed me >to at least pull my data off of the drive before formatting it. I guess I’ll now >format with FAT 32 and hope for the best. Sorry this isn’t a solution, but it at >least helped me get my data back. >Like others, I’m amazed that this bug exists and is not only unrepaired but also >unadressed by Microsoft. If this were Linux . . . [Reply or follow-up to this message] re: Tuesday, January 25, 2005 at 6:43 pm Posted by Tong Narak (3 messages posted) NTFS Directory Corruption with Frequent File Creation Article ID : 169404 Last Review : July 14, 2004 Revision : 1.0 SYMPTOMS A directory in which files are repeatedly created and deleted eventually becomes corrupt. Subsequent attempts to access files in the directory or to create or delete files in the directory yield pop-up window indicating that the directory is corrupt and instructing the user to run CHKDSK. When CHKDSK is run, it generates output like the following (although the specific file record segments affected will vary): Deleting corrupt attribute record (16, "") from file record segment 286. Deleting corrupt attribute record (32, "") from file record segment 286. Deleting corrupt attribute record (48, "") from file record segment 286. Deleting corrupt attribute record (80, "") from file record segment 286. Deleting corrupt attribute record (144, $I30) from file record segment 286. Deleting corrupt file record segment 286. Deleting orphan file record segment 8628. Deleting index entry DirectoryName in index $I30 of file 244. CHKDSK is recovering lost files. CAUSE Multiple attributes associated with a given file have the same attribute instance tag value. This is only likely to happen in directories where many files are repeatedly added and deleted in an "unbalanced" way. RESOLUTION To resolve this problem, you can do one of the following: • Run CHKDSK /f. By running CHKDSK /f, all files contained in a directory that is corrupted in this way should be recovered. CHKDSK is also capable of detecting when instance counts are exceptionally large and will proactively renumber attribute instance values. Specifically, if an attribute instance tag is larger than 0xF000, CHKDSK will send the following message (file number will vary): Adjusting instance tags to prevent rollover on file 252. Thus, by periodically running read-only CHKDSK, it is possible to detect problem directories before they become corrupt. If the above message is encountered while running CHKDSK in read-only mode, you should schedule a full CHKDSK to correct the problem. -or- • To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base: 152734 How to Obtain the Latest Windows NT 4.0 Service Pack STATUS Microsoft has confirmed this to be a problem in Windows NT version 3.51. A supported fix is now available, but has not been fully regression tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information. Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4. MORE INFORMATION Attribute entries within an NTFS File Record Segment (FRS) are labeled with an "instance tag" that must be unique for the attributes in a given FRS. The value for an attribute instance tag is generated when an attribute is created. Thus, typical instance tag values range from 0 to about 10 on most files. If an attribute is deleted and recreated, it receives a new instance tag. Each time a new instance tag is needed, NTFS increments a counter associated with the FRS in question and uses the next previously unused value. Thus, instance tags can grow without bound if attributes are repeatedly destroyed and recreated. For the vast majority of files and directories, the scheme described above does not result in any problems because, once created, FRS attributes tend not to be deleted and recreated. There is one scenario that is known to be an exception. If many files are repeatedly added to a directory and then deleted from the directory in such a way that the "binary tree" that indexes the directory becomes unbalanced, the "index root" attribute for the directory is repeatedly destroyed and re-created. Because instance tags are only 16 bits in size, this means that instance tags can be duplicated after a directory index has been rebalanced 65,535 times. Note that even if instance tags are duplicated, the directory will not be considered corrupt unless, at some point, it contained a sufficiently large enough number of files. Therefore this problem may be difficult to reproduce except in directories containing large numbers of files. [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Wednesday, February 2, 2005 at 11:25 am Posted by Linden Arden (1 messages posted) You seemed to summarize my problems perfectly. I had a massive mp3 collection (30k files or so) and I am always ripping CDs, decompressing SHNs, compressings mp3s and so on. Quite frequently these files are moving back and forth between my networked computers using file sharing. Sometimes the drive is moved from computer to computer (all different OSes) and sometimes it is used as a USB drive. There have been about a dozen times I thought I've lost my entire collection. Sometimes the drive won't get recognized. Sometimes it is recognized but some of my file folders are empty. Sometimes the files are there and play fine. Sometimes I will play one song at Winamp instead plays an entirely different song. I have a relatively up to date backup (its a 200gig backup!) but that drive shows a few errors every now and agan too. Most of my use is through WinXp, but I've had problems with W2k as well. I will need to start doing some experimenting. We'll see how it all works out. >In regards to my problem, I just found this article: Microsoft Knowledge Base Article >- 327009 (This article was previously published under Q327009) >Here's the link: http://support.microsoft.com/default.aspx?scid=kb;EN-US;327009 >I'm hoping this is helpful to anyone as well as me. It involves similar messages/problems >I'm receiving so I've posted it for people. It mentions something about transferring >a large number of files which result in security descriptor errors & file system >corruption that chkdsk will find. These are supposedly minor index problems that >arise when the original files have certain security features enabled by a user and >these files get copied or transferred over to another drive. For some reason when >the files get moved over to another system, those security features that were enabled >via the prior computer system, are by default not enabled on the new computer they >were transplanted to. Subsequently, this results in these errors. Does this make >sense to anyone? Hopefully someone can shed some more light on the subject. I'm only >posting here so that people can build on this info and provide more insight. I really >don't want to go back to FAT32. > >Hope This Helps Someone, > >Ed > > > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Wednesday, February 23, 2005 at 11:52 pm Posted by Mitch (1 messages posted) I see alot of these kinds of problems with Dell systems. It could be one or the other scenario. Dell installs their "Dell Utility" 40 meg fat file system before the NTFS. This causes a problem with MFT defragmentation from Diskkeeper 9.0, because when you reboot to defrag the MFT.... It sees the fat partition [Dell Utility] first, then states that the defrag of the MFT failed. I've had this problem mostly on systems without the Dell Utility fat partition. Or maybe it's the other way around. [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Monday, February 28, 2005 at 4:10 pm Posted by XmadXsickXp:? (1 messages posted) hi all..not sure wat is all about..but let me tell yur..becareful with NORTON GOBACK..or maybe some restore software(not sure)..If u had `em ..after got prob wit yur windows..make sure BEFORE installing new fresh WinXp ..make sure you uninstall it..u gonna loose yur primary slave hard disk . Could be invisible or /no Volume/cant assign new volume letter. DO NOT DELETE!! OR CONVER TO DYNAMIC DISK!!...simply INSTALL NEW FRESH `NTFS` winXp. Then install NORTON GOBACK../RESTART/OPEN NORTON GOBACK /CLIcK RESTORE drIVE/CHECK MY computer/ can u see your Primary Slave Hard Drive?/No more parameter F*****g F not specified/problem solved!! ..yaaaahooo.....and now I realized that fix the prob better than RUN...uhuhuhhuh..Pass it on ..This prob Not typiccal one .could corrupting your hard disk and be happy if it yur present problem or keep it for later on On Friday, October 4, 2002 at 10:02 pm, Paul wrote: > >I have a question about Prevent >file corruption problems: > >I have tried running the "new" CHKDSK under Windows XP using both the Error Checking >tool in "My Computer/File/Properties" and from the command line. > >When I used the Error Checking tool (without selecting the Automatic fix of file >system errors or the scan for bad sectors) XP displayed a dialogue with a sequence >of messages, telling me that the Error Checker was performing phase 1 of its check, >then phases 2 and 3 and finally a new dialogue appeared telling me that the check >had been completed - and nothing more. > >When I ran CHKDSK from the command prompt, using the command "CHKDSK C: /V" the output >was more informative: > >"The type of the file system is NTFS. > >WARNING! F parameter not specified. >Running CHKDSK in read-only mode. > >CHKDSK is verifying files (stage 1 of 3)... >File verification completed. >CHKDSK is verifying indexes (stage 2 of 3)... >Index verification completed. >Detected minor inconsistencies on the drive. >CHKDSK is verifying security descriptors (stage 3 of 3) >Cleaning up 33 unused index entries from index >Cleaning up 33 unused index entries from index >Cleaning up 33 unused security descriptors. >Security descriptor verification completed. >CHKDSK is verifying Usn Journal... >Usn Journal verification completed. >Correcting errors in the Volume Bitmap. >Windows found problems with the file system. >Run CHKDSK with the /F (fix) option to correct" > >My question is, which should I trust - the Error Checking tool (which I assume invokes >CHKDSK in the background) or the command line? Or perhaps a third party program? [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Friday, April 22, 2005 at 8:00 am Posted by Eric Hunsader (1 messages posted) Hello Everyone, I found this thread while researching reasons why my maxtor 250GB drive failed when reading a file from it. I have been using 250GB Hard drives for 2 years (mostly Maxtor, but a few WD), and other than Dead-On-Arrival drives or complete start-up failures, haven't experienced sector/cluster problems -- either the whole drive was dead or it was good -- nothing in-between. Until last evening when I had the read error. Chkdsk reported the same results found throughout this thread. After reading the thread and adding my experience (windows software developer 20 years, plus using lots of 250GB drives for an 8 Terabyte database), I think there are several causes for the failures reported on this thread. The most likely cause for many of them, and the one causing my issue, was the premature shutdown of a dell box that had 4 of the drives (windows 2000 pro). I was reading a read-only file from the problem drive -- in fact, all the files are read-only. I never use Windows indexing, so I wondered how just reading the drive could cause a problem. Then I realized Win2k was updating the Last Access Time on my Read-only files -- duh! From reading documents at MS and elsewhere, I learned that MS optimized the updating of the last access time to once an hour -- or.. could it be -- yes, at shutdown.. Earlier in the day, I was checking devices in Device Manager on that machine and noticed a problem with the Computer Device/Standard Setting, and changed it to ACPI. Then restarted the system (and later in the day shut it down at least once). Any bells ringing? I believe my machine shut down too early and during the time when Windows was updating the last access entries on the read-only files. So I learned how to disable automatic updating on Win2k: change the value of the NtfsDisableLastAccessUpdate registry entry (in HKEY_LOCAL_MACHINE \SYSTEM \CurrentContolSet \Control \Filesystem) to 1. If the entry is not already present in the registry, add it before setting the value. And I set the machine back to Standard PC. And before shutting down, I first log off, then wait until the disk appears quiet. My 2 cents. P.S. I fixed my problem by formatting the drive and copying from the back-up drive (drives only have data, no OS, etc to deal with). Drive appears fine. [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Wednesday, June 1, 2005 at 6:41 pm Posted by B. Wright (1 messages posted) The real problem with this entire thread comes down to NTFS. This filesystem was designed by Veritas under a contract from Microsoft. However, the only tool that Microsoft provides to help fix and manage this filesystem type is chkdsk. There is nothing else (other than third party tools that usually tie right back into chkdsk). At best, this tool is sloppy and haphazard. At worst, it will corrupt the entire volume and is chock full of bugs (like most of the rest of Windows). Even Veritas has come up with better filesystems like vxfs, yet Microsoft won't let them introduce it onto Windows (for who knows what reason) Clearly, Linux has had alternative filesystems for a long time (Reiser, ext3, XFS, JFS, etc) and are very mature and complete filesystems. However, Microsoft has not extended the same courtesy to the Windows users. As a Windows user, you are completely stuck with NTFS or FAT32 as there are no other filesystems supported natively. Worse, if you need security on your files, you're stuck solely with NTFS without any other alternatives. I've worked with NTFS in the past, and it's simply an unstable filesystem when used in a corporate heavy use environment. We ran a very large database and file sharing on two different Dell boxes under Windows. We would consistently have blue screens based on corrupted volume messages which would require chkdsk to fix the filesystems. I would spend hours chkdsk'ing the volumes 2, 3, 4 and even 5 times in a row before I could get one clean pass. We finally decided that NTFS was not-ready-for-primetime in a production environment and abandoned Windows for Linux. Since that decision, we've had no more problems with crashing because of the filesystem or problems resulting from the filesystem. If a Linux system does lockup or go down hard (for whatever reason) filesystem recovery is easy and painless (thanks to mature filesystems under Linux). For corporate desktops and home use, NTFS is fine. But, when you're jamming hundreds of thousands of files in a directory continually or utilizing heavy read/writing in a database environment, NTFS is a disaster waiting to happen. I ultimately believe we were continually running out of MFT space (NTFS's version of the FAT table) without errors stating this fact. So, the MFT became corrupted causing the blue screen, then, subsequently, requiring an extended chkdsk process that might not even complete. If you value your data, you should opt for a system like a Network Appliance system that offers snapshot recovery. If you must use NTFS, then I recommend you back up your data as frequently as is feasibly possible. I just can't recommend a heavy use fileserver formatted as NTFS in a production environment simply based on past experiences. [Reply or follow-up to this message] re: Problem solved - System Restore causing false chkdsk errors! Monday, June 27, 2005 at 10:01 am Posted by thegigglerx (4 messages posted) Thanks for your idea - I'v tried it but unfortunately it hasn't resolved the problem on my pc and 'chkdsk' error remains. If you have any other ideas they would be much appreciated... (Before I rip XP out of pc!!!) On Wednesday, December 22, 2004 at 2:36 pm, Jeet Sukumaran wrote: >Hi all. I have been going through a nightmarish time with these chkdsk problems. >chkdsk consistently reported errors as described here ... and nothing could fix it >... every time I ran chkdsk, the same errors would get reported. > >Till I figured it out. > >It's the System Restore Point files screwing it up, resulting in false alarms raised >by chkdsk. Switch of the System Restore facility and run chkdsk ... VOILA! No more >corrupted bitmaps or what-have-up. > >Whew! > > > [Reply or follow-up to this message] NTFS Dynamic Disk problems Monday, August 15, 2005 at 8:41 am Posted by JASC^ (24 messages posted) Hello, I think my problem fits best on this thread: I'm a subscriber to PC Magazine's daily tip e-mailing, and I read the article on optimizing Windows XP Disk Performance http://www.pcmag.com/article2/0,1895,1845189,00.asp). I followed the instructions very, very carefully. I opened the disk management console, and changed my only hard drive to be a dynamic disk on my Windows XP OS. After the changing process, 8MB of unallocated space appeared on the disk management console. I allocated it into my second hard drive partition (D), as guided on the article. Nevertheless, a new mysterious partition, G (in addition to my boot-partition C and second partition D) appeared. I couldn’t open this new partition, since Windows claimed it was not formatted. I didn’t format it. The “properties” window claimed its file system to be RAW – not NTFS, as my other partitions were. It claimed that the partition held no data – 0 bytes. I followed PC Magazine’s instructions, or more appropriately, got reminded to check the hard drive for errors – Windows was reporting that one of my programs currently running had corrupted files in its folder and I should run chkdsk. I checked both options (the first concerning automatic fixing and the second that attempts scan and recovery of bad sectors), and Windows wanted to restart, so that I could also check the files in use. That’s what I did, but I never got so far. At the first splash screen of Windows loading, the computer restarted. It gave me five options – to start windows normally, in safe mode, in safe mode with networking or the command prompt, or revert to the last settings that worked. None of these did any good, the computer kept rebooting after the splash screen of WinXP had appeared. When attempting to load to safe mode, it loaded a bunch of text onto the screen, and it was loading something, but then restarted. Then I tried something else – before the five options appeared, I opened the BIOS, and changed the primary booting source from the floppy drive to my cd drive. Then I saved the changes and exited BIOS, and after it restarted due to BIOS changes, I inserted the WinXP Professional cd so that it would boot from it. I opened the Windows setup, and I took the option to repair an existing Windows installation with the recovery console. I ran chkdsk in the recovery console to both C and D, as the one I earlier scheduled at restart never begun, because the computer restarted before Windows got to it. It complained something about the file system (I cannot recall), but ran anyway -- both partitions claimed to have one or more problems on the disk. I ran them once more, and exited the recovery console, after which Windows XP booted normally. I worked on it normally – installed a new program and did text processing. But the next day when I opened my computer again, the same boot problem appeared. I did the same thing as I did earlier, and the computer booted to windows again. But this time my SoundBlaster Live! sound card didn’t produce any sound – instead all I heard was beeps from the internal system beeper. I couldn’t see any start menu, either, and Windows Media Player refused to open due to lack of memory, as it told me in an error message. Disk manager was unable to work, and System Restore refused to work as well, although I restarted the computer (this time with no boot problems) as it told me to do. I tried to restart the display theme and reset taskbar settings to regain the taskbar & start menu, without success. There was a faint bar on the bottom of the screen, I tried to drag it up, but it didn’t respond to my dragging. I right-clicked on the bar and got the normal menu that you’d get when right-clicking on the taskbar. I checked Toolbars -> Desktop, and I could now see the start menu, but the taskbar wasn’t operating as it should, but showing the Desktop’s contents. Undoing the checking just made the start menu re-disappear. In addition, my PCI Wireless internet card wasn’t recognized, although it showed to be present in the device manager, and so I couldn’t connect to my broadband Wi-Fi 802.11g network. Items didn’t always open up properties-boxes, things didn’t appear properly, it felt, and still feels, as if the whole computer was coming down. To ease matters, I’ll attach my system specs to the bottom. System Specs: - Intel Pentium 4 with HyperThreading @ 3.0GHz. - 1024MB RAM - Maxtor 6Y160M0 160GB S-ATA Hard Drive, 4 months old - ATI (Club 3d) Radeon 9800 Pro 256MB - SoundBlaster Live! audio card - Intel D865PERL Motherboard - Windows XP Professional [Reply or follow-up to this message] re: NTFS Dynamic Disk problems Monday, August 15, 2005 at 3:45 pm Posted by thegigglerx (4 messages posted) Hello. Ta for all info. I've replaced a perfectly ok harddrive because of these errors. Could they just be completely 'misreported' errors - as they are there one minute, gone the next?!! As my pc is stable at mo...I'm wondering if 'chkdsk' is winding me up... and on checking 'bootex log' in root, all appears clear there. No errors are reported in the log. On Monday, August 15, 2005 at 8:41 am, JASC^ wrote: >Hello, I think my problem fits best on this thread: > >I'm a subscriber to PC Magazine's daily tip e-mailing, and I read the article on >optimizing Windows XP Disk Performance http://www.pcmag.com/article2/0,1895,1845189,00.asp). >I followed the instructions very, very carefully. I opened the disk management console, >and changed my only hard drive to be a dynamic disk on my Windows XP OS. After the >changing process, 8MB of unallocated space appeared on the disk management console. >I allocated it into my second hard drive partition (D), as guided on the article. > >Nevertheless, a new mysterious partition, G (in addition to my boot-partition C and >second partition D) appeared. I couldn’t open this new partition, since Windows claimed >it was not formatted. I didn’t format it. The “properties” window claimed its file >system to be RAW – not NTFS, as my other partitions were. It claimed that the partition >held no data – 0 bytes. > >I followed PC Magazine’s instructions, or more appropriately, got reminded to check >the hard drive for errors – Windows was reporting that one of my programs currently >running had corrupted files in its folder and I should run chkdsk. I checked both >options (the first concerning automatic fixing and the second that attempts scan >and recovery of bad sectors), and Windows wanted to restart, so that I could also >check the files in use. That’s what I did, but I never got so far. At the first splash >screen of Windows loading, the computer restarted. It gave me five options – to start >windows normally, in safe mode, in safe mode with networking or the command prompt, >or revert to the last settings that worked. None of these did any good, the computer >kept rebooting after the splash screen of WinXP had appeared. When attempting to >load to safe mode, it loaded a bunch of text onto the screen, and it was loading >something, but then restarted. > >Then I tried something else – before the five options appeared, I opened the BIOS, >and changed the primary booting source from the floppy drive to my cd drive. Then >I saved the changes and exited BIOS, and after it restarted due to BIOS changes, >I inserted the WinXP Professional cd so that it would boot from it. I opened the >Windows setup, and I took the option to repair an existing Windows installation with >the recovery console. I ran chkdsk in the recovery console to both C and D, as the >one I earlier scheduled at restart never begun, because the computer restarted before >Windows got to it. It complained something about the file system (I cannot recall), >but ran anyway -- both partitions claimed to have one or more problems on the disk. >I ran them once more, and exited the recovery console, after which Windows XP booted >normally. I worked on it normally – installed a new program and did text processing. > >But the next day when I opened my computer again, the same boot problem appeared. >I did the same thing as I did earlier, and the computer booted to windows again. >But this time my SoundBlaster Live! sound card didn’t produce any sound – instead >all I heard was beeps from the internal system beeper. I couldn’t see any start menu, >either, and Windows Media Player refused to open due to lack of memory, as it told >me in an error message. Disk manager was unable to work, and System Restore refused >to work as well, although I restarted the computer (this time with no boot problems) >as it told me to do. I tried to restart the display theme and reset taskbar settings >to regain the taskbar & start menu, without success. There was a faint bar on the >bottom of the screen, I tried to drag it up, but it didn’t respond to my dragging. >I right-clicked on the bar and got the normal menu that you’d get when right-clicking >on the taskbar. I checked Toolbars -> Desktop, and I could now see the start menu, >but the taskbar wasn’t operating as it should, but showing the Desktop’s contents. >Undoing the checking just made the start menu re-disappear. In addition, my PCI Wireless >internet card wasn’t recognized, although it showed to be present in the device manager, >and so I couldn’t connect to my broadband Wi-Fi 802.11g network. Items didn’t always >open up properties-boxes, things didn’t appear properly, it felt, and still feels, >as if the whole computer was coming down. > >To ease matters, I’ll attach my system specs to the bottom. > >System Specs: >- Intel Pentium 4 with HyperThreading @ 3.0GHz. >- 1024MB RAM >- Maxtor 6Y160M0 160GB S-ATA Hard Drive, 4 months old >- ATI (Club 3d) Radeon 9800 Pro 256MB >- SoundBlaster Live! audio card >- Intel D865PERL Motherboard >- Windows XP Professional [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Thursday, October 13, 2005 at 1:08 am Posted by Eileen Goodall (1 messages posted) When using the chkdsk command I normally use: CHKDSK /f This seems to always sort out any problems that the system may have come up against. Recently had problem on Mozilla that kept showing error messages to tell me a file had been corrupted, I had already noticed that there was a general slowing down of the pc's performance while online. Running the above sorted out whatever corruption there had been. I then re-ran the installation of Mozilla to totally ensure that everything was back to brand spanking new condition. Hope this helps someone. [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Thursday, February 23, 2006 at 6:39 am Posted by Alien (1 messages posted) All this is simple misreporting and nothing else. Windows XP built-in CHKDSK command is there to work with both NTFS as well as FATxx file system. Apparently it doesn't give best possible results with NTFS as we all can see... I am assuring you that all those errors you get while checking from within Windows using built-in CHKDSK command, are not errors at all. This is just a misreport, nothing else. I get exactly the same problems even though I am 100% sure nothing is wrong with my HDs (which are both BTW, brand new... Maxtor 160Gb and Seagate 80Gb). Besides, not a single thing works bad in my Windows. This is what I get when checking with built-in CHKDSK: http://img60.imageshack.us/img60/1494/error6gu.jpg And this is what I get when checking directly from DOS. I used NTFS 4 DOS in this case... I trust it much more than checking the disk from within Windows. Just use NTFS 4 DOS, type CHKDSK and you all will get the same results... no errors at all... of course, assuming your HDs are in good condition and there is really no errors on them... http://img61.imageshack.us/img61/5167/noerror5bf.jpg Cheers! [Reply or follow-up to this message] re: Persistant File ystem Corruption Thursday, April 6, 2006 at 4:21 am Posted by Liam O'Donnell (1 messages posted) Agreed. I too thought NTFS was as reliable as they make out. But a straightforward system crash the other day left random chunks of my harddrive inaccessible. After doing a chkdsk /f the files were all there, just that some of them are now full of random data. Virus checked and full disk scan, no problems. If I didn't know better, I'd say this looks like cross-linked files. The drive is relatively new and still seems fine, but some of the files aren't backed up. Help! Any ideas on a decent tool to fix what chkdsk has screwed up for me? On Sunday, June 20, 2004 at 7:49 pm, garbage wrote: >I purchased a Dell Dimension 8250 with XP Pro in February 2003. It has required reformatting >& reinstalling dozens of times under XP Pro. > >I tried all of the suggestions in this thread. >All of them seem to work for a short time whereupon the problem reccurs. > >I can reliably reproduce the fault by simply enabling the indexing service. But disabling >it does prevent recurrunces again at some time e.g. doing a large file transfer. > >I have previously used Linux on this for 6 months using ReiserFS with ZERO file system >problems. > >As soon as I returned it to Xp Pro/NTFS => problems. > >Dell support response : Wha? >Microsoft support response : Wha? > >I cannot find a solution & must discontiue the use of Microsoft operating systems >due to frequent & costly data loss. > >This is not a M$ bashing exercise, I simply cannot use their OS... [Reply or follow-up to this message] re: Sins of NTFS Tuesday, May 30, 2006 at 7:48 am Posted by Brian B (1 messages posted) After a week or so trying to find some solution I found this posting. It was so true and beautiful it made me cry -- for all of us, and when I think of all the files that disappeared (old family photos, etc) . Time to wipe the whole thing clean.. On Thursday, January 22, 2004 at 8:22 pm, Down For The Count wrote: > >I come here, frequently now. I find some comfort in knowing I am not alone. I am >truly sad however that I along with so many others have lost our beloved systems. >I know I probably shouldn’t but I keep asking: what have I done to my system to deserve >this? > >I have read and reread the epitaphs looking for a reason for all this but I find >none. Grasping for meaning to grab hold of. I find none except that we all fell prey >to running after Microsoft. I feel punished as I recall my decision to abandon more >open systems. > >Oh sure, they weren’t perfect but I can’t help but feel my files would still be here >if I had not given in to the seduction of Microsoft. I am tormented, daily now, to >recall the good times with little hope of seeing them again. Those times when I shared >files and happily listened to MP3s and knew my personal data was safe. My files now >are corrupt, dirty and unusable. I cannot bear to tell anyone about my failings for >fear they will think I am not geek enough. > >Sadly, Microsoft is silent on this subject while perhaps thousands suffer. You know >they know. And every day more and more files, entire folders of files disappear from >the face of this Earth with barely a cryptic display from CHKDSK. Sometimes I think >it would be better to just have it all go at once. > >And yet, I visit nearly daily. Hoping against hope that someone will emerge with >an answer to answer everyone: why my system? > > > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Wednesday, June 28, 2006 at 9:56 pm Posted by Joe (2 messages posted) There is nothing wrong with XP or NTFS. Unlike Fat 32 where if the computer did not shut down properly, the system would automatically run a CHKDSK C: /F. With XP and NTFS Windows is constantly doing this while the computer is running. Just give your computer a few days and everything will be OK again. Sometimes a corruption will prevent you from doing a proper defrag but after a few days this will fix itself also. Nowhere in my search could I find why Windows XP with NTFS would not do a CHKDSK after an improper shutdown. Interesting to note that I upgraded my daughters computer from Me which had Fat 32. After the upgrade to XP Pro her computer ran great but the file system was still Fat 32. I did an improper shutdown and sure enough it did an automatic CHKDSK C: /F after booting up just like Win 98 and Me. Hope that helps. I have run my computer flawlessly for two years with Win XP and NTFS. On Monday, January 6, 2003 at 12:44 pm, Randy J. Anderson wrote: >Warning, Chkdsk errors are occuring high chances are because you are running Chkdsk >with open files. The accurate reporting can only be done when running Chkdsk during >bootup mode (when not using Windows and Chkdsk runs *before* the Windows desktop >loads). Chkdsk often *will* report an error if the >hard disk drive has open files. > > [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Wednesday, June 28, 2006 at 10:14 pm Posted by Joe (2 messages posted) There is nothing wrong with XP or NTFS. Unlike Fat 32 where if the computer did not shut down properly, the system would automatically run a CHKDSK C: /F. With XP and NTFS Windows is constantly doing this while the computer is running. Just give your computer a few days and everything will be OK again. Sometimes a corruption will prevent you from doing a proper defrag but after a few days this will fix itself also. Nowhere in my search could I find why Windows XP with NTFS would not do a CHKDSK after an improper shutdown. Interesting to note that I upgraded my daughters computer from Me which had Fat 32. After the upgrade to XP Pro her computer ran great but the file system was still Fat 32. I did an improper shutdown and sure enough it did an automatic CHKDSK C: /F after booting up just like Win 98 and Me. Hope that helps. I have run my computer flawlessly for two years with Win XP and NTFS. [Reply or follow-up to this message] Fix the USN Journal Monday, March 19, 2007 at 10:48 am Posted by Arthur L. Zamora (1 messages posted) The USN journal is a log of fixed size that records all changes that take place on NTFS 5.0-formatted partitions. NTFRS monitors the NTFS USN journal file for closed files in FRS replicated directories as long as FRS is running. Journal wrap errors occur if a sufficient number of changes take place while FRS is turned off such that the last USN change that FRS recorded during shutdown no longer exists in the USN journal during startup. The risk is that changes to files and folders for FRS replicated trees may have taken place while the service was turned off, and no record of the change exists in the USN journal. To guard against data inconsistency, FRS asserts into a journal wrap state. When you use the check disk utility whitout the /F parameter CHKDSK C: Something like that will be showing: "The type of the file system is NTFS. WARNING! F parameter not specified. Running CHKDSK in read-only mode. CHKDSK is verifying files (stage 1 of 3)... File verification completed. CHKDSK is verifying indexes (stage 2 of 3)... Index verification completed. CHKDSK is verifying security descriptors (stage 3 of 3) Security descriptor verification completed. CHKDSK is verifying Usn Journal... Usn Journal verification completed. Windows found problems with the file system. Run CHKDSK with the /F (fix) option to correct" This mean that the USN journal is corrupted, not the partition, usually Windows boot normal... and you dont need to change to FAT32 or disable the Index Server or other stupid solution. The solution is easy, delete the USN journal, in the Command Prompt type: FSUTIL USN DELETEJOURNAL /D C: Reboot your PC and run: CHKDSK C: /F Program the scan to the next reboot and... reboot again, if a problem is fixed I recomend to scan once again. [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Saturday, March 24, 2007 at 3:00 pm Posted by Arlette (1 messages posted) I came upon your forum while looking for help with a new chkdsk error situation. I run XP pro with a 200 Gigs SATA Seagate drive in two partitions of 80 Gigs & 120 Gigs. All was well until the last week in February. At that point, I removed the Microsoft LiveOneCare and installed BitDefender IS-V10. A week later I left for a 3 weeks trip so the computer was switched off and unused. When I returned, I was unable to complete the Windows booting up process. A few seconds into the process a blue screen with checkdisk appeared stating that my C dive was unstable and I should let CHKDSK do a consistency check. It completed stage 1 (files verification) but immediately upon starting stage 2, it announced 0% completion and there it stuck. I tried resetting the process 4 times with the same constant failure to proceed beyond stage 1. I then canceled CHKDSK and forced Windows to complete its booting up. The computer seemed to perform OK save for OE which was very sluggish opening all 3 identities. That was yesterday. This morning, after canceling CHKDSK yet again, OE just could not get to the server at all. “Working online” was indicated at the bottom of the frame but so was “program not responding” in the header line. I downloaded SeaTools and used DOS boot-up disk to locate the problems. 5 bad errors were located and repaired successfully but when I rebooted, here was the CHKDSK blue screen again with the same attitude: Check stage 1 and no further. If I cancel that hurdle, Windows will boot up to completion and the systems appears to work fine, including OE email retrieval, so why is Windows inserting this CHKDSK with its refusal to perform stage 2 - the indexes verification? According to SeaTools all is well with the C drive now so what other problem could there be? Any feedback/suggestion welcome please. Thank you. [Reply or follow-up to this message] re: Fix the USN Journal Tuesday, July 17, 2007 at 11:39 am Posted by FeniX (1 messages posted) On Monday, March 19, 2007 at 9:48 am, Arthur L. Zamora wrote: ... >The solution is easy, delete the USN journal, in the Command Prompt type: > >FSUTIL USN DELETEJOURNAL /D C: > >Reboot your PC and run: > >CHKDSK C: /F > >Program the scan to the next reboot and... reboot again, if a problem is fixed I >recomend to scan once again. Maybe the solution is easy, but it simply doesn't work!! I have the same problem and so far I was unable to find ANY solution that would permanently fix it. The corruption return after every reboot ALWAYS on the system volume, no matter is the system is installed on as C: partition or X: partition. some times the corruption exists also on other data partitions, but those can be fixed by chkdsk /f, however the system partition once fixed becomes corrupted right after the system boot up.... that's ridiculous! I found this USN journal log file and MFT BITMAP corruption issue to exist on every Windows XP SP2 Pro computer in my company (windows 2000/2003 domain environment), as well as on my standalone home desktop (also Pro SP2)... at the same time we have a dozen of windows 2000 SP4 workstations at work and none of them show those errors on NTFS volumes. The real question is if those errors are real ones or they are simply misidentified by "over-reacting" XP's chkdsk. Please keep in mind that 2000's chkdsk do not find those errors, only XP's have this issue... It is very possible that you are all chasing a dead horse as someone stated on the other forum ... as per M$ - this error can be safely ignored - don't ya wonder why? Probably the XP's chkdsk contains a bug which they cannot fix. I guess this problem with false corruption of NTFS system volume under Win XP will stay unsolved no matter what you do until M$ releases a patch for that. So far I think that this behaviour is by design. Have a nice day or night folks! :) FeniX. [Reply or follow-up to this message] re: Question about 'Prevent file corruption problems' Friday, March 28, 2008 at 11:37 pm Posted by kumar (1 messages posted) I want to know if the file bootex.log can be disabled. Every time chkdsk performs a disk check, it saves the bootex.log file in the corresponding drive and I have to delete it manually everytime. Is there any way to disable this autosaving feature? On Monday, March 22, 2004 at 9:32 pm, Bob Smith wrote: >No. Bootex.log is a file created by chkdsk.exe when it is run; its results are rolled >into the main log after the system finished booting. If chkdsk.exe is interrupted, >bootex.log can become corrupted. When chkdsk.exe runs again, it tries to write to >bootex.log, which is, unfortunately, now corrupt. It doesn't know this until after >the check; so even though it was deleted by chkdsk.exe, it was written to in the >mean time and is therefore still corrupt. The fix is to run under the Recovery console >by either booting from the Windows XP CD or running \i386\winnt32.exe on the Windows >XP CD with the argument /cmdcons. When in the console, run chkdsk.exe /p to fix the >file. Then type del c:\bootex.log to remove the offending file. Reboot, and all is >taken care of. [Reply or follow-up to this message] Tip: Use one of the [Reply or follow-up to this message] links above to add a message to this thread Search this forum Start a new thread on a different subject Report abuse of the forum Return to the Windows XP Discussion Forum