TrueNAS SCALE 22.02.2 is Now Available

eturgeon

Super Moderator
Moderator
iXsystems
Joined
Nov 29, 2021
Messages
60
We are pleased to announce the release of TrueNAS SCALE 22.02.2 (Angelfish). This new release has several bug fixes and improvements and a few new features. With this release, the Enclosure view is now available for the following TrueNAS platforms, R10, R20, R20B, R40, R50B, Mini 3.0 X, Mini 3.0 X+, Mini 3.0 XL+, Mini 3.0 E, Mini 3.0 E+, and M50. See the Release Notes below for more details.

Release Notes: https://www.truenas.com/docs/scale/scalereleasenotes/#22022
Download: https://www.truenas.com/download-truenas-scale/

Thanks for trying TrueNAS SCALE 22.02.2, and as always, we appreciate your feedback!
 
Joined
Jun 2, 2019
Messages
591

Geek Baba

Explorer
Joined
Sep 2, 2011
Messages
73

Geek Baba

Explorer
Joined
Sep 2, 2011
Messages
73

Ericloewe

Server Wrangler
Moderator
Joined
Feb 15, 2014
Messages
20,175
And keep in mind that some Python packages break a lot when you upgrade willy-nilly.
 

jct

Explorer
Joined
Aug 14, 2021
Messages
52
Using pip (and apt) for that matter on the base install is not supported. You are welcome to hack around and re-enable apt (chmod +x the binaries) and install pip on your own, but please note that prominently in any future jira tickets.
And keep in mind that some Python packages break a lot when you upgrade willy-nilly.
It'd be nice to be able to guide people into isolated venvs for this reason.

Debian seems to be leading the way here: “Warning: Recent Debian/Ubuntu versions have modified pip to use the “User Scheme” by default, which is a significant behavior change that can be surprising to some users.”

But unfortunately, it takes a system-level venv/pip to install a user-scoped venv/pip. Better to stick with containers.
 

openwinz

Cadet
Joined
Aug 22, 2020
Messages
6
Post upgrade iSCSI service failed to start. I reviewed and updated the configuration just to confirm settings were correctly saved each setting. Rolled back to 22.02.1 and iSCSI started on boot, no issues. Any recommended process for reviewing the logs on this. Also note, I was able to get the service to show it started after trying to start it a few times. "netstat -tulpna | grep 3620" did not show any listening ports even when the service indicated it was running under 22.02.2.
 

hyec

Cadet
Joined
Jul 4, 2022
Messages
1
Post upgrade iSCSI service failed to start. I reviewed and updated the configuration just to confirm settings were correctly saved each setting. Rolled back to 22.02.1 and iSCSI started on boot, no issues. Any recommended process for reviewing the logs on this. Also note, I was able to get the service to show it started after trying to start it a few times. "netstat -tulpna | grep 3620" did not show any listening ports even when the service indicated it was running under 22.02.2.
I had the same issue and also rolled back. The main issue is scst.service stucked at 'modprobe isert_scst' process and never start or stop properly. I didn't found any relative messages why modprobe stucked in dmesg and messages.
 

speedtriple

Explorer
Joined
May 8, 2020
Messages
75
22.02.1 fixed that UPS reporting problem for me.
Not for me. Still no UPS reporting.

Using a LAN connected APC Smart-UPS RT 2000VA.
It does work on UPS-setup, and the NUT-server in TrueNAS is relaying UPS info to my Home Assistant.

Also CLI lookup in TrueNAS-shell will report all UPS parameters.
 

morganL

Captain Morgan
Administrator
Moderator
iXsystems
Joined
Mar 10, 2018
Messages
2,691
We're looking to get TrueNAS SCALE 22.02.3 out this week.

There will be over 100 bug fixes including:
  • Drive scalability improvements
  • SMB ACL fixes
  • Security updates for Linux Kernel and Libraries
  • Drive resizing and over-provisioning tool
  • OpenZFS Linux ARC improvements
  • WebUI bug fixes
 

HarryMuscle

Contributor
Joined
Nov 15, 2021
Messages
161
We're looking to get TrueNAS SCALE 22.02.3 out this week.

There will be over 100 bug fixes including:
  • Drive scalability improvements
  • SMB ACL fixes
  • Security updates for Linux Kernel and Libraries
  • Drive resizing and over-provisioning tool
  • OpenZFS Linux ARC improvements
  • WebUI bug fixes
Any details on the drive resizing and over provisioning tool?

Thanks,
Harry
 

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
9,543
We're looking to get TrueNAS SCALE 22.02.3 out this week.

There will be over 100 bug fixes including:
  • Drive scalability improvements
  • SMB ACL fixes
  • Security updates for Linux Kernel and Libraries
  • Drive resizing and over-provisioning tool
  • OpenZFS Linux ARC improvements
  • WebUI bug fixes

There aren't really any ACL fixes related to SMB for SCALE 22.02.2 -> 22.02.3. Appearance of that in the middlewared repo git log may be caused by new regression tests added to provide additional test coverage for bugs that were in TrueNAS 13.

On SMB side:
(middleware)
- improved validation for dataset configuration settings when creating SMB shares. Creating an SMB share should raise a validation error now if dataset settings on child datasets is inconsistent in a way that can't be easily handled in the SMB server (for example inconsistent case sensitivity settings.
- fixes related to "OWNER RIGHTS" SID handling
- add more robust checks on whether the SMB service was properly initialized during boot (if for some reason system dataset fails to set up it can leave the SMB service unconfigured / broken). Now we'll log this situation more clearly and attempt to fix it if it happens.
- deprectated an undocumeted feature to allow an empty path for homes shares
- fixed a few bugs with the APIs for creating / using ACL templates (not currently exposed through webui)
- bugfix related to race on server boot / AD startup that in some cases would cause the server to have the AD service stopped after reboot.

(Samba)
- Update from Samba 4.15.7 to 4.15.9 (see relevant samba release notes for full details)
- bugfix for situation where shadow copies may not work on child datasets
- fix assertion when legacy AFP-SMB shares also have recycle bin enabled

(ZFS)
- New behavior for NFSv4 ACL type (to ease migration from Core to SCALE). On new file creation, owning group will be inherited from parent directory rather than GID of process creating it.

These are the primary things that affect the SMB service.
 

morganL

Captain Morgan
Administrator
Moderator
iXsystems
Joined
Mar 10, 2018
Messages
2,691
Hello guys, New user here, and i was wondering if the issue is addressed.

I have the latest version installed, and i have the same error reported. Using a X540-T2 card.

Can i flash a old firmware on my network card to mitigate this issue?

Yes, update the firmware and run SCALE 22.12.1.... if the issue exists, you can report.
 

AT1411832

Cadet
Joined
Mar 18, 2023
Messages
2
Yes, update the firmware and run SCALE 22.12.1.... if the issue exists, you can report.
I am using 22.12.1 ( the latest stable build).

The network driver seem to be working and functional, but the console keeps hijacked with the following warning messages
Mar 16 15:33:39 truenas kernel: ixgbe 0000:01:00.0: Warning firmware error detected FWSM: 0x00000000
Mar 16 15:33:41 truenas kernel: ixgbe 0000:01:00.1: Warning firmware error detected FWSM: 0x00000000
Mar 16 15:33:41 truenas kernel: ixgbe 0000:01:00.0: Warning firmware error detected FWSM: 0x00000000
Mar 16 15:33:43 truenas kernel: ixgbe 0000:01:00.1: Warning firmware error detected FWSM: 0x00000000
Mar 16 15:33:43 truenas kernel: ixgbe 0000:01:00.0: Warning firmware error detected FWSM: 0x00000000
Mar 16 15:33:45 truenas kernel: ixgbe 0000:01:00.1: Warning firmware error detected FWSM: 0x00000000
Mar 16 15:33:45 truenas kernel: ixgbe 0000:01:00.0: Warning firmware error detected FWSM: 0x00000000
Mar 16 15:33:47 truenas kernel: ixgbe 0000:01:00.1: Warning firmware error detected FWSM: 0x00000000
Mar 16 15:33:47 truenas kernel: ixgbe 0000:01:00.0: Warning firmware error detected FWSM: 0x00000000
Mar 16 15:33:49 truenas kernel: ixgbe 0000:01:00.1: Warning firmware error detected FWSM: 0x00000000

I did manage to update the firmware to the latest from Intel site, but that doesn't seem to address this.

Any suggestions on getting this warning messages supressed till they release an update with new linux Kernel? I did submit a ticket on this at ixsystems ( https://ixsystems.atlassian.net/browse/NAS-121174).
 
Top