How can we help?

My Cases

Appliance Cannot Be Initialized If USB Device Uses NTFS File System
Last Updated: Dec 15, 2017 04:47PM EST

This article applies to:  Echo360 Admins

Summary

This troubleshooting article describes a known issue that affects the initialization process of Echo360 capture appliances when the USB device used for initialization is formatted with NTFS.

Symptoms

  • A new Echo360 capture appliance does not respond in any way to the presence of a device.xmlfile on the root of a plug-and-play compatible USB mass storage device.
  • Diagnostic text files normally written back to the USB mass storage device when connected to the appliance cannot be found. Such files have names of the following formats:
    echo_network_info_00-50-C2-{NN-NN-NN}.txt
    00-50-C2-{NN-NN-NN}
    • Note: {NN-NN-NN} is used to represent the significant digits of an appliance MAC address. All SD appliance MAC addresses begin with the digits 00-50-C2. SafeCapture HD appliances have MAC addresses beginning in 00-13-95.

Cause

The Echo360 capture appliance is an embedded Linux device. NTFS drivers for Linux are considered to be experimental by the community at large, and therefore are not included in the appliance's kernel. The appliance thus has no means to read from an NTFS-formatted volume.

Solution

Providing a device.xml file with a USB device formatted for NTFS is not a supported method for initializing an Echo360 capture appliance. Please use a USB mass storage device that has been formatted for FAT or FAT32 instead.

c9f5f1d87ac29bd0c146e9565da3c739@echo360.desk-mail.com
https://cdn.desk.com/
false
desk
Loading
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
about
false
Invalid characters found
/customer/en/portal/articles/autocomplete