All: I have been noting repeated system hangs and/or crashes that drops my zimacube off the network - it is not pingable nor can I connect with ssh. My only recourse is to do a hard reboot with the power button.
After doing some reading here in the forums, I think that resetting my Zimacube’s CMOS may be needed.
My question is: will this affect my current RAID5 setup ?
Hi, Pat,
It seems that the situation you described is strange. We are not sure whether resetting CMOS can help solve the problem. However, it is certain that resetting CMOS will not affect the RAID5 configuration because its information is stored in the database and RAID member disks.
If possible, can you provide your network ID and ssh user and password through DM so that we can provide remote support at the appropriate time to help you quickly and effectively eliminate the root cause of the fault.
BR,
Orca
@orca-zhang I will DM you about this and the smb file dialog list issue I have noted. Interestingly, I have stopped using the MacOS Zima client software and have had no further hangs or crashes. I use various VPN connections (mostly openVPN connections with one SonicWall connection) for work and found that these hang/crash issues seemed to be more likely when using VPN and the Zima client had an active connection to my Zimacube. Could it be possible for a VPN connection to interfere in this way?
That sounds like a socket exhaustion error - you could use something like netstat -na to dump the current socket and connection list so we can see if the number of handles/sockets are being left in a time-wait state
To solve the Zima Client (MacOSX) problem, you can refer to Zima Client: Stuck at Initializing?! - #10 by JohnGuan to obtain the log (if the log still exists)
Could this be over-heat problem?