I'm running 4.7. Two days ago everything was fine(and has been for a couple years). Then while trying to update some files from a Windows PC to the UnRaid Tower yesterday, I started getting an error that I do not have permission while trying to delete or copy files onto Tower. I'm using user shares. Anyone suggest something I can try to correct this issue? Let me know if you need more info.

You need to provide the syslog to give people some information to help with diagnosis.

You need to provide the syslog to give people some information to help with diagnosis.

 

and the permissions of the files/folders you're being declined permission to.

My bet is that you have some file system corruption, and the drive is being mounted read only. Find a post by dgaschk, he has all the relevant info in his signature.

I've attached my syslog. As far as I know the files/folders I'm not allowed to manipulate should be just under the base root user.

 

Looking at the permissions for a file in a folder I'm having difficulty with this is what I'm seeing when I do an ls -la

 

-rwx------  1 root root  136092 Aug 25  2007 070823ftprev.txt*

 

For a file I'm not having issues with I'm seeing this when I do an ls -la

 

-rwx------ 1 root root  141998 Nov 16  2009 Wefile.txt*

 

I don't see an issue with the permissions. Appears to belong to root, and root should be able to alter the file.

 

syslog.txt

The root user can only alter the file is a console session logged on as root.  The root user is not a valid user for Samba (network) access in the latest unRAID releases.

The root user is not a valid user for Samba (network) access in the latest unRAID releases.

I'm running 4.7.

The root user is not a valid user for Samba (network) access in the latest unRAID releases.

 

Can I ask what you mean by this? My files located in shares (/mnt/user) are owned by a combination of "Nobody" and "Root", the exact same owner follows over from the disk (/mnt/disk).

The root user is not a valid user for Samba (network) access in the latest unRAID releases.

 

Can I ask what you mean by this? My files located in shares (/mnt/user) are owned by a combination of "Nobody" and "Root", the exact same owner follows over from the disk (/mnt/disk).

 

This does not apply to version 4.7.

 

 

The system was not cleanly shutdown. How do you shut the server down? See check disk file system in my sig.

The root user is not a valid user for Samba (network) access in the latest unRAID releases.

 

Can I ask what you mean by this? My files located in shares (/mnt/user) are owned by a combination of "Nobody" and "Root", the exact same owner follows over from the disk (/mnt/disk).

 

This does not apply to version 4.7.

 

I'm on 5R12, I'm asking what he meant by it because I want to make sure I'm not doing something incorrect.

I'm not sure of Jonathanm's point other than pointing out what I already said... I'm running 4.7 not 5. I do want to upgrade to 5, but I've been putting it off until an official finished release instead of a beta or RC. Though it appears to be stuck where it is at.

 

dgaschk - Usually I shut it down by pushing the power down button which starts the shut down procedure. It's possible that I may have shut it down more forcefully at some point, but I don't remember doing so. Not saying I didn't, just that I don't remember it. I'll take a look at the check disk file system in your sig. I had already started looking at it from a previous suggestion actually.

 

Thank you

The root user is not a valid user for Samba (network) access in the latest unRAID releases.

 

Can I ask what you mean by this? My files located in shares (/mnt/user) are owned by a combination of "Nobody" and "Root", the exact same owner follows over from the disk (/mnt/disk).

 

This does not apply to version 4.7.

 

I'm on 5R12, I'm asking what he meant by it because I want to make sure I'm not doing something incorrect.

I think it means that samba cannot log in as root so if the root user had specific share privileges they could not be applied. Everyone has full access to public shares so this only matters for secure or private shares.

Thank you for those instructions dgaschk. I had 3 files that were having issues. Following those directions fixed the issue and I'm back up and running. And Jonathanm thank you for giving the early advice.