warpspeed

The kernel change section seems incomplete/lacking formatting. i.e. From/To versions Why is the usb auto suspend bit there on the same line,

What about the NFS version setting in the NFS settings in the unraid GUI?

Perhaps the variant of Android you're using only works with NFSv3. I'm using Kodi on Debian based systems. i.e. not a fault of unraid, but rather an Android system limitation

As I've previously posted, I'm using NFSv4 just fine with Kodi. What I'm doing: Using autofs or fstab directly on the host, don't configure NFS directly from Kodi itself. i.e. do not do it in the GUI, do it from the command line using fstab or autofs (autofs recommended, it's more resilient) Then set Kodi to use the NFS mounted path for media Set unraid NFS Max Protocol setting to NFSv4. I have my unraid shares using 'sec=sys,anonuid=99,anongid=100,all_squash' Using fstab, I have the mounts basically using defaults Using autofs, I found I had to add 'fstype=nfs4' to the NFS config Exclusive Shares disabled

I'm having none of those problems. The only issue I have right now is when I turn on Exclusive Shares, they don't show up in NFS. But that's easily mitigated by turning off Exclusive Shares.

7.3.0 > 7.3.1 working fine here so far

Use autofs or fstab rather than doing it in Kodi autofs is best

How are you mounting in Kodi? I had some similar issues a long while back with some NFS hosts connecting to unraid. It might not be the same, but I found I had to add "fstype=nfs4" to the mount point configs.

Updated from 7.2.6. Uneventful so far. No issues observed so far.

Thanks, did that and it did come back as precleared.

I have a disk I precleared some time ago, but it's no longer showing as precleared. Is there a way to a. do a recheck to make it show precleared and/or b. verify that if i add it to the array it's not going to try and clear when I add it to the array.

Great stuff keeping on top of these security updates. Well done.

Great work getting this out so fast and including CVE-2026-31431 Up and running fine here so far from rc2.

Can we get 7.2.5 patched for CVE-2026-31431

Will CVE-2026-31431 be addressed in 7.3.0?

I've been running this version for several days and it's been a complete non-event for me. Everything appears to be working fine.

Possibly this: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v6.12.83&id=ba4811c8b433bfa681729ca42cc62b6034f223b0

Since upgrading from 7.2.4, I've seen this in my log files, not sure if it's an issue or not: 20:43:03 <hostname> nfsdcltrack[484481]: Unable to write to /proc/fs/nfsd/v4_end_grace: Device or resource busy 20:52:38 <hostname> nfsdcltrack[526390]: Unable to write to /proc/fs/nfsd/v4_end_grace: Device or resource busy 21:10:07 <hostname> nfsdcltrack[603065]: Unable to write to /proc/fs/nfsd/v4_end_grace: Device or resource busy

Thanks, nice to see the Kernel update too

It's great to see a stability release for 7.2.x ahead of 7.3, also great to see an RC ahead of releasing it. 👍

If that's the case, there should be an outright block on upgrading if any reiserfs file systems are found.. along with an explanation of why.

unraid uses the LTS kernel, the next LTS is 6.18. I've also seen mentions that the 7.3 alphas are already on 6.18.

Given 7.3 will move to 6.18, it would have been good to see a kernel update to the latest 6.12 stable kernel in this release.

I've read in a few spots that 7.3 is getting close to a beta with a new LTS kernel, 6.18. It got me wondering about the 7.2.x series, and whether that's now done and finished? Given the kernel change, I wonder if it's worth at least a final house keeping / security update for 7.2.x which moves to the very latest 6.12 kernel train and applies any outstanding linux security updates. i.e. change nothing else aside from kernel+security updates? I'm wondering whether that might be a good idea in general for various release trains when major changes are upcoming. My thoughts on that is that at least then it enables people to sit on that final version for a while with the most refined and up to date version of that kernel along with the latest security patches. So that in general, the last stable release of any particular unraid release train is as up to date as it can be package/security wise.

Just curious, did this ever happen? if not, why not? I also wonder if it should at least be an option to enable in the webgui. Is there any good reason not to do this?