Friday, May 20, 2011 5:30 PM
I'm getting this error several times a day on an HP server we have. I've run chkdsk /r and everything came back fine but I still continue to see these errors.
"The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility o the volume CASEFILES."
Another thing that is troubling me is the server reboots itself every 2 months or so. I thought the reboots may have caused the disk curruption, but maybe it's the other way around after looking at this post. http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/025cfbdf-544f-4cf7-8000-ae4b81feb4d3/
I'm finding a lot of stuff on this topic but nothing conclusive. I would really appreciate your help on this one.
Friday, May 20, 2011 5:40 PM
Have a look to this Microsoft article about the error: http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Windows+Operating+System&ProdVer=5.2&EvtID=55&EvtSrc=ntfs&LCID=1033
Run chkdsk /r /f and check if this disappear.
If this does not solve it, I think it will be better to contact Support to report that.
Friday, May 20, 2011 5:50 PMI ran /f and /r separably, but not at the same time. I thought that /R implied /F. Will running running them together in the same command produce different results?
Saturday, May 21, 2011 5:59 AM
Don;t bother chkdsk /f /r because it won't help much on that. Well contacting the hardware vendor will only replace ur disk. Which that is not the whole idea about troubleshooting. Contacting support will only be the very last resort.
There is another solution for you to try out.
kindly download scantools and burnt it to bootable ISO format, kindly boot the disc into DOS mode and use < hard disk regen tools >
Hiren boot disc does comes with hard disk regen tools as well.
execute the hard disk regen tools and it will slowly fix your faulty sectors.. In any case i have encountered such issues after fixed. The fix will require at least 2 to 3 hours depending on how big your hard disk is. Remember to run the fix in a air conditioner place.
the error event 55 never reflect again.
Let me know if you need further assistance on that.
Guowen Su | CCNA, CCIP, MCP, MCSA, MCSE, MCTS, MCITP, CEH | http://www.microsoft.com/en/sg/default.aspx Our Goal? VERY SATISFIED Customers. If you're not...let's talk!! Please don't vote me for answers... because i does not want others to feels that i'm cheating ? :) In any case God knows :)
Thursday, May 26, 2011 2:15 AMModerator
I searched for the error and noticed that it can be caused by third party programs and/or the firmware of the hard disk.
First you can have a test in Safe Mode to see if same error still exists. If so, it should be hardware related issue and you will need to contact manufaturer. Check if there is any newer firmware/driver is available for the device or maybe you need to replace the hard disk.
Shaon Shan |TechNet Subscriber Support in forum |If you have any feedback on our support, please contact email@example.com
Tuesday, May 31, 2011 4:43 PM
I apologize for the delayed response. I did get some more info. These errors are occurring when the nightly backups run on the server. It constantly produces 4 of these errors within the first 8 min of the backup. I use BackupAssist and it's running a windows image job. Shaon, did you find anything related to Backup Assist when you were searching for this?
Because the server has been rebooting, I've also had ongoing support from HP and so far we have replaced both power supplies, motherboard, memory and the power backplane. We just did the power backplane last Friday. That didn't help these NTFS errors, but will hopefully help the reboots. I'm still unsure if they are related at this time.
Guowen, I have not had a chance to do what you suggested. I'm curious to see what Shaon found before proceeding further.
Tuesday, June 28, 2011 9:42 PMSo I have eliminated Backup Assist from the equation. This error occurs only when running a windows image backup on the server (2008 R2). the odd thing is that it that the error still mentions the H: drive as being corrupt, when I am only backing up the C: drive. Does anyone know why this would occur. Is the snapshot being written to the H: drive?
Wednesday, June 29, 2011 10:03 PM
Because I was able to identify Windows Backup as the trigger that is producing this problem, I went ahead and made a post over in the Windows Backup forum.
Tuesday, July 12, 2011 5:43 PM
I finally solved this problem. For more detail you can visit another post I started Here:
I opened up a Microsoft Support Case yesterday for this issue.It turns out that the shadow copies on the C: and the H: volume were corrupt. After deleting these shadow copies the backup ran without generating any NTFS errors. The tech said that the corrupted shadow copies were caused by an outdated NTFS.sys driver version. He had me update the NTFS driver version with KB982018, which appears to contain a whole slew of updates to core system files. This can be found here:
He also said the reason why check disk did not detect these issues is that check disk doesn't check or repair any volume shadow copies.This makes sense to me that it doesn't repair these, but I thought it should check all files on the volume. (the tech was planning to confirm this, as he was a little unsure himself)
I plan to run another check disk after deleting these shadow copies just to confirm the file system is in tact, but I expect the results to be ok.
- Marked As Answer by Caleb44 Tuesday, July 12, 2011 5:43 PM