Connor Zook

Solved by @MonadProxy. If you would like to claim your $20 bounty, please send me an email at [email protected].

@Frank1940 I have attempted this specific solution several times, including multiple times with power cycles in between. I am considering reenabling guest access with blank credentials in the registry even though it is recommended against by msft and lime tech. All of this shit just worked before windows decided my home network was too dangerous for me to have control over in the way I want.

I have now deleted the user credentials I was attempting to access my SMB shares with, "homenet", and attempted to access the same folder that is causing issues with alternate user credentials. I am still locked out. I then created a new user on unraid and checked permissions to ensure I have read and write access to the entire share, then attempted to access the same folder on the SMB share using the new credentials. I'm still locked out. Is my unraid install corrupt?

^The error I received when attempting to test functions by deleting a file I had JUST made a copy of. ^The error I'm now getting when attempting to access the folder again. Monolith/homenet is the user credentials I've got set up on my windows access credentials for the SMB share. Additionally, homenet is a new set of user credentials, only set up last night. Zooker is an older set. I was mistaken, homenet is the name of my workgroup (of which unraid is the local master) as WELL AS the credentials that I log in with. Could this be causing issues?

@trurl I have attempted to access the Games folder from both computers which are using my dummy access credentials. I was temporarily (for unknown reasons, I have done nothing new) able to read files, and create files now, but unable to delete files. I was being thrown an error of needing permission from my dummy credentials user (the same user that I have logged into the SMB share with) to delete a file, and once it threw that error I am now locked out of the folder again. This behavior is extremely strange and has me worried that user permissions are being corrupt somehow on unraid's end.

@trurl Could the dark souls (legally owned) file be corrupting user access? That user is not the same user that has been locked out of the games folder.

@trurl redacted two files that are not relevant

These folders have existed in the share since its inception. They're just subfolders of /Media/ which is my main storage share. In this case it's /Media/Games, which was working until I tried to copy files to it and then stopped allowing access halfway through a normal file copy operation. Forgive my horrible syntax, terminal does not get along with android and I'm a noob(ish).

@trurl This article is exactly why I set up dummy credentials on my server for use with windows credentials manager. This was originally a good solution, until random folders on the share started locking out that user. This is my big issue.

Good point, how do I do that?

@MonadProxyI recently edited this to reflect some further info. Just wanted to catch you in case you were reading the outdated revision of this post.

I was attempting to transfer some game backups from an external drive to my unraid server, the transfer partially started (got to several percent of the way done) and then stopped abruptly giving an error akin to "you'll need permissions to do that". Some of my files transferred. After this I am now completely locked out of that folder on the share. This has been continuous headache after headache ever since upgrading to windows 11. Piece of shit OS. I have completed two troubleshooting steps- I've restarted my PC and I've restarted the server. I recently added a new disk to the array with no issues, and I've recently had to reconfigure credentials manager on windows to see a dummy username on my unraid server so that it stops blocking me from connecting. I've also recently updated the unraid server to 7.0.1, and my windows install is as fresh as it gets. I originally started with my samba shares set to export as public, and simply added dummy user credentials to satisfy windows, but now I have tested exporting the share as secure and requiring the username under my windows credentials to sign in when accessing, to no avail. Tested accessing this specific folder on one other device which is able to connect using blank credentials, and it is able to access the folder. Tested accessing this specific folder on one other device which is using the same dummy credentials to enable access to the share, and it is unable to access the folder. All devices are able to see the share as a whole, devices using Credential 1 are now locked out of the specific folder, and the device using no credentials is able to access the specific folder just fine. Any advice would be greatly appreciated. Thanks. monolith-diagnostics-20250227-0851.zip

I had corrputed files on my OS drive that were causing all kinds of issues. I purchased a new OS drive and reinstalled, ran a chkdsk on the original drive and everything is now working okay. Thanks anyways @Michael_P. Oh yeah and I ran memtest with no issues.

When initializing an outbound (Windows 11 to unraid) file transfer via my mapped network share or via unmapped local network browsing, I experience strange behavior from the windows explorer transfer dialog box. If i begin a file transfer of an extremely small file (~100kb), it is able to complete, however even though the file then shows up on my array's cache drive, attempting to access that file brings up this error: However I am able to download this "file" and when I run an MD5 hash comparison against it vs the original, it comes back different. Additionally, when I return this file to my PC (copy to unraid share and then copy back) it shows that the file contains most of the original contents, and displays a thumbnail which is accurate to the original, however attempting to open the copied file results in this error: These files show as the correct size on the unraid filesystem, though I am sure they are either garbled or damaging the integrity of the filesystem records somehow. Also, I am able to connect other devices on my network to the share and read the files back normally. I am able to open them directly from the share and also download them and view them as being correct to the original. When copying a file of roughly the next order of magnitude (~10MB) the file again will hand the explorer.exe transfer dialog box, but still "complete" anyways. However attempting to access this file and open it on another computer does not work as this file is corrupted to the point it is not opening. Additionally, when I attempt to copy a larger file (~5GB) to my unraid share it will begin the copy at Copying - 0%, and then either transmit a few KBs of data or transmit nothing at all, then freeze and hang my explorer.exe. However, even though this transfer does not finish normally and is obviously glitching out, the file is still transmitted and shows up on my cache drive as the correct size. However attempting to open this file on either machine again shows it to be corrupt. I have attached two images of the behavior of failed transfers. The strangest bit of all of this is that I am fully able to download and view every file that is currently on my array with no issues. I am even getting full gigabit throughput when reading data, just nothing when writing. I am also getting strange issues with my file associations in windows being unassigned, and when I attempt to open windows utilities (notepad, snipping tool) they will fail to open the first time, giving the error "This app can't open, check windows store for more details", though when I attempt to open them a second time they open without issue and function normally. STEPS TAKEN-- I have run a filesystem integrity check of windows 11. I have restored my system using a system restore point. I am downloading a windows update to see if that will save my bacon. I have deleted the files that I transferred to the server from the array, and verified that the cache drive is empty so that it does not write corrupt filesystem records to my array. I have run XFS_check on my array in maintenance mode in order to verify none of my disks have filesystem errors. I have deleted my SMB credentials, and disconnected and remapped my network drive in windows. ADDITIONAL INFO-- I have recently changed my wireguard configuration to allow untunneled traffic, as before I was unable to access my SMB shares when the wireguard client was running. I think this is the event that may have precipitated being unable to copy data to the array. I am not sure how this is the case but they happened at nearly the same time AFAIK. I have recently added a new drive to my array, but only after running an extended SMART test and verifying that all results met with pass. I recently installed oracle virtualbox. I know this is a long shot but It's the only idea I have. I have been using WFS tools in the past week or so to make backups of my WII U external data USB drive, including using the simple command line backup utility on windows, and (on the same drive though a different partition) using the wfs-fuse tool to append a virtual filesystem of my WFS-format data usb drive so that I may browse the files directly. Any help would be greatly appreciated. I've created a windows 11 repair disk and am now going to attempt to repair my install via USB. Beyond that I am worried that I may have to fully reinstall windows, something I'm not easily able to do as I don't have a backup drive to store my data on now that I'm unable to access my array. Thanks.

Server was running fine, up for several weeks with no issue, then one day it just stopped working without shutting down. I reboot today and am getting this error on repeat: Monolith login: XFS (nd3) : Internal error xfs_trans_cancel at line 1041 of file fs/xfs/xfs_trans.c. Caller xfs_inactive_truncate+0x9/0xca [xifs] XFS (md3): Corruption of in-memory data detected. Shutting down filesystem XFS (md3): Please unount the filesysten and rectify the problem(s) Any recommendations on how to proceed from here? I have discovered that my insanely important backups are not on a functioning drive, as the one I was working with went down.