Dear all
This is a HP microserver:
FreeNAS Build FreeNAS-8.0.4-RELEASE-p3-x64 (11703)
Platform AMD Turion(tm) II Neo N40L Dual-Core Processor
Memory 8049MB
OS Version FreeBSD 8.2-RELEASE-p9
4 x 1tb with one ZFS raid 2 volume, various CIFs shares and one isci on top of that.
Active directory, cifs, smart, SSH and ISCI services enabled.
All runs perfectly for a couple of weeks and then quite quickly the whole thing becomes unresponsive, no connections available, no web ui. I do sometimes seem to still be able to get in to the console via SSH (more below)
Basically my current fix is to pull the plug on the box and it reboots back to normal, but this is obviously not a good thing.
SMART on one of the disks is reporting Device: /dev/ada3, 2 Offline uncorrectable sectors but this seems to be stable so I haven't bothered to replace the disk yet, though I do have one if it gets worse.
Questions:
1) At least a soft reboot via SSH would be better - but what command do I use?
2) Might the problem be logged somewhere? Where would I find this?
3) Setting up a scheduled reboot every week at some convenient time might be a solution, albeit not very satisfactory.... how?
4) Is there some other setting I could adjust which might fix the problem more permanently?
Thanks in advance
Richard
This is a HP microserver:
FreeNAS Build FreeNAS-8.0.4-RELEASE-p3-x64 (11703)
Platform AMD Turion(tm) II Neo N40L Dual-Core Processor
Memory 8049MB
OS Version FreeBSD 8.2-RELEASE-p9
4 x 1tb with one ZFS raid 2 volume, various CIFs shares and one isci on top of that.
Active directory, cifs, smart, SSH and ISCI services enabled.
All runs perfectly for a couple of weeks and then quite quickly the whole thing becomes unresponsive, no connections available, no web ui. I do sometimes seem to still be able to get in to the console via SSH (more below)
Basically my current fix is to pull the plug on the box and it reboots back to normal, but this is obviously not a good thing.
SMART on one of the disks is reporting Device: /dev/ada3, 2 Offline uncorrectable sectors but this seems to be stable so I haven't bothered to replace the disk yet, though I do have one if it gets worse.
Questions:
1) At least a soft reboot via SSH would be better - but what command do I use?
2) Might the problem be logged somewhere? Where would I find this?
3) Setting up a scheduled reboot every week at some convenient time might be a solution, albeit not very satisfactory.... how?
4) Is there some other setting I could adjust which might fix the problem more permanently?
Thanks in advance
Richard