June 2, 201214 yr Hi! I use unmenu together with only a few plugins. On the first of June my server started the "monthly parity check". At the beginning everything looked good. After 24 hours the hard disks are still spinning and I can't access the array via the GUI or telnet. Due to the fact that the check takes normally around 700-800 minutes I restarted (hard reset) the machine and the parity check began again. This morning I discovered the same. I can't access the system via GUI or telnet. I would like to provide a syslog. Unfortunately it is gone due to the reboot. To avoid further problems I stopped the check after today's reboot. Running: RC3 and the Supermicro board in my signature... Bye.
June 2, 201214 yr Hi! I use unmenu together with only a few plugins. On the first of June my server started the "monthly parity check". At the beginning everything looked good. After 24 hours the hard disks are still spinning and I can't access the array via the GUI or telnet. Due to the fact that the check takes normally around 700-800 minutes I restarted (hard reset) the machine and the parity check began again. This morning I discovered the same. I can't access the system via GUI or telnet. I would like to provide a syslog. Unfortunately it is gone due to the reboot. To avoid further problems I stopped the check after today's reboot. Running: RC3 and the Supermicro board in my signature... Bye. It sounds as if you are running out of memory, (possibly by filling the syslog with errors?) If as repeatable as you describe, in a telnet window type tail -f /var/log/syslog and start another non-correcting parity check. You'll be able to see (hopefully) what is happening before the crash occurs.
June 3, 201214 yr Author Hi! Hm. This is a weird one. After 800 minutes the parity check ended successful without any problems. Bye.
Archived
This topic is now archived and is closed to further replies.