Troubleshooting Unable to connect to external storage Errors on the MiSeq i100 Series

Background

The MiSeq i100 Series instruments require off-instrument storage of sequencing run data either in the form of local External Storage or Cloud Storage. When using local external storage with either USB External Hard Drive or local Network Storage, the connection to this storage is configured through the External Storage UI.

If there are issues connecting to the external storage option, the following error displays:

Unable to connect to external storage. Check your configuration settings and try again.

Troubleshooting Actions

1. Select the View Error Details link below the error message to bring up additional information on the issue.

2. See the following common error messages and their resolution actions. Please note, Illumina strongly recommends discussing these issues and the error messages with the local IT team as they will likely need to be addressed by them.

   1. IMPORTANT NOTE: The orientation of the slashes (either forward or back slashes) does not effect the mounting process on the MiSeq i100, the Control Software accepts either direction.

Permission Denied (SMB)

1. Confirm the username, domain, and password credentials are input correctly and there are no typos.

2. If the username is part of an Active Directory, input the domain in the Domain text field and not in the username field as DOMAIN\username

3. Confirm the network user has read and write access to the intended share folder, and at least read access to all parent folders.

Access Denied by server while mount... (NFS)

1. Caused by errors when configuring the /etc/exports file on the network storage server, resulting in the instrument having incorrect permissions.

2. Confirm NFS Export settings on storage server to ensure MiSeq i100 has read/write privileges to share directory.

No such file or directory

1. Review the share path in the Server Location field to confirm there are no typos and that the full path to the share is present.

2. Confirm the share path exists on the network storage location and that it is not part of a hidden share.

Mount error: could not resolve address

1. Review the server hostname and confirm that it is accurate and there are no typos.

2. If server is joined to a domain, include the domain name with the hostname to use the Fully Qualified Domain Name (FQDN) (ex. //servername.domain.com/share)

3. Use the IP address for the server instead of the hostname or the Fully Qualified Domain Name (FQDN).

Output channel does not have correct permissions

1. Caused by read-only permissions at the share folder. Work with local IT team to confirm that the network user has full read, write, and execute permissions on the share folder.

Blank or Empty View error details window

1. Generally caused by spaces in the share folder path names.

2. Review share folder path names and remove any spaces from the folder names.

Failed to validate request DTO

1. Generally caused by using the incorrect Server location syntax for the SMB or NFS protocol selected.

2. Review the Server Location input and match it to the appropriate network protocol in use:

   1. SMB Shares: //servername.domain.com/share

   2. NFS Shares: IP address:/share (ex. 10.1.10.123:/output)

Error: Invalid argument. Please check your mount options.

1. Generally caused by hidden shares specified by $ in the share name. The $ symbol is an illegal character for the Illumina Run Manager and Universal Copy Service (UCS) software, which establishes the External Storage mount.

2. Work with local IT team to rename the share and remove the $ symbol from the share folder name.

Mount error(95): Operation not supported

1. Generally caused by incompatible SMB versions between the instrument and network storage.

   1. If the 'Require encryption' option is selected, the network storage must use SMBv3.

      1. To resolve, de-select the 'Require encryption' option and repeat Test Configuration or work with local IT team to update server to use SMBv3.

   2. The MiSeq i100 does not support connections over SMBv1.

      1. If network storage uses SMBv1, work with local IT team to update network storage protocol to at least SMBv2 or higher.