Unauthorized Reboot - 11.1-RELEASE

[GrahamBB]

I believe that you can turn of that watchdog in the bios - I would at least try that as a test to see if the reboots stop.

I'll take a look at that, Ta!

 

[GrahamBB]

Just an update:
We rolled back to 9-10-2-U6 and the problems have gone away, the system is now functioning as before, with no issues.

I have updated the bug report to reflect that. No response from the team so far to the watchdog issue, or to the rollback behavior.

Cheers

 

[Scharbag]

No details but my bug reports has been changed to target 11.2. On a positive note, my system has not rebooted for 20+ days.

 

[hoserama]

No details but my bug reports has been changed to target 11.2. On a positive note, my system has not rebooted for 20+ days.

I reported this bug as well. Mine was also updated today to reflect a 11.2 target.



Sent from my iPhone using Tapatalk

 

[I-Tech]

No details but my bug reports has been changed to target 11.2. On a positive note, my system has not rebooted for 20+ days.

after reverting back to 11.1 mine was also up for 20 days.. until yesterday.. another reboot.
/sigh

 

[Hossa]

Hello,

I tried reverting also.
With 11.1 Release it was still rebooting.
But now I am back on 11.0-U4 and, until now, the system did not reboot....
I keep my fingers crossed! ;-)

Cheers
Hossa

Oh...I just realized 11.1-U2 popped up! Anyone tried it yet !? ;-)

 

[Alecmascot]

Oh...I just realized 11.1-U2 popped up! Anyone tried it yet !? ;-)

I just updated to 11.1-U2 from 11.0-U4 and got my first reboot at 03:04......
If it does it again I will revert to 11.0.

 

[Hossa]

Hello,

thanks for the feedback!
11.0-U4 is running just fine.
I will not update to 11.1-U2 ! :-/

Cheers
Hossa

 

[hoserama]

Out of curiosity, does anyone experiencing a reboot have Transmission or Plex installed? I have been able to initiate this unauthorized reboot via Transmission.

 

[Hossa]

Hello,

I have plex running in a Jail!
And plexpy in another Jail!
Nothing else...

 

[Alecmascot]

Out of curiosity, does anyone experiencing a reboot have Transmission or Plex installed? I have been able to initiate this unauthorized reboot via Transmission.

Transmission plugin in a warden jail

 

[Scharbag]

Out of curiosity, does anyone experiencing a reboot have Transmission or Plex installed? I have been able to initiate this unauthorized reboot via Transmission.

I also have Transmission in a warden jail.

 

[hoserama]

interesting.... so i am running transmission in a jail.i have been able to force a kernal crash resulting in an authorized reboot by saturating my downstream via Transmission and the gbit connection i have at home. i dont necessary suspect its a transmission issue but more of an issue with FreeNas and its ability to process so many packets within the network stack

 

[I-Tech]

ok.. updated to 11.1-U2 and still have reboots..
no jails / transmission or such..
question:
been a while .. any major issues with reverting back to 11.0 ???
thx

 

[FFF]

I updated several nodes to 11.1-U2 in the last 24 hours and one of them just emailed me this:

System booted at Tue Feb 27 04:27:55 2018 was not shut down properly

The system's lastlog & uptime do not show such a boot time was recorded:

boot time Mon Feb 26 01:44

6:00AM up 1 day, 4:17, 1 user, load averages: 1.17, 3.60, 4.37

Tue Feb 27 06:00:04 UTC 2018

 

[gurtonBuster]

I too am having this issue. After I updated to 11.1. I started receiving this message and confirmed this with uptime and have physically seen it reboot. It is only happening on one of my machines though. it is an intel server with dual xeon processors and 8GB of ecc ram. I use it to store my photography. I thought it was hardware so I disassembled the whole thing and cleaned it, re-assembled it with different hard disks, and did a fresh install. it didn't happen for about a week, It started rebooting again a few days ago.

It's on the same power supply as the other two freenas boxes. Neither are having problems. Both are on 11.1 one is an old dell workstation, and the other is an old hp board I slapped together with some non ecc ram, in a case I cut a hole in the front of and tack welded to a botched together drive cage. just to put my old drives in when I rebuilt the intel server. which seems counter intuitive. They have no jails or transmission, and all running 11.1-u2

It's not on a ups, but it would stand to reason they would all reboot, wouldn't you think?

 

[Hossa]

Hello,

some news....
Remember I reverted to 11.0-U4, because the system was rebooting all the time with 11.1-U1 and 11.1.

Now I updated to 11.1-U2, just out of curiosity.
And.....since then (about 15 hours ago) did not have any reboots.....

Someone understands this ??

Cheers
Hossa

 

[FFF]

Another one of my upgraded 11.1-U2 systems emailed this overnight:

Code:

System booted at Wed Feb 28 12:19:15 2018 was not shut down properly

But after checking the lastlog & uptime it appears to be another bogus one for me. No reboot took place since the upgrade (which was over a day earlier).

 

[Hossa]

Good morning

It happend again ! :-(

But in my case it looks like it is connected with the pool scrubs....
My system was running fine.....
until 04:00:
starting scrub of pool 'Storage01'
starting scrub of pool 'Storage02'
starting scrub of pool 'Storage03'

at 04:21:
System booted at Thu Mar 1 03:11:01 2018 was not shut down properly

and again at 08:10:
System booted at Thu Mar 1 07:00:49 2018 was not shut down properly

I remember that the scrub resumes every time, the system reboots.......so it "takes some time" and it creates another reboot!

The next time I am at the machine I will reschedule the scrubs for the different pools to not happen at the same time.....

Cheers
Hossa

PS:
As expected:
System booted at Thu Mar 1 08:39:42 2018 was not shut down properly
System booted at Thu Mar 1 09:22:44 2018 was not shut down properly
System booted at Thu Mar 1 09:52:34 2018 was not shut down properly
System booted at Thu Mar 1 10:20:52 2018 was not shut down properly
System booted at Thu Mar 1 10:37:44 2018 was not shut down properly
System booted at Thu Mar 1 11:24:25 2018 was not shut down properly
System booted at Thu Mar 1 11:46:50 2018 was not shut down properly
System booted at Thu Mar 1 12:16:13 2018 was not shut down properly
System booted at Thu Mar 1 13:05:10 2018 was not shut down properly
System booted at Thu Mar 1 14:06:42 2018 was not shut down properly
System booted at Thu Mar 1 14:35:50 2018 was not shut down properly
...
02.03.2018 09:56
Update:
Scrub of Storage03 is finished. Scrub of Storage 01 and Storage02 is still running....but the reboots have stopped !?

 

[Hossa]

Hello all,

Update from my side:

All scrubs finished and the system was running fine.....

For me it looked like the random reboots had something to do with "scrub of storage03".
So I just started another scrub of storage03 and......

not short after I got:
System booted at Sun Mar 4 00:18:37 2018 was not shut down properly
System booted at Sun Mar 4 10:07:57 2018 was not shut down properly

scrub is now finished....system is running fine again.

Conclusion:

I can provoke the (not so random anymore) reboots by starting a scrub of storage03 !

Anyone else ?

Cheers
Hossa