May 15, 20251 yr Yeah, unfortunately most of my disks are 4k and they all seem to come with at least two versions, one with and one without Chapters. Im just going to manually rip instead of using autoripper, not too much time-savings anyways
May 16, 20251 yr Hi, I need to understand what to do: I installed MakeMKV and plug-in my external BD drive through USB 3.0 but MakeMKV does not recognize any drives available... I added /dev/sr0 but I do not see in the logs any errors i norder to find the second device to be added What do I have to do? Edited May 16, 20251 yr by Lybra85
May 16, 20251 yr Author 3 hours ago, Lybra85 said: Hi, I need to understand what to do: I installed MakeMKV and plug-in my external BD drive through USB 3.0 but MakeMKV does not recognize any drives available... I added /dev/sr0 but I do not see in the logs any errors i norder to find the second device to be added What do I have to do? Can you share the container log ?
May 16, 20251 yr Author 1 minute ago, Lybra85 said: Sorry I am from mobile phone We need the full log from the beginning. If you can't scroll up, you can get the log from the terminal by executing the command "docker logs MakeMKV".
May 16, 20251 yr Thanks to your advice I found in the full log the second device....thank you very much now it's working
May 17, 20251 yr I have a weird issue that when I insert a disc I receive an error message that no disc has been inserted. The disc looks alsmost flawless and works perfectly on my windows computer. The drive also gets detected inside the container ... Anyone got an idea what might be the issue ?
May 18, 20251 yr Author 15 hours ago, matuopm said: I have a weird issue that when I insert a disc I receive an error message that no disc has been inserted. The disc looks alsmost flawless and works perfectly on my windows computer. The drive also gets detected inside the container ... Anyone got an idea what might be the issue ? Do you get this problem for any discs ?
May 18, 20251 yr i tested one audio cd and one dvd so far. As a test I put the drive into a windows vm by "iommu grouping" the SATA controller and pass it to the VM. Inside the windows vm both discs were detected flawlessly. I have a suspicion that I might made a mistake by forwarding the drive to the container. I used this method I saw in youtube: (see screenshot) it seems the number behind SG has changed since the last reboot. I test again. Still... no disc ... In the log I can find this: Quote Debug log started at Sun May 18 11:31:27 2025 , written by MakeMKV v1.18.1 linux(x64-release) 001005:0000 MakeMKV v1.18.1 linux(x64-release) gestartet 001004:0000 Debug-Aufzeichnung eingeschaltet. Aufzeichnung wird gespeichert als file:///config/MakeMKV_log.txt Using 6144KB for read cache. Network access is ENABLED, CURL version 7.88.1/OpenSSL/3.0.15/1.52.0 (x86_64-pc-linux-gnu) , proxy server not set. 001003:0020 DEBUG: Code 0 at *s,+4m-r">yFd&'k/Y<sa&:29393631 No SDF v098: HL-DT-ST_BD-RE_BU40N_1.05_212404231347_MO2OCB94752 SDF id v098: HL-DT-ST_BD-RE_BU40N_1.05_212404231347_MO2OCB94752 001003:0020 DEBUG: Code 1 at [U=QLy!_;2fC'+t^1R>#<:121265062 005010:0000 Das Öffnen der Disk schlug fehl Application exited at Sun May 18 11:31:27 2025 Opening the disc failed: 005010:0000 Das Öffnen der Disk schlug fehl Edited May 18, 20251 yr by matuopm
May 19, 20251 yr 16 hours ago, matuopm said: i tested one audio cd and one dvd so far. As a test I put the drive into a windows vm by "iommu grouping" the SATA controller and pass it to the VM. Inside the windows vm both discs were detected flawlessly. I have a suspicion that I might made a mistake by forwarding the drive to the container. I used this method I saw in youtube: (see screenshot) it seems the number behind SG has changed since the last reboot. I test again. Still... no disc ... In the log I can find this: Opening the disc failed: 005010:0000 Das Öffnen der Disk schlug fehl review older post on this forum... Explained mutiple time here.. review:
May 20, 20251 yr Author On 5/18/2025 at 7:03 AM, matuopm said: i tested one audio cd and one dvd so far. As a test I put the drive into a windows vm by "iommu grouping" the SATA controller and pass it to the VM. Inside the windows vm both discs were detected flawlessly. I have a suspicion that I might made a mistake by forwarding the drive to the container. I used this method I saw in youtube: (see screenshot) it seems the number behind SG has changed since the last reboot. I test again. Still... no disc ... In the log I can find this: Opening the disc failed: 005010:0000 Das Öffnen der Disk schlug fehl Review the full container log (docker logs MakeMKV) and make sure everything is fine for the detected drive. Also, I would recommend that you temporarily switch MakeMKV to English so that we can have a better understanding of the log it provides.
May 23, 20251 yr On 5/19/2025 at 6:00 AM, bmartino1 said: review older post on this forum... Explained mutiple time here.. review: Well first of all iam not very experienced with how linux is handling stuff like this.I have a Hitachi-LG BU40N drive which is a blu ray drive that also can read DVDs and normal Audio CDs.Maybe you overlooked it but the drive was reading the discs I tried without any issues when I passed the drive to a Windows VM.I executed the commands I saw in your post so here are the outputs:root@mServer:~# ls /dev/{cdrom,sr*,sg*}/dev/cdrom@ /dev/sg1 /dev/sg11 /dev/sg13 /dev/sg15 /dev/sg17 /dev/sg19 /dev/sg4 /dev/sg6 /dev/sg8 /dev/sr0/dev/sg0 /dev/sg10 /dev/sg12 /dev/sg14 /dev/sg16 /dev/sg18 /dev/sg3 /dev/sg5 /dev/sg7 /dev/sg9root@mServer:~# lshw -C disk*-disk:0description: ATA Diskproduct: ST18000NM000J-2Tphysical id: 0.6.0bus info: scsi@12:0.6.0logical name: /dev/sdjversion: SN02serial: WR504920size: 16TiB (18TB)capabilities: 7200rpm gpt-1.00 partitioned partitioned:gptconfiguration: ansiversion=6 guid=2f8df12c-bfed-4ec2-a43d-fda052642567 logicalsectorsize=512 sectorsize=4096*-disk:1description: ATA Diskproduct: ST18000NM000J-2Tphysical id: 0.7.0bus info: scsi@12:0.7.0logical name: /dev/sdkversion: SN02serial: WR500AB7size: 16TiB (18TB)capabilities: 7200rpm gpt-1.00 partitioned partitioned:gptconfiguration: ansiversion=6 guid=a79b79c3-11a0-4353-8ce3-d24a2d5b0a75 logicalsectorsize=512 sectorsize=4096*-disk:2description: ATA Diskproduct: ST18000NM000J-2Tphysical id: 0.8.0bus info: scsi@12:0.8.0logical name: /dev/sdlversion: SN02serial: WR501B6Lsize: 16TiB (18TB)capabilities: 7200rpm gpt-1.00 partitioned partitioned:gptconfiguration: ansiversion=6 guid=3cf43bb8-14fe-48f6-8c5a-fd0f6cd599fa logicalsectorsize=512 sectorsize=4096*-disk:3description: ATA Diskproduct: ST18000NM000J-2Tphysical id: 0.9.0bus info: scsi@12:0.9.0logical name: /dev/sdmversion: SN02serial: ZR561S99size: 16TiB (18TB)capabilities: 7200rpm gpt-1.00 partitioned partitioned:gptconfiguration: ansiversion=6 guid=cc88ca3e-a73c-42a6-b3e0-99ed1179af07 logicalsectorsize=512 sectorsize=4096*-disk:4description: ATA Diskproduct: ST18000NM000J-2Tphysical id: 0.a.0bus info: scsi@12:0.10.0logical name: /dev/sdnversion: SN04serial: ZR5FDB0Qsize: 16TiB (18TB)capabilities: 7200rpm gpt-1.00 partitioned partitioned:gptconfiguration: ansiversion=6 guid=bfbcd991-9d91-4965-a741-e655ca4f7018 logicalsectorsize=512 sectorsize=4096*-disk:5description: ATA Diskproduct: Samsung SSD 870physical id: 0.b.0bus info: scsi@12:0.11.0logical name: /dev/sdoversion: 3B6Qserial: S75CNX0X339189Zsize: 931GiB (1TB)capacity: 931GiB (1TB)capabilities: partitioned partitioned:dosconfiguration: ansiversion=6 logicalsectorsize=512 sectorsize=512 signature=f426d01c*-disk:6description: ATA Diskproduct: WD Green 2.5 2TBvendor: Western Digitalphysical id: 0.c.0bus info: scsi@12:0.12.0logical name: /dev/sdpversion: 00WDserial: 25074T4A0F10size: 1863GiB (2TB)capacity: 1863GiB (2TB)capabilities: partitioned partitioned:dosconfiguration: ansiversion=6 logicalsectorsize=512 sectorsize=512*-disk:7description: ATA Diskproduct: ST18000NM000J-2Tphysical id: 0.d.0bus info: scsi@12:0.13.0logical name: /dev/sdqversion: SN02serial: ZR5BN2REsize: 16TiB (18TB)capabilities: 7200rpm gpt-1.00 partitioned partitioned:gptconfiguration: ansiversion=6 guid=8916f811-cb75-4b36-a4ba-aefe37c4fe8c logicalsectorsize=512 sectorsize=4096*-disk:8description: ATA Diskproduct: ST18000NM000J-2Tphysical id: 0.0.0bus info: scsi@12:0.0.0logical name: /dev/sddversion: SN01serial: ZR52J0ZDsize: 16TiB (18TB)capabilities: 7200rpm gpt-1.00 partitioned partitioned:gptconfiguration: ansiversion=6 guid=fc8692cc-2f96-4f3d-96e1-ebe657dcce09 logicalsectorsize=512 sectorsize=4096*-disk:9description: ATA Diskproduct: ST18000NM000J-2Tphysical id: 0.1.0bus info: scsi@12:0.1.0logical name: /dev/sdeversion: SN02serial: WR504EQZsize: 16TiB (18TB)capabilities: 7200rpm gpt-1.00 partitioned partitioned:gptconfiguration: ansiversion=6 guid=2c082ecd-7271-4e7b-8201-92bf9af945c8 logicalsectorsize=512 sectorsize=4096*-disk:10description: ATA Diskproduct: ST18000NM000J-2Tphysical id: 0.2.0bus info: scsi@12:0.2.0logical name: /dev/sdfversion: SN02serial: ZR53Y4DWsize: 16TiB (18TB)capabilities: 7200rpm gpt-1.00 partitioned partitioned:gptconfiguration: ansiversion=6 guid=45318839-2de1-422e-b717-a8426fc07e5a logicalsectorsize=512 sectorsize=4096*-disk:11description: ATA Diskproduct: ST18000NM000J-2Tphysical id: 0.3.0bus info: scsi@12:0.3.0logical name: /dev/sdgversion: SN02serial: ZR5CMYYTsize: 16TiB (18TB)capabilities: 7200rpm gpt-1.00 partitioned partitioned:gptconfiguration: ansiversion=6 guid=46452ea4-81f8-4a28-83d3-6c1ed8284c37 logicalsectorsize=512 sectorsize=4096*-disk:12description: ATA Diskproduct: ST18000NM000J-2Tphysical id: 0.4.0bus info: scsi@12:0.4.0logical name: /dev/sdhversion: SN01serial: ZR52HZR8size: 16TiB (18TB)capabilities: 7200rpm gpt-1.00 partitioned partitioned:gptconfiguration: ansiversion=6 guid=9f388617-cc81-47b2-be1c-e08bd52c3401 logicalsectorsize=512 sectorsize=4096*-disk:13description: ATA Diskproduct: ST18000NM000J-2Tphysical id: 0.5.0bus info: scsi@12:0.5.0logical name: /dev/sdiversion: SN02serial: WR500JJGsize: 16TiB (18TB)capabilities: 7200rpm gpt-1.00 partitioned partitioned:gptconfiguration: ansiversion=6 guid=6a88ec13-94e7-40ec-83f6-2cd201cd9a30 logicalsectorsize=512 sectorsize=4096*-namespace:0description: NVMe diskphysical id: 0logical name: hwmon4*-namespace:1description: NVMe diskphysical id: 2logical name: /dev/ng0n1*-namespace:2description: NVMe diskphysical id: 1bus info: nvme@0:1logical name: /dev/nvme0n1size: 465GiB (500GB)capabilities: partitioned partitioned:dosconfiguration: logicalsectorsize=512 sectorsize=512 wwid=nvme.c0a9-323233384536363939333130-4354353030503353534438-00000001*-diskdescription: SCSI Diskproduct: File-Stor Gadgetvendor: Linuxphysical id: 0.0.0bus info: scsi@0:0.0.0logical name: /dev/sdaversion: 0510size: 21GiB (22GB)capabilities: removableconfiguration: ansiversion=2 logicalsectorsize=512 sectorsize=512*-mediumphysical id: 0logical name: /dev/sdasize: 21GiB (22GB)*-cdromdescription: DVD-RAM writerproduct: BD-RE BU40Nvendor: HL-DT-STphysical id: 0.0.0bus info: scsi@8:0.0.0logical name: /dev/cdrlogical name: /dev/cdr0logical name: /dev/cdromlogical name: /dev/cdrom0logical name: /dev/cdrwlogical name: /dev/cdrw0logical name: /dev/cdwriterlogical name: /dev/cdwriter0logical name: /dev/dvdlogical name: /dev/dvd0logical name: /dev/dvdrlogical name: /dev/dvdr0logical name: /dev/dvdrwlogical name: /dev/dvdrw0logical name: /dev/dvdwriterlogical name: /dev/dvdwriter0logical name: /dev/sr0version: 1.05capabilities: removable audio cd-r cd-rw dvd dvd-r dvd-ramconfiguration: ansiversion=5 status=nodisc*-namespace:0description: NVMe diskphysical id: 0logical name: hwmon1*-namespace:1description: NVMe diskphysical id: 2logical name: /dev/ng1n1*-namespace:2description: NVMe diskphysical id: 1bus info: nvme@1:1logical name: /dev/nvme1n1size: 1863GiB (2TB)capabilities: partitioned partitioned:dosconfiguration: logicalsectorsize=512 sectorsize=512 wwid=eui.002538435143b5a8*-namespace:0description: NVMe diskphysical id: 0logical name: hwmon3*-namespace:1description: NVMe diskphysical id: 2logical name: /dev/ng2n1*-namespace:2description: NVMe diskphysical id: 1bus info: nvme@2:1logical name: /dev/nvme2n1size: 465GiB (500GB)capabilities: partitioned partitioned:dosconfiguration: logicalsectorsize=512 sectorsize=512 wwid=nvme.c0a9-323233384536363939324633-4354353030503353534438-00000001*-disk:0description: ATA Diskproduct: CT2000MX500SSD1physical id: 0bus info: scsi@11:0.0.0logical name: /dev/sdrversion: 045serial: 2245E684AE89size: 1863GiB (2TB)capabilities: partitioned partitioned:dosconfiguration: ansiversion=5 logicalsectorsize=512 sectorsize=4096 signature=f426d026*-disk:1description: ATA Diskproduct: CT2000MX500SSD1physical id: 1bus info: scsi@10:0.0.0logical name: /dev/sdcversion: 045serial: 2245E684AF5Csize: 1863GiB (2TB)capabilities: partitioned partitioned:dosconfiguration: ansiversion=5 logicalsectorsize=512 sectorsize=4096 signature=f426d024*-namespace:0description: NVMe diskphysical id: 0logical name: hwmon2*-namespace:1description: NVMe diskphysical id: 2logical name: /dev/ng3n1*-namespace:2description: NVMe diskphysical id: 1bus info: nvme@3:1logical name: /dev/nvme3n1size: 1863GiB (2TB)capabilities: partitioned partitioned:dosconfiguration: logicalsectorsize=512 sectorsize=512 wwid=eui.002538435143b5a9*-diskdescription: SCSI Diskproduct: Cruzer Fitvendor: SanDisk'physical id: 0.0.0bus info: scsi@1:0.0.0logical name: /dev/sdbversion: 1.00serial: 03019714111221120739size: 14GiB (15GB)capabilities: removableconfiguration: ansiversion=6 logicalsectorsize=512 sectorsize=512*-mediumphysical id: 0logical name: /dev/sdbsize: 14GiB (15GB)capabilities: partitioned partitioned:dosI put all the devices from the first output into the container like this: (see screenshot)here is the MakeMKV_log.txt file:Debug log started at Fri May 23 16:30:30 2025 , written by MakeMKV v1.18.1 linux(x64-release)001005:0000 MakeMKV v1.18.1 linux(x64-release) started001004:0000 Debug logging enabled, log will be saved as file:///config/MakeMKV_log.txtUsing 6144KB for read cache.Network access is ENABLED, CURL version 7.88.1/OpenSSL/3.0.15/1.52.0 (x86_64-pc-linux-gnu) , proxy server not set.001003:0020 DEBUG: Code 0 at *s,+4m-r">yFd&'k/Y<sa&:29393631No SDF v098: HL-DT-ST_BD-RE_BU40N_1.05_212404231347_MO2OCB94752SDF id v098: HL-DT-ST_BD-RE_BU40N_1.05_212404231347_MO2OCB94752001003:0020 DEBUG: Code 1 at [U=QLy!_;2fC'+t^1R>#<:121265062005010:0000 Failed to open discApplication exited at Fri May 23 16:30:31 2025I hope this somehow helps. Let me know if you need any informations. Iam also on the discord if you guys want me to share my screen or dm meold Discord ID matuopm#8951 Edited May 23, 20251 yr by matuopm
May 25, 20251 yr Author Note that there is no need to pass all these devices to the container. In your case, according to a previous screenshot, only /dev/sr0 and /dev/sg2 are needed (the ones associated your drive).You said that the drive was reading the discs under Windows. I assume you also used MakeMKV ?Could you share the output of "docker logs MakeMKV" ?
July 23, 2025Jul 23 I have multiple optical drives connected to my UnRaid server. Right now, I have separate instances of MakeMKV dockers set up, one for each optical drive. This works with no issues. However, is there a way to get one docker instance of MakeMKV to see multiple optical drives? I could then select the drive I want to use via the drop-down menu in MakeMKV, similar to how the Windows version of MakeMKV works when I have multiple optical drives connected to my Windows device. I tried adding additional device parameters for the additional optical drives to the docker container settings (the same ones I use in my separate instances of MakeMKV), but that didn't seem to work. Any help would be appreciated.Thanks! Edited July 23, 2025Jul 23 by Rojma
July 23, 2025Jul 23 21 hours ago, Rojma said:I have multiple optical drives connected to my UnRaid server. Right now, I have separate instances of MakeMKV dockers set up, one for each optical drive. This works with no issues. However, is there a way to get one docker instance of MakeMKV to see multiple optical drives? I could then select the drive I want to use via the drop-down menu in MakeMKV, similar to how the Windows version of MakeMKV works when I have multiple optical drives connected to my Windows device. I tried adding additional device parameters for the additional optical drives to the docker container settings (the same ones I use in my separate instances of MakeMKV), but that didn't seem to work. Any help would be appreciated.Thanks!Never mind. I tried it again and it worked. Not sure what I did wrong the first time.
August 11, 2025Aug 11 Any one have any suggestions or ideas on how to set the date back to July? It seems like currently you can't purchase a key and the beta key has not been updated.
August 28, 2025Aug 28 On 8/11/2025 at 2:49 AM, Lioncat55 said:Any one have any suggestions or ideas on how to set the date back to July? It seems like currently you can't purchase a key and the beta key has not been updated.Someone says the new key was posted on MakeMKV forum but its SOOOOOOOOOOOOO slow I am dying of old age waiting for the search page to loadhttps://forum.makemkv.com/forum/viewtopic.php?f=5&t=1053 Edited August 28, 2025Aug 28 by methanoid
August 29, 2025Aug 29 Author 23 hours ago, methanoid said:Someone says the new key was posted on MakeMKV forum but its SOOOOOOOOOOOOO slow I am dying of old age waiting for the search page to loadhttps://forum.makemkv.com/forum/viewtopic.php?f=5&t=1053Access is ok for me now.Note that you don't need to enter the key yourself, the container takes care of that.
September 12, 2025Sep 12 I wanted to report an error that I am seeing with this docker version of MakeMKV. When ripping the 4K UHD disc of Elio, I got the following error messages in the MakeMKV log window:FFMPEG_ERROR: FFDEC000: [truehd @ 0x147b99b5fb40] No restart header present in substream 1.FFMPEG_ERROR: FFDEC000: [truehd @ 0x147b9990be40] No restart header present in substream 1.FFMPEG_ERROR: FFDEC000: [truehd @ 0x147b987a8a40] No restart header present in substream 1....The error repeated 103 times, with the 0x code being different most times (although sometimes it would repeat once or twice). The ripping job though appeared to finish without issue.I was not trying to transcode any audio to FLAC or other format - the audio was being copied as is. I tried with both the Default profile and a Custom profile (that just changes something with Forced subtitles) and the error occurred both times.I used MakeMKV on Windows 11 to rip the same disc and did not get the above errors. I also tried the binhex docker version of MakeMKV on the same Unraid server where I got the above errors and again didn't get the above errors.I searched in the MakeMKV forums for the above errors, and it seems like the problem might be related to the version of ffmpeg, and upgrading the version of ffmpeg might resolve the error. Would it be possible to update the docker image with a newer version of ffmpeg to see if it resolves the error? Edited September 12, 2025Sep 12 by Rojma
September 14, 2025Sep 14 Author On 9/12/2025 at 7:52 PM, Rojma said:I wanted to report an error that I am seeing with this docker version of MakeMKV. When ripping the 4K UHD disc of Elio, I got the following error messages in the MakeMKV log window:FFMPEG_ERROR: FFDEC000: [truehd @ 0x147b99b5fb40] No restart header present in substream 1.FFMPEG_ERROR: FFDEC000: [truehd @ 0x147b9990be40] No restart header present in substream 1.FFMPEG_ERROR: FFDEC000: [truehd @ 0x147b987a8a40] No restart header present in substream 1....The error repeated 103 times, with the 0x code being different most times (although sometimes it would repeat once or twice). The ripping job though appeared to finish without issue.I was not trying to transcode any audio to FLAC or other format - the audio was being copied as is. I tried with both the Default profile and a Custom profile (that just changes something with Forced subtitles) and the error occurred both times.I used MakeMKV on Windows 11 to rip the same disc and did not get the above errors. I also tried the binhex docker version of MakeMKV on the same Unraid server where I got the above errors and again didn't get the above errors.I searched in the MakeMKV forums for the above errors, and it seems like the problem might be related to the version of ffmpeg, and upgrading the version of ffmpeg might resolve the error. Would it be possible to update the docker image with a newer version of ffmpeg to see if it resolves the error?Can you try the image jlesage/makemkv:ffmpeg7 to see if you still get the error ?
September 16, 2025Sep 16 On 9/14/2025 at 2:49 PM, Djoss said:Can you try the image jlesage/makemkv:ffmpeg7 to see if you still get the error ?Thank you for the response @Djoss. I updated to the suggested image and confirmed that the error no longer occurs. Thanks for the fix. Should I keep the image as jlesage/makemkv:ffmpeg7?
September 16, 2025Sep 16 Author 24 minutes ago, Rojma said:Thank you for the response @Djoss. I updated to the suggested image and confirmed that the error no longer occurs. Thanks for the fix. Should I keep the image as jlesage/makemkv:ffmpeg7?Thank you for confirming that the new FFmpeg version fixes the problem. I will release a new image with the fix, so no need to keep using jlesage/makemkv:ffmpeg7.
October 2, 2025Oct 2 Author 1 hour ago, Rojma said:FYI version 1.18.2 of MakeMKV has been released.Thank you! I will update the image.
October 2, 2025Oct 2 FYI version 1.18.2 of MakeMKV has been released.Just now, Djoss said:Thank you! I will update the image.Thanks!
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.