Interstellar 4K UHD Bluray
Interstellar 4K UHD Bluray
Hello everyone! I recently got myself the interstellar 4k uhd bluray. So I wanted to rip it to watch it on my projector in full quality but for some reason makemkv says that it is unable to open the disc. I have a Asus BW16D1HT and tried it once on 3.01MK (i think it was) and after a upgrade on the newest 3.10MK version with makemkv version 1.18.3
So, did anyone else who had this disc encounter the same issue and maybe has a solution to it? I'm still very new to all of this. I also tried ripping Inception (4k UHD Bluray) and that just worked fine and was done after an hour. So it must be something with the disc.
Thanks for helping!
So, did anyone else who had this disc encounter the same issue and maybe has a solution to it? I'm still very new to all of this. I also tried ripping Inception (4k UHD Bluray) and that just worked fine and was done after an hour. So it must be something with the disc.
Thanks for helping!
Re: Interstellar 4K UHD Bluray
Did MakeMKV create a TGZ dump file called something like MKB20_v61_INTERSTELLAR_????.tgz?
If yes, email it to svq@makemkv.com and then wait patiently. However, you could also upload that same TGZ file into (say) OneDrive or Google Drive and thn reply here with a public download link, because this would allow people to try adding your disk to the public KEYDB.cfg file too.
Re: Interstellar 4K UHD Bluray
I tried creating one but it always failed. I think it's just because the disc was for so long in the box and just has some dust on it or fingerprints. I'll "wash" the disc tomorrow and see what happensMrPenguin wrote: ↑Mon Feb 23, 2026 10:05 pmDid MakeMKV create a TGZ dump file called something like MKB20_v61_INTERSTELLAR_????.tgz?
If yes, email it to svq@makemkv.com and then wait patiently. However, you could also upload that same TGZ file into (say) OneDrive or Google Drive and thn reply here with a public download link, because this would allow people to try adding your disk to the public KEYDB.cfg file too.
Re: Interstellar 4K UHD Bluray
Except you don't create a TGZ dump file, MakeMKV does.
Could you at least post some of MakeMKV's log output please? There are many different kinds of "failed" here.
Re: Interstellar 4K UHD Bluray
SO makemkv does not create one. I searched for the logs (/root/.MakeMKV/) and there we no logs and no TGZ for some reason. Is it because I'm using makemkvcon , because I'm on linux...? i can't use the GUI because I don't have/want a dekstop environment.
Re: Interstellar 4K UHD Bluray
A few points:
- Running as "root" is a Bad Idea.
- Really, running as "root" is a Bad Idea.
- makemkvcon works fine when running as a non-root user, so long as it has write access to your BD/UHD drive's /dev/sgX device node.
- I suspect makemkvcon writes its log messages to Standard Output, i.e. the terminal.
- And finally, running as "root" is still a Bad Idea.
Re: Interstellar 4K UHD Bluray
Thanks for the information! I now have a user called player and I tried the same process as before, still the same error and sadly no logs anywhere. The only thing the terminal says is:MrPenguin wrote: ↑Tue Feb 24, 2026 11:41 amA few points:
- Running as "root" is a Bad Idea.
- Really, running as "root" is a Bad Idea.
- makemkvcon works fine when running as a non-root user, so long as it has write access to your BD/UHD drive's /dev/sgX device node.
- I suspect makemkvcon writes its log messages to Standard Output, i.e. the terminal.
- And finally, running as "root" is still a Bad Idea.
MakeMKV v1.18.3 linux(x64-release) gestartet
Das Öffnen der Disk schlug fehl
(in english it says that the process started and the process of opening the disc failed)
And inside the ~/.MakeMKV of the user it only has the update.conf and the private data archive. I hope this helps
Re: Interstellar 4K UHD Bluray
Is this the only UHD/BD disk you own? Does MakeMKV work for any other disk? Does your /dev/ directory contain any sg devices at all, e.g.
Code: Select all
$ ls -als /dev/sg*Code: Select all
$ lsscsi -gRe: Interstellar 4K UHD Bluray
No it is not the only. I also successfully ripped Inception in 4k UHD (Bluray) and it worked just fine. And the drive shows up:MrPenguin wrote: ↑Tue Feb 24, 2026 12:23 pmIs this the only UHD/BD disk you own? Does MakeMKV work for any other disk? Does your /dev/ directory contain any sg devices at all, e.g.andCode: Select all
$ ls -als /dev/sg*Code: Select all
$ lsscsi -g
[0:0:0:0] disk ATA Samsung SSD 860 1B6Q /dev/sda /dev/sg0
[2:0:0:0] cd/dvd ASUS BW-16D1HT 3.10 /dev/sr0 /dev/sg1
[3:0:0:0] disk ATA INTEL SSDSC2KW25 002C /dev/sdb /dev/sg2
0 crw-rw---- 1 root disk 21, 0 24. Feb 09:08 /dev/sg0
0 crw-rw----+ 1 root cdrom 21, 1 24. Feb 09:08 /dev/sg1
0 crw-rw---- 1 root disk 21, 2 24. Feb 09:08 /dev/sg2
So it shouldn't be a problem I think
I guess it is maybe dust that lays on the physical disc itself. Because it was in the box for 2 week because I needed to wait for the drive to arrive. I'll probably clean/wash the drive today and see what happens, because it is mentioned that this bluray is a very sensitive one
Re: Interstellar 4K UHD Bluray
You should be fine so long as your "player" user also belongs to the "cdrom" group. Does your "Interstellar" disk even mount as a filesystem so that you can see its files?BrunoGC13 wrote: ↑Tue Feb 24, 2026 12:32 pmNo it is not the only. I also successfully ripped Inception in 4k UHD (Bluray) and it worked just fine. And the drive shows up:
[0:0:0:0] disk ATA Samsung SSD 860 1B6Q /dev/sda /dev/sg0
[2:0:0:0] cd/dvd ASUS BW-16D1HT 3.10 /dev/sr0 /dev/sg1
[3:0:0:0] disk ATA INTEL SSDSC2KW25 002C /dev/sdb /dev/sg2
0 crw-rw---- 1 root disk 21, 0 24. Feb 09:08 /dev/sg0
0 crw-rw----+ 1 root cdrom 21, 1 24. Feb 09:08 /dev/sg1
0 crw-rw---- 1 root disk 21, 2 24. Feb 09:08 /dev/sg2
Re: Interstellar 4K UHD Bluray
The user belongs to cdrom and it should not be a problem, but trying to mount the disc gives an error and when trying too get its size with blockdev says "No medium found"MrPenguin wrote: ↑Tue Feb 24, 2026 12:38 pmYou should be fine so long as your "player" user also belongs to the "cdrom" group. Does your "Interstellar" disk even mount as a filesystem so that you can see its files?BrunoGC13 wrote: ↑Tue Feb 24, 2026 12:32 pmNo it is not the only. I also successfully ripped Inception in 4k UHD (Bluray) and it worked just fine. And the drive shows up:
[0:0:0:0] disk ATA Samsung SSD 860 1B6Q /dev/sda /dev/sg0
[2:0:0:0] cd/dvd ASUS BW-16D1HT 3.10 /dev/sr0 /dev/sg1
[3:0:0:0] disk ATA INTEL SSDSC2KW25 002C /dev/sdb /dev/sg2
0 crw-rw---- 1 root disk 21, 0 24. Feb 09:08 /dev/sg0
0 crw-rw----+ 1 root cdrom 21, 1 24. Feb 09:08 /dev/sg1
0 crw-rw---- 1 root disk 21, 2 24. Feb 09:08 /dev/sg2
Here the output of mounting the filesystem:
mount: /mnt/bluray: fsconfig() failed: /dev/sr0: Can't open blockdev.
dmesg(1) may have more information after failed mount system call.
So it probably is the disc itself being not "clean". I'll try to wash it and then try it again
Re: Interstellar 4K UHD Bluray
If you cannot even mount a disk then the problem isn't MakeMKVBrunoGC13 wrote: ↑Tue Feb 24, 2026 2:55 pmThe user belongs to cdrom and it should not be a problem, but trying to mount the disc gives an error and when trying too get its size with blockdev says "No medium found"
Here the output of mounting the filesystem:
mount: /mnt/bluray: fsconfig() failed: /dev/sr0: Can't open blockdev.
dmesg(1) may have more information after failed mount system call.
E.g. I have one drive that refuses to mount one specific disk, no matter how much I clean it. Fortunately, that disk still works fine in my other drives.
Re: Interstellar 4K UHD Bluray
Oh ok, I actually have a second UHD friendly drive (external) so I'll try that one and then we'll seeMrPenguin wrote: ↑Tue Feb 24, 2026 3:14 pmIf you cannot even mount a disk then the problem isn't MakeMKVBrunoGC13 wrote: ↑Tue Feb 24, 2026 2:55 pmThe user belongs to cdrom and it should not be a problem, but trying to mount the disc gives an error and when trying too get its size with blockdev says "No medium found"
Here the output of mounting the filesystem:
mount: /mnt/bluray: fsconfig() failed: /dev/sr0: Can't open blockdev.
dmesg(1) may have more information after failed mount system call.. Basically, some drives just don't "like" some disks, and so it's usually a Good Idea to have more than one UHD/BD drive to use, especially for cases like these.
E.g. I have one drive that refuses to mount one specific disk, no matter how much I clean it. Fortunately, that disk still works fine in my other drives.
Re: Interstellar 4K UHD Bluray
I now tried using my asus external UHD friendly drive and it actually came a bit further and created the files in .MakeMKV/ (see google drive link) but it still says failed to open dics at the end.BrunoGC13 wrote: ↑Tue Feb 24, 2026 4:07 pmOh ok, I actually have a second UHD friendly drive (external) so I'll try that one and then we'll seeMrPenguin wrote: ↑Tue Feb 24, 2026 3:14 pmIf you cannot even mount a disk then the problem isn't MakeMKVBrunoGC13 wrote: ↑Tue Feb 24, 2026 2:55 pmThe user belongs to cdrom and it should not be a problem, but trying to mount the disc gives an error and when trying too get its size with blockdev says "No medium found"
Here the output of mounting the filesystem:
mount: /mnt/bluray: fsconfig() failed: /dev/sr0: Can't open blockdev.
dmesg(1) may have more information after failed mount system call.. Basically, some drives just don't "like" some disks, and so it's usually a Good Idea to have more than one UHD/BD drive to use, especially for cases like these.
E.g. I have one drive that refuses to mount one specific disk, no matter how much I clean it. Fortunately, that disk still works fine in my other drives.
https://drive.google.com/file/d/1ff9PCH ... sp=sharing
Here is the console output:
MSG:1005,0,1,"MakeMKV v1.18.3 linux(x64-release) gestartet","%1 gestartet","MakeMKV v1.18.3 linux(x64-release)"
DRV:0,0,999,0,"BD-RE ASUS BW-16D1HT 3.10 KLUP9994013","","/dev/sr0"
DRV:1,2,999,12,"BD-RE HL-DT-ST BD-RE BU40N 1.03 MODO52A0203","INTERSTELLAR","/dev/sr1"
DRV:2,256,999,0,"","",""
DRV:3,256,999,0,"","",""
DRV:4,256,999,0,"","",""
DRV:5,256,999,0,"","",""
DRV:6,256,999,0,"","",""
DRV:7,256,999,0,"","",""
DRV:8,256,999,0,"","",""
DRV:9,256,999,0,"","",""
DRV:10,256,999,0,"","",""
DRV:11,256,999,0,"","",""
DRV:12,256,999,0,"","",""
DRV:13,256,999,0,"","",""
DRV:14,256,999,0,"","",""
DRV:15,256,999,0,"","",""
MSG:1011,0,1,"Using LibreDrive mode (v06.3 id=866A98CB9C4E)","%1","Using LibreDrive mode (v06.3 id=866A98CB9C4E)"
MSG:3007,0,0,"Direkter Zugriffsmodus wird verwendet","Direkter Zugriffsmodus wird verwendet"
MSG:5050,0,2,"Evaluierungsversion. Es verbleiben noch 30 von 30 Tagen.","Evaluierungsversion. Es verbleiben noch %1 von %2 Tagen.","30","30"
MSG:5085,0,0,"Inhalte-Hashtabelle geladen, überprüfe Integrität der M2TS-Dateien.","Inhalte-Hashtabelle geladen, überprüfe Integrität der M2TS-Dateien."
MSG:3338,0,2,"Lade aktuelle HK in /home/player/.MakeMKV ... ","Lade aktuelle %1 in %2 ... ","HK","/home/player/.MakeMKV"
MSG:3339,0,1,"Automatisches Herunterladen von HK ist deaktiviert oder fehlgeschlagen.","Automatisches Herunterladen von %1 ist deaktiviert oder fehlgeschlagen.","HK"
MSG:3332,16908288,2,"AACS Ausgabedatei als file:///home/player/.MakeMKV/MKB20_v61_Interstellar_9A93.tgz gesichert","%1 Ausgabedatei als %2 gesichert","AACS","file:///home/player/.MakeMKV/MKB20_v61_Interstellar_9A93.tgz"
MSG:3303,0,0,"Der Volumenschlüssel für die DVD/Blu-ray ist unbekannt - das Video kann nicht entschlüsselt werden","Der Volumenschlüssel für die DVD/Blu-ray ist unbekannt - das Video kann nicht entschlüsselt werden"
MSG:5010,0,0,"Das Öffnen der Disk schlug fehl ","Das Öffnen der Disk schlug fehl "
TCOUNT:0
Re: Interstellar 4K UHD Bluray
The fact that MakeMKV has now created a TGZ dump file means that the problem here is likely that MakeMKV just doesn't know your disk's decryption keys. In which case, you need to email your TGZ dump file to svq@makemkv.com. You can also try downloading the latest KEYDB.cfg file, copying it into MakeMKV's data directory (i.e. where MakeMKV also writes its TGZ dump files - /home/player/.MakeMKV in your case), and restarting MakeMKV, in case the public KEYDB database already has an entry for your disk.
Note that since you're using Linux, you must ensure that your KEYDB file is literally named "KEYDB.cfg" and not (say) "keydb.cfg", because Linux file systems are case-sensitive.