Crash and cores since TrueNAS-12.0-U3.1 upgrade

vthinsel

Dabbler
Joined
May 18, 2021
Messages
19
Hello,

I upgraded to TrueNAS-12.0-U3.1 on the 5th of May, and since 15th of May I get regularly python3.8.core alerts :
Code:
New alerts:
The following system core files were found: python3.8.core. Please create a ticket at https://jira.ixsystems.com/ and attach the relevant core files along with a system debug. Once the core files have been archived and attached to the ticket, they may be removed by running the following command in shell: 'rm /var/db/system/cores/'.


In addition, I also get a daily unscheduled reboot:

Code:
* freenas.thinselin.local had an unscheduled system reboot.

The operating system successfully came back online at Tue May 18 09:01:53 2021.

* freenas.thinselin.local had an unscheduled system reboot.

The operating system successfully came back online at Mon May 17 07:44:42 2021.

* freenas.thinselin.local had an unscheduled system reboot.

The operating system successfully came back online at Sun May 16 21:59:32 2021.

My dmesg is here for details : https://gist.github.com/vthinsel/c878b56855d13ef40e4c22d0d9b620c9
Any idea on what could cause this issue ?

Vincent
 

vthinsel

Dabbler
Joined
May 18, 2021
Messages
19

vthinsel

Dabbler
Joined
May 18, 2021
Messages
19
Hum. After applying the patch, my box doesnt boot properly. I get a mountroot> prompt
Loader variables:
vfs.root.mountfrom=zfs:freenas-boot/ROOT/12.0-INTERNAL-U3-py39_3
panic: mountroot: unable ro (re-)mount root

Any idea to rollback ?
thanks
 

vthinsel

Dabbler
Joined
May 18, 2021
Messages
19
Hum. After applying the patch, my box doesnt boot properly. I get a mountroot> prompt
Loader variables:
vfs.root.mountfrom=zfs:freenas-boot/ROOT/12.0-INTERNAL-U3-py39_3
panic: mountroot: unable ro (re-)mount root

Any idea to rollback ?
thanks
Just went through the boot menu to revert to U3.1
 

vthinsel

Dabbler
Joined
May 18, 2021
Messages
19
Even after reverting to U3.1 I still get crash. Got one while console was on.
 

Attachments

  • IMG_20210518_170319.jpg
    IMG_20210518_170319.jpg
    397.6 KB · Views: 141

vthinsel

Dabbler
Joined
May 18, 2021
Messages
19
Well, looks like a faulty memory stick. Bad coincidence I guess, sorry.
 
Top