TrueNAS 12.0-U1.1 not booting after Update - Creating and/or trimming log files

Joined
Jan 21, 2021
Messages
4
Hello Forum,

yesterday I updated a Truenas Server of mine from TrueNAS 12.0 to TrueNAS 12.0-U1.1 which now refuses to boot if I don't set safe mode to on.

It is stuck at "Creating and/or trimming log files" which I don't find any google results to.

The hardware is:
Supermicro X11SSL-F
16 GB DDR4 ECC
i3-6100
I am booting of a 64GB SSD and have a RAIDZ with 4 x 3TB Drives.


I had the same error when updating to TrueNAS 12.0-U1 before and rolled back to 12.0 but hoped it was fixed with TrueNAS 12.0-U1.1. Am I forever stuck with TrueNAS 12.0?

Can anyone help me to trouble shoot this?

I see a few errors in /var/log/messages when booting to safe mode:

* Jan 21 09:09:59 backup2 1 2021-01-21T09:09:59.944040+01:00 backup2.lcl mountd 1651 - - can't open /etc/zfs/exports
* Jan 21 09:10:49 backup2 kernel: in6_purgeaddr: err=65, destination address delete failed
* Jan 21 09:10:52 backup2 1 2021-01-21T09:10:52.824584+01:00 backup2.lcl ntpd 1709 - - ntpd exiting on signal 15 (Terminated)

Best Regards

Code:
Jan 21 09:09:31 backup2 1 2021-01-21T09:09:31.516128+01:00 backup2.lcl mountd 1650 - - can't open /etc/zfs/exports
Jan 21 09:09:31 backup2 1 2021-01-21T09:09:31.563350+01:00 backup2.lcl ntpd 1708 - - ntpd 4.2.8p15-a (1): Starting
Jan 21 09:09:31 backup2 1 2021-01-21T09:09:31.563487+01:00 backup2.lcl ntpd 1708 - - Command line: /usr/sbin/ntpd -p /var/db/ntp/ntpd.pid -c /etc/ntp.conf -f /var/dbWith bes/ntp/ntpd.drift -g
Jan 21 09:09:31 backup2 1 2021-01-21T09:09:31.563506+01:00 backup2.lcl ntpd 1708 - - ----------------------------------------------------
Jan 21 09:09:31 backup2 1 2021-01-21T09:09:31.563509+01:00 backup2.lcl ntpd 1708 - - ntp-4 is maintained by Network Time Foundation,
Jan 21 09:09:31 backup2 1 2021-01-21T09:09:31.563511+01:00 backup2.lcl ntpd 1708 - - Inc. (NTF), a non-profit 501(c)(3) public-benefit
Jan 21 09:09:31 backup2 1 2021-01-21T09:09:31.563513+01:00 backup2.lcl ntpd 1708 - - corporation.  Support and training for ntp-4 are
Jan 21 09:09:31 backup2 1 2021-01-21T09:09:31.563515+01:00 backup2.lcl ntpd 1708 - - available at https://www.nwtime.org/support
Jan 21 09:09:31 backup2 1 2021-01-21T09:09:31.563517+01:00 backup2.lcl ntpd 1708 - - ----------------------------------------------------
Jan 21 09:09:31 backup2 nfsd: can't register svc name
Jan 21 09:09:31 backup2 Security policy loaded: MAC/ntpd (mac_ntpd)
Jan 21 09:09:34 backup2 kernel: igb0: link state changed to UP
Jan 21 09:09:38 backup2 1 2021-01-21T09:09:38.821261+01:00 backup2.lcl smartd 1799 - - Device: /dev/ada1, 5 Currently unreadable (pending) sectors
Jan 21 09:09:39 backup2 1 2021-01-21T09:09:39.794506+01:00 backup2.lcl smartd 1799 - - Device: /dev/ada1, 1 Offline uncorrectable sectors
Jan 21 09:09:41 backup2 1 2021-01-21T09:09:41.441710+01:00 backup2.lcl mountd 1651 - - can't open /etc/zfs/exports
Jan 21 09:09:41 backup2 1 2021-01-21T09:09:41.443164+01:00 backup2.lcl mountd 1651 - - can't open /etc/zfs/exports
Jan 21 09:09:41 backup2 kernel: bridge0: Ethernet address: 02:95:2c:9a:05:00
Jan 21 09:09:41 backup2 kernel: igb0: link state changed to DOWN
Jan 21 09:09:41 backup2 kernel: bridge0: link state changed to UP
Jan 21 09:09:41 backup2 kernel: igb0: promiscuous mode enabled
Jan 21 09:09:41 backup2 kernel: epair0a: Ethernet address: 02:79:2e:98:61:0a
Jan 21 09:09:41 backup2 kernel: epair0b: Ethernet address: 02:79:2e:98:61:0b
Jan 21 09:09:41 backup2 kernel: epair0a: link state changed to UP
Jan 21 09:09:41 backup2 kernel: epair0b: link state changed to UP
Jan 21 09:09:41 backup2 kernel: epair0a: changing name to 'vnet0.1'
Jan 21 09:09:42 backup2 kernel: tap0: Ethernet address: 58:9c:fc:10:ae:34
Jan 21 09:09:42 backup2 kernel: tap0: changing name to 'vnet0'
Jan 21 09:09:42 backup2 kernel: bridge0: link state changed to DOWN
Jan 21 09:09:42 backup2 kernel: vnet0: promiscuous mode enabled
Jan 21 09:09:42 backup2 kernel: vnet0: link state changed to UP
Jan 21 09:09:42 backup2 kernel: bridge0: link state changed to UP
Jan 21 09:09:42 backup2 kernel: vnet0.1: promiscuous mode enabled
Jan 21 09:09:46 backup2 kernel: igb0: link state changed to UP
Jan 21 09:09:46 backup2 kernel: lo0: link state changed to UP
Jan 21 09:09:59 backup2 1 2021-01-21T09:09:59.944040+01:00 backup2.lcl mountd 1651 - - can't open /etc/zfs/exports
Jan 21 09:09:59 backup2 1 2021-01-21T09:09:59.944962+01:00 backup2.lcl mountd 1651 - - can't open /etc/zfs/exports
Jan 21 09:09:59 backup2 1 2021-01-21T09:09:59.946108+01:00 backup2.lcl mountd 1651 - - can't open /etc/zfs/exports
Jan 21 09:10:00 backup2 kernel: epair1a: Ethernet address: 02:c7:7f:81:d4:0a
Jan 21 09:10:00 backup2 kernel: epair1b: Ethernet address: 02:c7:7f:81:d4:0b
Jan 21 09:10:00 backup2 kernel: epair1a: link state changed to UP
Jan 21 09:10:00 backup2 kernel: epair1b: link state changed to UP
Jan 21 09:10:00 backup2 kernel: epair1a: changing name to 'vnet0.2'
Jan 21 09:10:01 backup2 kernel: epair1b: changing name to 'epair0b'
Jan 21 09:10:01 backup2 kernel: vnet0.2: promiscuous mode enabled
Jan 21 09:10:06 backup2 kernel: lo0: link state changed to UP
Jan 21 09:10:16 backup2 1 2021-01-21T09:10:16.146602+01:00 backup2.lcl mountd 1651 - - can't open /etc/zfs/exports
Jan 21 09:10:16 backup2 1 2021-01-21T09:10:16.148906+01:00 backup2.lcl mountd 1651 - - can't open /etc/zfs/exports
Jan 21 09:10:16 backup2 1 2021-01-21T09:10:16.150475+01:00 backup2.lcl mountd 1651 - - can't open /etc/zfs/exports
Jan 21 09:10:16 backup2 kernel: epair2a: Ethernet address: 02:6c:b2:22:33:0a
Jan 21 09:10:16 backup2 kernel: epair2b: Ethernet address: 02:6c:b2:22:33:0b
Jan 21 09:10:16 backup2 kernel: epair2a: link state changed to UP
Jan 21 09:10:16 backup2 kernel: epair2b: link state changed to UP
Jan 21 09:10:16 backup2 kernel: epair2a: changing name to 'vnet0.3'
Jan 21 09:10:19 backup2 kernel: epair2b: changing name to 'epair0b'
Jan 21 09:10:19 backup2 kernel: vnet0.3: promiscuous mode enabled
Jan 21 09:10:27 backup2 kernel: lo0: link state changed to UP
Jan 21 09:10:48 backup2 syslog-ng[4010]: syslog-ng starting up; version='3.29.1'
Jan 21 09:10:48 backup2 kernel: pid 1502 (syslog-ng), jid 0, uid 0: exited on signal 6 (core dumped)
Jan 21 09:10:48 backup2 kernel: vnet0.1: link state changed to DOWN
Jan 21 09:10:48 backup2 kernel: epair0b: link state changed to DOWN
Jan 21 09:10:48 backup2 kernel: in6_purgeaddr: err=65, destination address delete failed
Jan 21 09:10:48 backup2 kernel: vnet0.2: link state changed to DOWN
Jan 21 09:10:48 backup2 kernel: epair0b: link state changed to DOWN
Jan 21 09:10:49 backup2 kernel: vnet0.3: link state changed to DOWN
Jan 21 09:10:49 backup2 kernel: epair0b: link state changed to DOWN
Jan 21 09:10:49 backup2 kernel: in6_purgeaddr: err=65, destination address delete failed
Jan 21 09:10:52 backup2 1 2021-01-21T09:10:52.824584+01:00 backup2.lcl ntpd 1709 - - ntpd exiting on signal 15 (Terminated)
Jan 21 09:11:19 backup2 kernel: vnet0: link state changed to DOWN
Jan 21 09:11:19 backup2 kernel: igb0: link state changed to DOWN
Jan 21 09:11:19 backup2 kernel: vnet0: promiscuous mode disabled
Jan 21 09:11:23 backup2 syslog-ng[4010]: syslog-ng shutting down; version='3.29.1'
Jan 21 09:23:54 backup2 syslog-ng[1502]: syslog-ng starting up; version='3.29.1'
Jan 21 09:23:54 backup2 ---<<BOOT>>---
Jan 21 09:23:54 backup2 Copyright (c) 1992-2020 The FreeBSD Project.
Jan 21 09:23:54 backup2 Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Jan 21 09:23:54 backup2         The Regents of the University of California. All rights reserved.
Jan 21 09:23:54 backup2 FreeBSD is a registered trademark of The FreeBSD Foundation.
Jan 21 09:23:54 backup2 FreeBSD 12.2-RELEASE-p2 663e6b09467(HEAD) TRUENAS amd64
Jan 21 09:23:54 backup2 FreeBSD clang version 10.0.1 (git@github.com:llvm/llvm-project.git llvmorg-10.0.1-0-gef32c611aa2)
Jan 21 09:23:54 backup2 VT(vga): text 80x25
Jan 21 09:23:54 backup2 CPU: Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz (3696.12-MHz K8-class CPU)
 

Attachments

  • boot.png
    boot.png
    190.6 KB · Views: 239

Kris Moore

SVP of Engineering
Administrator
Moderator
iXsystems
Joined
Nov 12, 2015
Messages
1,448
Please go ahead and file a ticket on jira.ixsystems.com with this information / debug file. We'll need to investigate further to see if its a bug in kernel or services...
 
Joined
Jan 21, 2021
Messages
4
I would love to, but I think I live too far away from your jira instance. I run into a blank/empty dashboard 9 out of 10 times and the loading time is between 5 to 10 minutes. There's no way I can possible register an account and navigate the site if I need to successfully get a 1/10 roll a few times in a row with those loading times :confused:

I am on 1GBit fibre symmetrical with a beefy workstation.
 

Attachments

  • jira.png
    jira.png
    693.5 KB · Views: 243

Kris Moore

SVP of Engineering
Administrator
Moderator
iXsystems
Joined
Nov 12, 2015
Messages
1,448
Woah... That is nuts. We have IX engineers that use it from around the world, and nothing like those speeds... If you want to PM me on here with a traceroute output or some further browser dev output of network times, please do so and I'll get that over to our IT team. I can't ask you to file a bug if you can't even reach the tracker :P
 
Joined
Jan 21, 2021
Messages
4
Ok, my struggle intensifies.

U2 still has the issue, I did a mistake of clean installing U2, I had a backup but can't restore the backup with 12Release even though it was created with it because apparently this backup is a version ahead...

I am now stuck at "Updating CPU Microcode" which comes after "Creating and/or trimming log files."

Via google the third entry is your jira with


but I can't access it. Can anyone copy paste or screenshot whats written in the issue or if there is any solution mentioned?
 
Joined
Jan 21, 2021
Messages
4
I could access it via LTE so apparently there's an issue with bridged networks. A few years ago I had some LACP Trunk configured in this installation. But this shouldn't be the problem when a clean install is stuck I guess.

I don't know....
 

altuin

Cadet
Joined
Mar 1, 2021
Messages
2
Hello! I fixed this issue by updating BIOS and BMC Firmware on the Supermicro board. Mine was an UEFI installation.
 
Top