dlandon

Execute the following command and see if the disk spins up: /bin/lsblk -nb -o size /dev/sdX

I'm working on a solution, but I can't be sure the disk size query is the issue. Most likely it is. Pretty much nothing else is queried when a disk is marked as passed through. When the disk is passed through it is managed by the docker or vm where the disk is passed through. There really is no value in UD displaying the disk size. No. This is totally contrary to the Unraid UI design. It would also a solution to a single use case and I don't code UD for special cases. The UD code is not an easy read.

I'm working on a solution, but I can't be sure the disk size query is the issue. Most likely it is. Pretty much nothing else is queried when a disk is marked as passed through. When the disk is passed through it is managed by the docker or vm where the disk is passed through. There really is no value in UD displaying the disk size. No. This is totally contrary to the Unraid UI design. It would also a solution to a single use case and I don't code UD for special cases. The UD code is not an easy read.

If "Pass Thru" is set, the disk should not wake up. I suspect your disk is waking up when UD checks the disk size. That is executed only if you click on the rescan disks icon. Not really. With "Pass Thru" set the disk should not wake up. It is not executed.

What happened is that UD saw that the device /dev/sdj1 was mounted, but failed to check if UD had mounted the device. UD needs to check that the device is mounted at /mnt/disks, which indicates that UD has mounted the device. If it is not mounted at /mnt/disks, UD should refuse to unmount the device. I need to think through whether or not it makes sense for UD to show a device as mounted if UD did not mount it, or disable the 'Unmount' button. Kind of like the latter, but I need to see what I can do in the code.

You set per user access in the UD settings. This is the same way that Unraid does user access.

How are you using the remote share?

This setting does not control user access. Access is controlled by the UD settings and is set by user for all UD shared devces. This is how Unraid share access is controlled, except UD does not set access by share. You can change the share name by changing the mountpoint. There is no plan to add user access control by share.

Others in this forum are better at solving docker issues than I am.

That error doesn't help a lot.

What is the execution error? What Plex docker are you using? Your issue sounds like it is with Plex.

Try restarting Plex the next time it happens. See if that doesn't clear it up.

I see nothing in the log that indicates any issues mounting and unmounting or accessing the remote shares. How is Plex accessing the share? How are you trying to browse the share?

Take a look at these issues in the log: May 25 14:26:02 919 root: Fix Common Problems: Error: Docker application Deezloader-Remix has volumes being passed that are mounted by Unassigned Devices, but they are not mounted with the slave option May 25 14:26:02 919 root: Fix Common Problems: Error: Docker application nzbhydra2 has volumes being passed that are mounted by Unassigned Devices, but they are not mounted with the slave option May 25 14:26:02 919 root: Fix Common Problems: Error: Docker application radarr has volumes being passed that are mounted by Unassigned Devices, but they are not mounted with the slave option May 25 14:26:02 919 root: Fix Common Problems: Error: Docker application readarr has volumes being passed that are mounted by Unassigned Devices, but they are not mounted with the slave option May 25 14:26:02 919 root: Fix Common Problems: Error: Docker application resilio-sync has volumes being passed that are mounted by Unassigned Devices, but they are not mounted with the slave option May 25 14:26:02 919 root: Fix Common Problems: Error: Docker application transmission has volumes being passed that are mounted by Unassigned Devices, but they are not mounted with the slave option

If Linux (Unraid uses Slackware) doesn't recognize the partition on the disk, UD can't do anything to fix that - it's not a bug. Unraid uses xfs, btrfs, and reiserfs (for compatibility), and doesn't natively use ext4. Because of that, ext4 support in Unraid may not be what it is in other Linux implementations. I'm not sure what you are planning on using the disk for, but my suggestion would be to use another format that is better supported by Unraid.

All I see is a lot of mounting and unmounting. DId you have issues when you provided the diagnostics?

Go into LMS settgings and you can browse the /config/playlists folder. You can browse to the appdata/LogitechMediaServer/playlists folder and check the contents.

I don't have any idea why that is, but UD can't do anything with the drive unless Linux recognizes the partition format. Is it a USB connected drive? If so try a USB2 port?

Linux does not recognize the drive partition.

Get into a terminal session and show the results of 'ls /mnt/dksks/'.

Post your diagnostics.

Be sure you have set the correct folder in settings:

Playlists are at appdata/LogitechMediaServer/playlists. The docker creates the folder if it is not available when it is started.

Do your credentials have any special characters? If so they will cause a problem.

UD will not try SMB1 mounting unless NetBIOS is on. Likewise, you cannot set force use SMB1 in the settings unless NetBIOS is on.