I have recently installed OMV and am now experiencing an annoying problem. When the sever has been running for some time (typically less than 24 hours) it suddenly stops working. When this has happened I can no longer access the Web GUI (server typically throws a 403 authentification error), also SSH does not let me connect and SMB shares are visible but no longer possible to connect to. I have googled for answers to the problem without success. I read somewhere that a failing usb stick for the OS might cause problems like this, but mine is a brand new sandisk cruzer blade, which it seems as others are using without problems. Another post suggested that insufficient capacity of the OS disk could make it impossible to login through the web GUI but this is not my problem either (df -h says that only ~800 MB of 4 GB is used so far).
As a quick fix I tried to enable the auto reboot feature but it seems as the server does not reboot when it has entered this state. The only remedy I have found is to cut the power and reboot the server. I have no idea what could be causing the problem and was hoping for some guidance how to further troubleshoot.
Below is some short info about my installation
Hardware:
MB:Intel DN2700MT (integrated Atom CPU)
RAM: 8 GB
HDD: 2x WD 1TB (WD10EZRX) in RAID mirror
OS Disk: Sandisk Cruzer Blade 4 GB
Software:
OMV Version: 0.3.0.17 (Omnius)
Kernel: Linux 2.6.36-5-amd64
Plugins: no additional plugins installed
Services running: SMB/CIFS, SSH, NFS
Any help how to troubkeshoot or fix this problem would be highly appreciated. I would really like to avoid to reinstall OMV since I am worried for the data on my raid disks and the OMV configuration data.
Many thanks.
/Jonas