Guest Radek__ Posted July 23, 2008 Posted July 23, 2008 Hello, I have problem with FS on Windows 2003. I have still one problem on local disk system when is performed backup of system disk and systemstate. When backup starts then I receive error NTFS 55. When I backup DB on disk attached on SAN storage then everything is ok I ran many times defrag and chkdsk after restart but without any result. Could you help me? Event Type: Error Event Source: Ntfs Event Category: Disk Event ID: 55 Date: 7/22/2008 Time: 9:01:32 PM User: N/A Computer: ZO1DBMR1 Description: The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume OS. ------------------ After error I ran chkdsk: C:\>chkdsk c: The type of the file system is NTFS. Volume label is OS. WARNING! F parameter not specified. Running CHKDSK in read-only mode. CHKDSK is verifying files (stage 1 of 3)... 38656 file records processed. File verification completed. 32 large file records processed. 0 bad file records processed. 0 EA records processed. 0 reparse records processed. CHKDSK is verifying indexes (stage 2 of 3)... 73 percent complete. (98461 of 129514 index entries processed) Deleting index entry system in index $I30 of file 12747. 81 percent complete. (110401 of 129514 index entries processed) Deleting index entry lpt$vpn.423 in index $I30 of file 22694. Deleting index entry lpt$vpn.425 in index $I30 of file 22694. Deleting index entry tmwhite.331 in index $I30 of file 22694. 93 percent complete. (129062 of 129514 index entries processed) Deleting index entry SecEvent.Evt in index $I30 of file 38581. Deleting index entry SysEvent.Evt in index $I30 of file 38581. 129514 index entries processed. Index verification completed. Errors found. CHKDSK cannot continue in read-only mode. -----------------------
Guest Pegasus \(MVP\) Posted July 23, 2008 Posted July 23, 2008 Re: NTFS Error at backup of system and systemstate - Win 2003 "Radek__" <Radek@discussions.microsoft.com> wrote in message news:85FC575C-B82A-413D-AE39-FC165413EBB5@microsoft.com... > Hello, > > I have problem with FS on Windows 2003. > I have still one problem on local disk system when is performed backup of > system disk and systemstate. > When backup starts then I receive error NTFS 55. > When I backup DB on disk attached on SAN storage then everything is ok > > I ran many times defrag and chkdsk after restart but without any result. > > Could you help me? > > Event Type: Error > Event Source: Ntfs > Event Category: Disk > Event ID: 55 > Date: 7/22/2008 > Time: 9:01:32 PM > User: N/A > Computer: ZO1DBMR1 > Description: > The file system structure on the disk is corrupt and unusable. Please run > the chkdsk utility on the volume OS. > ------------------ > After error I ran chkdsk: > C:\>chkdsk c: > The type of the file system is NTFS. > Volume label is OS. > > WARNING! F parameter not specified. > Running CHKDSK in read-only mode. > > CHKDSK is verifying files (stage 1 of 3)... > 38656 file records processed. > File verification completed. > 32 large file records processed. > 0 bad file records processed. > 0 EA records processed. > 0 reparse records processed. > CHKDSK is verifying indexes (stage 2 of 3)... > 73 percent complete. (98461 of 129514 index entries processed) > Deleting index entry system in index $I30 of file 12747. > 81 percent complete. (110401 of 129514 index entries processed) > Deleting index entry lpt$vpn.423 in index $I30 of file 22694. > Deleting index entry lpt$vpn.425 in index $I30 of file 22694. > Deleting index entry tmwhite.331 in index $I30 of file 22694. > 93 percent complete. (129062 of 129514 index entries processed) > Deleting index entry SecEvent.Evt in index $I30 of file 38581. > Deleting index entry SysEvent.Evt in index $I30 of file 38581. > 129514 index entries processed. > Index verification completed. > > Errors found. CHKDSK cannot continue in read-only mode. > ----------------------- Defragging will NOT fix any file system errors. When running chkdsk, you MUST specify the /F switch, as the screen report says. If you don't then chkdsk won't fix any errors.
Guest Radek__ Posted July 23, 2008 Posted July 23, 2008 Re: NTFS Error at backup of system and systemstate - Win 2003 I already tried chkdsk with all switches :-) I tried many times chkdsk /r or /f with restart I'm not dummy user.. Defrag temporarry solved problem. After derragmentation chkdsk passed successfully. But after some hours or days the problem occures again.
Guest Pegasus \(MVP\) Posted July 23, 2008 Posted July 23, 2008 Re: NTFS Error at backup of system and systemstate - Win 2003 "Radek__" <Radek@discussions.microsoft.com> wrote in message news:DD708CF8-1241-477F-88B1-D982806E4B73@microsoft.com... > > I already tried chkdsk with all switches :-) > I tried many times chkdsk /r or /f with restart > I'm not dummy user.. > Defrag temporarry solved problem. > After derragmentation chkdsk passed successfully. > But after some hours or days the problem occures again. > I never said you were a "dumb user". However, your own report (see below) clearly shows that you ran chkdsk without the /f switch: ================ After error I ran chkdsk: C:\>chkdsk c: The type of the file system is NTFS. Volume label is OS. WARNING! F parameter not specified. Running CHKDSK in read-only mode. ================ If the problem keeps recurring then you probably have a damaged file system. I had one of those too some time ago and I solved the problem like so: 1. I connected a spare disk as a slave disk to the server. 2. I partitioned & formatted this disk. 3. I booted the server with a Bart PE CD. 4. I used robocopy.exe to copy all files & folders from the damaged disk to the spare disk. 5. I disconnected the damaged disk. 6. I made the spare disk the master disk. 7. I checked if the server booted normally. 8. I repartitioned & formatted the damaged disk. 9. I reversed the above copy process. This is a zero-risk process as long as you don't skip any steps.
Guest Radek__ Posted July 23, 2008 Posted July 23, 2008 Re: NTFS Error at backup of system and systemstate - Win 2003 Thanks I have hw RAID-1 on system disks. I'm not sure If will this solution work. I had same problem on another three servers. But now is only on one... I tkink that it is sw(OS, TSM, Veritas) or fw problem. I would like know what did the problem and how to solve. I use Tivoli storage manager for backuping, Veritas storage foundation for sw mirroring on DB disks between two storages. But system disks are basic disks on HW mirror. DB disks are dynamic.
Guest Pegasus \(MVP\) Posted July 23, 2008 Posted July 23, 2008 Re: NTFS Error at backup of system and systemstate - Win 2003 I would break the mirror and see if the problem persists. "Radek__" <Radek@discussions.microsoft.com> wrote in message news:7D6BA61A-E8B1-4221-A974-CEE690845AA1@microsoft.com... > Thanks > > I have hw RAID-1 on system disks. > I'm not sure If will this solution work. > I had same problem on another three servers. But now is only on one... > I tkink that it is sw(OS, TSM, Veritas) or fw problem. > I would like know what did the problem and how to solve. > > I use Tivoli storage manager for backuping, Veritas storage foundation for > sw mirroring on DB disks between two storages. > But system disks are basic disks on HW mirror. > DB disks are dynamic.
Guest Radek__ Posted July 23, 2008 Posted July 23, 2008 Re: NTFS Error at backup of system and systemstate - Win 2003 I already did it..but no result
Guest Pegasus \(MVP\) Posted July 23, 2008 Posted July 23, 2008 Re: NTFS Error at backup of system and systemstate - Win 2003 "Radek__" <Radek@discussions.microsoft.com> wrote in message news:474ABFCA-98DF-47FE-9035-E6A83F148390@microsoft.com... > > > I already did it..but no result Sorry, I have run out of magic bullets. You may have to perform a complete backup, followed by partitioning/ formatting your hard disk. If this was my machine then I would restore the backup to a different disk so that I could test it BEFORE repartitioning the old disk. For future posts I recommend that you do not only post the details of your problem but also what steps you took to resolve it. This avoids the awkward situation where respondents suggest remedies that you have already tried yourself.
Recommended Posts