Auto update

This commit is contained in:
Andrea Mazzoleni 2016-06-27 22:22:41 +02:00
parent f9ba5a9951
commit b65c0154eb

View file

@ -142,6 +142,7 @@ Frequently Asked Questions for <span class="bold">SnapRAID</span>.
<h3>Know Problems</h3>
<ul>
<li><a href="#panic">Why does my machine reboots or crashes while SnapRAID is running?</a></li>
<li><a href="#oomkiller">Why in Linux does SnapRAID abort without any error message?</a></li>
<li><a href="#pargrowerror">Why in 'sync' do I get the error 'Failed to grow parity file 'xxx' to size xxx due lack of space.'?</a></li>
<li><a href="#dupinode">Why do I get the error 'Internal inode xxx inconsistency...'?</a></li>
@ -1216,6 +1217,22 @@ RAID functions used for recovering with 'fix':
<h2>Know Problems</h2>
<h3 id="panic">Why does my machine reboots or crashes while SnapRAID is running?</h3>
<p>
When the machine reboots or crashes, it's clearly a hardware issue.
SnapRAID cannot reboot or crash the system.
</p>
<p>
Possible thing to checks are:
<ul>
<li>Check your memory with <a href="http://www.memtest86.com/">memtest86</a></li>
<li>Check your HD cabling</li>
<li>Ensure that your power supply can sustatin all the HDs spinning at the same time</li>
<li>Check that the temperature of your system is not too high</li>
<li>Check in systemlog or EventViewer if there is any hint of the possible issue</li>
</ul>
</p>
<h3 id="oomkiller">Why in Linux does SnapRAID abort without any error message?</h3>
<p>
Likely you have too few free memory, and the Linux OOM (out-of-memory) killer