Thanks for observation… please report a bug and leave the NAS ticket here.
1 Like
Sure, created NAS-134717.
1 Like
I noticed that with this latest update, my Incus profiles were deleted. That didn’t happen with the previous ones.
Will we still be able to modify vfs objects via CLI after migrating to 25.04?
No. What VFS objects are you trying to change?
I have some customers that need the full_audit option for some homegrown audit scripts that report file deletions daily.
Then again, I’ve been adding this manually via CLI for a long time now, don’t know if it is already included in SCALE versions that do have Samba auditing built-in.
What about the smb_options section? Will we be locked out of this too?
You can’t override vfs objects through smb_options. At most you will break the IPC$ share. You will need to use the builtin auditing functionality in SMB. If it’s not delivering a particular feature you need, you can make a request for it.
Writing a script to generate a daily report of SMB deletions using our API should be basically a one-liner.
Pity. It is too specialized to be of general interest to iX. It is, however, important - dare I say, essential - to one of my clients.
Also, I think that simply locking people out is a bit excessive - if they understand the risks involved, and the possibility of breaking stuff, wouldn’t a big disclaimer when invoking the CLI suffice?
I don’t see how you can’t do this with existing SMB auditing framework. It will require some work on your part, but your customers are probably paying you for this effort 
Users overriding these parameters are basically the primary cause for Core->Scale migration failures and a very common problem in the forums and our bug tracker. It has also led to some cases of data loss, server crashes, and generally broken SMB servers. So no, experience has shown that they are too sharp of a knife to give users.
They require a somewhat intimate knowledge of how samba works, a very intimate knowledge of filesystem, and understanding of all the moving parts in between.
Well, you’ve removed the ability to send mail from the shell, and now you’re removing the ability to customize auditing and generate a daily report of deleted files, a functionality that is not essential - except for my customers.
Although I understand some of the reasons behind iX’s increasing customization restrictions, they are gradually making TrueNAS more difficult to work with, for those of us who are in need of something beyond what the GUI offers.
I’m not a paying customer, though, so my two cents here are too poor a contribution to merit much attention, of course - thank you anyway for taking the time to answer my previous posts.
1 Like
you’re removing the ability to customize auditing
Have you tested our SMB auditing to determine whether meets your needs? If it doesn’t then, as mentioned, file a feature enhancement request or a bug report.
1 Like
Just a note, in future this could be natively in Incus. Optional -rtc base=localtime · Issue #1752 · lxc/incus · GitHub
1 Like
Hope you don’t think I’m being argumentative or disrespectful.
A couple of my customers need to receive a daily, formatted report containing all files that were deleted during the previous 24 hours, including the user and workstation responsible, for reasons of their own.
In TrueNAS 24.04 I could do that easily, via a shell script developed for such specialized case.
In TrueNAS 24.10 I had to jump thru some hoops to make it work, because it turns out you can’t send mail from the shell anymore.
In TrueNAS 25.04 I won’t be able to do it anymore, because the customizations my script depends upon won’t be there.
I have not investigated built-in auditing in TrueNAS, mainly because I never had to, having created my own, customizable shell solution.
Again, I don’t expect iX to accomodate me, a non-paying customer. I’m just registering an opinion, even if a fringe one.
2 Likes
I don’t think there’s any way to configure a Windows VM from the UI since you can’t add a second disk to the VM with the VirtualIO drivers. I hate how you can only specify zvols within the Disks section instead of also being able to specify iso files.
I thought I saw a workaround where someone put the drivers on a USB stick, and passed that to the VM to install drivers from.
Your reply is appreciated. Is there any documentation for the API - if indeed it is exposed to the user?
Yep, in the product UI click your username, top right → My API Keys → API Documentation. Examples of API clients are here:
1 Like
I’ve been using TrueNAS Scale 24.10.2 for about two months and was eager to test out the 25.04-RC.1 release. Although I had concerns regarding Incus VM support, I felt prepared since I successfully set up two Windows 11 instances on 24.10.2 using VirtIO drivers, a virtual TPM device, and configured my bridge network. To address the unreliable web spice implementation in TrueNAS Scale, I used Windows Remote Desktop.
When trying 25.04-RC.1, it seemed straightforward to recreate the VM instance with my existing ZVol. Both Windows VMs were operational, but I encountered several issues:
- There’s an unnecessary 10GB root drive that I can’t remove.
- The Device Manager shows exclamation marks on some devices like PCI and PCI Simple Communications Controller, which I don’t know how to fix.
- Due to these device issues, I attempted to reinstall the VirtIO driver or QEMU Guest Agent ISO via SMB, as it wasn’t possible through the TrueNAS Web interface, but this didn’t resolve the problem.
- The VMs shut down or went into sleep mode after being idle for a while. I couldn’t find the sleep settings in Windows, which is problematic since one of my Windows 11 VMs runs Blue Iris Video Security and needs to be operational 24/7.
- Although this is an RC release, the documentation on managing Windows 11 VMs is insufficient.
- The bridge network setup seems mandatory, unlike in 24.10.2 where I used different VLANs for each Windows VM. This flexibility appears unavailable in 25.04.
To better understand how Incus handles Windows VMs, I plan to delve into the Incus documentation rather than relying solely on TrueNAS resources. From what I’ve seen in forums, configuring settings through the console is possible, though not recommended by TrueNAS documentation.
For now, I’ve reverted to using TrueNAS 24.10.2 and will continue learning from community discussions before attempting 25.04 again.
1 Like