The backup operation that started at has failed with following error code '2155348010'

I have read a lot of forums and google search and they all say it's related to the larger HDD.

Let me start by saying it isn't, not in my case.

We use a 1TB HDD for backup. We have 5 of them. They all have been working fine.

recently it started failed, but not everyday, only every 2nd day.

Looking at the log in the eventviewer I saw MSSQL@SBSMonitoring had a error, i fixed this but still failed.
Then did a HDD diagnostic test using HP tool and found one HDD is faulty in the raid5. So i replaced the HDD.

Run the backup again, still failed.

I get the following error in the event viewer.
The backup operation that started at  has failed with following error code '2155348010'

In the WIndows Server Backup I get the following error.
Items Tab:
Backup ended before completing.
Erros Tab:
The requested could not be performed because of an I/O device error.

Currently I am stuck on how to fix this issue.


Thanks in advance.
Kap HengAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

noxchoGlobal Support CoordinatorCommented:
The error message says that it is not able to write or read. Thus you need to find out at which side the problem is.
First of all try to different HDD - will it fail as well?
If it still fails then the problem is at backup source drive. Have you checked the partitions on backup source drive (RAID) with CHKDSK x: command where X: is a drive letter of your partition(s)?
Kap HengAuthor Commented:
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)...
  436928 file records processed.
File verification completed.
  2699 large file records processed.
  0 bad file records processed.
  0 EA records processed.
  182 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
  503682 index entries processed.
Index verification completed.
  0 unindexed files processed.
CHKDSK is verifying security descriptors (stage 3 of 3)...
  436928 security descriptors processed.
Security descriptor verification completed.
  33378 data files processed.
CHKDSK is verifying Usn Journal...
Examining Usn Journal file record segment.152 USN bytes processed)
  537773152 USN bytes processed.
Usn Journal verification completed.
Windows found problems with the file system.
Run CHKDSK with the /F (fix) option to correct these.

 573364223 KB total disk space.
 273992608 KB in 176999 files.
    107540 KB in 33379 indexes.
         0 KB in bad sectors.
   1048719 KB in use by the system.
     65536 KB occupied by the log file.
 298215356 KB available on disk.

      4096 bytes in each allocation unit.
 143341055 total allocation units on disk.
  74553839 allocation units available on disk.

Looks like there is an issue with the file system.

What do I need to do before running a /F?

I would like to do a full backup before I run it, just in case. But currently backup isn't working.
noxchoGlobal Support CoordinatorCommented:
Well, in this case you can manually copy out the important data from the volume you are trying to check. This is the only one step you can do. Robocopy for example.
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Kap HengAuthor Commented:
I have done a CHKDSK /F, after it finished, ran another CHKDSK and this time no problems were found.

Started another backup, same errors.

Any other suggestions?
noxchoGlobal Support CoordinatorCommented:
Have you tried to do this backup to different drive?
And did you perform CHKDSK on all drives of the system?
Kap HengAuthor Commented:
I have tried doing a backup on a few different drives and still fails.

I even formatted a few of them to try. Still fails.

There's only C: drive.

Currently doing a backup to a network drive, will update once it finishes.
noxchoGlobal Support CoordinatorCommented:
So you are taking backup of a single partition, right? If not, can you try to backup this single partition only? I mean C: drive.
Kap HengAuthor Commented:
The data size is 220GB and it fails around the 165GB. There is around 286GB of free space available on the server.

Here is how I start the backup process.
I select Custom
Check "Local Disk (C:)"
Local Drive - Destination TYpe
VSS copy Backup - Selected

Backing up to network fails, backing up to external USB HDD also fails.
noxchoGlobal Support CoordinatorCommented:
So problem is on source drive then. Do you have any other events or backup logs on the server?
Any way  to try this backup with third party tool?
Check with trial version of Hard Disk Manager 15 Business:
Can it backup your C: drive till the end? This test will show if it is possible at all to backup the drive in current state.
Kap HengAuthor Commented:

Installed Paragon and failed as well. It failed near the end like windows server backup.

This is the error message.
Backup partitions or disk to virtual containers - VSS: Can't read volume data (source: Hard Disk Manager)
Kap HengAuthor Commented:
I follow the instruction below to try and solve VSS.

But I get the following errors when I get to STEP 4.
The Module "msxml.dll" failed to load.
The module "eventcls.dll" was loaded but the call to DllInstall failed with error code 0x8000ffff.
The module "es.dll" was loaded but the entry-point DLLRegisterServer was not found.
noxchoGlobal Support CoordinatorCommented:
You don't need to re-register the VSS dlls in this case.
Is this RAID based system or a single HDD based one? The error sounds pretty as a harddrive error. It could be a bad block on HDD surface. Have you checked it with HDD vendor made surface test tool?
Kap HengAuthor Commented:
It's a HP Server running Windows Server 2008. It's in RAID5. I have already used HP Diagnostic tool to test the HDD. Found one HDD was faulty, but that has now been replaced with a brand new one. I ran the HP Diagnostic tool again and everything is good, no errors.
Kap HengAuthor Commented:
I ran "sfc /scannow" to see if there is any issues.

I get the following error
"Windows Resource Protection found corrupt files but was unable to fix some of them."

I have attached the CBS log file.
Kap HengAuthor Commented:
noxchoGlobal Support CoordinatorCommented:
2015-07-31 22:51:27, Info                  CSI    0000010b [SR] Cannot repair member file [l:32{16}]"scwvariables.xml" of Microsoft-Windows-Security-Configuration-Wizard, Version = 6.0.6002.18005, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch 2015-07-31 22:51:29, Info                  CSI    0000010c Hashes for file member \SystemRoot\WinSxS\amd64_microsoft-windows-s..onfiguration-wizard_31bf3856ad364e35_6.0.6002.18005_none_99f97c2900b9a29f\scwvariables.xml do not match actual file [l:32{16}]"scwvariables.xml"

You can try what was suggested here:
Kap HengAuthor Commented:
is this issue related to my failed backups?

The more I try to repair WIndows Server Backup, the more issues I find with this server.
noxchoGlobal Support CoordinatorCommented:
According to the log you've posted - sfc could not repair this file.
And yes, there could be more issues with this server and there is always a way to reinstall it from scratch which will possibly fix all problems.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Kap HengAuthor Commented:
really appreciate the help.
noxchoGlobal Support CoordinatorCommented:
Thanks for points.
Have you managed to resolve the problem? If yes then how?
Kap HengAuthor Commented:

I haven't solved it yet. I'm trying one more thing, and that is to run the update. The previous IT never updated our server. By looking back to the updates that is required, it's dated all the way back to 2012.

So hopefully doing a few updates at a time, hopefully fixes it. I'm not putting my hopes up.

If it doesn't fix the problem. Then I'm going to leave it as is.

The server is no longer using exchange, we only have two software running on the server and that is it. No file storage to share or anything. Very basic stuff.

I dont see the point of spending more time and money on this 4 year old server.

Do you have any suggestion on a backup software? I only need to backup a few folders.
noxchoGlobal Support CoordinatorCommented:
The easiest and simplest way is using robocy or xcopy script (you'll find easily one in google search). No other software is needed.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.