Mooks

Did you definitely roll back everything inside the unassigned.devices folder (and delete the .zip of the latest version, which wouldn't have been in your back) as well as replace the .plg file? Then reboot the whole server? That fortunately worked for me.

Update.... Almost certain it's an Unassigned Devices plugin issue. I fortunately had been taking weekly backups and was able to revert my UD plugin folder and .plg file back to 2024.01.22b. This immediately resolved the issue. Everything is working again but now I'm scared to update to 6.12.6 again, 6.12.4 running stable with the earlier version of UD. Maybe you guys can have a look into it? Cheers

Hi All A bit of a critical issue as I can't get my VMs or any Dockers up and online. I upgraded my plugins and Unraid today and now can't mount my NVME drives. I've scoured the net and this thread and have seen people with similar issue but never found a resolution thats relevant to me. Please assist ASAP if possible ❤️ I have tried downgrading back to 6.12.4 but the issue is now persisting. Diagnostics attached. To be clear I'm referring to "Feb 10 13:00:50 mw-nott unassigned.devices: Error: Device '/dev/nvme1n1p1' mount point 'nvme_vms' - name is reserved, used in the array or a pool, or by an unassigned device." Same thing happening for both NVME. Many thanks for all assistance. EDIT: I have tried to rename the device as well as the Disk Mount Point but it makes no difference. EDIT2: I have also updated the password for both disks in UD settings. EDIT3: With UDEV debug turned on in UD. Feb 10 16:15:14 mw-nott unassigned.devices: Error: Device '/dev/nvme0n1p1' mount point 'nvme_appdata' - name is reserved, used in the array or a pool, or by an unassigned device. Feb 10 16:15:14 mw-nott unassigned.devices: Disk with serial 'Samsung_SSD_970_EVO_Plus_1TB_S4EWNF0M315736L', mountpoint 'nvme_appdata' cannot be mounted. Feb 10 16:20:29 mw-nott unassigned.devices: Error: Device '/dev/nvme1n1p1' mount point 'nvme_vms' - name is reserved, used in the array or a pool, or by an unassigned device. Feb 10 16:20:29 mw-nott unassigned.devices: Disk with serial 'Samsung_SSD_970_EVO_Plus_1TB_S4EWNF0M315657T', mountpoint 'nvme_vms' cannot be mounted. Feb 10 16:23:04 mw-nott unassigned.devices: Error: Device '/dev/nvme0n1p1' mount point 'nvme_appdata' - name is reserved, used in the array or a pool, or by an unassigned device. Feb 10 16:23:04 mw-nott unassigned.devices: Disk with serial 'Samsung_SSD_970_EVO_Plus_1TB_S4EWNF0M315736L', mountpoint 'nvme_appdata' cannot be mounted. Feb 10 16:25:39 mw-nott ool www[7907]: /usr/local/emhttp/plugins/unassigned.devices/scripts/rc.settings 'save' Feb 10 16:25:47 mw-nott unassigned.devices: Partition found with the following attributes: serial_short='S4EWNF0M315736L', device='/dev/mapper/nvme_appdata', serial='Samsung_SSD_970_EVO_Plus_1TB_S4EWNF0M315736L', uuid='0b40712f-132c-4718-9ed5-f04c2752fd36', part='1', disk='/dev/nvme0n', label='S4EWNF0M315736L', disk_label='', array_disk='', fstype='crypto_LUKS', mountpoint='/mnt/disks/nvme_appdata', luks='/dev/nvme0n1p1', file_system='luks', not_udev='', mounting='', unmounting='', pass_through='', mounted='', part_read_only='', pool='', pool_name='', not_unmounted='', disable_mount='', target='', size='0', used='0', avail='0', owner='user', read_only='', shared='1', command='', user_command='', command_bg='true', enable_script='false', prog_name='', logfile='', running='', formatting='', preclearing='' Feb 10 16:25:47 mw-nott unassigned.devices: Error: Device '/dev/nvme0n1p1' mount point 'nvme_appdata' - name is reserved, used in the array or a pool, or by an unassigned device. Feb 10 16:25:47 mw-nott unassigned.devices: Disk with serial 'Samsung_SSD_970_EVO_Plus_1TB_S4EWNF0M315736L', mountpoint 'nvme_appdata' cannot be mounted. Feb 10 16:26:39 mw-nott unassigned.devices: Partition found with the following attributes: serial_short='S4EWNF0M315657T', device='/dev/mapper/nvme_vms', serial='Samsung_SSD_970_EVO_Plus_1TB_S4EWNF0M315657T', uuid='a22ec698-8f23-4b3f-9197-cbaa8ebc2d5e', part='1', disk='/dev/nvme1n', label='nvme_vms', disk_label='nvme_vms', array_disk='', fstype='crypto_LUKS', mountpoint='/mnt/disks/nvme_vms', luks='/dev/nvme1n1p1', file_system='luks', not_udev='', mounting='', unmounting='', pass_through='', mounted='', part_read_only='', pool='', pool_name='', not_unmounted='', disable_mount='', target='', size='0', used='0', avail='0', owner='user', read_only='', shared='', command='', user_command='', command_bg='true', enable_script='false', prog_name='', logfile='', running='', formatting='', preclearing='' Feb 10 16:26:39 mw-nott unassigned.devices: Error: Device '/dev/nvme1n1p1' mount point 'nvme_vms' - name is reserved, used in the array or a pool, or by an unassigned device. Feb 10 16:26:39 mw-nott unassigned.devices: Disk with serial 'Samsung_SSD_970_EVO_Plus_1TB_S4EWNF0M315657T', mountpoint 'nvme_vms' cannot be mounted. mw-nott-diagnostics-20240210-1308.zip

Yeh same issue. If you go into the Admin section you can add a currency there, it'll find the exchange rate and then update it. Then you will find the added currency to all the dropdown menus.

FYI to those having issues with VNC etc for Calibre. I managed to get it working by opening console and typing: and it loaded straight away, didn't even have to reboot container. Hope this helps some. If it doesn't help then sorry I have no idea, not a coder, just something that worked for me ❤️

Hi all I'm trying to use the youtube-dl docker container and I'm getting the attached error. I've tried using ENV variables to increase the max_old_space_size to even 20GB and I still get the same error, it just takes longer to appear. has anyone seen this or know why? Thanks

Hi all Apologies if this is a dumb question but I did a little bit of digging and couldn't find an answer. Unraid is for some reason reporting the size as below. If I map the drive in Windows, I get this: I have thought about mapping using NFS but I don't know if that has any real benefits in this situation so I haven't attempted that. Is this normal? What will happen if I move stuff over, will that fill up and then what? I can confirm there is no quota of any sorts set in Synology. Cheers

Hi all I am having trouble with the Backblaze Personal Backup docker, hopefully you guys have some ideas. I think the issue is around permissions, and for some reason the docker isn't able to 'write' to the destination. Here's some context. I use Unassigned Devices with the following settings. Legacy Mount is something I turned on to see if that would fix my issue, and it unfortunately didn't. Here is the remote mount that I am trying to pass through to the Backblaze docker. Here is the Backblaze docker Path entry. You can see I have tried to use /mnt/disks/10.20.30.205_CloudSync (Legacy Mount Point) but unfortunately it didn't fix my issue. Previously I did try /mnt/remote/10.20.30.205_CloudSync. FYI the Cloudsync folder is sitting on a NAS and I have confirmed the user account Unraid is using, has read/write permissions. When the docker starts, I am greeted with this notification. As you can see, the application can see the drive, and the folders, but for whatever reason, it can't create the .bzvol folder. I have confirmed that the symlink was created successfully. A few interesting points I discovered: if I open the docker console and go to /drive_d/ and do "mkdir test" then it actually creates the folder no problem. if I change the path in the docker settings to one of Unraid's Shares (e.g. /mnt/user/movies) then everything works fine and the D drive is selectable to backup. Does anyone have any ideas please? Thanks

Thanks for this - worked for me. Hopefully this gets updated in the next release so that we don't have to keep changing this with every update. Cheers

Getting the exact same error. I also tried both the :dev and the :latest docker tag versions and they both respond the same.

Hi all, Thanks for this app/container, though I'm having some issues uploading my wedding videos. They are mp4 and shouldn't be anything special or weird. See attached. Can anyone help please? I would prefer not to convert them myself.

No support needed...but just wanted to say Thank You! (Also thanked you on Patreon).

Hi all Thanks for a great project...I've been putting off this post for ages but I'm getting very frustrated. I have for a long time had issues with the VPN connection dropping out. I use AirVPN and when I restart the docker, I can see the VPN session opening up, and the port Check on rutorrent is Green, everything is good. Then after an unspecified amount of time, the port checker goes Yellow and my connection drops. The only way to fix it is to restart the docker. Is there some kind of keepalive setting I can use? or tweak? At the moment my workaround is a User Script that restarts the container every hour...not ideal. Logs attached. EDIT: Have moved all settings and everything over to Qbittorrent which seems to be much more stable for now. Would still like to get this resolved in case the same thing happens with Qbittorrent? supervisord.log

Thanks for your reply. At the time my container was definitely up to date yeah, but I have since checked again and there was an update. I applied it and we're all good now. Thanks!

Hey all I started getting this error today: rfbProcessClientProtocolVersion: read: I/O error I can't login, when I open the docker web GUI the VNC says "disconnected" and it cant connect. Anyone else getting the same thing? EDIT: Randomly started working again....didn't make any changes. I see now there is a banner saying "Code42 wasn't able to upgrade, but will try again in 1hour". Im guessing this has something to do it with it. Any way to stop/prevent it from trying to do taht? Thanks