Samba write issues with Mac OSX and Windows 7

Have done multiple clean installs with full updates/upgrades adding SSH and SAMBA from the OSMC App Store, cannot add files to the external USB hard drive connected on the MAC Finder as user osmc.

I can see/read the files and folders there on my MACs or a Win7 box, but not add more.

I’m a newbie to RasbPi and Linux.

Is this just a permission thing that the Apps didn’t set up correctly?

Explicit CLI instructions I can paste into the Mac Terminal would be GREATLY appreciated!

Thanks in advance,

Gonster

Normally all permissions for the samba server are handled automatically but it might be a problem with/on the USB disk.

  1. Which filesystem you use on the USB disk?
  2. Can you add files on the USB disk as user OSMC when you login on the command line
  3. What does sudo journalctl _COMM=smbd report?

Details regarding how to access the command line interface can be found here on our Wiki: Accessing the command line - General - OSMC

Last login: Mon Sep 4 09:42:15 2017 from johns-mac-pro.local
osmc@osmc1:~$ sudo journalctl _COMM=smbd
– Logs begin at Mon 2017-09-04 11:01:48 EDT, end at Thu 2017-09-07 11:33:25 EDT. –
Sep 04 11:02:01 osmc1 smbd[636]: [2017/09/04 11:02:01.186218, 0] …/lib/param/loadparm.c:743(lpcfg_map_parameter)
Sep 04 11:02:01 osmc1 smbd[636]: Unknown parameter encountered: “valid user”
Sep 04 11:02:01 osmc1 smbd[636]: [2017/09/04 11:02:01.188456, 0] …/lib/param/loadparm.c:1659(lpcfg_do_service_parameter
Sep 04 11:02:01 osmc1 smbd[636]: Ignoring unknown parameter “valid user”
Sep 04 11:02:01 osmc1 smbd[616]: Starting SMB/CIFS daemon: smbd.
Sep 04 11:02:01 osmc1 smbd[637]: [2017/09/04 11:02:01.291042, 0] …/lib/util/become_daemon.c:124(daemon_ready)
Sep 04 11:02:01 osmc1 smbd[637]: STATUS=daemon ‘smbd’ finished starting up and ready to serve connections
Sep 04 11:02:03 osmc1 smbd[687]: [2017/09/04 11:02:03.131156, 0] …/lib/param/loadparm.c:743(lpcfg_map_parameter)
Sep 04 11:02:03 osmc1 smbd[687]: Unknown parameter encountered: “valid user”
Sep 04 11:02:03 osmc1 smbd[687]: [2017/09/04 11:02:03.131367, 0] …/lib/param/loadparm.c:1659(lpcfg_do_service_parameter
Sep 04 11:02:03 osmc1 smbd[687]: Ignoring unknown parameter “valid user”
Sep 04 11:02:03 osmc1 smbd[688]: [2017/09/04 11:02:03.134796, 0] …/lib/param/loadparm.c:743(lpcfg_map_parameter)
Sep 04 11:02:03 osmc1 smbd[688]: Unknown parameter encountered: “valid user”
Sep 04 11:02:03 osmc1 smbd[688]: [2017/09/04 11:02:03.134979, 0] …/lib/param/loadparm.c:1659(lpcfg_do_service_parameter
Sep 04 11:02:03 osmc1 smbd[688]: Ignoring unknown parameter “valid user”
Sep 04 11:02:03 osmc1 smbd[689]: [2017/09/04 11:02:03.135472, 0] …/lib/param/loadparm.c:743(lpcfg_map_parameter)
Sep 04 11:02:03 osmc1 smbd[689]: Unknown parameter encountered: “valid user”
Sep 04 11:02:03 osmc1 smbd[689]: [2017/09/04 11:02:03.135649, 0] …/lib/param/loadparm.c:1659(lpcfg_do_service_parameter
Sep 04 11:02:03 osmc1 smbd[689]: Ignoring unknown parameter “valid user”
Sep 04 11:02:03 osmc1 smbd[690]: [2017/09/04 11:02:03.153757, 0] …/lib/param/loadparm.c:743(lpcfg_map_parameter)
Sep 04 11:02:03 osmc1 smbd[690]: Unknown parameter encountered: “valid user”
Sep 04 11:02:03 osmc1 smbd[690]: [2017/09/04 11:02:03.153992, 0] …/lib/param/loadparm.c:1659(lpcfg_do_service_parameter
Sep 04 11:02:03 osmc1 smbd[690]: Ignoring unknown parameter “valid user”
Sep 06 18:51:40 osmc1 smbd[3793]: [2017/09/06 18:51:40.611978, 0] …/lib/param/loadparm.c:743(lpcfg_map_parameter)
Sep 06 18:51:40 osmc1 smbd[3793]: Unknown parameter encountered: “valid user”
Sep 06 18:51:40 osmc1 smbd[3793]: [2017/09/06 18:51:40.613331, 0] …/lib/param/loadparm.c:1659(lpcfg_do_service_paramete
Sep 06 18:51:40 osmc1 smbd[3793]: Ignoring unknown parameter “valid user”
Sep 06 18:51:47 osmc1 smbd[3793]: [2017/09/06 18:51:47.536217, 0] …/source3/param/loadparm.c:2900(check_usershare_stat)
Sep 06 18:51:47 osmc1 smbd[3793]: check_usershare_stat: file /var/lib/samba/usershares/ owned by uid 0 is not a regular f
Sep 07 10:43:06 osmc1 smbd[4016]: [2017/09/07 10:43:06.261010, 0] …/lib/param/loadparm.c:743(lpcfg_map_parameter)
Sep 07 10:43:06 osmc1 smbd[4016]: Unknown parameter encountered: “valid user”
Sep 07 10:43:06 osmc1 smbd[4016]: [2017/09/07 10:43:06.265371, 0] …/lib/param/loadparm.c:1659(lpcfg_do_service_paramete
Sep 07 10:43:06 osmc1 smbd[4016]: Ignoring unknown parameter “valid user”
Sep 07 10:43:31 osmc1 smbd[4018]: [2017/09/07 10:43:31.541841, 0] …/lib/param/loadparm.c:743(lpcfg_map_parameter)
Sep 07 10:43:31 osmc1 smbd[4018]: Unknown parameter encountered: “valid user”
Sep 07 10:43:31 osmc1 smbd[4018]: [2017/09/07 10:43:31.544347, 0] …/lib/param/loadparm.c:1659(lpcfg_do_service_paramete
Sep 07 10:43:31 osmc1 smbd[4018]: Ignoring unknown parameter “valid user”
Sep 07 10:43:36 osmc1 smbd[4018]: [2017/09/07 10:43:36.635403, 0] …/lib/param/loadparm.c:743(lpcfg_map_parameter)
Sep 07 10:43:36 osmc1 smbd[4018]: Unknown parameter encountered: “valid user”
Sep 07 10:43:36 osmc1 smbd[4018]: [2017/09/07 10:43:36.637807, 0] …/lib/param/loadparm.c:1659(lpcfg_do_service_paramete
Sep 07 10:43:36 osmc1 smbd[4018]: Ignoring unknown parameter “valid user”
Sep 07 10:44:34 osmc1 smbd[4062]: [2017/09/07 10:44:34.580460, 0] …/lib/param/loadparm.c:743(lpcfg_map_parameter)
Sep 07 10:44:34 osmc1 smbd[4062]: Unknown parameter encountered: “valid user”
Sep 07 10:44:34 osmc1 smbd[4062]: [2017/09/07 10:44:34.583351, 0] …/lib/param/loadparm.c:1659(lpcfg_do_service_paramete
Sep 07 10:44:34 osmc1 smbd[4062]: Ignoring unknown parameter “valid user”
lines 1-46/46 (END)

have you changed the smb.conf?
Can you provide cat /etc/samba/smb.conf | paste-log
And
ls -lah /var/lib/samba/usershares/

osmc@osmc1:~$ cat /etc/samba/smb.conf | paste-log
https://paste.osmc.tv/ofehulemiy

cat: /etc/samba/smb-local.conf: No such file or directory
https://paste.osmc.tv/sepisuxona

osmc@osmc1:~$ ls -lah /var/lib/samba/usershares/
total 28K
drwxrwx–T 2 root sambashare 4.0K Sep 4 11:02 .
drwxr-xr-x 5 root root 4.0K Mar 4 2017 …
-rw-r–r-- 1 root root 147 Sep 4 11:02 2tbmac
-rw-r–r-- 1 root root 149 Aug 31 16:17 4gb usb
-rw-r–r-- 1 root root 141 Sep 4 11:02 efi
-rw-r–r-- 1 root root 151 Sep 4 11:02 recovery
-rw-r–r-- 1 root root 151 Sep 4 11:02 settings

Looks ok

That looks about right.
Which of the drives are you trying to write to? Are all of them not working?
What is the file system you are using?
Can you write a file to it as user OSMC from the command line?

Sorry to be such a NOOB, but I’m having trouble navigating the CLI. I tried going to the root as root to get to that USB drive, but I don’t think it’s mounted (SWAG). When I tried to get to it with root@osmc1:/dev# cd /dev/sda2/ it comes back with:
bash: cd: /dev/sda2/: Not a directory

I obviously haven’t paid enough synTAX.

The cheat sheets assume a lot as do many of the other linux sites I’ve flobbed around in looking for the steps and examples to get me there. Can you recommend any?

They should be mounted in /media. There’s no need for you to flop around in CLI as root.

What about the answers to these important questions?

Shared Folder was unchecked, so I checked it. Could that be it??? I see it named in the /Media folder

root@osmc1:/# cd media
root@osmc1:/media# ls
2TBMac EFI README RECOVERY SETTINGS
root@osmc1:/media# cd /2TBMac
bash: cd: /2TBMac: No such file or directory
root@osmc1:/media# cd media/2TBMac
bash: cd: media/2TBMac: No such file or directory
root@osmc1:/media# cd media/2TBMac/
bash: cd: media/2TBMac/: No such file or directory

When in /media, command should be cd 2TBMac
From anywhere, command should be cd /media/2TBMac

OOPS! I WAS in the 2TBMac directory, too dizzy to notice!

Now I need to figure out file copy syntax

Just touch test.file

This will create an empty file simply for testing purposes.

Tried to remove a folder and got the message “cannot remove…Read-only file system”

That would make it hard to write to, too!

Is the solution to give chown to @users, or a better way to change that to read, write & execute?

Sorry for the NOOBNESS and aversion to risk!

Actually I believe your problem is that the harddisk is hfs+ journaled formatted which by default will be mounted read-only.
You can check that with mount | grep media
`

What do you think about ExtFS? I already own the Paragon Drivers.

ext2/3/4 are natively supported on Linux so they would be the best choice if already have the paragon drivers.
An alternative (while not as ideal) that might have broader usage would be exfat.

Well that was disappointing! Mounted a newly formatted drive (formatted ext4 via the terminal on the Pi) and am getting the same result. Still mounting as read only.

Should I change the ownership with CHOWN giving ownership to USERS, or maybe force the write/execute to a user or the group?

What’s the syntax for either of those?