Russ -- Thanks for the lengthy response. The reboots are being triggered by an external process that SSHes in and executes "reboot".
I was aware of the /.autofsck file's purpose though I'm not sure if it's the culprit. Here's the grep fsck results: [root@psc2897 init.d]# grep fsck * functions:# Log that something passed, but may have had errors. Useful for fsck halt:rm -f /.autofsck halt: echo $"On the next boot fsck will be skipped." halt:elif [ -f /forcefsck ]; then halt: echo $"On the next boot fsck will be forced." netfs: fsck -A -T -M -a -t opts=_netdev [root@psc2897 init.d]# I can also try removing the non-root file systems in attempt narrow the possible culprit file systems. I will also give the k99 step a shot... Do you know of any kernel parameters I could add to zipl.conf to produce more informational messages that might help diagnose the problem? Neale -- "uname -a" produces: Linux psc2897 2.6.32-573.cl6.s390x #1 SMP Wed Oct 14 08:14:21 EDT 2015 s390x s390x s390x GNU/Linux Thanks again to you both for the help! Kevin Morris Reed Elsevier - Technology Services zOS Systems Engineering ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
