Symantec System recovery 2011 will not backup to USB 3.0 Drive

We have a 2003 R2 Server and are trying to get a Symantec System Recovery 2011 trial running over usb 3.0 to a backup drive.  I have this running with the same software and hardware at other sites but cannot get it to work here.  It works fine if you plug the drive into a USB 2 port.

When running the backup it gets up to 5%, the file is about 400MB on the drive and it stops, erases the file on the USB drive and pops up a error:  "Unable to Write File".  Clicking details gives the following "--Error EBAB03F1: The request could not be performed because of a I/O device error"  (UMI:V-281-2001-31)

We have tried 2 different USB 3.0 Controllers, 2 different External Drives same results.  Any suggestions?
ggobleAsked:
Who is Participating?
 
noxchoGlobal Support CoordinatorCommented:
Have you tried different USB3.0 drivers?
0
 
Alan HardistyCo-OwnerCommented:
Is the drive formatted as NTFS or FAT32?

If it is FAT32 - please reformat it as NTFS and try the backup again.
0
 
ggobleAuthor Commented:
It is NTFS on the Drive, and it is not a 4K drive (in case that comes up).  We have tried 2 different USB3.0 Controllers with different drivers.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
Alan HardistyCo-OwnerCommented:
Do you have a Y cable - one which has two USB A connectors and the other end (the tail of the Y) that fits the drive?

I had a similar issue with a USB 3.0 drive and it just wasn't getting enough power.  As soon as I doubled up the USB ports to it, it was happy.
0
 
ggobleAuthor Commented:
Interesting.  I don't have one but I'll find one and try it.
0
 
noxchoGlobal Support CoordinatorCommented:
If your drive has external power supply then you do not need additional connector on the cable.
0
 
ggobleAuthor Commented:
Thanks,  I just found that out also but didn't get a chance to post back on that.
0
 
ggobleAuthor Commented:
It turned out it was the drivers, the customer said they had the latest drivers on but they didn't.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.