FreeBSD 13.1 with latest TrueNAS CORE 13 causes problem for several people, described below. According to iXsystems it is due to latest FreeBSD, from iXsystems bug-report: "I am sorry you're having trouble, but since this seems to be an upstream FreeBSD there isn't much we can do other than wait for fixes. If you are running OK with SCALE my suggestion is that you stick to it unless there is any reason you can't?" -------------- The problem, bug report for TrueNAS CORE: VMware ESXi 6.7 with TrueNAS CORE 12U8.1, been rock stable since first CORE 12U1 version. Upgrade to CORE 13 went fine to begin with. But at sometime it did shut down (after an hour or so). When rebooting it halts after identification of LSI-card, and gives a looped fault “doorbell handshake failed”. Then second attempt 3-4 weeks later, manual upgrade to 13U1-prerelease, all fine then shuts down after short time. Unable to reboot, stuck at same “Doorbell handshake failed”. This time unable to recover into 12U8.1. (Stopped using CORE after this and clean installed a SCALE VM - working ok).
> But at sometime it did shut down (after an hour or so). What do you mean? Was there a kernel panic, hang, or? > When rebooting it halts after identification of LSI-card, and gives a looped fault “doorbell handshake failed”. So some LSI HBA is passed into the VM? There is not much detail to go from. Was HBA firmware updated at any point? What happens after the host is rebooted?
(In reply to Mark Johnston from comment #1) ----What do you mean? Was there a kernel panic, hang, or? I do not know. TrueNAS just did shut down. ----So some LSI HBA is passed into the VM? There is not much detail to go from. ----Was HBA firmware updated at any point? What happens after the host is rebooted? LSI HBA passtrough yes. Has been rock stable for a year until last TrueNAS update which uses FreeBSD 13.1. HBA FW updated a year ago to the latest. Host reboot does not change anything. I know there is not much info here, but iXsystems concluded "since this seems to be an upstream FreeBSD there isn't much we can do other than wait for fixes". So I do not have any more specific info for this problem solving.
I don't have much helpful information, other than i'm experiencing the same issue. i'm running an lsi controller in IT mode, using hardware pass through under vmware 7.0U2 The system has been rock solid under truenas12 root@truenas[/var/log]# uname -a FreeBSD truenas.stivachtis.net 12.2-RELEASE-p14 FreeBSD 12.2-RELEASE-p14 325282c09a5(HEAD) TRUENAS amd64 However when i updated to truenas13, (no other changes made), which is running freebsd 13 i had all the same problems as @dag , i downgraded back down to truenas12 and it immediately resolved the issues. Unfortunately I have no time to try and update the system again or do any significant troubleshooting until the Christmas holiday season due to being on the road for the next 3 months. output from sas3ircu root@truenas[/var/log]# sas3ircu 0 display Avago Technologies SAS3 IR Configuration Utility. Version 16.00.00.00 (2017.04.26) Copyright (c) 2009-2017 Avago Technologies. All rights reserved. Read configuration has been initiated for controller 0 ------------------------------------------------------------------------ Controller information ------------------------------------------------------------------------ Controller type : SAS3008 BIOS version : 8.37.00.00 Firmware version : 16.00.01.00 Channel description : 1 Serial Attached SCSI Initiator ID : 0 Maximum physical devices : 1023 Concurrent commands supported : 9664 Slot : 5 Segment : 0 Bus : 4 Device : 0 Function : 0 RAID Support : No ------------------------------------------------------------------------
There is thread regarding this issue on the TrueNAS forum: https://www.truenas.com/community/threads/truenas-will-not-boot-after-upgrade-to-13.101701/ The topic has had over 2k views so it seems that more than a handful of people could be impacted by this. Seems to happen with different HBAs across different ESXi versions where 12.x has been rock solid Wish that IXSystem Engineers would engage with the FreeBSD community to offer more help/info surrounding the issue. (Collecting logs pointing to a smoking gun is not that easy on TrueNAS) I've ran my current TrueNAS 12.x version for years without any issues. Steps to reproduce: - Install a VM with TrueNAS 12.x which has a passthrough HBA (I have a LSI SAS9211-8i). - Upgrade it to 13.x (I did a reinstall into a new boot environment and uploaded the save config ) - The VM crashes within a couple of minutes.
I also offer my setup: Running the TrueNAS Core VM on a SuperMicro X10SRA-F running ESXI 6.7 : Version: 6.7.0 Build: Releasebuild-20497097 Update: 3 Patch: 189 HBA installed in passthrough mode. view from the TrueNAS VM: sas2ircu 0 display LSI Corporation SAS2 IR Configuration Utility. Version 20.00.00.00 (2014.09.18) Copyright (c) 2008-2014 LSI Corporation. All rights reserved. Read configuration has been initiated for controller 0 ------------------------------------------------------------------------ Controller information ------------------------------------------------------------------------ Controller type : SAS2008 BIOS version : 7.37.00.00 Firmware version : 19.00.00.00 Channel description : 1 Serial Attached SCSI Initiator ID : 0 Maximum physical devices : 255 Concurrent commands supported : 3432 Slot : 238 Segment : 0 Bus : 11 Device : 0 Function : 0 RAID Support : No ------------------------------------------------------------------------ IR Volume information ------------------------------------------------------------------------