Failed to set file group to 'users' for '/srv/dev-disk-by-id-ata-ST4000LM024-2AN17V_WCK1M9H9-part2/untitled folder 2':

I'm guessing it is a windows filesystem?

Zitat von J_Swan1315

I am trying to be able to access the files mainly on Macs, but I am using windows for the set-up. The media vault is on a Raspberry Pi 3B+ with a partitioned hard drive attached.

I am guessing the drives are NTFS? I am not sure why is failing, in NTFS filesystems mounted in omv you cannot set any fs permissions, basically ntfs drives are mounted read-write for everyone. But from my experience when doing this to ntfs fs chmod,chgrp is just ignored, they return zero exit code, but nothing happens effectively., which should be the same for the omv webui

What version of omv are you using?

If you have ssh enabled, please post this command:

omv-confdbadm read conf.system.filesystem.mountpoint

cat /etc/fstab

Also post this command:

mount

I am guessing here the disk got kicked when accessed, underpowered RPI and hub maybe?

Ok, vfat fails. that's why. Not sure what to do, this needs code to be fixed at share management. Also on the other side the dev doesn't like this kind of fs, so it could be that support is removed.

cc @votdev

You cannot set permissions in fat drives. The drives are mounted with same permissions for folder and files contents inside. Go in terminal and check who owns files and folder and permission mode.
This would be much easier if you use native Linux filesystem, not some fs from 30 years ago.

Zitat von J_Swan1315

What file system would you recommend that can be accessed by both Windows and Mac, yet modifiable on Linux?

I don't think you understand the NAS concept then. Disks in omv are not be on a pull off, plug in basis, except for a portable disk that you can used for the usbbackup plugin. As a NAS server your disks should be plugged 24/7, you can access your disks through the network using samba, nfs, ftp, afp, is not like omv doesn't give you sharing options.

If you pull a registered drive in omv then boot without that disk, that causes all sort of problems. Avoid this, always

And if you insist then use NTFS all chown, chmod, etc fail silently (zero exit code), so they don't produce any errors in the webui. Of course forget about setting permissions (less ACL). As i understand ntfs is readable in OSX

You will be able to read/write to the drive using the sharing protocols, means mounting the share as a drive in windows, the same goes for OSX.

Performance is not gonna be the best as you choose the worst board for this job