Window Backup Failure 2155348258

NTDEV
1

Dear All,

I create a RAID0 disk using my own RAID controller.
And I can read/write to this disk using IOMeter and Winthrax.

But when I backup the system to this disk, the backup failed with the
following information:
*The backup operation that started at ‘2013-01-28T08:50:28.174370800Z’
has failed with following error code ‘2155348258’ (Windows Backup failed to
write the file: ‘\WindowsImageBackup<computer>Name>\MediaId’.). Please review the event details for a solution, and then
rerun the backup operation once the issue is resolved.*

And a event related the disk is received:
The driver detected a controller error on \Device\Harddisk1\DR7.

I cannot figure out what’s the problem with this process. Or something
special needed for supporting shadow copy?

–

Best regards,
David Zeng

2

>*The driver detected a controller error on \Device\Harddisk1\DR7.*

What else could that be, if not “The driver detected a controller error”?

3

Many things. From a filter driver, just fail a read/write to the boot sector. Voila, same eventlog. Didn’t even get close to the controller.

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@broadcom.com
Sent: Monday, January 28, 2013 8:59 AM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Window Backup Failure 2155348258

*The driver detected a controller error on \Device\Harddisk1\DR7.*

What else could that be, if not “The driver detected a controller error”?

NTDEV is sponsored by OSR

OSR is HIRING!! See http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

4

After the failure, I saw the following folder and file created:
WindowsImageBackup\WIN-D0A6xxxxxxx\TempMediaId

But the file just has 16 Bytes content.
And the raid controller did not report any error.

Best regards,
David Zeng

5

Thank you all!

This is caused by the SRB_FUNCTION_FLUSH SRB failure.

–

Best regards,
David Zeng