bmartino1

you are corect he has finsihed his rewrite and it appears to be working as orignaly intended... I ahve udpated the gihub repo and docker very little will need changed in the unriad temaptle but overal rewirte has brought back the origal intentions of a 1 click install form the CA. Suplly the plex image (better) or let this docker image auto detcet and find plex and run the scirpt based on teh dp repair mode... i'm wokring on the updated uraid template... this means new and old users will need to delete the old and install the new CA once ready... Please go too add containers in the template drop down list selct dbrepair. delete the old image by hitting the black x go to ca and install the updated template due to changes. *at this time the template has not been updated but other facets have been testing... see github for a quick docker run in the mean time... #!/usr/bin/env bash # Plex DBRepair v26.10.00 one-shot run: match the LinuxServer Plex test settings. # Run ONLY after ensuring a recoverable backup. Change Plex name when needed. set -euo pipefail docker rm plex-dbrepair-test 2>/dev/null || true docker run --name plex-dbrepair-test \ --hostname plex-dbrepair-test \ --network bridge \ --restart no \ -v /var/run/docker.sock:/var/run/docker.sock \ -v /mnt/user/appdata/plex-dbrepair-logs:/logs \ -e DBREPAIR_MODE=automatic \ -e PLEX_CONTAINER_NAME=auto \ -e PLEX_CONTAINER_MATCH=plex \ -e PLEX_MOUNT=/config \ -e PLEX_REL='Library/Application Support/Plex Media Server' \ -e ENABLE_BACKUPS=true \ -e ALLOW_PLEX_KILL=true \ -e RESTART_PLEX=true \ -e PRUNE_DAYS=30 \ -e DBREPAIR_TIMEOUT=7200 \ -e STOP_TIMEOUT=90 \ bmmbmm01/plex-dbrepair:latest printf '\nRepair exit code: ' docker inspect plex-dbrepair-test --format '{{.State.ExitCode}}'

I'm still waiting on a reply from Chuck PA on other forms, I will rework the docker once I get the OK form him. May rework how the docker works orginaly when made it was runing Chuck PA scirpt but had isseus with deplyment adn the script stalling... had to rework the entire setup then the FTS (Text Search) repairs and issues started comeing in as I esteal re wrote by coping out his repair work form the script... once i have dev done and comunication with how to procede in teh future... (may have a docker var tempatle and log do other things and acutal run the docker exec and script commands based on tempatle.. IDK yet... the point is I'm looking into it and waiting on more info be fore impelementation and execution..

I did at one time but it has changed. A lot of it, if any, is pulled from the website and their forum.... https://forum.makemkv.com/forum/ if any at all... similar with older variation of the DVD encryption key and the large number being a prime number university researcher prime number archive using a long number to get the dvd decode key example... with the above options checked mkaemkv dumps and pulls a simlar decode data from disk (and per disk drive firmware) I've had good luck with LG and asus with makemkv not all disk drives work... Sorry, I don't know that data off hand any more if it is talking elsewhere at all... there may be more info int in the code of the github porject: https://github.com/jlesage/docker-makemkv

sounds like your ptr data dind't download and or issues with decod file... blueray pulls and makes a privatedata tar file I would have you mkae sure the config folder has read write unraid docker safe permissions 777 and nobody:users I would also have you double check your makmkv settings But I can confirm the lattest image is working... MakeMKV | ╭――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――╮ MakeMKV | │ │ MakeMKV | │ Application: MakeMKV │ MakeMKV | │ Application Version: 2.0.0 │ MakeMKV | │ Docker Image Version: 26.09.2 │ MakeMKV | │ Docker Image Platform: linux/amd64 │ MakeMKV | │ │

while i'm not experiencing these issues with the latest and have used this same docker on other platforms. I am using an older generated appdata config settings file... # MakeMKV settings file, written by MakeMKV v1.18.3 linux(x64-release) Example of my settings.conf # # MakeMKV settings file, written by MakeMKV v1.18.3 linux(x64-release) # app_DataDir = "/config/data" app_DestinationDir = "/output" app_DestinationType = "2" app_InterfaceLanguage = "eng" app_Java = "" app_Key = "my mkv key" app_PreferredLanguage = "eng" app_Proxy = "" app_ShowDebug = "1" app_ccextractor = "/opt/makemkv/bin/mmccextr" bdplus_DumpAlways = "1" sdf_Stop = "" speed_ASUS_BC-12B1ST___b_3.00_211512151340_SIK9RH1LJ494 = "" I can only recommend deleting the AppData folder as deleting the Docker from the Unraid webUI DOES NOT remove old configuration, which may be broken or problematic. DELETE YOUR OLD APPDATA FOLDERS!!! Having a Unraid test system, this Docker is working correctly out of the box on a fresh Unraid... but I made the folder beforehand and set Docker safe permissions per Unraid tools, which sets 777 and nobody:users... https://hub.docker.com/r/jlesage/makemkv/tags jlesage/makemkv:v1.18.1 so I would recommend those having issues to use the older Docker tagged image... then once its up and working. stop the Docker, edit it and bring it to the latest jlesage/makemkv:latest as of writing: jlesage/makemkv:v26.09.2

at this time no, because this is a multi-stack requiring multiple database Docker containers as a prerequisite... I would recommend using Docker Compose to run this on Unraid... https://github.com/elie222/inbox-zero/blob/main/docker-compose.yml

... https://bmartino1.weebly.com/immich-on-unraid-docker-compose-guide.html

what kind of issues by default it will try and pull the beta key, which sometimes works... you need a makemkv license... https://forum.makemkv.com/forum/viewtopic.php?t=1053 Second, what kind of dvd/blueray disk drive, and how is it connected to Unraid... *now all disk firmware is compatible with the needed functions to read and rip disks... https://forum.makemkv.com/forum/viewforum.php?f=19 Third, what does Unraid see to pass the disk... ls /dev/{cdrom,sr*,sg*} As seen earlier in the forum: https://forums.unraid.net/topic/182065-resetting-optical-devsr-devices-without-a-restart/#findComment-1496296 you will need to pass all /dev/sr# and /dev/srg# Fourth, file permissions and Docker permissions... chmod 777 and chown nobody:users Waiting on changes; I've moved to Docker Compose... here is my working Docker Compose version... I use this with a single Asus Blu-ray connected via acpi usb... This is my working Docker Compose config... the Unraid default template; you need to add the device based on what your Unraid box sees as the disk drive... the default config works out of the box... name: makemkv services: makemkv: image: jlesage/makemkv:latest container_name: MakeMKV restart: unless-stopped # Debian cgroup v2 resource controls mem_reservation: 2g mem_limit: 6g memswap_limit: 8g #cpu_shares: 2048 pids_limit: 2048 shm_size: 2gb #privileged: true environment: - TZ=America/Chicago - MAKEMKV_KEY=BETA - AUTO_DISC_RIPPER=1 - AUTO_DISC_RIPPER_EJECT=1 - AUTO_DISC_RIPPER_PARALLEL_RIP=0 - AUTO_DISC_RIPPER_BD_MODE=mkv - AUTO_DISC_RIPPER_DVD_MODE=mkv - AUTO_DISC_RIPPER_FORCE_UNIQUE_OUTPUT_DIR=0 - AUTO_DISC_RIPPER_NO_GUI_PROGRESS=0 - USER_ID=0 - GROUP_ID=0 - APP_NICENESS=0 - DISPLAY_WIDTH=1920 - DISPLAY_HEIGHT=1080 - DARK_MODE=1 - WEB_AUDIO=0 - WEB_FILE_MANAGER=0 - WEB_FILE_MANAGER_ALLOWED_PATHS=AUTO - WEB_FILE_MANAGER_DENIED_PATHS=None - WEB_NOTIFICATION=0 - WEB_AUTHENTICATION=0 - WEB_AUTHENTICATION_TOKEN_VALIDITY_TIME=24 - WEB_AUTHENTICATION_USERNAME= - WEB_AUTHENTICATION_PASSWORD= - SECURE_CONNECTION=0 - SECURE_CONNECTION_VNC_METHOD=SSL - SECURE_CONNECTION_CERTS_CHECK_INTERVAL=60 - WEB_LISTENING_PORT=5800 - VNC_LISTENING_PORT=5900 - MAKEMKV_GUI=1 - AUTO_DISC_RIPPER_MAKEMKV_PROFILE= - AUTO_DISC_RIPPER_INTERVAL=5 - AUTO_DISC_RIPPER_MIN_TITLE_LENGTH= ports: - 7806:5800/tcp - 7906:5900/tcp volumes: - /mnt/users/This is the path to the makemkv needed docker data/storage:/storage:rw - /mnt/users/This is the path to the riped disk:/output:rw - /mnt/users/This is the path to the appdata config:/config:rw tmpfs: - /tmp:size=1g,mode=1777 #security_opt: # - apparmor=unconfined # - seccomp=unconfined #cap_add: # - SYS_ADMIN devices: - /dev/sr0:/dev/sr0 - /dev/sg0:/dev/sg0 - /dev/sg1:/dev/sg1 - /dev/sg2:/dev/sg2 - /dev/sg3:/dev/sg3 - /dev/sg4:/dev/sg4 - /dev/sg5:/dev/sg5 - /dev/sg5:/dev/sg6 - /dev/sg5:/dev/sg7 networks: {}You can add the above compose to a docker run to test... https://www.decomposerize.com/ And pull the side data that I may or may not have in the above compose to add a manula unraid option... (data lost in this post as I've shared my template and config data before... including the extra option to add the disk drive I have moved away from Unraid and now run Debian due to other issues, so I wish you luck... all I can say is go back to post 1 and move forward; your issues may have been addressed already...

I'm curently waiting on more info form plex regaridng teh sql chagnes to fts and chuck pa on how we wnat to hanle some version of plex ftl sql database chagnes... https://github.com/ChuckPa/DBRepair Due to changes in PMS beginning with PMS 1.43.0, DBRepair.sh, as currently written, is incompatible with PMS 1.43.0 and above. It manifests as FTS "Malformed inverted index" errors. Because of this, major changes are coming. DBRepair.sh -- As it exists in the main repo, has been patched to disable FTS repair. Existing 1.17.x packages have been taken down for everyone's safety You may safely use it for normal optimization but it not address any FTS issues. DBRepair.sh - NEEDS PATCHING.Falsely reports "Malformed inverted index" and marks the DB as damaged. This is the incompatibility showing itself. This will be worked around. Changes in Plex's SQLite version require major changes to address the incompatibilities being seen between 1.42.2 & 1.43.x Schema changes in PMS require DBRepair perform its tasks differently. I have temporarily patched the main DBRepair.sh to disable FTS (Text Search) repairs and removed the posted packages for everyone's safety. While I have some ideas on how to go about it I'm ultimately waiting on chuck PA and what they do per Plex forum... https://forums.plex.tv/t/dbrepair-development/822684/846 I do not have plans to update and/change this untill we get word on how plex / sql should handle these errors...

It is important to back up your flash drive... From the original USB copy, copy off the config folder and keep it safe. See docs: https://docs.unraid.net/unraid-os/system-administration/maintain-and-update/changing-the-flash-device/ Otherwise, go manual: The config folder on the OG usb is everything from license key, settings, disk layout, plugins etc... Due to new license structure, you may need to download and use an older version first: https://docs.unraid.net/unraid-os/download_list/ On the new USB flash device, format it and make a new up-to-date Unraid USB. The creator tool can do this. https://docs.unraid.net/unraid-os/getting-started/set-up-unraid/create-your-bootable-media/ Once created, copy your backed-up config folder to the newly created Unraid USB, replacing all files on the new usb and boot Unraid. ONLY THE CONFIG FOLDER! see also Unraid docs: https://docs.unraid.net/unraid-os/troubleshooting/common-issues/boot-and-startup-failures/ for continued issues, contact support, especially for usb licensing changes.

yep, this appears to be fixed now. thank you.

https://product.unraid.net/b/unraid-os-feature-requests?bucket_id=17494 appears to be broken... I used to go to the Feature request to review others' items, vote, and check on previous replies... It's frustrating when the Unraid forums don't work as intended or items get stripped... If trying to block users, that's fine, but don't remove their own posted content! (not saying people are being blocked...) Regardless, read or other access appears broken in bug reports...

IDK why immich became such a mess. duplication of postgress same tag and other... The OG forum page... https://forums.unraid.net/topic/146106-immich-docker-self-hosted-google-photos-setup yes ther are ways form docker volume shanagins to offical imach settings with the storage tempate settings... see offical docs...https://docs.immich.app/administration/storage-template/

Everything I have set up and use is official from Immich GitHub and per there documentations... the manufacturer behind Immich wants unraid users to use Compose; that is the official setup. The CA AIO, as you describe, reuses Space Invaders and the official Immich machine learning and Immich server bundled in 1 container... They are offical dockers per immich. see offical documentation https://docs.immich.app/install/unraid/

... Does no one search or read the forums... Offical Support for Immich: https://forums.unraid.net/topic/146106-immich-docker-self-hosted-google-photos-setup Guides were out a long while... CA: https://bmartino1.weebly.com/immich-on-unraid-ca-docker.html Compose: https://bmartino1.weebly.com/immich-on-unraid-docker-compose-guide.html I also have the apps in the CA under my repository bmartino1 https://ca.unraid.net/apps?q=bmartino which use the Space Invaders template for immich via ca...