Jump to content

Ubuntu write issues to SMB share


Go to solution Solved by modem7,

Recommended Posts

Hey guys, 

 

I know there's a 1000 different topics surrounding this, but yet to find a solution:

 

Scenario: 

New unRAID server

Transferring files from old (Ubuntu based) server using rsync

Created SMB shares (private)

Set fstab to mount shares

 

I'm currently unable to edit the current data within those shares inside Ubuntu. Windows (10) works. 

root@Tower:/mnt/user/docker/HDA# smbstatus --resolve-uids

Samba version 4.17.3
PID     Username     Group        Machine                                   Protocol Version  Encryption           Signing
----------------------------------------------------------------------------------------------------------------------------------------
28353   alex         users        192.168.0.251 (ipv4:192.168.0.251:47268)  SMB3_11           -                    partial(AES-128-CMAC)
1617    alex         users        192.168.50.254 (ipv4:192.168.50.254:37140) SMB3_00           -                    partial(AES-128-CMAC)
19130   alex         users        192.168.50.104 (ipv4:192.168.50.104:39458) SMB3_00           -                    partial(AES-128-CMAC)
28354   alex         users        192.168.0.250 (ipv4:192.168.0.250:34312)  SMB3_11           -                    partial(AES-128-CMAC)
13314   alex         users        192.168.0.100 (ipv4:192.168.0.100:33598)  SMB3_11           -                    partial(AES-128-CMAC)
1616    alex         users        192.168.50.254 (ipv4:192.168.50.254:37142) SMB3_00           -                    partial(AES-128-CMAC)
18964   alex         users        192.168.50.105 (ipv4:192.168.50.105:43408) SMB3_00           -                    partial(AES-128-CMAC)

Service      pid     Machine       Connected at                     Encryption   Signing
---------------------------------------------------------------------------------------------
IPC$         1617    192.168.50.254 Sun Apr  9 10:39:52 PM 2023 BST  -            -
IPC$         19130   192.168.50.104 Sun Apr  9 10:08:27 PM 2023 BST  -            -
IPC$         18964   192.168.50.105 Sun Apr  9 10:08:18 PM 2023 BST  -            -
docker       1616    192.168.50.254 Sun Apr  9 10:39:52 PM 2023 BST  -            -
projects     13314   192.168.0.100 Sun Apr  9 10:00:01 PM 2023 BST  -            -
IPC$         1616    192.168.50.254 Sun Apr  9 10:39:52 PM 2023 BST  -            -
docker       13314   192.168.0.100 Sun Apr  9 10:03:57 PM 2023 BST  -            -
downloads    13314   192.168.0.100 Sun Apr  9 10:03:57 PM 2023 BST  -            -
docker       19130   192.168.50.104 Sun Apr  9 10:08:27 PM 2023 BST  -            -
proxmox      28353   192.168.0.251 Sun Apr  9 09:42:19 PM 2023 BST  -            -
IPC$         28354   192.168.0.250 Sun Apr  9 09:42:18 PM 2023 BST  -            -
desktopcontent 13314   192.168.0.100 Sun Apr  9 10:03:57 PM 2023 BST  -            -
media        13314   192.168.0.100 Sun Apr  9 10:02:28 PM 2023 BST  -            -
docker       18964   192.168.50.105 Sun Apr  9 10:08:18 PM 2023 BST  -            -
oldhd        13314   192.168.0.100 Sun Apr  9 09:48:11 PM 2023 BST  -            -
IPC$         28353   192.168.0.251 Sun Apr  9 09:42:19 PM 2023 BST  -            -
proxmox      28354   192.168.0.250 Sun Apr  9 09:42:18 PM 2023 BST  -            -
media        1617    192.168.50.254 Sun Apr  9 10:39:52 PM 2023 BST  -            -


Locked files:
Pid          User(ID)   DenyMode   Access      R/W        Oplock           SharePath   Name   Time
--------------------------------------------------------------------------------------------------
13314        alex       DENY_ALL   0x100080    RDONLY     NONE             /mnt/user/oldhd   .   Sun Apr  9 22:03:57 2023
13314        alex       DENY_NONE  0x100081    RDONLY     NONE             /mnt/user/docker   .   Sun Apr  9 22:12:45 2023
13314        alex       DENY_NONE  0x100081    RDONLY     NONE             /mnt/user/docker   .   Sun Apr  9 22:04:05 2023
13314        alex       DENY_NONE  0x100081    RDONLY     NONE             /mnt/user/docker   .   Sun Apr  9 22:04:05 2023
1616         alex       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /mnt/user/docker   .git/objects/pack/pack-b4d0ba1b6aeae7aafd9414def746bb1283cd19e2.idx   Sun Apr  9 22:40:43 2023
13314        alex       DENY_NONE  0x100080    RDONLY     NONE             /mnt/user/projects   .   Sun Apr  9 22:02:31 2023
1616         alex       DENY_NONE  0x120089    RDONLY     LEASE(RWH)       /mnt/user/docker   .git/objects/pack/pack-b4d0ba1b6aeae7aafd9414def746bb1283cd19e2.pack   Sun Apr  9 22:40:43 2023
13314        alex       DENY_ALL   0x100080    RDONLY     NONE             /mnt/user/downloads   .   Sun Apr  9 22:03:57 2023
13314        alex       DENY_ALL   0x100080    RDONLY     NONE             /mnt/user/desktopcontent   .   Sun Apr  9 22:03:56 2023

 

 

ls -la
total 184
drwxr-xr-x 2 alex users      0 Apr  9 22:47  .
drwxr-xr-x 2 alex users      0 Apr  9 22:40  ..
-rwxr-xr-x 1 alex users   1346 Apr  7 11:51  borgmatic.restore.yml
drwxr-xr-x 2 alex users      0 Apr  8 05:37  .cache
-rwxr-xr-x 1 alex users  22455 Apr  7 11:51  compose.dot
drwxr-xr-x 2 alex users      0 Apr  8 05:37 'Conf Files'
-rwxr-xr-x 1 alex users    721 Apr  7 11:51  docker.code-workspace
-rwxr-xr-x 1 alex users  15643 Apr  7 11:51  docker-compose-public-consumption.yml
-rwxr-xr-x 1 alex users 109614 Apr  7 11:51  docker-compose.yml
-rwxr-xr-x 1 alex users    628 Apr  7 11:51  Docker-viz.txt
-rwxr-xr-x 1 alex users  15101 Apr  7 11:51  .env
-rwxr-xr-x 1 alex users    544 Apr  7 11:51 'netdata docker nvidia.txt'
-rwxr-xr-x 1 alex users      0 Apr  9 22:47  test.txt
drwxr-xr-x 2 alex users      0 Apr  8 05:37  .vscode
-rwxr-xr-x 1 alex users    148 Apr  7 11:51  yt-dlp.txt

 

Troubleshooting steps:

Able to see all files inside folder.

Tried on separate Windows box. Successful

Ran newperms /mnt/user/docker/ - No change

Tried mounting using uid and gid - No change (//192.168.50.111/media  /mnt/media  cifs vers=3.0,uid=alex,gid=users,credentials=/home/alex/.smb_credentials)

Tried creating new file - successful

Tried editing new file - successful

 

 

If I run newperms on the new file, I get nobody:users on unraid, and I'm able to edit on the Ubuntu box with no issues. 

 

This seems to be an issue with existing files that have been rsynced, not an issue with Samba/Unraid/Ubuntu(fstab) config.

My rsync command was: rsync -avP /mnt/disks/Z2K9R3BT/gh/TV /mnt/user/media/

 

No idea why it'd work in Windows, but not in Linux.

 

Unsure where to go from here! Linux permissions are definitely not my forte.

Edited by modem7
Link to comment
  • Solution

Things got weirder - after you posted the question, I had a check on other files, and they were absolutely fine....Just the one .env file.

I've recreated it, and now it all seems bloody fine. -.-

Let's consider this resolved as an ID10T issue with a dose of "huh?" - if it's just that one file, I honestly couldn't give a rat's hoohah! I should have checked before I posted - blame lack of sleep.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...