Event 55 - ntfs - The file system structure on the disk is corrupt and unusable
HP ML350 G5 E5420
7 Gig RAM
4x 146Gig 15,000rpm SAS drives in RAID 5 (Via Smart Array E200i Embedded card)
2 NICs Teamed together for full duplex 2Gb/s
Windows 2008 R2 Std SP1
This Server has installed and configured the following Roles:
-Active Directory Domain Services
-Application Server
-DHCP Server
-DNS Server
-Fax Server
-File Services
-Network Policy and Access Services
-Print and Document Services
The software build is about a year old, the hardware is about 2 and a half years old
Currently backup setup is built in Windows Server Backup. This backs up to Dell R200 server running Ubuntu 11.04 64bit server running a samba share with likewise for domain membership.
The backup is set to run at 21:00hrs each night
Today I checked the Server Manager console this morning to find in the events for File Servers an Error 55 from Ntfs at 21:00:10, 21:00:33 and 21:01:05 stating;
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolumeShad
I ran CHKDSK and had the following output;
C:\>chkdsk
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)...
254976 file records processed.
File verification completed.
745 large file records processed.
0 bad file records processed.
0 EA records processed.
95 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
354032 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
254976 file SDs/SIDs processed.
Security descriptor verification completed.
49529 data files processed.
CHKDSK is verifying Usn Journal...
538405744 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.
430023839 KB total disk space.
178018684 KB in 169751 files.
116448 KB in 49530 indexes.
0 KB in bad sectors.
876491 KB in use by the system.
65536 KB occupied by the log file.
251012216 KB available on disk.
4096 bytes in each allocation unit.
107505959 total allocation units on disk.
62753054 allocation units available on disk.
I have set CHKDSK to run the next time the server restarts which I will carry out tonight.
I used the HP Array COnfiguration Utility and checked the disks and the controller and it seems happy there's nothing physical wrong with either the disks or the controller.
Can anyone suggest something I've missed or anything else I can check or do?
What should I be looking to do next?
Will I have to do a full restore from the last backup?
7 Gig RAM
4x 146Gig 15,000rpm SAS drives in RAID 5 (Via Smart Array E200i Embedded card)
2 NICs Teamed together for full duplex 2Gb/s
Windows 2008 R2 Std SP1
This Server has installed and configured the following Roles:
-Active Directory Domain Services
-Application Server
-DHCP Server
-DNS Server
-Fax Server
-File Services
-Network Policy and Access Services
-Print and Document Services
The software build is about a year old, the hardware is about 2 and a half years old
Currently backup setup is built in Windows Server Backup. This backs up to Dell R200 server running Ubuntu 11.04 64bit server running a samba share with likewise for domain membership.
The backup is set to run at 21:00hrs each night
Today I checked the Server Manager console this morning to find in the events for File Servers an Error 55 from Ntfs at 21:00:10, 21:00:33 and 21:01:05 stating;
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolumeShad
I ran CHKDSK and had the following output;
C:\>chkdsk
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)...
254976 file records processed.
File verification completed.
745 large file records processed.
0 bad file records processed.
0 EA records processed.
95 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
354032 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
254976 file SDs/SIDs processed.
Security descriptor verification completed.
49529 data files processed.
CHKDSK is verifying Usn Journal...
538405744 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.
430023839 KB total disk space.
178018684 KB in 169751 files.
116448 KB in 49530 indexes.
0 KB in bad sectors.
876491 KB in use by the system.
65536 KB occupied by the log file.
251012216 KB available on disk.
4096 bytes in each allocation unit.
107505959 total allocation units on disk.
62753054 allocation units available on disk.
I have set CHKDSK to run the next time the server restarts which I will carry out tonight.
I used the HP Array COnfiguration Utility and checked the disks and the controller and it seems happy there's nothing physical wrong with either the disks or the controller.
Can anyone suggest something I've missed or anything else I can check or do?
What should I be looking to do next?
Will I have to do a full restore from the last backup?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It is ok.
Just observe your server for some days and everything should be ok.
Just observe your server for some days and everything should be ok.
ASKER
If I may, I will keep this open for the next 24 hours, as tonight after work I'm going to reboot the server and allow CHKDSK to do it's thing. I will then report my findings tomorrow morning and if all goes well close this incident.
Cheers gtworek :-)
Cheers gtworek :-)
I can understand this. Leaving the question open for some time allows you to read suggestion from other experts too.
ASKER
Ok, The CHKDSK/F ran fine and didn't seem to find anything. Though I've checked the Server Manager today and found the same error message;
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolumeShad
and again it was just after the backup started.
Any ideas?
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume \Device\HarddiskVolumeShad
and again it was just after the backup started.
Any ideas?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ran command;
C:\>vssadmin list shadows
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Contents of shadow copy set ID: {665fe8ac-3023-42ff-8f83-b
Contained 1 shadow copies at creation time: 23/06/2011 21:00:38
Shadow Copy ID: {4d902765-bf0b-4682-a508-4
Original Volume: (C:)\\?\Volume{72986fdf-e9
Shadow Copy Volume: \\?\GLOBALROOT\Device\Hard
Originating Machine: RS1.MYDOMAIN.co.uk
Service Machine: RS1.MYDOMAIN.co.uk
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ApplicationRollback
Attributes: Persistent, No auto release, Differential, Auto recovered
Contents of shadow copy set ID: {69ffff2f-6225-4dc4-b2a8-7
Contained 1 shadow copies at creation time: 02/08/2011 21:00:23
Shadow Copy ID: {355d87e0-7d5b-48cb-bb14-0
Original Volume: (C:)\\?\Volume{72986fdf-e9
Shadow Copy Volume: \\?\GLOBALROOT\Device\Hard
Originating Machine: RS1.MYDOMAIN.co.uk
Service Machine: RS1.MYDOMAIN.co.uk
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ApplicationRollback
Attributes: Persistent, No auto release, Differential, Auto recovered
C:\>
C:\>vssadmin list shadows
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Contents of shadow copy set ID: {665fe8ac-3023-42ff-8f83-b
Contained 1 shadow copies at creation time: 23/06/2011 21:00:38
Shadow Copy ID: {4d902765-bf0b-4682-a508-4
Original Volume: (C:)\\?\Volume{72986fdf-e9
Shadow Copy Volume: \\?\GLOBALROOT\Device\Hard
Originating Machine: RS1.MYDOMAIN.co.uk
Service Machine: RS1.MYDOMAIN.co.uk
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ApplicationRollback
Attributes: Persistent, No auto release, Differential, Auto recovered
Contents of shadow copy set ID: {69ffff2f-6225-4dc4-b2a8-7
Contained 1 shadow copies at creation time: 02/08/2011 21:00:23
Shadow Copy ID: {355d87e0-7d5b-48cb-bb14-0
Original Volume: (C:)\\?\Volume{72986fdf-e9
Shadow Copy Volume: \\?\GLOBALROOT\Device\Hard
Originating Machine: RS1.MYDOMAIN.co.uk
Service Machine: RS1.MYDOMAIN.co.uk
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ApplicationRollback
Attributes: Persistent, No auto release, Differential, Auto recovered
C:\>
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
so then do I run;
vssadmin delete shadows /shadow={4d902765-bf0b-468
Also, do I have to run a restore of our backup first before I do that?
vssadmin delete shadows /shadow={4d902765-bf0b-468
Also, do I have to run a restore of our backup first before I do that?
> do I have to run a restore of our backup first before I do that?
No. If your backup is ok you can just delete old shadow.
No. If your backup is ok you can just delete old shadow.
ASKER
We are currently using Windows Server Backup (The built in one) which VSS Settings are set to "VSS Full Backup". Every backup that has been done has come back with the status of "Successful".
(Within a matter of days we will be going over to an incremental off site backup service from another company.)
So as Windwos Server currently thinks the backups are completing successfully should that mean the backups being made are reliable?
(Within a matter of days we will be going over to an incremental off site backup service from another company.)
So as Windwos Server currently thinks the backups are completing successfully should that mean the backups being made are reliable?
If they are "Successful" they should be reliable.
You can test them on a virtual machine if you are not perfectly sure.
You can test them on a virtual machine if you are not perfectly sure.
ASKER
Can this operation be carried out during the day or best out of office hours (when the server won't be in use)?
It doesn't matter in this case but it is generally great idea to do some maintenance tasks after work hours.
ASKER
Ok I will do this after everyone has logged off and let you know how it all goes
ASKER
Tried using that command and got the following message
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Administrator>vss
4ae3e2670472}
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Error: Snapshots were found, but they were outside of your allowed context. Try
removing them with the
backup application which created them.
C:\Users\Administrator>
What does this mean please?
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Administrator>vss
4ae3e2670472}
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Error: Snapshots were found, but they were outside of your allowed context. Try
removing them with the
backup application which created them.
C:\Users\Administrator>
What does this mean please?
ASKER
Just thinking about this message, if I removed the current backup setup with Windows Server Backup would that then allow me to delete this shadow copy?
I guess no... you can still do this with vshadow utility from vss sdk.
ASKER
managed to delete it in the end, I went into the properties of the drive, found that shodow copies had been disabled, so I re-enabled them and then went to delete the offending shadow copy but the process of enabling shodow copies removed all the old ones.
I will leave this question open for 24 hours to make sure the error message has gone.
I will leave this question open for 24 hours to make sure the error message has gone.
ASKER
No more error messages!
Cheers for your help
Cheers for your help
ASKER
I ran the command you suggested and got the following;
C:\>fsutil dirty query C:
Volume - C: is NOT Dirty
So can I take that to be a good thing then?