Zotac CI323 crashes / shuts down / sleeps / turns off nics unexpectately
-
@thenarc said in Zotac CI323 crashes / shuts down / sleeps / turns off nics unexpectately:
Also if I can inject a question of my own . . . you mentioned updating the BIOS. Can I assume that means you're running the latest (Version 2K180507)? If so, did you experience any issues? I tried updating one of my CI323s to that BIOS as soon as it came out, but it had the effect of making pfSense "lose" one of the NICs. I double checked all the BIOS settings, but on boot pfSense consistently saw only one NIC and bailed, so I had to downgrade to the prior BIOS release.
Yes I'm running the 2K180507 BIOS and I had no problems upgrading to this BIOS: both NICs work fine.
I've enabled Wake-on-LAN and run Win8 boot sequence. -
@martinnl said in Zotac CI323 crashes / shuts down / sleeps / turns off nics unexpectately:
@thenarc said in Zotac CI323 crashes / shuts down / sleeps / turns off nics unexpectately:
Also if I can inject a question of my own . . . you mentioned updating the BIOS. Can I assume that means you're running the latest (Version 2K180507)? If so, did you experience any issues? I tried updating one of my CI323s to that BIOS as soon as it came out, but it had the effect of making pfSense "lose" one of the NICs. I double checked all the BIOS settings, but on boot pfSense consistently saw only one NIC and bailed, so I had to downgrade to the prior BIOS release.
Yes I'm running the 2K180507 BIOS and I had no problems upgrading to this BIOS: both NICs work fine.
I've enabled Wake-on-LAN and run Win8 boot sequence.Thanks for the info, maybe I'll be brave and try again ;) Not sure why it went sideways for me, but at least I know it can work now.
-
I'll do A) some log-catching first. I have a spare SSD and memory too (both different brands). I'll have a look if I can B) image the disk and place it on the other SSD and swap memory.
Plan C) would be to put an other OS on the system :) -
Mine started acting up when I moved from 2.3 embedded to 2.4, then 2.4 was stable for some reason, then again at one point it started acting up recently. Last thing I did was plug in the UPS USB cable for apcupsd
Also, interestingly enough, when I plugged in that usb cable, it freaked out and either crashed or rebooted, I can't remember, I run it headless and could never get anything useful out of the log either.
I have removed the usb cable / connection and it's been running fine for 7 days.
I'm pretty sure the first time i had 2.4 and it was unstable, I had a logitech usb wireless receiver for keyboard/mouse plugged in and at some point I removed it and it was stable for approx 70 days.
So, while I can't confirm at the moment, I think there's something going on with the USB. If you have anything USB plugged in, try removing it and see what happens.
-
@gertjan said in Zotac CI323 crashes / shuts down / sleeps / turns off nics unexpectately:
If so, boot, enter, and shut down one or more interfaces (the box becomes useless, that just fine during testing). If it stops crashing, enable them one by one until you found the faulty NIC.
I disabled all interfaces except the LAN interface and I shut down all services except the syslogd service. PfSense is now running for 16 hours without problems. Though pretty much bricked.
I'm bringing services back on every 3 hours now and then see when it crashes again. Now running including the DHCP service an NTP service.
-
@duren said in Zotac CI323 crashes / shuts down / sleeps / turns off nics unexpectately:
So, while I can't confirm at the moment, I think there's something going on with the USB. If you have anything USB plugged in, try removing it and see what happens.
Thx for the suggestion. That won't be a cause in my case: I have nothing plugged in except two ethernet cables and the power supply.
-
I'd suspect that the power supply is flaking out. But memory test can't hurt.
-
Power supply is an interesting thought . . . the CI323 uses an external AC-to-DC brick. Are you still using the one that came with the machine? If you have another with the same specs (same voltage, same polarity, and at least as high a current rating as the official brick) you could try swapping that out.
-
@vamike said in Zotac CI323 crashes / shuts down / sleeps / turns off nics unexpectately:
I'd suspect that the power supply is flaking out. But memory test can't hurt.
I had this very issue. I ended up trading mine out for a rackmount unit because my Zotac kept crashing and turning completely off. Took me a few times until I realized that if I wiggled the cord, it would turn on and off. No matter how I turned or secured the cord, it would lose power randomly. Plus I needed more NIC ports so it was inevitable to switch out. Great little box until I ran into those issues a few months ago.
Note - Mine was the internal power barrel connectors and not the brick itself. That's why I didn't bother trying to fix it. Could be an easy fix with some solder, but oh well :)
-
Ok, my CI323 is back on track! It has run for 48 hours until a manual reboot and is now running over 60 hours.
But what was the missing puzzle in the unexpected shutdowns?
I haven't been able to reproduce the error, but I guess that resetting all logs and enlarging the maximum file size did the trick.I have reset the logs in order to solve the 'signal 15' message. But without the effected result: the 'signal 15' message is still there.
After this step I have disabled all but the LAN interface and all but the syslogd service. Bringing back all services and interfaces one by one, every 3 hours. Ending up in the situation that all interfaces and services were up, without the system shutting down anymore.
After 48 hours I've rebooted to start with all interfaces and services enabled by default. And still it did not shut down anymore.As the only actual change in the system is de reset of the logging I would say this solved my problem.
An other option would be that the gradual enabling of the services/interfaces could have broken some kind of chain of events. This seems less likely to me.So: I'm happily using my CI323 again! (on 1.95 realtek drivers).
I'll be back when i'm able to reproduce the error (solving). -
I would be surprised if that is what solved it. The behaviour really looks hardware related.
Still, it would be nice if that has resolved it.
Steve
