dlandon

This is related to the preclear diskinfo daemon and will be cleared up soon.

Thank you all for reporting in. gfjardim and I are now working on getting his latest (2017.06.28a) changes working. It seems there is a subtle bug that is causing the share name modification issue in a drive with more than one partition. The other issues with wrong disks showing in UD comes from a diskinfo daemon he is using in preclear to keep disk status without working the disk too hard by constantly monitoring status. When preclear is installed, UD takes advantage of the diskinfo daemon to supply disk status. These issues should be pretty easy to sort out. For the time being I have disabled the diskinfo usage in UD until preclear gets updated. The changes gfjardim is implementing is to allow preclear and UD to play nice together. It seems that UD is doing too much disk work and this can cause preclear issues - slow downs, hangs, non-responsive, etc.

Change the share name by clicking on the mount point to change it to a name without the '$'.

New release of UD plugin with the following changes: Disable the preclear diskinfo daemon that was causing array disks to show as unassigned devices. Revert changes that prevented the first partition of a multiple partitioned disk from being changed. Add root path to cookie used for simple/complete status to keep status correct. Let me know if this fixes the issues recently reported here.

This is happening because of some changes made to the preclear plugin that were also integrated into the UD plugin. There is a background daemon running that collects disk information periodically to try to cut down on the disk queries. This daemon is apparently getting some wrong information about unassigned and array disks. I'll take it up with gfjardim and see if we can't come up with a fix.

Post diagnostics.

Can you post your diagnostics?

Can you show a screen shot of UD with the array drives that are not supposed to be there?

Here is the log from a failed eject attempt: [makemkvcon] Current progress - 100%, Total process - 100% [makemkvcon] 7 titles saved [makemkvcon] Copy complete. 7 titles saved. [autoDiscRipper] Disc rip terminated successfully. [autoDiscRipper] Ejecting disc from drive 0 (/dev/sr0)... [autoDiscRipper] ERROR: Failed to eject drive 0 (/dev/sr0).

I'm converting a lot of ripped vob files to mkv and I lost that log. I'll run another test and let you know when I get a chance to rip a DVD.

Do you have cookies disabled? UD uses a cookie to store that status.

Don't see that with Chrome.

I don't think the disk eject when the rip is done is working. I put in a DVD and it ripped, but the disk has not ejected. EDIT: Just noticed this error in the log: Jul 1 10:25:02 MediaServer kernel: blk_update_request: I/O error, dev sr0, sector 8480772 Jul 1 10:25:02 MediaServer kernel: Buffer I/O error on dev sr0, logical block 2120193, async page read Maybe this is why the disk did not eject.

It looks to be a problem on disks with multiple partitions. It appears to affect the first partition only. Working on a fix.

It seems to work when I press enter but stays on the field. I'll have a look.

The output folders and files don't have enough write permission for Windows to manipulate the files. Maybe 777?

Partly. You need to slow down a little bit and understand how UD works before firing off and saying that UD auto mount is broken. You are also not giving me enough information to help you. The auto mount script is run on an unRAID event when disks are mounted. This event occurs when the drives are all mounted and the array is started. This is the right time for UD to auto mount drives, remote shares, etc. No one else is having an issue with this operation so it is something unique to your setup. I suspect it's a timing issue because it seems you can run the auto mount command at the command line and the drives mount. So whatever prevented the initial auto mount has had time to settle. There are several tools to help you with UD. Hover your mouse over any active area and a tool tip will show you what clicking that area will do. Click the 'Help' text in the menu bar and it will turn on help and there is a description of the UD operations. Many questions like how to rename a share are answered in this help text. Here is what I need you to do. Follow these steps and give me the information before doing any array operations. Reboot your server. Get the diagnostics zip at Tools->Diagnostics. Post that file in response to this message. Click on the log download button on the UD web page and post that in response to this message. Capture a screen shot of the UD page so I can see the devices you are trying to mount that you say do not auto mount. I'll then be able to get the information I need to help you with your issue.

That's exactly what it does. Post the ud log so I can see why you are having trouble.

It would be a nice feature, but I'm not sure it's worth it if it creates problems.

I am accessing the Docker by remote desktop and the keyboard repeat does not work when a key is held down. Is this an issue with this Docker, or all Dockers?

Ok. I understand.

It should be. I added the nvme drive recognition some time ago. I think he is saying that it is working. It's just not real clear what he is saying.

Which auto mount slider is not working? Post the UD log. ReiserFS support is built into unRAID. UD will mount a ReiserFS disk.

The excluded files input field in the settings is now 150 characters.

Sorry. I misunderstood.