Has anyone else had a problem with the latest version of truenas causing Windows to blue screen when accessing a file/files in a SMB share hosted by TrueNAS.
We are a a robotic systems integrator and use solidworks to do our 3D design work. I updated our TNS to 24.10 last friday and today when we tried to open solidworks file from our network share it cause a windows kernel panic with a stopcode of PAGE_FAULT_IN_NONPAGES_AREA. When I downgrade trueNAS scale back to 24.0.2 I am able to open the file with no issue or blue screen. We test this with both a Win10Pro and Win11Pro machine and both got blue screen when TrueNAS was on 24.10 and no blue screen when on 24.0.2.
I have reported the issue to ixsystems but they seem to thing it is a windows bug and not a truenas bug. I just find that hard to believe when changing the version of trueNAS fixes it.
https://ixsystems.atlassian.net/browse/NAS-133322
100% a Windows bug. The system should never, ever BSoD. That’s not to say there isn’t a TrueNAS bug, but you can’t blame TrueNAS for a BSoD.
Then why do I only get a BSoD when trueNAS is booted in 24.10.1
Usually with these sorts of bugs there’s two sides to the story. TrueNAS is responding to an SMB request solidworks is generating and the response is causing windows to BSOD. Someone opened a bug ticket about it and I have more information.
This is very much a Windows problem and a quite bad one at that (server responses shouldn’t cause a client to BSOD). I have opened an issue report with MS. I’ll track down the offending code at some point probably today or tomorrow and give WIP fix for testing.
3 Likes
I’m the one who opened the bug report. I was just posting here to see if anyone else was experiencing the same issue.
FYI I uploaded a fix candidate to your bug ticket a day or so ago.
Thanks, I have not had a chance to implement this yet. We got snowed in here in STL and I don’t want to implement this remotely. It won’t be until this weekend that I can take the server down to test if this fixes it. I will report back after I put the fix in place.
@awalkerix
Here is the output, I was asked if i wanted to overwrite local change with the system provided changes. I answered “Yes” was that correct? The instructions provided in the ticket did not mention this. It seem to be working though, I am able to open files without causing a BSoD
admin@MMCI-VM-TN2[~]$ sudo /usr/local/libexec/disable-rootfs-protection
[sudo] password for admin:
Flagging root dataset as developer mode
Setting readonly=off on dataset boot-pool/ROOT/24.10.1/opt
Setting readonly=off on dataset boot-pool/ROOT/24.10.1/usr
/usr/bin/apt-cache: setting 0o755 on file.
/usr/bin/apt-mark: setting 0o755 on file.
/usr/bin/apt: setting 0o755 on file.
/usr/bin/dpkg: setting 0o755 on file.
/usr/bin/apt-cdrom: setting 0o755 on file.
/usr/bin/apt-key: setting 0o755 on file.
/usr/bin/apt-config: setting 0o755 on file.
/usr/bin/apt-ftparchive: setting 0o755 on file.
/usr/bin/apt-extracttemplates: setting 0o755 on file.
/usr/bin/apt-sortpkgs: setting 0o755 on file.
/usr/bin/apt-get: setting 0o755 on file.
/usr/local/bin/pkg_mgmt_disabled: setting 0o644 on file.
admin@MMCI-VM-TN2[~]$ ls
admin@MMCI-VM-TN2[~]$ sudo dpkg -i truenas-samba_4.20.5+ix-3_amd64.deb
(Reading database ... 98432 files and directories currently installed.)
Preparing to unpack truenas-samba_4.20.5+ix-3_amd64.deb ...
Unpacking truenas-samba (2:4.20.5+ix-3) over (2:4.20.5+ix-3) ...
Setting up truenas-samba (2:4.20.5+ix-3) ...
Samba is not being run as an AD Domain Controller: Masking samba-ad-dc.service
Please ignore the following error about deb-systemd-helper not finding those services.
(samba-ad-dc.service already masked)
Masking samba-bgqd service: Masking samba-bgqd.service
Please ignore the following error about deb-systemd-helper not finding those services.
(samba-bgqd.service already masked)
Failed to preset unit, unit /etc/systemd/system/samba-bgqd.service is masked.
/bin/deb-systemd-helper: error: systemctl preset failed on samba-bgqd.service: No such file or directory
samba-bgqd.service is a disabled or a static unit not running, not starting it.
Processing triggers for libc-bin (2.36-9+deb12u7) ...
Processing triggers for man-db (2.11.2-2) ...
admin@MMCI-VM-TN2[~]$
