Unauthorized system reboot
I have been having an issue with my freenas server restarting every night at the same time; 3:04am. This is right after the daily security report. The only information that I can find on why this occurs is in the messages log:
Mar 24 03:05:51 freenas amdsbwd0: Previous Reset was caused by Watchdog
Mar 24 03:05:51 freenas amdsbwd0: <AMD SB600/SB7xx Watchdog Timer> at iomem 0xfec000f0-0xfec000f3,0xfec000f4-0xfec000f7 on isa0
This began to happen when I updated to 11.1 U2 and persisted to the most recent U4. Any help with this would be appreciated. Thanks
#3 Updated by Alexander Motin over 3 years ago
- Status changed from Unscreened to Blocked
- Priority changed from No priority to Important
- Severity set to Low Medium
- Reason for Blocked set to Waiting for feedback
"Previous Reset was caused by Watchdog", if true, could explain why system reboots. But for quite a some time we do not run watchdogd on AMD-based systems. Could you check whether your system runs watchdogd process with `ps ax |grep watchdogd`? If no, as ot supposed to, could you try to disable the watchdog driver completely with setting loader tunable `hint.amdsbwd.0.disabled=1` and reboot?
#4 Updated by Brian Hawley over 3 years ago
I tried the ps command and watchdog is not currently running. I also set the tunable as attached picture indicates with a restart as requested. The server still rebooted this morning at 3:04. Is there anything in the daily scripts that would warrant a reboot every night?
#5 Updated by Alexander Motin over 3 years ago
- Status changed from Blocked to Closed
- Assignee changed from Alexander Motin to Benno Rice
- Priority changed from Important to Expected
- Severity changed from Low Medium to Medium
- Reason for Closing set to Duplicate Issue
- Reason for Blocked deleted (
Waiting for feedback)
My first guess about watchdog was wrong. It can not be the cause, because it is not even enabled there. It was a message from the amdsbwd driver the confused me.
Benno, looking on core dumps in provided debug, it seems like another case of vnode reclamation recursion.