Ask the Community
Groups
AWS cloud file system damaged or not unmounted cleanly - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="summary"><strong>SUMMARY</strong></h2> <p>Steps to repair a cloud file system damaged by an unclean shutdown.</p> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p></p> <h2 data-id="issue-1">Issue</h2> <p>The cloud storage returns the message: “File system damaged or not unmounted cleanly, run fsck!”</p> <h2 data-id="cause">Cause</h2> <p>An unclean shutdown</p> <h2 data-id="resolution">Resolution</h2> <p>Since release 8.0 (cloudadm 1.13), the file system repair should occur automatically. If it does not, execute the following commands from the command line:</p> <pre class="code codeBlock" spellcheck="false" tabindex="0"> # /usr/bp/bin/cloudadm get cloudadm version 1.09 storage_id = 18 […] # /usr/bp/bin/cloudadm prep -f 18</pre> <p>This will run the cloud fsck.s3ql on storage_id = 18 (replace 18 with your actual storage id). The –f option forces a full check.</p> <h2 data-id="reference">Reference</h2> <p><a rel="nofollow" href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Funitrends-support.zendesk.com%2Fhc%2Fen-us%2Farticles%2F360013175837">Additional CloudHook Information </a></p> </article> </main>