Jump to content
Djoss

[Support] Djoss - MakeMKV

493 posts in this topic Last Reply

Recommended Posts

Now get a 

This site can’t be reached

192.168.1.133 refused to connect.

ERR_CONNECTION_REFUSED

Edited by bob5731

Share this post


Link to post

I have figured out what was causing my DVDs to only rip at 2.0x and it does appear to be related to the ccextractor thing. Disable the "Subtitles CC>Text English (lossy conversion)" and it will bypass the need for the ccextractor.

 

I have makemkv setup to auto select the English audio and subtitle tracks so I didn't notice this new option before.

Edited by Runtime24

Share this post


Link to post
11 hours ago, bob5731 said:

Now get a 

This site can’t be reached

192.168.1.133 refused to connect.

ERR_CONNECTION_REFUSED

Are you using default container settings?  What is the URL you are using to connect to the interface?

Share this post


Link to post
2 hours ago, Runtime24 said:

I have figured out what was causing my DVDs to only rip at 2.0x and it does appear to be related to the ccextractor thing. Disable the "Subtitles CC>Text English (lossy conversion)" and it will bypass the need for the ccextractor.

 

I have makemkv setup to auto select the English audio and subtitle tracks so I didn't notice this new option before.

Great, thanks for the feeback!

Share this post


Link to post
6 hours ago, bob5731 said:

url 192.168.1.133

You have to set the port.  If you use default container settings, your url should be http://192.168.1.133:7806.

Share this post


Link to post
On 7/30/2017 at 10:59 PM, tryphon said:

Hello,

 

Just to say THANK YOU for this work. This container works great on my server, especially the stream capability. It has been years I wanted to build my own video disc player without the need to rip, transcode or convert ... just put the disc and play it freely with all the devices connected to my network.

 

Good job.

Per the post above, has streaming support been removed? I don't see "Stream" in the file menu. I have never used this feature in MakeMKV, so I could be just 'doing it wrong'. :)

Thanks for any clarification you can provide!

Share this post


Link to post
5 hours ago, harshl said:

Per the post above, has streaming support been removed? I don't see "Stream" in the file menu. I have never used this feature in MakeMKV, so I could be just 'doing it wrong'. :)

Thanks for any clarification you can provide!

Yes streaming support has been removed since MakeMKV v1.14.0:

Quote

Obsolete features:

  • Removed UPNP streaming (Use VLC or Kodi with libmmbd instead)
  • Linux: Removed mmdtsdec/libdcadec (Use latest ffmpeg instead)

See https://www.makemkv.com/download/ for the change history.

Share this post


Link to post

This docker has been working perfectly for me up until the last week or so. I was able to successfully rip Ready Player One on BR 3 days ago. After that, I insert any BR or DVD, it spins up, and then says "No Disc Inserted". I've uninstalled, re-installed, added a 2nd drive (with sg/sr info), restarted system, and still nothing. Anyone have any suggestions? Here is my log:

 

 

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-app-niceness.sh: executing...
[cont-init.d] 00-app-niceness.sh: exited 0.
[cont-init.d] 00-app-script.sh: executing...
[cont-init.d] 00-app-script.sh: exited 0.
[cont-init.d] 00-app-user-map.sh: executing...
[cont-init.d] 00-app-user-map.sh: exited 0.
[cont-init.d] 00-clean-logmonitor-states.sh: executing...
[cont-init.d] 00-clean-logmonitor-states.sh: exited 0.
[cont-init.d] 00-clean-tmp-dir.sh: executing...
[cont-init.d] 00-clean-tmp-dir.sh: exited 0.
[cont-init.d] 00-set-app-deps.sh: executing...
[cont-init.d] 00-set-app-deps.sh: exited 0.
[cont-init.d] 00-set-home.sh: executing...
[cont-init.d] 00-set-home.sh: exited 0.
[cont-init.d] 00-take-config-ownership.sh: executing...
[cont-init.d] 00-take-config-ownership.sh: exited 0.
[cont-init.d] 00-xdg-runtime-dir.sh: executing...
[cont-init.d] 00-xdg-runtime-dir.sh: exited 0.
[cont-init.d] 10-certs.sh: executing...
[cont-init.d] 10-certs.sh: exited 0.
[cont-init.d] 10-cjk-font.sh: executing...
[cont-init.d] 10-cjk-font.sh: exited 0.
[cont-init.d] 10-nginx.sh: executing...
[cont-init.d] 10-nginx.sh: exited 0.
[cont-init.d] 10-vnc-password.sh: executing...
[cont-init.d] 10-vnc-password.sh: exited 0.
[cont-init.d] 10-web-index.sh: executing...
[cont-init.d] 10-web-index.sh: exited 0.
[cont-init.d] 90-makemkv.sh: executing...
[cont-init.d] 90-makemkv.sh: generating machine-id...
app_ccextractor = "/usr/bin/ccextractor"
Checking for new beta key...
Registration key already up-to-date.
[cont-init.d] 90-makemkv.sh: exited 0.
[cont-init.d] 95-check-optical-drive.sh: executing...
[cont-init.d] 95-check-optical-drive.sh: looking for usable optical drives...
[cont-init.d] 95-check-optical-drive.sh: found optical drive [/dev/sr0, /dev/sg4], group 19.
[cont-init.d] 95-check-optical-drive.sh: found optical drive [/dev/sr1, /dev/sg7], group 19.
[cont-init.d] 95-check-optical-drive.sh: exited 0.
[cont-init.d] 96-install-autodiscripper-srv.sh: executing...
[cont-init.d] 96-install-autodiscripper-srv.sh: installing automatic disc ripper service...
[cont-init.d] 96-install-autodiscripper-srv.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] starting s6-fdholderd...
[services.d] starting certsmonitor...
[services.d] starting nginx...
[services.d] starting xvfb...
[nginx] starting...
[certsmonitor] disabling service: secure connection not enabled.
[xvfb] starting...
[services.d] starting autodiscripper...
[services.d] starting statusmonitor...
[statusmonitor] no file to monitor: disabling service...
[services.d] starting logmonitor...
[services.d] starting openbox...
[logmonitor] no file to monitor: disabling service...
[autodiscripper] starting...
[openbox] starting...
[autodiscripper] Ready.
[services.d] starting x11vnc...
[services.d] starting app...
[x11vnc] starting...
[app] starting MakeMKV...
[services.d] done.
28/01/2019 15:52:56 passing arg to libvncserver: -rfbport
28/01/2019 15:52:56 passing arg to libvncserver: 5900
28/01/2019 15:52:56 passing arg to libvncserver: -rfbportv6
28/01/2019 15:52:56 passing arg to libvncserver: -1
28/01/2019 15:52:56 passing arg to libvncserver: -httpportv6
28/01/2019 15:52:56 passing arg to libvncserver: -1
28/01/2019 15:52:56 passing arg to libvncserver: -desktop
28/01/2019 15:52:56 passing arg to libvncserver: MakeMKV
28/01/2019 15:52:56 x11vnc version: 0.9.14 lastmod: 2015-11-14 pid: 1275
28/01/2019 15:52:56 Using X display :0
28/01/2019 15:52:56 rootwin: 0x43 reswin: 0x400001 dpy: 0xa9418a00
28/01/2019 15:52:56
28/01/2019 15:52:56 ------------------ USEFUL INFORMATION ------------------
28/01/2019 15:52:56 X DAMAGE available on display, using it for polling hints.
28/01/2019 15:52:56 To disable this behavior use: '-noxdamage'
28/01/2019 15:52:56
28/01/2019 15:52:56 Most compositing window managers like 'compiz' or 'beryl'
28/01/2019 15:52:56 cause X DAMAGE to fail, and so you may not see any screen
28/01/2019 15:52:56 updates via VNC. Either disable 'compiz' (recommended) or
28/01/2019 15:52:56 supply the x11vnc '-noxdamage' command line option.
28/01/2019 15:52:56 X COMPOSITE available on display, using it for window polling.
28/01/2019 15:52:56 To disable this behavior use: '-noxcomposite'
28/01/2019 15:52:56
28/01/2019 15:52:56 Wireframing: -wireframe mode is in effect for window moves.
28/01/2019 15:52:56 If this yields undesired behavior (poor response, painting
28/01/2019 15:52:56 errors, etc) it may be disabled:
28/01/2019 15:52:56 - use '-nowf' to disable wireframing completely.
28/01/2019 15:52:56 - use '-nowcr' to disable the Copy Rectangle after the
28/01/2019 15:52:56 moved window is released in the new position.
28/01/2019 15:52:56 Also see the -help entry for tuning parameters.
28/01/2019 15:52:56 You can press 3 Alt_L's (Left "Alt" key) in a row to
28/01/2019 15:52:56 repaint the screen, also see the -fixscreen option for
28/01/2019 15:52:56 periodic repaints.
28/01/2019 15:52:56 GrabServer control via XTEST.
28/01/2019 15:52:56
28/01/2019 15:52:56 Scroll Detection: -scrollcopyrect mode is in effect to
28/01/2019 15:52:56 use RECORD extension to try to detect scrolling windows
28/01/2019 15:52:56 (induced by either user keystroke or mouse input).
28/01/2019 15:52:56 If this yields undesired behavior (poor response, painting
28/01/2019 15:52:56 errors, etc) it may be disabled via: '-noscr'
28/01/2019 15:52:56 Also see the -help entry for tuning parameters.
28/01/2019 15:52:56 You can press 3 Alt_L's (Left "Alt" key) in a row to
28/01/2019 15:52:56 repaint the screen, also see the -fixscreen option for
28/01/2019 15:52:56 periodic repaints.
28/01/2019 15:52:56
28/01/2019 15:52:56 XKEYBOARD: number of keysyms per keycode 7 is greater
28/01/2019 15:52:56 than 4 and 51 keysyms are mapped above 4.
28/01/2019 15:52:56 Automatically switching to -xkb mode.
28/01/2019 15:52:56 If this makes the key mapping worse you can
28/01/2019 15:52:56 disable it with the "-noxkb" option.
28/01/2019 15:52:56 Also, remember "-remap DEAD" for accenting characters.
28/01/2019 15:52:56
28/01/2019 15:52:56 X FBPM extension not supported.
28/01/2019 15:52:56 X display is not capable of DPMS.
28/01/2019 15:52:56 --------------------------------------------------------
28/01/2019 15:52:56
28/01/2019 15:52:56 Default visual ID: 0x21
28/01/2019 15:52:56 Read initial data from X display into framebuffer.
28/01/2019 15:52:56 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/5120
28/01/2019 15:52:56
28/01/2019 15:52:56 X display :0 is 32bpp depth=24 true color
28/01/2019 15:52:56
28/01/2019 15:52:56 Listening for VNC connections on TCP port 5900
28/01/2019 15:52:56
28/01/2019 15:52:56 Xinerama is present and active (e.g. multi-head).
28/01/2019 15:52:56 Xinerama: number of sub-screens: 1
28/01/2019 15:52:56 Xinerama: no blackouts needed (only one sub-screen)
28/01/2019 15:52:56
28/01/2019 15:52:56 fb read rate: 1156 MB/sec
28/01/2019 15:52:56 fast read: reset -wait ms to: 10
28/01/2019 15:52:56 fast read: reset -defer ms to: 10
28/01/2019 15:52:56 The X server says there are 10 mouse buttons.
28/01/2019 15:52:56 screen setup finished.
28/01/2019 15:52:56

The VNC desktop is: 91c773d25fac:0

0

******************************************************************************
Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet?

The scheme stores pixel data offscreen on the VNC viewer side for faster
retrieval. It should work with any VNC viewer. Try it by running:

x11vnc -ncache 10 ...

One can also add -ncache_cr for smooth 'copyrect' window motion.
More info: http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching

28/01/2019 15:54:46 Got connection from client 127.0.0.1
28/01/2019 15:54:46 other clients:
28/01/2019 15:54:46 Got 'ws' WebSockets handshake
28/01/2019 15:54:46 Got protocol: binary
28/01/2019 15:54:46 - webSocketsHandshake: using binary/raw encoding
28/01/2019 15:54:46 - WebSockets client version hybi-13
28/01/2019 15:54:46 Disabled X server key autorepeat.
28/01/2019 15:54:46 to force back on run: 'xset r on' (3 times)
28/01/2019 15:54:46 incr accepted_client=1 for 127.0.0.1:46320 sock=10
28/01/2019 15:54:46 Client Protocol Version 3.8
28/01/2019 15:54:46 Protocol version sent 3.8, using 3.8
28/01/2019 15:54:46 rfbProcessClientSecurityType: executing handler for type 1
28/01/2019 15:54:46 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8
28/01/2019 15:54:46 Pixel format for client 127.0.0.1:
28/01/2019 15:54:46 32 bpp, depth 24, little endian
28/01/2019 15:54:46 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
28/01/2019 15:54:46 no translation needed
28/01/2019 15:54:46 Enabling NewFBSize protocol extension for client 127.0.0.1
28/01/2019 15:54:46 Enabling full-color cursor updates for client 127.0.0.1
28/01/2019 15:54:46 Using image quality level 6 for client 127.0.0.1
28/01/2019 15:54:46 Using JPEG subsampling 0, Q79 for client 127.0.0.1
28/01/2019 15:54:46 Using compression level 9 for client 127.0.0.1
28/01/2019 15:54:46 Enabling LastRect protocol extension for client 127.0.0.1
28/01/2019 15:54:46 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFECC)
28/01/2019 15:54:46 Using tight encoding for client 127.0.0.1
28/01/2019 15:54:46 Got connection from client 127.0.0.1
28/01/2019 15:54:46 other clients:
28/01/2019 15:54:46 Got 'ws' WebSockets handshake
28/01/2019 15:54:46 Got protocol: binary
28/01/2019 15:54:46 - webSocketsHandshake: using binary/raw encoding
28/01/2019 15:54:46 - WebSockets client version hybi-13
28/01/2019 15:54:46 Disabled X server key autorepeat.
28/01/2019 15:54:46 to force back on run: 'xset r on' (3 times)
28/01/2019 15:54:46 incr accepted_client=1 for 127.0.0.1:46320 sock=10
28/01/2019 15:54:46 Client Protocol Version 3.8
28/01/2019 15:54:46 Protocol version sent 3.8, using 3.8
28/01/2019 15:54:46 rfbProcessClientSecurityType: executing handler for type 1
28/01/2019 15:54:46 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8
28/01/2019 15:54:46 Pixel format for client 127.0.0.1:
28/01/2019 15:54:46 32 bpp, depth 24, little endian
28/01/2019 15:54:46 true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0
28/01/2019 15:54:46 no translation needed
28/01/2019 15:54:46 Enabling NewFBSize protocol extension for client 127.0.0.1
28/01/2019 15:54:46 Enabling full-color cursor updates for client 127.0.0.1
28/01/2019 15:54:46 Using image quality level 6 for client 127.0.0.1
28/01/2019 15:54:46 Using JPEG subsampling 0, Q79 for client 127.0.0.1
28/01/2019 15:54:46 Using compression level 9 for client 127.0.0.1
28/01/2019 15:54:46 Enabling LastRect protocol extension for client 127.0.0.1
28/01/2019 15:54:46 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFECC)
28/01/2019 15:54:46 Using tight encoding for client 127.0.0.1
28/01/2019 15:54:46 client_set_net: 127.0.0.1 0.0000
28/01/2019 15:54:46 created xdamage object: 0x40002c
28/01/2019 15:54:47 copy_tiles: allocating first_line at size 41
28/01/2019 15:54:49 client 1 network rate 2789.4 KB/sec (43680.7 eff KB/sec)
28/01/2019 15:54:49 client 1 latency: 1.0 ms
28/01/2019 15:54:49 dt1: 0.0021, dt2: 0.0023 dt3: 0.0010 bytes: 10839
28/01/2019 15:54:49 link_rate: LR_LAN - 1 ms, 2789 KB/s
28/01/2019 15:54:56 created selwin: 0x40002d
28/01/2019 15:54:56 called initialize_xfixes()
28/01/2019 15:59:47 idle keyboard: turning X autorepeat back on.
28/01/2019 15:59:47 idle keyboard: turning X autorepeat back on.

 

 

Edited by WillWorkForAmmo

Share this post


Link to post
On 1/28/2019 at 7:08 PM, WillWorkForAmmo said:

This docker has been working perfectly for me up until the last week or so. I was able to successfully rip Ready Player One on BR 3 days ago. After that, I insert any BR or DVD, it spins up, and then says "No Disc Inserted". I've uninstalled, re-installed, added a 2nd drive (with sg/sr info), restarted system, and still nothing. Anyone have any suggestions?

Everything looks fine in the log.  So MakeMKV sees your drives but none of them are able to read the disc?  Do you know if problem started after a container update?

Share this post


Link to post
7 hours ago, Djoss said:

Everything looks fine in the log.  So MakeMKV sees your drives but none of them are able to read the disc?  Do you know if problem started after a container update?

Correct. When I insert the disc (BR or DVD) the GUI shows the spin up like it's reading, then shows "No disc inserted". The drive light stops as well. I'm not 100% sure if it started after an update, but I feel as though it may have. I also tried removing the docker, but I'm not sure if that removes 100% of everything including maybe settings or something in Unraid (I'm a novice).

Share this post


Link to post
1 hour ago, WillWorkForAmmo said:

Correct. When I insert the disc (BR or DVD) the GUI shows the spin up like it's reading, then shows "No disc inserted". The drive light stops as well. I'm not 100% sure if it started after an update, but I feel as though it may have. I also tried removing the docker, but I'm not sure if that removes 100% of everything including maybe settings or something in Unraid (I'm a novice).

You can try to remove the appdata folder:

  • Stop the container.
  • Remove the appdata folder by running: rm -r /mnt/user/appdata/MakeMKV
  • Start the container.

Share this post


Link to post
42 minutes ago, Djoss said:

You can try to remove the appdata folder:

  • Stop the container.
  • Remove the appdata folder by running: rm -r /mnt/user/appdata/MakeMKV
  • Start the container.

That fixed it! Thanks!

Share this post


Link to post

I’ve been having issues stopping the container. I will click the stop button for the container and it will hang and never fully stop. I’ve tried to kill it from the Cali, but haven’t had any luck either. I’ve tried docker kill MakeMkV, docker rm MakeMKV and neither work. I will have to force shut down my system to get it back. I’ve deleted my MakeMKv folder in app data and reinstalled. Still the same scenario. I am using an external USB Blu-ray drive, if that makes any difference. It works great and is able to read the disk when I am able to VNC into MakeMKV. 

 

Any thoughts?

 

here are my logs when I try to stop the container. 

 


15/02/2019 20:56:24 Statistics events Transmit/ RawEquiv ( saved)
15/02/2019 20:56:24 FramebufferUpdate : 107 | 0/ 0 ( 0.0%)
15/02/2019 20:56:24 ZRLE : 272 | 182954/ 5909520 ( 96.9%)
15/02/2019 20:56:24 RichCursor : 2 | 1776/ 1776 ( 0.0%)
15/02/2019 20:56:24 TOTALS : 381 | 184730/ 5911296 ( 96.9%)
15/02/2019 20:56:24 Statistics events Received/ RawEquiv ( saved)
15/02/2019 20:56:24 PointerEvent : 216 | 1296/ 1296 ( 0.0%)
15/02/2019 20:56:24 FramebufferUpdate : 107 | 1070/ 1070 ( 0.0%)
15/02/2019 20:56:24 SetPixelFormat : 2 | 40/ 40 ( 0.0%)
15/02/2019 20:56:24 SetEncodings : 2 | 112/ 112 ( 0.0%)
15/02/2019 20:56:24 TOTALS : 327 | 2518/ 2518 ( 0.0%)
15/02/2019 20:56:24 destroyed xdamage object: 0x200034
[services.d] stopping services
[services.d] stopping app...
[services.d] stopping openbox...
[services.d] stopping statusmonitor...
[services.d] stopping logmonitor...
[services.d] stopping x11vnc...
caught signal: 15
16/02/2019 07:26:03 deleted 40 tile_row polling images.
[services.d] stopping xvfb...
[services.d] stopping nginx...
[services.d] stopping certsmonitor...
[services.d] stopping s6-fdholderd...
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
 

Share this post


Link to post

Well I see no errors now with the install.  However the webUI tells me it sees not drive.  Without the webUI open I insert a disk and watch the dive spin up and then stop.  I have the auto flag for start and eject set to 1.

Not sure whats wrong now.

 

** SOLVED** I needed to turn on Privileged Mode

Edited by Salmack

Share this post


Link to post
On 2/16/2019 at 8:56 AM, hovee said:

I’ve been having issues stopping the container. I will click the stop button for the container and it will hang and never fully stop. I’ve tried to kill it from the Cali, but haven’t had any luck either. I’ve tried docker kill MakeMkV, docker rm MakeMKV and neither work. I will have to force shut down my system to get it back. I’ve deleted my MakeMKv folder in app data and reinstalled. Still the same scenario. I am using an external USB Blu-ray drive, if that makes any difference. It works great and is able to read the disk when I am able to VNC into MakeMKV. 

 

Any thoughts?

 

here are my logs when I try to stop the container. 

 


15/02/2019 20:56:24 Statistics events Transmit/ RawEquiv ( saved)
15/02/2019 20:56:24 FramebufferUpdate : 107 | 0/ 0 ( 0.0%)
15/02/2019 20:56:24 ZRLE : 272 | 182954/ 5909520 ( 96.9%)
15/02/2019 20:56:24 RichCursor : 2 | 1776/ 1776 ( 0.0%)
15/02/2019 20:56:24 TOTALS : 381 | 184730/ 5911296 ( 96.9%)
15/02/2019 20:56:24 Statistics events Received/ RawEquiv ( saved)
15/02/2019 20:56:24 PointerEvent : 216 | 1296/ 1296 ( 0.0%)
15/02/2019 20:56:24 FramebufferUpdate : 107 | 1070/ 1070 ( 0.0%)
15/02/2019 20:56:24 SetPixelFormat : 2 | 40/ 40 ( 0.0%)
15/02/2019 20:56:24 SetEncodings : 2 | 112/ 112 ( 0.0%)
15/02/2019 20:56:24 TOTALS : 327 | 2518/ 2518 ( 0.0%)
15/02/2019 20:56:24 destroyed xdamage object: 0x200034
[services.d] stopping services
[services.d] stopping app...
[services.d] stopping openbox...
[services.d] stopping statusmonitor...
[services.d] stopping logmonitor...
[services.d] stopping x11vnc...
caught signal: 15
16/02/2019 07:26:03 deleted 40 tile_row polling images.
[services.d] stopping xvfb...
[services.d] stopping nginx...
[services.d] stopping certsmonitor...
[services.d] stopping s6-fdholderd...
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
 

What you are describing looks more like an issue with Docker itself.  According to the logs, the container seems to shutdown itself correctly.  Also, in the case a container doesn't shutdown itself, Docker will forcefully kill it after a few seconds.

Is your Docker image full?

Share this post


Link to post
On 2/16/2019 at 10:40 AM, Salmack said:

Well I see no errors now with the install.  However the webUI tells me it sees not drive.  Without the webUI open I insert a disk and watch the dive spin up and then stop.  I have the auto flag for start and eject set to 1.

Not sure whats wrong now.

 

** SOLVED** I needed to turn on Privileged Mode

You should not have to run it with privilege mode.  Did you properly exposed the drive to the container?  Do you have the container's log when the privileged mode is disabled?

Share this post


Link to post
On 2/16/2019 at 11:05 AM, Salmack said:

I do not want them to be in sub-folders.  How can I stop this?

Extraction is done in a subfolder because generated files have all the same filenames, meaning that ripping more than one disc would create conflicts.

Share this post


Link to post
On 2/18/2019 at 5:26 AM, Djoss said:

What you are describing looks more like an issue with Docker itself.  According to the logs, the container seems to shutdown itself correctly.  Also, in the case a container doesn't shutdown itself, Docker will forcefully kill it after a few seconds.

Is your Docker image full?

I checked my docker image and I have plenty of space. I have a 100gb file.

 

I've been able to re-produce this a few times now. When I have a disc that has a scratch on it and it is unable to copy successfully, MakeMKV keeps ticking up in time till completion. I then try and stop the copy in MakeMKV and then try and stop the container and am unable to. I can then go into htop and search for the container id and kill it. After that is killed, I can remove the container and re-add it, however there is still a process that has a signal D and is waiting for the drive. I am unable to kill that process regardless of Sigterm/Sigkill. You can see in the screenshot process 20667 that can not be killed which is hanging up the system from stopping the array/rebooting/shutting down/etc... 


Any thoughts on how to make sure this doesn't happen if a disc doesn't copy successfully?

Screen Shot 2019-02-18 at 6.08.45 PM.png

Edited by hovee

Share this post


Link to post
On 2/18/2019 at 6:24 PM, hovee said:

I checked my docker image and I have plenty of space. I have a 100gb file.

 

I've been able to re-produce this a few times now. When I have a disc that has a scratch on it and it is unable to copy successfully, MakeMKV keeps ticking up in time till completion. I then try and stop the copy in MakeMKV and then try and stop the container and am unable to. I can then go into htop and search for the container id and kill it. After that is killed, I can remove the container and re-add it, however there is still a process that has a signal D and is waiting for the drive. I am unable to kill that process regardless of Sigterm/Sigkill. You can see in the screenshot process 20667 that can not be killed which is hanging up the system from stopping the array/rebooting/shutting down/etc... 


Any thoughts on how to make sure this doesn't happen if a disc doesn't copy successfully?

Screen Shot 2019-02-18 at 6.08.45 PM.png

Yeah scratched discs can be problematic...  Are you using the UI or the automatic disc ripper? 

Share this post


Link to post
5 minutes ago, hovee said:

I’m using the UI through Web and VNC.

Ok, so if cancelling the rip from the UI doesn't work, then I guess there is nothing I can really do.  You may have better luck by posting your issue to the MakeMKV forum.

Share this post


Link to post
Ok, so if cancelling the rip from the UI doesn't work, then I guess there is nothing I can really do.  You may have better luck by posting your issue to the MakeMKV forum.

Good point. Next time this happens I’ll wait longer after I hit cancel to see if that stops the operation. I’ll check out the MakeMKV forums. Thanks for your help!

Share this post


Link to post

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.