Jump to content

Squid

Community Developer
 View Profile  See their activity

  • Posts

    28,769

  • Joined

  • Last visited

  • Days Won

    314

 Content Type 

Everything posted by Squid

  1. Squid
    Not going to pretend to be an samba options guru, but you've got browseable = no, writeable=no and no users being allowed to read and a type in write list (wtite list)
  2. Squid
    And in this case the system isn't doing what you want it to do and FCP is catching that. Your appdata share only exists on disk 1 and FCP caught that because of a config mistake / GUI bug or confusion (depending upon how you think about it)
  3. Squid
    Pointless to specify both include and excluded disks as they are opposites of each other, and it's easy to create a conflict. You only should specify one or the other. Include / Excluded disks only applies to new files being written. A previously existing file will always get overwritten on the same disk it already exists on Additionally (although this isn't your problem), split level also override include / exclude when files / folders already exist on another drive
  4. Squid
    They're supposed to be accordingly to the link @ljm42 posted
  5. Squid
    Shares on the shares page are only what the OS handles. Symlinking or direct mounts within it is always going to be troublesome at best and will also potentially have other issues (inability to stop the array?) Within smb-extra.conf you need to add a section akin to [MYIMG] path=/mnt/disks/whateverhere valid users = andrew write list = andrew force user = root A reboot (or a change to a share setting) will result in MYIMG being shared over the network.
  6. Squid
    You would add in appropriate entries to smb-extra.conf on the flash drive (/config). The symlink has the same result for the same reason. It's not under the OS control.
  7. Squid
    Click on the icon for Nextcloud and various support options will all be there.
  8. Squid
    Anything mounted within /mnt/user the OS expects to have full control over. You're better off mounting them instead within /mnt/disks
  9. Squid
    It's because NextCloud is writing the files with a different set of permissions that aren't compatible with what Unraid wants for SMB and its users. Probably best to ask in LinuxServer's discord about this.
  10. Squid
    And that's part of the reason why this test is catching things that at first glance appear to be correct but would actually not have the desired effect the user wants without making a change. Would the better course of action be to display what it's actually set to in Share Settings and then put up some red text saying pool doesn't exist?
  11. Squid
    Include / Exclude settings do not affect files that currently exist. Those settings only affect new files being written. (oh and also Split level settings override include / exclude for new files)
  12. Squid
    See if this helps diagnose
  13. Squid
    Correct. Remote access, flash backups etc shouldn't be affected, but you will see that error and a Network error on the MyServers page
  14. Squid
    Any thing that's not ultimately within /mnt/user is lost on a reboot. You would want to modify the yaml file you're using so that you can map a folder outside of the image (ideally) to somewhere within /mnt/user/appdata
  15. Squid
    From the terminal, unraid-api stop should fix you up
  16. Squid
    Changed Status to Closed
  17. Squid
    I was actually surprised it wasn't on the website (IIRC RC's always used to be present)
  18. Squid
    Can you ping github.com?
  19. Squid
    Thanks. See if the update fixes it.
  20. Squid
    I need the diagnostics then as this may be a false positive
  21. Squid
    You would have to first deselect the what ever you've got isolated in Tools - System Devices, and then turn off ACS override in VM Settings. After rebooting you would then isolate the applicable devices you need for passthrough in VM Settings and adjust the VMs as necessary
  22. Squid
    You fix this all on the Share Settings in question. Your share's settings explictly refer to a pool named "cache" but you do not have a pool named "cache" (it is named something else). This results in files winding up on the array when you don't actually want them to. If you've got any problems, then post your diagnostics
  23. Squid
    Repeated errors like that mean that you haven't as of yet run a correcting parity check to actually fix them.
  24. Squid
    Is SSH enabled in Settings - Management Settings? Also if issues with this continue, then uninstall that plugin and try again with just the base OS to see if SSH works
  25. Squid
    Is this because one or more of the containers are updating themselves? ca.update.applications.plg - 2021.09.24 (Up to date) and other containers are "running through them" eg: connected to a VPN being managed by another container?
×
×
  • Create New...