Re: Event ID 55 After SP1 Install on Win Server 2003

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



paul.anderson@xxxxxxxxxxxx napisał(a):
I've applied firmware updates to the drives, array controller and
system BIOS. However, I'm still getting the following error every time
an attempt is made to change ACLs on a file:

"Unable to save permission changes on <filename>. The file or
directory is corrupted or unreadable."

The following event will then typically occur:

Event Type: Error
Event Source: Ntfs
Event Category: Disk
Event ID: 55
Date: 24/07/2006
Time: 20:17:35
User: N/A
Computer: CAMPUSCOMMVAULT
Description:
The file system structure on the disk is corrupt and unusable. Please
run the chkdsk utility on the volume OS.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 15 00 04 00 02 00 52 00 ......R.
0008: 02 00 00 00 37 00 04 c0 ....7..À
0010: 00 00 00 00 02 01 00 c0 .......À
0018: 18 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: a7 39 03 00 §9..

The above event mostly occurs alongside the following one:

Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 24/07/2006
Time: 17:32:53
User: N/A
Computer: CAMPUSCOMMVAULT
Description:
Application popup: <filename> - Corrupt File : The file or directory
C:\$Secure is corrupt and unreadable. Please run the Chkdsk utility.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

I'm certain that this is not a hardware problem. What I would like to
do now is fix C:\$Secure, which I think may be the current source of
errors. I think this is a file used by NTFS to store ACLs.

This is a backup server. One approach would be to wipe C:\, install
Windows Server again (along with SP1) and then install our backup
software again. We then do a 'disaster recovery' using our backup
software, which will install the backup software again and reattach the
backup stores, reinstall the tape library, restore the backup database,
restore the tape pools, etc. This is not a desireable option. It's a
painful option which will probably not go smoothly.

If there is another option, I want to know about it. The backups are
still working and the system is still stable to an extent. Can I
recover the filesystem and its ACL data without disrupting the system
and software files ? I'd love to be able to just remove or reset all
ACL data to replace the corrupt C:\$Secure, then use the Security
Configuration & Analysis MMC snap-in to apply a standard ACL template
that will apply proper restrictions to C:\Windows\..., C:\Program
Files\..., etc.

Is it possible to do the latter ? Would really appreciate some help.

huddie wrote:

Hi,

Our critical backup server has started writing Event ID 55 (filesystem is
corrupt) after I installed SP1. I followed the correct procedure for the
install, including stopping third-party services and apps and restarting
before the install.

This may or may not relate to a system file - cpqcissm.sys - "Compaq Smart
Array Controllers SCSI Miniport Driver (IA-32)". I was offered by SP1
install to replace this 3rd party file with an SP1 MS version, with Yes being
the default and I chose Yes. Can I use the recovery console to restore the
previous version of this file and, if so, how should I do this without system
file protection rolling the SP1 version back ?

Can you please help as this server is critical and needs to be 100% stable ?
Your help would be greatly appreciated :)

Thanks.
--
--
Paul Anderson

What type of backup software do you have?
There is some problem with agent for open files on NTFS volume after SP1 install.
I have the same error with TSM (Tivoli) backup agent. The simple way is uninstall Open Files Agent (disabling only sometimes not help). Open Files Agent should be upgraded, I think.
I heard about the same problem with Veritas and Arcserve.

Szyja
.



Relevant Pages

  • Re: Event ID 55 After SP1 Install on Win Server 2003
    ... The file system structure on the disk is corrupt and unusable. ... This is a backup server. ... Windows Server again (along with SP1) and then install our backup ...
    (microsoft.public.windows.server.general)
  • Re: Transition Pack question/problem
    ... Do a thorough, complete, VERIFIED backup. ... Disconnect the server from the internet completely. ... (ie, SP1 for SP1 SBS, etc.) ... Server '03 R2 before i can even install this? ...
    (microsoft.public.windows.server.sbs)
  • Re: Full Exchange System Restore
    ... you are putting 100% faith on the current backup solution, ... Exchange binaries with SP1? ... It seems a little odd that I should bring the Exchange SP1 install ...
    (microsoft.public.exchange.admin)
  • Re: SQL Server 2005 faulure when updating to SP1
    ... i have installed Sql Server 2000 SP4 also, ... people to install SP1 on a SQL 2005 Server, ... If you were to look at the permissions on the $4IDR files only the Backup ...
    (microsoft.public.sqlserver.setup)
  • Re: RAID, SCHMAID.......
    ... And risky to change it later without a full image backup. ... partition, & then restore only the OS, but still verydoable. ... partition before an install of something you havent installed before, ... but so many ppl make a mess of things esp with today's big drives. ...
    (comp.sys.ibm.pc.hardware.storage)