Community Developer
  • Posts

  • Joined

  • Last visited

  • Days Won


dlandon last won the day on June 24

dlandon had the most liked content!


  • Gender
  • Location
    Georgetown, Texas

Recent Profile Visitors

17314 profile views

dlandon's Achievements

  1. The root share is Unraid shares and I don't think it appropriate to add UD devices to that.
  2. Remove the docker and then add it back. At the bottom of the template click on 'Show more settings' Confirm that the appdata mappings make sense for your system.
  3. I'm looking into this issue and need some information. Please provide me with the following: Screen shot of the disk on the UD page. Output of the command 'zfs list' when the disk is mounted. How was the disk created? Is this a disk you will leave as a UD device?
  4. In Linux, return code -13 usually corresponds to the error code EACCES, which stands for "Permission denied". This implies that the system does not have the necessary permissions to access or mount the CIFS share. It could be credentials or permission settings. Try to use credentials that don't use special characters.
  5. Try this procedure to create a root share on your Synology NAS: To make an entire Synology NAS appear as a root share, you'll need to configure the NAS's shared folders and permissions accordingly. Here are the steps you can follow: 1. Access DSM (DiskStation Manager): Log in to the DSM interface of your Synology NAS. 2. Create Shared Folders: * Go to Control Panel > Shared Folder. * Click on Create to make a new shared folder. * Configure the settings, such as name, description, and location. * If you want the entire NAS to be accessible, you might want to create one shared folder that encompasses all the data. 3. Set Permissions: * After creating the shared folder, go to Permissions tab. * Click Create to add a new permission. * Select the user or group you want to grant access to. * Choose the level of access (e.g., Read/Write) you want to provide. 4. Enable Advanced Permissions (Optional): * In the Permissions tab, click Advanced Permissions. * Here, you can further customize permissions based on specific users or groups. 5. Enable SMB (or NFS) Service: * Go to Control Panel > File Services. * Make sure that the appropriate protocol (SMB or NFS) is enabled based on your network setup. 6. Set Up Shares: * For SMB, go to Control Panel > File Services > SMB/AFP/NFS. * In the SMB tab, select Advanced Settings. * Check Enable SMB service. * Configure any other settings as per your preferences. 7. Configure Shared Folder Advanced Settings: * In the Shared Folder settings, select the shared folder you created earlier. * Click on Edit. * Under the Advanced Settings tab, ensure that Enable Recycle Bin and Enable Transfer Log are configured according to your needs. 8. Apply Changes: * After making all the necessary adjustments, click Apply or Save to confirm the changes. 9. Access the Root Share: * Using a file manager on your computer, try connecting to the NAS using its IP address or hostname. For example, in Windows Explorer, you can type \\[NAS_IP] or \\[NAS_Hostname] to access the root share. Remember to replace [NAS_IP] and [NAS_Hostname] with the actual IP address or hostname of your Synology NAS. Please note that making an entire NAS appear as a root share means that users accessing it will have access to all shared folders and files within. Make sure to manage permissions carefully to prevent unauthorized access to sensitive data.
  6. It looks like 'volume1' is not shared on the DS918 with SMB. That's why UD can't find it when searching for shares. The error message indicates that the operation failed with error code 95, which is typically associated with an unsupported operation.
  7. What happens if you let UD search for the server and then search for the share? If you manually enter the server and share: Server: DS918 Share: top level share_name Don't try to add slashes. UD will do the right thing on its own.
  8. You'll need to share the complete DS918. UD cannot mount it if it is not shared.
  9. Internet domains are not resolved on Unraid. That is your DNS server. Only local names are resolved on Unraid. That's expected because the name can be found very quickly in the hosts file and the DNS server is not used to resolve the name. You need to look into your DNS server and possibly change it to another one.
  10. Click the double arrows on the upper right of the UD web page. If that doesn't solve the issue it's probably a historical device. Please pm me the following files: /flash/config/plugins/unassigned.devices/iso_mount.cfg /flash/config/plugins/unassigned.devices/samba_mount.cfg /flash/config/plugins/unassigned.devices/unassigned.devices.cfg
  11. Why is it expected to encounter a mounting error? What would be the error?