kjclark23

I had to install the production branch driver, which is 580 vs 590. Doesn't look like my card will be supported in future.

Just to update, I edit my Emby docker and got rid of the extra parameters "--runtime=Nvidia" and the docker runs fine. I got to put the extra parameter back and it fails again. Now I'm trying to figure out what causes this to happen. Hoping it's not having to wait for another driver update.

I deleted the vDisk and created a new one. Went to add the Dockers and most ran successfully, but some didn't. I noticed that it has something to do with Nvidia. I copied some of log for the Emby docker below. But each docker that uses the video card fails their docker build. docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running prestart hook #0: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy' nvidia-container-cli: initialization error: nvml error: driver not loaded: unknown. The command failed. So I'm guessing this is an Nvidia driver issue now. I checked and I have the lastest driver. gamingnas-diagnostics-20251222-1403.zip

I updated from 7.2.2 to 7.2.3 today. First, the update wasn't smooth, as my server froze when rebooting. I was able to see that it was stuck in the loading screen where you can enter the bios. After shutting off and turning back on, I was able to see Unraid going through the rest of the update. The server booted back up, but now I have Dockers not starting, giving "Execution Error". Wanting to post this in case there's something going on with the update. It of course could be my issue. I also have no clue what to do here. I did a scrub, with no errors (not sure if this even helps). I had a docker I didn't regularly use do this before, I just waited and it corrected itself. However, I don't want to wait for these Dockers since they're Emby and Plex, which gets used regularly. Any next steps would be appreciated. Posted diagnostics. gamingnas-diagnostics-20251222-1233.zip

Thank you! Back up again. I will backup and reformat it.

All of a sudden my server crashed. I had to manually restart it and now my cahce drive is back to unmountable again. Ugh. I tried doing what you said before with "btrfs rescure..." but that resulted in "No valid Btrfs found on /dev/sdr1 ERROR: could not open ctree" Posting diagnostics. Starting to worry I have a hardware problem. gamingnas-diagnostics-20251005-2115.zip

Many thanks. The scrub came back with no errors. Now I just need to restore my previous containers. Thanks for holding my hand!

I disabled the docker and deleted the newer image file. I ran the scrub and got this output UUID: 6738fddc-e7e7-4acf-bf7a-c650d6ca514a Scrub started: Thu Oct 2 13:12:27 2025 Status: finished Duration: 0:07:09 Total to scrub: 455.63GiB Rate: 1.03GiB/s Error summary: csum=8 Corrected: 0 Uncorrectable: 8 Unverified: 0I then went to enable the docker again and I get Docker Service failed to start. Attached more diagnostics. gamingnas-diagnostics-20251002-1325.zip

I'm seeing I have two docker image files, caused by Unraid creating a new one when not finding the old one. I assume I should just delete the newly created one to fix this? Also, should I disable or enable the docker before I do this?

Awesome, that got them recognized now. And my appdata is back since they lived on my cache drive. However, my docker containers are still gone, not sure what happened to them. I believe I should be able to recover those, forgetting how. Attached diagnostics after starting the array. gamingnas-diagnostics-20251002-1228.zip

I just want to make sure I understand the steps. Assign the pool devices back Type "btrfs rescue zero-log /dev/sdr1" in the terminal Start array Is this right?

All my docker containers suddenly disappeared and noticed my cache drive was Unmountable: Unsupported or no file system. I have tried stopping the array and removing the cache drives (pool of 2) to start the array but then I get "Wrong Pool State Cache too many wrong or missing devices". I have attached diagnostics. I'm hitting a brick wall. gamingnas-diagnostics-20251002-1102.zip

I went and changed the /storage back to "ro" and MakeMKV is back to stating it is in read only mode and I get an error. I'm finally seeing, thanks to your post, that MakeMKV is somehow defaulting to using the /storage for its output. Not sure how this automatically happened, but I changed it to /output which has "rw". Seems to be working now, really sorry to waste your time on this. I will always be learning with this stuff.

Do I understand docker volume mapping? I can't really explain it myself, so no. I didn't think I would want the /storage to "rw", but changed it to see if the docker would then work. For the path, I have it mapped within MakeMKV GUI to send to just /storage (without /user). I guess I needed to change this in the settings too. I didn't originally have it this way, use to work for a long time. MakeMKV gave me a pop-up stating that the path doesn't exist, which I thought was odd. So I changed it in the GUI to get it working. Not sure if this has anything to do with updating to Unraid 7.

I see this now. This is interesting. Can these settings get changed on their own? I did not change this and wonder why it didn't work, lol. Curious how it has been working for such a long time. But I changed the /storage to "rw" and fixed the /mnt to /mnt/user. I'm really not sure if the /mnt was always like that or if I had the default (which I usually keep). Just really not sure how this even happened.

I think this is what you're asking for a docker run: docker run -d --name='MakeMKV' --net='bridge' --pids-limit 2048 --privileged=true -e TZ="America/New_York" -e HOST_OS="Unraid" -e HOST_HOSTNAME="gamingNAS" -e HOST_CONTAINERNAME="MakeMKV" -e 'MAKEMKV_KEY'='UNSET' -e 'AUTO_DISC_RIPPER'='0' -e 'AUTO_DISC_RIPPER_EJECT'='0' -e 'AUTO_DISC_RIPPER_PARALLEL_RIP'='0' -e 'AUTO_DISC_RIPPER_BD_MODE'='mkv' -e 'AUTO_DISC_RIPPER_FORCE_UNIQUE_OUTPUT_DIR'='0' -e 'AUTO_DISC_RIPPER_NO_GUI_PROGRESS'='0' -e 'USER_ID'='99' -e 'GROUP_ID'='100' -e 'UMASK'='000' -e 'APP_NICENESS'='' -e 'DISPLAY_WIDTH'='1280' -e 'DISPLAY_HEIGHT'='768' -e 'SECURE_CONNECTION'='0' -e 'X11VNC_EXTRA_OPTS'='' -e 'AUTO_DISC_RIPPER_MAKEMKV_PROFILE'='' -e 'AUTO_DISC_RIPPER_INTERVAL'='5' -e 'AUTO_DISC_RIPPER_MIN_TITLE_LENGTH'='' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:5800]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/jlesage/docker-templates/master/jlesage/images/makemkv-icon.png' -p '7806:5800/tcp' -p '7906:5900/tcp' -v '/mnt':'/storage':'ro' -v '/mnt/user/Media/':'/output':'rw' -v '/mnt/user/appdata/MakeMKV':'/config':'rw' --device /dev/sr0 --device /dev/sg0 'jlesage/makemkv' f5bbc4047bfa80f8ea7803244fa6ab07170001a1813f8cc0acbda17c52467dfc The command finished successfully! The error I get in MakeMKV is: Error 'Posix error - Read-only file system' occurred while creating '/storage/user/Media/Rip Here First/Rankin_Bass Holiday Favorites.mkv' Failed to save title 0 to file /storage/user/Media/Rip Here First/Rankin_Bass Holiday Favorites.mkv 0 titles saved, 1 failed I have had this MakeMKV Docker setup for sometime now, so this is a sudden change that I'm not sure what happened. Started when having the cache drive issues.

When I go to use a docker (MakeMKV) it fails to write anything due to Read-Only status. Scrub results: UUID: 6738fddc-e7e7-4acf-bf7a-c650d6ca514a Scrub started: Wed Jan 15 09:03:31 2025 Status: finished Duration: 0:04:12 Total to scrub: 261.67GiB Rate: 1.04GiB/s Error summary: no errors found

Ok, good thing I waited... Here's the new diagnostics gamingnas-diagnostics-20250114-2316.zip

I spoke too soon. It was doing a balance but my screen for some reason took a bit to show that. Everything with the cache went to normal. I'm still having issues with read-only and not really sure how to correct that. Is there where I go to the New Permissions under Tools?

Replaced Cache 2, when starting the array back up I got this warning message... Warning [GAMINGNAS] - Cache pool BTRFS missing device(s) Samsung_SSD_860_EVO_500GB_S3Z1NB0M257300F (sdn) Which I thought was odd because that is the drive that wasn't removed. I later got this... Warning [GAMINGNAS] - pool BTRFS too many profiles (You can ignore this warning when a pool balance operation is in progress) Samsung_SSD_860_EVO_500GB_S3Z1NB0M257300F (sdn) So I'm guessing I just need to give it a minute. Not really sure, but posting new diagnostics. Really glad I had one of these 500GB SSDs ready to be used. gamingnas-diagnostics-20250114-2145.zip

I go to run the extended self test and it completes quickly stating Read Failure.

Performed another scrub and here's those results:: UUID: 6738fddc-e7e7-4acf-bf7a-c650d6ca514a Scrub started: Mon Jan 13 09:27:47 2025 Status: finished Duration: 0:04:42 Total to scrub: 257.49GiB Rate: 935.08MiB/s Error summary: read=2000 Corrected: 1998 Uncorrectable: 2 Unverified: 0 Also attached new diagnostics. gamingnas-diagnostics-20250113-0935.zip

I'm not sure how to really do this. I looked over the syslog and that's a lot of red going on... But I'm not sure I see what files are corrupt. I'm also not sure how to delete/restore them. Since this is due to a failing SSD (I think) in the cache pool, could I just replace that the drive to get by all this?

Ran the Scrub and here's the results: UUID: 6738fddc-e7e7-4acf-bf7a-c650d6ca514a Scrub started: Fri Jan 10 14:12:05 2025 Status: finished Duration: 0:12:49 Total to scrub: 258.77GiB Rate: 344.58MiB/s Error summary: read=60272 Corrected: 59897 Uncorrectable: 375 Unverified: 0

My read errors on Disk 1 have returned to normal after updated to Unraid 7.0.0, which required the restart. However, I cannot write to my shares as they are in read only mode. I went through the logs a couple times but not seeing anything that I can pick up on. Posting diagnostics if anyone could help here. I do know that one of my cache drives has smart health problems, but I haven't replaced it yet. I figured since I have that one in there as a backup drive that it wouldn't matter too much. But I do plan to replace it, whenever I can. Not sure if that's causing the issue or not. gamingnas-diagnostics-20250110-1133.zip