Jump to content
We're Hiring! Full Stack Developer ×

dlandon

Community Developer
  • Posts

    10,285
  • Joined

  • Last visited

  • Days Won

    20

Everything posted by dlandon

  1. Can you show a screen shot?
  2. Ok, that helps me understand your use case. I think the best thing here is for me to have a UD setting the same as the setting for the array for MacOS interoperability, but applies to UD devices. Currently if the array setting is 'Yes', then UD sets the MacOS interoperability on its shares.
  3. Help me better understand your use case. Do you need all or some UD devices to be "Enhanced macOS interoperability"?
  4. Yes, vfs_catia and streams_xattr are added to the drive share settings. This applies to all Unraid shares and UD devices. exFAT does not support extended attributes. Why exFAT? It is not a good choice for what you are trying to do.
  5. I would start by trying a different USB port. If that doesn't work, I'd look at cable or drive problems.
  6. What version of Unraid? I just made a fix for this on 6.9 and 6.10, but he doesn't appear to be on either.
  7. It's really not a UD problem. UD depends on Linux for determining the file system on a disk partition. Does the UD page show anything in the 'FS' column?
  8. NFS and SMB shares are forced to shutdown when the array is shutdown. Unfortunately, I just found a typo that was preventing that. I'll fix that in today's release.
  9. I was told today this is not true. I find most of the time the 'Dev X' designation is the same for a device, but it is not guaranteed.
  10. Today's release has a fix for SCSI disks that don't show in UD with the dynamix.scsi.devices plugin installed.
  11. Linux does not recogize the file system on that disk. What is the history of that disk? Was it formtted in UD? FYI, a disk that is passed through will show 'Passed' on the mount button.
  12. The 'Dev X' label is assigned by Unraid to all unassigned devices. The device is tracked by serial number and always assigned the same 'Dev X' when it is attached to the server. The idea behind the 'Dev X' label is similar to the array disks being designated 'DiskX'. How many UD devices do you have that makes identification so difficult?
  13. Try '*(rw,sec=sys,insecure,anongid=100,anonuid=99,no_root_squash)' for your rule.
  14. When you set up sharing as explained, you share out the mountpoint set for the device. e.g. /mnt/disks/mountpoint is shared with NFS.
  15. Here's your issue: Jan 6 02:11:48 Tower unassigned.devices: Mount drive command: /sbin/mount -t 'hfsplus' -o force,rw,users,umask=000 '/dev/sdb1' '/mnt/disks/My_Book' Jan 6 02:11:49 Tower kernel: hfsplus: Filesystem was not cleanly unmounted, running fsck.hfsplus is recommended. mounting read-only.
  16. Now we can get down to the UD disk issue. Please unmount and then remount the disk you were having issues with and post the diagnostics again.
  17. Not a dumb question. When on the UD or settings pages, click the 'Help' and you'll see some documentation. The other place is the first and second posts of this very long thread.
  18. Are the log messages continuing? If they are, stop those dockers and find out which one has the problem.
  19. Stop all your dockers and then start them one at a time to see which one is causing the logging.
  20. Go to the UD settings and set 'NFS Security' to 'Private'. Then enter this line: *(sec=sys,rw,insecure,anongid=100,anonuid=99,no_root_squash) in the 'Rules'.
×
×
  • Create New...