Ask the Community
Groups
'No S3QL filesystem was found' error when adding cloud storage - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>If this error occurs with cloudadm 1.67, update to cloudadm 1.69 or later.</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p>Symptoms<br>See this error message when trying to connect to CloudHook storage: </p> <pre class="code codeBlock" spellcheck="false" tabindex="0"> cmc_nas execution failed. No S3QL filesystem was found at s3://unitrends-free-aws/offsite-backups/ ERROR: Failed to mount directory unitrends-free-aws/offsite-backups/ on /backups/Cloud_Storage.</pre> You can verify the version of cloudadm by running this command from a PuTTY/ssh command line: <pre class="code codeBlock" spellcheck="false" tabindex="0"> cloudadm status</pre> <pre class="code codeBlock" spellcheck="false" tabindex="0"> cloudadm version 1.74 CLOUD TYPE | STORAGE |ONLINE| MAX_GB |USED_GB ... </pre> <br><br><br><br><br> <h2 data-id="resolution"><strong>RESOLUTION</strong></h2> <p>When trying to add or connect to CloudHook storage, sometimes an earlier error may have been masked and the S3QL cloud filesystem did not get created. The resolution is to upgrade the cloudadm binary to version 1.69 or later.<br><br>Steps to apply the hotfix from a PuTTY/ssh command line: </p> <ol><li>wget <a href="/home/leaving?allowTrusted=1&target=ftp%3A%2F%2Fftp.unitrends.com%2Fsupport%2FHotfixes%2Fcloudadmc6-174">ftp://ftp.unitrends.com/support/Hotfixes/cloudadmc6-174</a></li> <li>chmod +x cloudadmc6-174</li> <li>cp /usr/bp/bin/cloudadm /usr/bp/bin/cloudadm-orig</li> <li>cp -f cloudadmc6-174 /usr/bp/bin/cloudadm</li> </ol><h2 data-id="cause"><strong>CAUSE</strong></h2> <p>If you are receiving this error message and already have cloudadm 1.69 or later, then please examine the /usr/bp/logs.dir/cloudadm.log for any error messages preceding the 'No S3QL filesystem' error to determine the cause.</p> </article> </main>