It doesn't actually reboot, and the power is still on. There's a monitor on the console, but when this mysterious crash happens, I can't actually do anything with it, because it's switched into power saving mode, and the monitor light just flashes dimly. The NUM LOCK on the keyboard is off and doesn't respond. So I hold the power button down, and I hear the 'click' as the machine shuts down, so it's definitely not actually 'dying' from an electrical point of view. And when I power it back up, I don't see any evidence that it's running fsck... oh, hang on ...TrevorH wrote:Your symptoms sound suspiciously like a hardware error though. Does it reboot or you have to power cycle it manually? Did it start happening recently and had you changed anything just before it started?
[root@serverHostname conf]# grep "fsck" /var/log/*
/var/log/messages:Oct 5 18:24:47 serverHostname kernel: EXT4-fs (sdb1): warning: maximal mount count reached, running e2fsck is recommended
/var/log/messages:Oct 7 14:00:46 serverHostname kernel: EXT4-fs (sdb1): warning: maximal mount count reached, running e2fsck is recommended
Nah. That was after the crash.