SerpentMage
Dabbler
- Joined
- May 16, 2017
- Messages
- 29
Hello,
I've had this server up and running for a couple years now, only major issue so far has been the expected ASRock C2550D4I, however I've had the board replaced previously and this does not seem to be a similar issue as before the system would not boot at all. However I'm still not ruling out the board.
System Details:
So far over the past 2 to 3 weeks I've had my NAS stop responding over night. The first time, I could log in via the WebGUI (SSH was not enabled then), however I could not get status of my Pools nor my one Jail. I tried a normal shutdown via the GUI and after that did nothing via the Shell, which also failed. I was forced to hard reset via IPMI. Initially I did a reset via IPMI, which never fully lost power, a continuous ping never dropped at all. When it came back most of the network config was missing. At this point I powered the server down, ensuring it was off via IPMI and that my pings were failing then powered back on.
Everything was fine for a couple weeks, I can't remember exactly sorry. However I noticed nothing out of the ordinary. Night before last, morning of the 13th, same thing. I woke up to the shares unresponsive. Except this time, I could not log via GUI, I'd get to the prompt but it'd just sit there. Also I could not ping it. I logged into my IPMI interface on the motherboard and remembered it had a remote console (simulates a montitor and keyboard plugged in) and tried to shutdown that way, which failed. I shutdown via IPMI power control again, waited about 30 seconds, and restarted. No issues during boot that I could see. Everything came back normal.
After this I set the syslog to go to a remote system and setup a free syslog service on another PC to try to get some info. The same thing happened again this last night (morning of 14th). I had to shutdown I got the syslog files, however admittedly I'm not 100% sure what I'm looking at. I was unable to log in via GUI, SSH and Remote Console shutdown failed as before. I currently have the server powered off.
Any suggestions or guidance would be greatly appreciated. I do have some jobs set to run at night, SMART tests and such, I'm wondering if something with them is causing problems? I can upload the syslogs if that would help.
Thanks, and apologies for the long post. Trying to provide as much detail as possible.
-John
I've had this server up and running for a couple years now, only major issue so far has been the expected ASRock C2550D4I, however I've had the board replaced previously and this does not seem to be a similar issue as before the system would not boot at all. However I'm still not ruling out the board.
System Details:
- ASRock Rack C25504DI
- Intel Avoton C2550 Processor
- 16GB ECC
- 4 x Seagate Ironwolf 2TB in RaidZ2, 4 x WD Red 2TB in RaidZ2, also have a single 16GB Sandisk USB Flash Drive as boot.
- Onboard HardDrive controllers, I believe they're Marvell SE9230 or Marvell SE9220
- Onboard NICs, chipset is Intel I210.
So far over the past 2 to 3 weeks I've had my NAS stop responding over night. The first time, I could log in via the WebGUI (SSH was not enabled then), however I could not get status of my Pools nor my one Jail. I tried a normal shutdown via the GUI and after that did nothing via the Shell, which also failed. I was forced to hard reset via IPMI. Initially I did a reset via IPMI, which never fully lost power, a continuous ping never dropped at all. When it came back most of the network config was missing. At this point I powered the server down, ensuring it was off via IPMI and that my pings were failing then powered back on.
Everything was fine for a couple weeks, I can't remember exactly sorry. However I noticed nothing out of the ordinary. Night before last, morning of the 13th, same thing. I woke up to the shares unresponsive. Except this time, I could not log via GUI, I'd get to the prompt but it'd just sit there. Also I could not ping it. I logged into my IPMI interface on the motherboard and remembered it had a remote console (simulates a montitor and keyboard plugged in) and tried to shutdown that way, which failed. I shutdown via IPMI power control again, waited about 30 seconds, and restarted. No issues during boot that I could see. Everything came back normal.
After this I set the syslog to go to a remote system and setup a free syslog service on another PC to try to get some info. The same thing happened again this last night (morning of 14th). I had to shutdown I got the syslog files, however admittedly I'm not 100% sure what I'm looking at. I was unable to log in via GUI, SSH and Remote Console shutdown failed as before. I currently have the server powered off.
Any suggestions or guidance would be greatly appreciated. I do have some jobs set to run at night, SMART tests and such, I'm wondering if something with them is causing problems? I can upload the syslogs if that would help.
Thanks, and apologies for the long post. Trying to provide as much detail as possible.
-John