Hello, My flash drive died, I replaced it, copied files from backup and lost write access to my shares. In Windows (10 and 11) and Ubuntu. Everything seems fine on Unraid's side, already ran both New Permissions and Docker Safe New Perms. No change. also tried resetting SMB by renaming config files in /config and restarting Samba, still no write access

I can read the files in the shares, but no write access at all. The server is about to learn to fly, please help... I'm attaching my diagnostics.

Thanks in advance.

soundwave-diagnostics-20251219-1805.zip

Please post the name of one of the shares that is not working. Also, try creating a new test share and see if that works.

The shares that are not working are all of them (test is not accessible at all. that one is new). The shares are Shockwave, Soundwave, Torrents, isos, system and flash. Those ones I can read files, but not create/delete/modify via network.

test was created one or two days ago. I can't even have read access on either a real win11 machine or a kubuntu laptop. VMs on my win11 machine behave the same.

Edited December 20, 2025Dec 20 by Hamsterdan71

Ok so I created a new user (test) and THAT user has write access to both test and Soundwave (from the Linux laptop I kinda don't trust my Windows install at that point since it tells me something about trying to connect to a shared resource using more than one user is not authorised (or something like that)

But the new user WORKS fine in Linux.

Some screenshots and a new diagnostics file are included.

If it's only a user config hiccup, I guess I could just delete the user and create a new one? Or edit its file? Or restore it from an old flash backup?

Thanks in advance.

soundwave-diagnostics-20251220-1857.zip

OK. Quick comments:

58 minutes ago, Hamsterdan71 said:

(test is not accessible at all. that one is new

This share is 'Private'.

59 minutes ago, Hamsterdan71 said:

Shockwave, Soundwave, Torrents,

These three shares are 'Secure'. This means that there is read only access via the Samba "Public' permission to them

I would be checking to see that you are actually logging onto this server using Share Access users. On Windows 11, setup a Windows credential to do this. (Otherwise, it can be very easy to accidentally gain access the server using a guest account (Public permissions in 'Secure'). The fact that you have no access to the 'test' share supports this presumption since there is no guest access in 'Private'.

We can verify this if you access the server from your computers and then run this command in the GUI terminal:

smbstatus

Please capture the output using a screen capture if possible. If you copy-and-paste the text, please formatted the copy as in-line code. See here for how to do this in your reply:

Edited December 21, 2025Dec 21 by Frank1940

13 minutes ago, Hamsterdan71 said:

Ok so I created a new user (test) and THAT user has write access to both test and Soundwave (from the Linux laptop I kinda don't trust my Windows install at that point since it tells me something about trying to connect to a shared resource using more than one user is not authorised (or something like that)

My post above was being written during the time when you posted this post...

Yes, Windows allows only one user from each client computer to log onto each server. (This has been true for many, many years now!) Don't be afraid to permit your 'test' user to have read-write permissions from Windows. The only bad thing that can happen will be done by you. (What the airlines call 'cockpit error'!)

I am going to point to an thread that may help you understand what is required to set things up and addresses most of the problems.

https://forums.unraid.net/topic/191221-some-musings-on-smb-and-samba-and-unraid-and-windows/

How, I suspect that English is not your first language and I am not sure how well you can comprehend things. I do want to say one thing about Windows networking. IT is difficult to make changes to the windows SMB setup because there is no easy to stop and restart the the SMB service. So my advise is reboot the Windows Computer any time you make a change to the SMB settings.

Don't post any questions in that thread I just provided. Ask them in this thread.

smbstatus says those shares are readonly. But I can't access those either on the Linux laptop. Anyways, there's the screenshot.

And no, english is not my first language. I'm from Montreal. But absolutely no problem reading english.

Edited December 21, 2025Dec 21 by Hamsterdan71

OK, so it seems something's very wrong with both my kubuntu laptop and my win11 machine. in both VMs (ubuntu and win10), it works....

Any idea why it's not on the win11 host?

I deleted the dan user and recreated a new one on the server.

Edited December 21, 2025Dec 21 by Hamsterdan71

And creating a new user in Windows (the host) works. But I don't see why it wouldn't work on the linux laptop. I will try something tomorrow using a spare Unraid license.

OK---- Look at the /config/smbpaswd file on your flash drive. (It is a standard text file so any text editor can open it.) Typical below:

The number 1000 for smbuser is the User (ID) in the smbstatus output. That tells you which Unraid Share Access user is accessing the file.

Lets stat here with this part of the output:

I know that the IP address of my Windows 11PRO PC is 10.0.0.6. (I looked it up in Settings on the PC.) This also shows that I an logged as "user". The User (ID) for "user" 1001. And the PID for this login from my PC is 1727854.

Let's go on:

This section shows the Services that are running. By looking at the pid numbers I can determine what computer is using that service. (Remember that 1727854 is pid for my PC)

The final section-- "Locked files" is probably the least helpful.

The 'R/W' column is always "RDONLY" in my experience. It also seems to show every connection made since the PC started up. The listings seems to disappear when the PC is actually logged out of the server. (The top line with any actual file listed is the capture when I was actually playing a file.)

Please understand that if you have two or three computers actively using your server, the output from this command output becomes quite busy. (Lots of lines of information to review and figure out what is assigned to which PC.

FIXED!

Somehow getting rid of credentials using Credentials Manager didn't do squat. Ended up removing them using an older tool.

By running "rundll32.exe keymgr.dll,KRShowKeyMgr" in a command prompt as found on Stack Exchange

authentication - How do I clear cached credentials from my Windows Profile? - Information Security Stack Exchange

Thanks all...

Just getting rid of the credentials by editing them will (should???) remove them from the database. However, SMB is running using those parameters which it retrieved earlier. Deleting/changing a credential after that has occurred does not change that fact. You must force a restart of SMB to force it to access that database again and the simplest way is to reboot the Windows machine. (That is one thing that makes fixing SMB/Samba issues is frustrating is that changing something does not result in a instant change in the way that things are working. You have basically restart everything to make sure that your change has propagated through the entire chain.)