Alex@rtnVFRmedia Suffolk UK<p>TIL: an exhausted <a href="https://social.tchncs.de/tags/cmos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>cmos</span></a> <a href="https://social.tchncs.de/tags/battery" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>battery</span></a> can cause <a href="https://social.tchncs.de/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> to behave strangely after a hard <a href="https://social.tchncs.de/tags/shutdown" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>shutdown</span></a> (caused by a <a href="https://social.tchncs.de/tags/UPS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UPS</span></a> being incorrectly turned off) - it uses the BIOS time to check the filesystem block timestamps, and as it had gone back to 2012 the OS thinks the filesystem time is in the future! (At least the hard drive on this server isn't on the way out yet which is what I had feared, but this required an emergency visit to the office as it is the main <a href="https://social.tchncs.de/tags/VOIP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>VOIP</span></a> <a href="https://social.tchncs.de/tags/PBX" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PBX</span></a>) <a href="https://social.tchncs.de/tags/sysadmin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>sysadmin</span></a></p>