TrueNAS SCALE Bluefin 22.12.3.1 is Now Available!

[eturgeon]

We are pleased to release TrueNAS SCALE 22.12.3.1!

This is a small hotpatch designed to resolve issues with PCI passthrough to Virtual Machines, the order in which system services are started, and an issue with error logging when upgrading a High Availability (HA) system from 22.12.3.

See the Release Notes for more details.

Release Notes: https://www.truenas.com/docs/scale/scale22.12/#221231
Download: https://www.truenas.com/download-truenas-scale and https://download.truenas.com/TrueNAS-SCALE-Bluefin/22.12.3.1
Documentation: https://www.truenas.com/docs/scale

Thanks for using TrueNAS SCALE! As always, we appreciate your feedback!

 

[probain]

This upgrade too gave me an ECC alert. These only show up when doing upgrades. Never been seen on regular reboots. But 3/3 upgrades have now resulted in these alerts.
"

Sensor: 'Sensor #0' had an 'Assertion Event' (Correctable memory error ; OEM Event Data2 code = 5Ah ; OEM Event Data3 code = 80h)​

2023-06-26 14:14:37 (Europe/Stockholm)"

Previous posts explaining the same issue

TrueNAS SCALE Bluefin 22.12.3 is Now Available!

We are pleased to release TrueNAS SCALE 22.12.3! This release includes many new features and improved functionality that span new applications for deprecated services, changes to SMB service, additional tools for troubleshooting, and web UI improvements. Changes include: New applications for...

www.truenas.com

TrueNAS SCALE 22.12.2 is expected April 11th

See this thread: https://www.truenas.com/community/threads/cant-launch-docker-images-anymore.109262/ Thanks. I original posted my message before that thread existed, but it was a while before it got moderated. But yeah, the resolution in that thread fixed my issue. Thanks for pointing me...

www.truenas.com

Will file a JIRA. But writing these here for information and traceability

 

[probain]

This upgrade too gave me an ECC alert. These only show up when doing upgrades. Never been seen on regular reboots. But 3/3 upgrades have now resulted in these alerts.
"

Sensor: 'Sensor #0' had an 'Assertion Event' (Correctable memory error ; OEM Event Data2 code = 5Ah ; OEM Event Data3 code = 80h)​

2023-06-26 14:14:37 (Europe/Stockholm)"

Previous posts explaining the same issue

TrueNAS SCALE Bluefin 22.12.3 is Now Available!

We are pleased to release TrueNAS SCALE 22.12.3! This release includes many new features and improved functionality that span new applications for deprecated services, changes to SMB service, additional tools for troubleshooting, and web UI improvements. Changes include: New applications for...

www.truenas.com

TrueNAS SCALE 22.12.2 is expected April 11th

See this thread: https://www.truenas.com/community/threads/cant-launch-docker-images-anymore.109262/ Thanks. I original posted my message before that thread existed, but it was a while before it got moderated. But yeah, the resolution in that thread fixed my issue. Thanks for pointing me...

www.truenas.com

Will file a JIRA. But writing these here for information and traceability

JIRA-ticket

[NAS-122649] - iXsystems TrueNAS Jira

ixsystems.atlassian.net

 

[Carrotcruncher]

Just noticed the update. Thank you !

 

[troonas]

I think there are still issues with PCI passthrough to VMs. My GPU now passes through fine, but an NVMe SSD I was passing through to a Windows VM without issue is now regarded as "critical":

 

[troonas]

Looking through the code, this is honestly a really brittle check that'll catch a lot of false positives. I feel like it should either not be done at all (i.e. let the user shoot themselves in the foot), or should at least use the preceding word for more context.

Example from my machine:
0000:00:14.2 RAM memory [0500]: Intel Corporation Device [8086:7aa7] (rev 11) 0000:00:16.0 Communication controller [0780]: Intel Corporation Device [8086:7ae8] (rev 11) 0000:00:17.0 SATA controller [0106]: Intel Corporation Device [8086:7ae2] (rev 11) 0000:00:1a.0 PCI bridge [0604]: Intel Corporation Device [8086:7ac8] (rev 11) 0000:00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:7ab8] (rev 11) 0000:00:1c.2 PCI bridge [0604]: Intel Corporation Device [8086:7aba] (rev 11) 0000:00:1c.4 PCI bridge [0604]: Intel Corporation Device [8086:7abc] (rev 11) 0000:00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:7a86] (rev 11) 0000:00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:7aa3] (rev 11) 0000:00:1f.5 Serial bus controller [0c80]: Intel Corporation Device [8086:7aa4] (rev 11) 0000:01:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch [1002:1478] (rev c0) 0000:02:00.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch [1002:1479] 0000:03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Navi 22 [1002:73df] (rev c0) 0000:03:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:ab28] 0000:04:00.0 Non-Volatile memory controller [0108]: Phison Electronics Corporation PS5013 E13 NVMe Controller [1987:5013] (rev 01) 0000:05:00.0 Non-Volatile memory controller [0108]: Realtek Semiconductor Co., Ltd. Device [10ec:5765] (rev 01)

I'm going to guess the sensitive device keyword "memory" was attempting to prevent passing through "RAM memory", but catches "non-volatile memory" too :(

 

[morganL]

0000:04:00.0 Non-Volatile memory controller [0108]: Phison Electronics Corporation PS5013 E13 NVMe Controller [1987:5013] (rev 01)
0000:05:00.0 Non-Volatile memory controller [0108]: Realtek Semiconductor Co., Ltd. Device [10ec:5765] (rev 01)
[/ICODE]

I'm going to guess the sensitive device keyword "memory" was attempting to prevent passing through "RAM memory", but catches "non-volatile memory" too :(

TrueNAS users typically use NVMe devices as cache or data vdevs. So a warning makes sense.

 

[troonas]

TrueNAS users typically use NVMe devices as cache or data vdevs. So a warning makes sense.

A warning would be reasonable, but in this case, it simply disallowed using the device at all. Fortunately, the issue has been fixed for whenever the next release happens.