A healthy drive appears to have many bad sectors during imaging
The issue is likely caused by a loose port connection, leading to read errors and even drive identification issues.
To completely reset the physical link, unplug the cable from both the port and the storage device, wait for a whole minute and plug it snugly back in.
A spinning 3.5" SATA drive in a USB enclosure does not spin
All USB ports of the Taskforce are designed to work with USB devices conforming to the USB specification. However, some USB-enclosed HDDs consume too much current at spinup, in fact violating the specification.
For such drives, we have equipped USB 3 and USB 4 ports with extra electric load capacity. Try connecting the drive to USB 3 or USB 4 ports.
An M.2 NVMe drive does not get identified
Keep in mind that TaskForce does no support drive hotplug for M.2 PCIe NVMe drives. To replace an NVMe drive, TaskForce needs to be powered off:
When I click Continue upon selecting targets, TaskForce does not open the Imaging Settings page
The issue must have been caused by the browser cache.
Please note that TaskForce works properly only with the Chrome browser.
When I image to the network, the speed is low
When imaging to network, there are two potential bottlenecks:
1. Network performance
It can be enhanced with 10Gbit connection. Another important thing: Jumbo frames should be enabled in TaskForce settings, target computer/NAS network card and network switches/routers in between them.
2. Write speed of target network drive
It can be more difficult to improve. In particular, if one images several drives to the same network location. It leads to a situation when 8 source SSDs are read with 500 MB/s speed but the total writing capability of target network drive cuts it to just 400 MB/s. Distributed between 8 sessions, the speed becomes too low (400/8=50 MB/s per session).
The best solutions to achieve top speeds with target network locations:
How can I image a U.2 NVMe drive?
To use a drive with U.2 interface, attach the drive to TaskForce with the help of U.2-to-M.2 adapter and cable:
Connecting to TaskForce:
TaskForce booting does not get completed.
To make sure TaskForce boots correctly, reset TaskForce:
Internet Explorer renames TaskForce's .AFM firmware file into a ZIP file.
Internet Explorer identifies an AFM file as a ZIP file and automatically renames it to ZIP. Read this article about the reason Explorer does this. This issue only occurs in the Internet Explorer.
We suggest using other popular browsers, such as Chrome or Firefox.
IP address does not show when an Ethernet cable is plugged into the unit
Usually, your network router is responsible for assigning IP addresses to other computers or devices in the same network.
Make sure your router has DHCP support and it is enabled.
When I try to turn on the screen, a battery indicator starts blinking
Screen battery needs to be charged. Let the unit stay powered on for 5 - 10 minutes and avoid turning the screen on during this time. 10 minutes later, use the button on the screen to turn it on as usual.
I cannot find my network shared folderFollow these steps to setup Windows network folder:
We strongly recommend using the latest OS versions: Windows 10, Windows Server 2019/2016, Centos 7, Ubuntu 18.4. It is crucial for reaching high network transfer speeds.
I want to see the syslog for more information about the issue I am facing
To download the TaskForce logs: