Link to home
Start Free TrialLog in
Avatar of ggoble
ggobleFlag for United States of America

asked on

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?
Avatar of Alan Hardisty
Alan Hardisty
Flag of United Kingdom of Great Britain and Northern Ireland image

Is the drive formatted as NTFS or FAT32?

If it is FAT32 - please reformat it as NTFS and try the backup again.
ASKER CERTIFIED SOLUTION
Avatar of noxcho
noxcho
Flag of Germany image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of ggoble

ASKER

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.
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.
Avatar of ggoble

ASKER

Interesting.  I don't have one but I'll find one and try it.
If your drive has external power supply then you do not need additional connector on the cable.
Avatar of ggoble

ASKER

Thanks,  I just found that out also but didn't get a chance to post back on that.
Avatar of ggoble

ASKER

It turned out it was the drivers, the customer said they had the latest drivers on but they didn't.