SOLVED Shutdown and reboot problems

[joeschmuck]

That doesn't make sense to me, as you can see from my log it contained a few days worth of data. Where is your log data stored? Mine are on my pool, not that it should make a difference. Well I'm not sure where to go from here if you cannot check your log files.

We never established this before but what version of FreeNAS are you running? I'm using 9.3-Stable (most current version).

 

[74m]

The Syslog in the Web-GUI was unchecked... ;)
Now my messages log contains at least two reboot-series.

This is an example for the first shutdown, which usually results in a reboot. As you can see in this log, 3 minutes after the shutdown, my freenas was online again.

Code:

Apr  1 04:19:00 FreeNAS shutdown: power-down by root:
Apr  1 04:19:03 FreeNAS kernel: epair0a: link state changed to DOWN
Apr  1 04:19:03 FreeNAS kernel: epair0a: link state changed to DOWN
Apr  1 04:19:03 FreeNAS kernel: epair0b: link state changed to DOWN
Apr  1 04:19:03 FreeNAS kernel: epair0b: link state changed to DOWN
Apr  1 04:19:06 FreeNAS kernel: ifa_del_loopback_route: deletion failed
Apr  1 04:19:06 FreeNAS Freed UMA keg (udp_inpcb) was not empty (40 items).  Lost 4 pages of memory.
Apr  1 04:19:06 FreeNAS Freed UMA keg (udpcb) was not empty (504 items).  Lost 3 pages of memory.
Apr  1 04:19:06 FreeNAS Freed UMA keg (tcp_inpcb) was not empty (40 items).  Lost 4 pages of memory.
Apr  1 04:19:06 FreeNAS Freed UMA keg (tcpcb) was not empty (16 items).  Lost 4 pages of memory.
Apr  1 04:19:06 FreeNAS Freed UMA keg (ripcb) was not empty (20 items).  Lost 2 pages of memory.
Apr  1 04:19:06 FreeNAS hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
Apr  1 04:19:06 FreeNAS hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
Apr  1 04:19:06 FreeNAS kernel: epair1a: link state changed to DOWN
Apr  1 04:19:06 FreeNAS kernel: epair1a: link state changed to DOWN
Apr  1 04:19:06 FreeNAS kernel: epair1b: link state changed to DOWN
Apr  1 04:19:06 FreeNAS kernel: epair1b: link state changed to DOWN
Apr  1 04:19:06 FreeNAS kernel: em0: link state changed to DOWN
Apr  1 04:19:06 FreeNAS kernel: em0: link state changed to DOWN
Apr  1 04:19:06 FreeNAS kernel: bridge0: link state changed to DOWN
Apr  1 04:19:06 FreeNAS kernel: bridge0: link state changed to DOWN
Apr  1 04:19:06 FreeNAS kernel: em0: promiscuous mode disabled
Apr  1 04:19:09 FreeNAS kernel: em0: link state changed to UP
Apr  1 04:19:09 FreeNAS kernel: em0: link state changed to UP
Apr  1 04:19:10 FreeNAS afpd[3373]: AFP Server shutting down
Apr  1 04:19:10 FreeNAS cnid_metad[3374]: shutting down on SIGTERM
Apr  1 04:19:10 FreeNAS netatalk[3358]: Netatalk AFP server exiting
Apr  1 04:19:11 FreeNAS smbd[3110]: dnssd_clientstub DNSServiceProcessResult called with DNSServiceRef with no ProcessReply function
Apr  1 04:19:11 FreeNAS winbindd[3113]:   STATUS=daemon 'winbindd' finished starting up and ready to serve connectionsGot sig[15] terminate (is_parent=1)
Apr  1 04:19:12 FreeNAS syslog-ng[31566]: syslog-ng starting up; version='3.5.6'
Apr  1 04:19:12 FreeNAS , 3358.
Apr  1 04:19:12 FreeNAS kernel: pid 2258 (syslog-ng), uid 0: exited on signal 6 (core dumped)
Apr  1 04:19:12 FreeNAS ntpd[2816]: ntpd exiting on signal 15
Apr  1 04:19:12 FreeNAS syslog-ng[31566]: syslog-ng shutting down; version='3.5.6'
Apr  1 04:22:58 FreeNAS syslog-ng[2258]: syslog-ng starting up; version='3.5.6'

This is a log snippet from the second shutdown, 15 minutes after the first (as always the server stood down after this shutdown...):

Code:

Apr  1 04:34:01 FreeNAS shutdown: power-down by root:
Apr  1 04:34:03 FreeNAS kernel: epair0a: link state changed to DOWN
Apr  1 04:34:03 FreeNAS kernel: epair0a: link state changed to DOWN
Apr  1 04:34:03 FreeNAS kernel: epair0b: link state changed to DOWN
Apr  1 04:34:03 FreeNAS kernel: epair0b: link state changed to DOWN
Apr  1 04:34:06 FreeNAS kernel: ifa_del_loopback_route: deletion failed
Apr  1 04:34:06 FreeNAS Freed UMA keg (udp_inpcb) was not empty (40 items).  Lost 4 pages of memory.
Apr  1 04:34:06 FreeNAS Freed UMA keg (udpcb) was not empty (504 items).  Lost 3 pages of memory.
Apr  1 04:34:06 FreeNAS Freed UMA keg (tcp_inpcb) was not empty (20 items).  Lost 2 pages of memory.
Apr  1 04:34:06 FreeNAS Freed UMA keg (tcpcb) was not empty (8 items).  Lost 2 pages of memory.
Apr  1 04:34:06 FreeNAS hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
Apr  1 04:34:06 FreeNAS hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
Apr  1 04:34:06 FreeNAS kernel: epair1a: link state changed to DOWN
Apr  1 04:34:06 FreeNAS kernel: epair1a: link state changed to DOWN
Apr  1 04:34:06 FreeNAS kernel: epair1b: link state changed to DOWN
Apr  1 04:34:06 FreeNAS kernel: epair1b: link state changed to DOWN
Apr  1 04:34:07 FreeNAS kernel: em0: link state changed to DOWN
Apr  1 04:34:07 FreeNAS kernel: em0: link state changed to DOWN
Apr  1 04:34:07 FreeNAS kernel: bridge0: link state changed to DOWN
Apr  1 04:34:07 FreeNAS kernel: bridge0: link state changed to DOWN
Apr  1 04:34:07 FreeNAS kernel: em0: promiscuous mode disabled
Apr  1 04:34:11 FreeNAS kernel: em0: link state changed to UP
Apr  1 04:34:11 FreeNAS kernel: em0: link state changed to UP
Apr  1 04:34:11 FreeNAS cnid_metad[3372]: shutting down on SIGTERM
Apr  1 04:34:11 FreeNAS afpd[3371]: AFP Server shutting down
Apr  1 04:34:11 FreeNAS netatalk[3356]: Netatalk AFP server exiting
Apr  1 04:34:11 FreeNAS smbd[3110]: dnssd_clientstub DNSServiceProcessResult called with DNSServiceRef with no ProcessReply function
Apr  1 04:34:11 FreeNAS winbindd[3113]:   STATUS=daemon 'winbindd' finished starting up and ready to serve connectionsGot sig[15] terminate (is_parent=1)
Apr  1 04:34:12 FreeNAS syslog-ng[9486]: syslog-ng starting up; version='3.5.6'
Apr  1 04:34:12 FreeNAS kernel: pid 2258 (syslog-ng), uid 0: exited on signal 6 (core dumped)
Apr  1 04:34:12 FreeNAS ntpd[2816]: ntpd exiting on signal 15
Apr  1 04:34:13 FreeNAS syslog-ng[9486]: syslog-ng shutting down; version='3.5.6'

Any ideas?

 

[joeschmuck]

I'd submit a bug report and include this info. Maybe one of the developers can figure it out. Very odd.

 

[KristijanL]

i can reproduce this on my dedicated HP SE326M1, but the time is random on my machine.

 

[74m]

Okay, here is my bug report: https://bugs.freenas.org/issues/14420
It seems that this is not a failure with freenas.

Kristijan, very interesting that you can reproduce this error. Sadly i have no clue how we can identify the guilty part...?!
My guess is, that my mainboard or power supply is responsible for this strange shutdown/reboot behavior. But your HP SE326M1 is a server machine and i dont think that we have the same hardware...

 

[74m]

Hi,

good news from here. For me, i have solved the bug. I hope this is working for you too. The trick is...

*drum roll*
*drum roll*

;)

to enable the "headless mode" in the "ACPI Settings" under the "Advanced"-Tab in the BIOS.

After press "save and reset" in the BIOS, i had to do a full shutdown via ipmi. Only after the full shutdown, the new settings seems to be enabled. Since then, all my shutdowns worked. Shutdowns via cronjobs, shutdowns via CLI and shutdowns via GUI.

 

[Ruff.Hi]

I have the same motherboard as you ... just installed it 2 or 3 days ago ... and I am in the same boat as you. Everytime I tell the NAS to shut down ... it reboots.

The one wrinkle is that if I pull the power / reset cables out of the motherboard, then it DOES shut down.

I have a UPS and I am going to by-pass that to see if it is the UPS or something else.

Other stuff ...
- BIOS setting after power restore set to 'stay off'
- latest 9.10 FreeNAS software
- no data pool attached (at present)

 

[holt]

Same problem and motherboard here too. Just installed a few weeks ago.

I tried the solutions mentioned in this thread. Stay off, headless mode, full shutdown with IPMI after updating BIOS settings. Nothing helped.

What seemed to resolve it for me in the end, was loading optimized defaults in BIOS.

Supermicro X10SL7-F
BIOS version 3.0
Latest 9.10 FreeNAS

 

[StephenFry]

Beuh... now I have this problem popping up; on a system that's been running (on *and* off ;) ) for 5 years. Started after the U3 update, but that may be a coincidence.

An X9SCM-F board. So far, no luck, but will report back when I find something.