On 11/07/12 17:42, Mark Rogers wrote:
I'd also be interested to know if there's anything I can do down an SSH connection to force it to reboot, given the lack of access to the filesystem to even run "sudo" never mind "reboot". I'm guessing that sending Alt-Ctrl-Del or Alt-SysRq-B via SSH are out...
Solution in theory here: http://rackerhacker.com/2009/01/29/linux-emergency-reboot-or-shutdown-with-m...
It turns out that Alt-SysRq-B commands can be sent via SSH. However, you need to be root to do it, and I wasn't logged in as root when the filesystem disappeared, and of-course now there's no way to achieve that (that I can think of anyway).
When I do regain access, is there any way I can make /proc/sys/kernel/trigger and /proc/sysrq-trigger writable by anyone other than root? Or do I need to make sure I'm always logged in as root until I find the root cause of this problem?
Mark