Djoss

Where and how are you getting this error ?

People usually keep the /storage setting, but change to which unRAID path it is mapped. Or you can just create a new mapping, e.g. map /mnt/remotes to /remotes in the container.

The default /storage mapping will probably come back on the next update...

Are you using the GUI or the automatic disc ripper ?

Maybe you can check on the JDownloader forum to see if someone else reported this issue ?

Since it is working in another browser, I would try to clear the browser's cache.

Where did you map "/mnt/remotes" in the container ? "/storage/remotes" ? Do you also have a mapping for "/storage" ?

For the 1006 error, try to clear your browser cache.

Is the container still installed ? Did you try to re-install it ?

The AMC script invoked by the container uses /mnt/user/appdata/FileBot/amc-exlude-list.txt. Do you see your already-processed files in it ?

Did you check if ownership/permissions of folders/files remained the same? You may also report/ask about this issue to the unRAID pre-release thread.

The crash is now understood. Latest version 3.3.1 now available!

Check on the MakeMKV forum to see if the crash is reported for your disc. This topic looks interesting: https://forum.makemkv.com/forum/viewtopic.php?f=3&t=17268. Don't hesitate to add your input. The renaming should survive restarts. You only need to re-do it after re-creation of the container (e.g. after update or after changing settings).

Last versions of MakeMVV definitely fixed these crashes (at least for me). Are you still getting crashes when running the latest Docker image file ?

I don't expect any performance change between the container and the host (unRAID). Did you perform any disk performance test on unRAID itself ?

CloudBerry Backup always had problem displaying different mounts. Did you ask their support team about that ?

I need to provide a new Docker image with the new software. However, this latest version crashes (even when running on a "normal" PC running ubuntu). I have a case opened for that.

Is your question generic or specific to MakeMKV? Because when using MakeMKV, I guess the bottleneck is not the SSDs, but your optical drive.

Are you using multiple backup plans ?

The problem is under /tmp: What do you have under this directory? du -h /tmp

I'm not aware of an issue where the container would write outside /config... When you see the docker image is filling up, you can check where the container is writing stuff. First, login to the container: docker exec -ti CloudBerryBackup sh And run the following commands: add-pkg coreutils du -h -d1 --exclude /storage --exclude /proc --exclude /sys /

I think it's possible, but it's more complex to setup. You basically have to use use a single volume mapping between unRAID and the container. Then in container settings you adjust the input/output paths inside the container to be under this single mapped folder.

The plug-in is marked as outdated. You have nothing new if you click Help->Find Updates ? Also, the "Temp disabled" messages may be caused by wrong credentials for your account.

You can ignore these errors. As you can see later in the log, AMC worked fine. Don't forget to change the "Automated Media Center: Action" setting if you want FileBot to actually rename the files.

This container doesn't support nvenc, only Intel QSV.