Last night I followed the "cleaner alternative method 1" of enabling SSH on a one year old 500G MBWE v01.01.18. This system never had any stability problems requiring a reset prior to last night, and this is the only hack I've done on this system. Now it hangs anywhere from almost immediately after powering it on to several minutes or longer after reboot. When it goes unresponsive, samba stops serving up cifs shares, the web interface goes unresponsive, and a PuTTY SSH session terminates. Sometimes but not always holding the power button for many seconds will cause it to power off - other times I have to pull power. It doesn't seem to shutdown normally where you see activity through the LEDS and then a few moments later it goes off (not a clean shut down). When it goes unresponsive like I described, I can always still ping the IP address, although the NetBIOS name often goes away on my network (presumably because samba stops advertising it).
When the system stays up for a few minutes, I've successfully vi'ed inetd.conf to comment out the ssh line and the rebooting again. I confirmed that I can no longer ssh into the system but the same behavior occurs. I ran the enable upgrade script again to re-enable SSH.
I've attached the system to a network segment that has no route to the Internet and it sometimes appears to run longer here, but still will hang eventually.
At one point it felt like the problem was hardware heat related, but I think I ruled that out by testing it briefly over the lunch hour and having it go unresponsive within a couple minutes after starting cold.
Are there any logs that I can look at get try and get a sense on what is going on? I don't find the standard syslog and am concerned trying to perform a firmware update to version 2.current until I better understand why it's going unresponsive. I'm versed enough in UNIX to work my way around some basic troubleshooting, but I'm not currently positioned to be able to remove the drive and move it to another Linux system to recover if it fails to boot completely. Right now the system will frequently run for several minutes or more to where I feel if I can get a sense on what is going on I can fix it It's not a brick right now - it's been running fine the entire time I wrote this long-winded message but will eventually hang again!
Thanks in advance!