Windows Backup Error 2155348010 – The request could not be performed because of an I/O device error


Technically a Windows Backup/External USB Drive issue but it came about when trying to perform an Exchange backup.

Scenario:

Smaller customer running Exchange 2010 on a new deployment. They’d been having trouble setting up their backup and as a result had 30GB of transaction logs and were running low on space. Customer was trying to use a Western Digital USB 2TB HD as the backup destination. Backups would take forever on “Running Consistency Check for Application Exchange” and would ultimately fail with the following error message within Windows Server Backup:

“One of the backup files could not be created. Detailed Error: The request could not be performed because of an I/O device error”

Event Viewer would also give:

Source: Microsoft-Windows-Backup
failed with following error code ’2155348010′ (One of the backup files could not be created.). Please rerun backup once issue is resolved.

Resolution:

Ran vssadmin list writers and also enabled expert level logging (Set-EventLogLevel “MSExchangeIS\9002 System\Exchange Writer” -Level Expert) but the writers all showed a state of Stable.

The backup was hanging at “Running Consistency Check for Application Exchange…” because of all the transaction logs. Dismounted database, removed logs, checkpoint file, and re-mounted. The backup would now just take much less time to fail with the same error :(

Found the following articles that seemed to address this issue:

http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/5d9e2f23-ee70-4d41-8bfc-c9c4068ee4e2

http://www.cmoullas.net/windows-backup-error-0x8078002a-2-5tb-3tb-wd-drives/

The issue was being caused by the fact that Windows Server Backup does not support drives with large sector size (4096 bytes) unless they support 512 byte emulation.

Information about Microsoft Support policy for large-sector drives in Windows

http://support.microsoft.com/kb/2510009

Drive type Support/functionality
4K native (4K logical sector size): Most of the drives larger than 2 terabytes and with a USB connection are this kind of drive. Currently not supported on any released operating system version. Contact your drive manufacturer for support.

The fix was ultimately supplied from the blog post in the second link. We downloaded and used the WD Quick Formatter Tool (http://wdc.custhelp.com/app/answers/detail/search/1/a_id/3868) on the USB drive to format it with the non-XP compatible setting. Hopefully other manufacturers have similar tools or properly support 512 byte emulation.

Afterwards the Windows Backup completed successfully and the Exchange logs were being properly truncated.

About these ads

14 thoughts on “Windows Backup Error 2155348010 – The request could not be performed because of an I/O device error

  1. Thank you for this post. I have replaced 2 drives thinking that this was a hardware issue. running the utility suggested above on my WD external drive fixed the issue.

    • I’m not aware but their support may be able to assist you. I would be hesitant to use the WD tool on another model drive as I couldn’t be sure of the results.

    • vttech, I also have a 3TB Seagate drive, and getting these same IO errors when running SBS2011 Windows Backup…my drive was able to be formatted using CompMgr as GPT drive.
      Did you ever find a fix for this problem as yet?
      Thanks,
      robb

  2. I had to reply and say thanks. I fought for several hours trying to figure out how to use a WD MyBook Essential 3TB drive for backup of WHS 2011 Server. The I/O Error threw me off and I thought I had a USB driver issue or something. Thanks a ton for setting me straight!

  3. I brought 4 Seagate 2TB drives for rotational backup – 3 work OK and one has this error on backup. Any clues why one should be different to the other 3 ?
    If so what can I do to change this drive to be like the other 3 and work ?
    It’s not a disc error as such so I presume I can’t return the disc.
    Thanks

    • Not sure but I suppose it could be some kind of low-level sector corruption. First check if all drives are on same FW version. Then see if you can perform a reformat & then if that doesn’t work, a low-level reformat using the manufacturer utility (if they make one). Aside from that if the other 3 work then I would try to exchange it.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s