Aller au contenu principal

Unable to see USB attached disks (USB3?)

Thread needs solution

Have the current Latest Build: #6673 of Acronis True Image 2014.
Dell XPS L502X laptop
Windows 7 Home Pre. with sp1

Unable to see the following drives in Acronis.
1. Toshiba HDTB105EK3A (USB 3.0 STOR.E BASICS - 2.5" - 500GB)
2. Inateck FEU3NS-1 USB 3.0 FITTED with a Crucial M500 240GB SATA SSD

I initially thought the SSD drive was the issue. So swapped the laptop harddrive with the SSD, Acronis can see new SSD, but then can't my laptop harddrive which is now in the Inateck enclosure.

So tried the Toshiba drive but Acronis can't see that either.

Not currently able to clone anything. Unsure of what the issue is, can anyone suggest anything.

https://kb.acronis.com/content/15487
http://www.tweaktown.com/reviews/6235/inateck-feu3ns-1-usb-3-0-external…
http://www.toshiba.co.uk/hard-drives/portable/store-basics/hdtb105ek3aa/

Both products work in Window without any issue.

0 Users found this helpful

Make sure all drivers are up to date. When a drive is attached and ATI cannot recognize it, can it be seen in Windows Explorer? In same scenario, looking in Device Manager, do you see any exclamation marks?

Are you connecting both drives at same time when this occurs? If so are you using separate ports to do so or a single port using a hub? If using a hub remove it from the chain and see if the problem persists.

Don't see any issue in the device manager in Windows.

I have my old laptop disk in the Inateck USB device, and new ssd disk in the laptop both works 100% in Windows.
The USB disk appears to be using just the standard Microsoft Drivers...
Inateck USB Device Properties
C:\Windows\system32\DRIVERS\disk.sys
c:\Windows\system32\DRIVERS\FTSRV.SYS
C:\windows\system32\drivers\partmgr.sys
c:\windows\system32\DRIVERS\stdcftn.sys
c:\windows\system32\DRIVERS\VIDSFLT.SYS

Have same issue with Toshiba disk this comes with a disk when you buy it. (You don't need to put one in)
Both disks has been tried in each USB slot * 2 one at time and rebooted[F11] on each occasion.
Have a eSATA port on laptop but sadly no disk caddy to connect it to. Does anyone think the boot media will see a disk here?

Fichier attaché Taille
180993-114136.jpg 32.61 Ko

You are certain that the enclosure and the toshiba drive are usb 3 capable? Have you tried attaching to usb 2 port?

Is your bios up to date? Often times this is the problem.

Don't connect via a hub, a port in a monitor, a USB extension cord, etc. Connect the external drive directly to a USB port on the laptop.

And, as Enchantech suggests, try connecting to a USB 2.0 port. On your Dell L502x laptop, the USB port on the right-hand side of the case is USB 2.0.

Was never able to get the HD or SSD working on the USB PORTS. I just brought a cheap "eSATA Cable for SATA HDD and SSD" and then used the port on right hand-side of the laptop. Acronis True Image 2014 saw the disk and was able to clone. I suspect a USB 2/3 issue.

Thanks
Should have swap out the HD years ago.

Does anyone have any other solutions besides the ones listed? I am trying to image a Dell 3531. It sees the USB jump drive with Acronis on it but doesn't see the external hard drive to which I am trying to save the image to. I have tried Acronis 2013 & 2014 and have tried 3 external hard drives. Nothing seems to be working. I can't burn it to disk because the laptop doesn't have a DVD drive. It also does not have a ethernet port. It is WIFI and USB only.

I would say that these issues boil down to a driver issue either USB 3.0 drivers themselves or motherboard chipset set drivers. It is possible as well that the external drive itself has an issue with USB 3.0 connections. I know that WD released a firmware update for some drives for this issue.

The MOBO sees all of the external hard drives that I tried. I know this because they are a boot option under F12 which is the boot option menu. It's like Acronis can't get past the fact that the mobo doesn't have a ethernet port so it doesn't even look for external hard drives.

Your mobo sees the drives as attached devices. This does not mean that the ports will operate at the USB 3.0 spec.. You need current drivers that are not in conflict with the OS or the hardware itself to get things working. Do some research and you may find a solution.