nvme0n1 Unknown

tedquade

@stephenw10 In the widget Yes.
Ted

stephenw10

Ok looks like the way the drive devices are presented has changed slightly. nvme0n1 doesn't exist in 24.03. Digging.

DefenderLLC

@stephenw10 In that case, I'll roll the dice after hours. :)

stephenw10

Mmm, digging into what changed but it doesn't appear to be anything more than cosmetic. You can just exclude it from the widget manually for now.

DefenderLLC

@stephenw10 The ZFS widget is broken like it was when 24.03 was first being tested. Everything else is good so far!

stephenw10

Hmm, that was broken in earlier snaps but should be fixed now.

Check /usr/local/pfSense/include/Netgate/Services/ZFS/LibZFS.php line 109 should be:

				zfsState = zfs.asdict()

Assuming you do have ZFS pools on that system.

DefenderLLC

@stephenw10 Yeah, it's there. It's not a big deal. Everything else is working fine. Thanks.

			try:
				zfs = libzfs.ZFS()
				zfsState = zfs.asdict()
				jsonOutput = json.dumps(zfsState, default=str)
			except Exception:

stephenw10

Hmm and zpool status returns the correct values?

DefenderLLC

@stephenw10 Yes sir.

stephenw10

Does it appear if you refresh the dashboard a few times? The values used there are cached.

DefenderLLC

@stephenw10 Yes I have including a manual reboot (post-upgrade). I'm really not worried about it. Just thought you might want to know. Thanks.

stephenw10

Hmm, curious. Yes, that should be working .

stephenw10

Try clearing the cache with: rm -rf /tmp/symfony-cache

DefenderLLC

@stephenw10 No change - even with an incognito window or logging in from another device. I remember this came up exactly the same way during the early 24.03 development cycle, so let me scroll back through some of the older threads to see what you suggested before to fix it. Thanks.

stephenw10

Yeah it came up during early 24.08 testing internally because of a change to the python zfs library, but that should be fixed.

DefenderLLC

@stephenw10 Thanks - AS ALWAYS!

marcosm

Issue can be tracked at https://redmine.pfsense.org/issues/15586