I will post logs tomorrow, after i test again to verify.Įdit: I have tested using a 4K bluray and have attached the logs from the newly created docker.
#Makemkv registration code november 2017 manual
I have to remove the container and then add it back to Unraid to start another manual rip. The restart circles for a few minutes and then goes back to started and then the webui does not ever connect again. I am also having an issue where i cannot restart the docker. The copy stops and the remaining time climbs infinitely. I am having an issue with the manual rip of a movie, that if i try and monitor the progress of the rip, from a different device than what i started it on.
But in your scenario, the error is harmless (see and ). Currently, the automatic disc ripper stops for any scsi error (message code 2003). Then "Decrypting data", and proceeds to "Saving all titles". More PRGV and MSG records (either "too short" or "added" messages). MSG:3007,0,0,"Using direct disc access mode","Using direct disc access mode" After that, it shows all of the DRV records, then stuff like this: Are you getting the error a single time ? What is the message just after the error ?Ī single time, with each disc. There's a lot more, but I don't think it's very useful? MSG:2003,0,3,"Error 'Scsi error - ILLEGAL REQUEST:READ OF SCRAMBLED SECTOR WITHOUT AUTHENTICATION' occurred while reading 'DVD+R-DL ATAPI DVD A DH16AASH SA15' at offset '1048576'","Error '%1' occurred while reading '%2' at offset '%3'","Scsi error - ILLEGAL REQUEST:READ OF SCRAMBLED SECTOR WITHOUT AUTHENTICATION","DVD+R-DL ATAPI DVD A DH16AASH SA15","1048576"ĭRV:0,2,999,1,"DVD+R-DL ATAPI DVD A DH16AASH SA15","ROBIN_HOOD_S1_D1","/dev/sr1" I mean it does complain, but it doesn't immediately eject the disk and give up. opt/makemkv/bin/makemkvcon -r -cache=1 info disc:9999 If you don't know the disc ID, you can run: Container is gone now.Ĭould you try to rip the disc manually and provide the output ?Įnv HOME=/config /opt/makemkv/bin/makemkvcon -r -progress=-same mkv disc:0 all /output/manual_rip_test Is there a safe way to stop it from the command line? My other dockers are working fine (ie responding to restart and stop commands) and the container log just says there's no log because docker is marked for removal.Įdit: Docker became unresponsive so I had to stop and start the array. I'd reboot the server but I'm in the middle of a preclear. Finally tried to remove it and it's completely unresponsive. In my case, I just installed it, went to the webgui, no response, tried to restart then stop it, no response so I tried to edit it and same. Having a similar issue with this container. I can't make the docker stop or restart itself. The docker hangs and will not stop or restart when using the Unraid GUI. I have used the docker to rip about a dozen Blu Rays over several weeks, but over the last 3 weeks or so every rip requires an unclean (hold power button) shutdown before I can rip a second. Does anyone have any additional input on this issue?
0 kommentar(er)
