Hi,

 

Unfortunately my server is located in a place that is not convenient for swapping discs. I don't have much experience with UNRAID or know much about servers/networks in general. I was wondering if I could use my optical drives from my windows PC over the network in UNRAID (and this MakeMKV container). I was able to share one of my drives as a network share in windows. Using the unassigned devices plugin I can get it to appear in UNRAID as a networked drive in /mnt/remotes/xxx.xxx.x.xxx_AsusBD (my.IP.Address_ShareName). I can access the file system of the disc in UNRAID but unfortunately it does not appear as a device and does not have a srx or sgx assignment. Does anyone know if what I am trying to do is even possible? Has anyone successfully been able to map networked optical drives for use in this container? Running down and up three flights of stairs every time I need to swap discs is getting a bit old.

 

I would understand if it's not possible, I was mostly just wondering if anyone more capable than I am has had a similar issue and was able to come up with a solution.
 
Thank you

33 minutes ago, SamCam619 said:

I was wondering if I could use my optical drives from my windows PC over the network in UNRAID

In this case why not just use the Windows version of MakeMKV and set the output to an Unraid location?

 

I use the MakeMKV docker container for Unraid directly on my server with an optical disk drive installed there but I also use MakeMKV on a Windows PC with an optical disk drive which outputs to an Unraid share.  Both output to the same location and I can be ripping from both at the same time.

8 minutes ago, Hoopster said:

In this case why not just use the Windows version of MakeMKV and set the output to an Unraid location?

 

I use the MakeMKV docker container for Unraid directly on my server with an optical disk drive installed there but I also use MakeMKV on a Windows PC with an optical disk drive which outputs to an Unraid share.  Both output to the same location and I can be ripping from both at the same time.

Thanks, I hadn't thought of that, the more complex and, likely, impossible solution was the one that came to mind first.

 

I'm testing it out now and it appears to be working.

 

 

Is there a way to increase the amount of log lines displayed when selecting the Logs docker option of MakeMKV? Right now, it seems to only show the last 90 log lines. I know I can go view the full log under /var/lib/docker/containers/, but I was hoping to just increase the amount of viewable log lines from the Logs option. The reason I want to increase the number of displayed log lines is because the log is quickly rolling over when I start the container, and I lose the information regarding what optical drives it found so that I can determine the device IDs. I am planning to add a few more optical drives to my server and just want the process of looking up the device IDs to be a bit simpler vs. having to go look at the full log.

On 9/14/2024 at 8:10 AM, Rojma said:

Is there a way to increase the amount of log lines displayed when selecting the Logs docker option of MakeMKV? Right now, it seems to only show the last 90 log lines. I know I can go view the full log under /var/lib/docker/containers/, but I was hoping to just increase the amount of viewable log lines from the Logs option. The reason I want to increase the number of displayed log lines is because the log is quickly rolling over when I start the container, and I lose the information regarding what optical drives it found so that I can determine the device IDs. I am planning to add a few more optical drives to my server and just want the process of looking up the device IDs to be a bit simpler vs. having to go look at the full log.

?
stop all dockers > then go to settings dockers disable docker >

 

With docker stopped. You now have accesses to the docker log settings. Increase docker log size. Apply and enable docker.

https://docs.docker.com/engine/logging/configure/
you may need to add extra parameters to add more logging options to the docker...

 

--log-opt mode=non-blocking --log-opt max-buffer-size=4m

Edited September 17, 20241 yr by bmartino1

On 9/14/2024 at 8:10 AM, Rojma said:

Is there a way to increase the amount of log lines displayed when selecting the Logs docker option of MakeMKV? Right now, it seems to only show the last 90 log lines. I know I can go view the full log under /var/lib/docker/containers/, but I was hoping to just increase the amount of viewable log lines from the Logs option. The reason I want to increase the number of displayed log lines is because the log is quickly rolling over when I start the container, and I lose the information regarding what optical drives it found so that I can determine the device IDs. I am planning to add a few more optical drives to my server and just want the process of looking up the device IDs to be a bit simpler vs. having to go look at the full log.

It also sounds like you have log rotation on and the size set low.


It best to jsut add the devices at the end to capture you optical disk drive:

 

click add at the bottom


you need 2 min sr0 and sg1

you can also look at unraid host and get the path to your disk drive.
 

root@BMM-Unraid:~# ls /dev/{cdrom,sr*,sg*}
/dev/cdrom@  /dev/sg0  /dev/sg1  /dev/sg2  /dev/sg3  /dev/sg4  /dev/sg5  /dev/sg6  /dev/sr0  /dev/sr1
root@BMM-Unraid:~# 

Have more then 1 disk drive you can also run:

 

lshw -C disk

 

Edited September 17, 20241 yr by bmartino1
help to find disks

Thanks for the response. However, I think you misunderstood my problem. My log file sizes are fine. If I view them directly from /var/lib/docker/containers/, I can see the full log and all of the history. However, if view the log file by selecting MakeMKV from the Docker tab and selecting Logs, I can only see the last 90 files from the log. My problem is the amount of VIEWABLE log lines, not the total number of log lines in the log. With that said, this really isn't an issue for me anymore. Instead of looking at the log, I discovered I can view all of the optical drive info by just running the lsscsi -g command from the command line.

Edited September 23, 20241 yr by Rojma

The option doesn't really exist in the web ui... one could make a user script to accomplish this...

 

as you can see unraid devs chose 90 lines....

 

your probably fighting the unraid web ui default tail command and log number, then... php emhttp code some where. better asked as a separate topic.

https://www.papertrail.com/solution/tips/how-to-live-tail-docker-logs/

docker ps
docker logs --tail 100 <container ID>

Is the best I have for you, then. Other setting mentioned before play a role in how your previous docker log and lines it creates is stored and what to view within it...

Since you already know where the actual log data is stored. I would just tail that log file....

Edited October 2, 20241 yr by bmartino1
data

On 1/1/2024 at 5:54 PM, doctortt said:

Hi, it's the new year and the MakeMKV docker has stopped working. It was working a few days ago. Please see screenshot below.

 

 

 

I get this to and makemkv simply stop working, even though I have lifetime key that I put in and it accepts it, but when I restart I get the same message my temporary key has expired and that the version is to old. Any ideas ?

2 hours ago, Fotopaul said:

 

I get this to and makemkv simply stop working, even though I have lifetime key that I put in and it accepts it, but when I restart I get the same message my temporary key has expired and that the version is to old. Any ideas ?

Did you add you license key to the "Licence Key:" field in container settings ^

27 minutes ago, Djoss said:

Did you add you license key to the "Licence Key:" field in container settings ^

Yes, I've added it to the field in the container settings and registered with my key in the app as well, and it accepts the key, but when I restart it, it does the same thing all over again. 

Remove the docker and make sure you remove the makemkv image
you may need to also delete any existing appdata folder 

then go to the docker tab. add container in the top drop down select makemkv(this has all of your settings and the key...) then apply to bring the docker back.

This sounds like a corruption issues within the docker image affecting the application. or that you adjusted setting in the app and didn't close it within the docker then docker stop start the container to bring it back.... 

Thank you for the suggestion, did it step by step, but made no difference. same exact messages pops up regardless. 😞

what is your docker repo? are you running lattest?



Otherwise your Key was flagged and ban via MakeMkv.
contact there support...

try the beta key:
https://forum.makemkv.com/forum/viewtopic.php?t=1053

be sure to have the env correct for the docker:

Doh, I used the incorrect field when pasting in my key... now it recognize my key and it works. I also got my optical drive recognized by adding the device in the container /dev/sr0 and /dev/sg0 and checking the privileged mode in the container.  Very happy, thank you!

On 9/17/2024 at 12:58 PM, bmartino1 said:

It also sounds like you have log rotation on and the size set low.


It best to jsut add the devices at the end to capture you optical disk drive:

 

click add at the bottom


you need 2 min sr0 and sg1

you can also look at unraid host and get the path to your disk drive.
 

root@BMM-Unraid:~# ls /dev/{cdrom,sr*,sg*}
/dev/cdrom@  /dev/sg0  /dev/sg1  /dev/sg2  /dev/sg3  /dev/sg4  /dev/sg5  /dev/sg6  /dev/sr0  /dev/sr1
root@BMM-Unraid:~# 

Have more then 1 disk drive you can also run:

 

lshw -C disk

 

 

There is a much more simple way to figure this out, simply enter 'lsscsi -g' and get the following:

lsscsi -g
[9:0:0:0]    cd/dvd  HL-DT-ST BD-RE BU40N      1.03  /dev/sr0   /dev/sg6

 

@Djoss - Anyway to get the image updated to contain makemkv version 1.17.8?

 

Looks like the build failed on github.

On 11/7/2024 at 3:38 PM, MowMdown said:

@Djoss - Anyway to get the image updated to contain makemkv version 1.17.8?

 

Looks like the build failed on github.

New image is now available

Hello! I recently swapped out my old CD/DVD drive fort a brand new Asus Blu-Ray drive for use with MakeMKV. However, when I try to load into docker container, I'm running into MakeMKV hanging on this line.

 

I've double-checked my routings, and they are correct (the default /sr0, /sg2), I'm running the latest version of the container, and I know the drive works, because I hooked it up to my Windows machine and it worked just fine there. Any ideas why this might be just sitting on this step?

 

Sorry if this has been answered before, but the only answers I've seen so far is to do with multiple BD drives which doesn't apply to me. I had my entire movie collection ripped to disk using anydvd many years ago - with file structure all intact. I'm slowly working my way through converting them all to mkv. Is there a way to run multiple instances of makemkv but converting disk to disk, not BD-ROM to disk. Thanks

On 11/17/2024 at 12:09 AM, Alhon said:

Hello! I recently swapped out my old CD/DVD drive fort a brand new Asus Blu-Ray drive for use with MakeMKV. However, when I try to load into docker container, I'm running into MakeMKV hanging on this line.

 

I've double-checked my routings, and they are correct (the default /sr0, /sg2), I'm running the latest version of the container, and I know the drive works, because I hooked it up to my Windows machine and it worked just fine there. Any ideas why this might be just sitting on this step?

 

there may be more then 3 /dev of sg# sr# you need to pass all of them...

in my case for 1 blue ray dirve i had to pass allof theses:

On 11/17/2024 at 12:09 AM, Alhon said:

Hello! I recently swapped out my old CD/DVD drive fort a brand new Asus Blu-Ray drive for use with MakeMKV. However, when I try to load into docker container, I'm running into MakeMKV hanging on this line.

 

I've double-checked my routings, and they are correct (the default /sr0, /sg2), I'm running the latest version of the container, and I know the drive works, because I hooked it up to my Windows machine and it worked just fine there. Any ideas why this might be just sitting on this step?

 

Just to give the followup, I needed to flash the firmware of my drive before it could be fully read by the system. I thought that was only if I was intending to do UHD discs but myh drive required it regardless. Just FYI for people in the future!

3 hours ago, Alhon said:

Just to give the followup, I needed to flash the firmware of my drive before it could be fully read by the system. I thought that was only if I was intending to do UHD discs but myh drive required it regardless. Just FYI for people in the future!

What disk Manfacutire and fimrware flash driver?

I have not had to firmware flash a Optical Disk Drive (cd/dvd/blueray) drive since xp erra,..

Libra Drivers sometimes have special firmware.

@Djoss did you ever figure out why the latest container kills read speed on local files?

 

here is a screenshot from the latest container:

 

 

here is a screenshot from container version: v24.07.1

 

Edited January 9, 20251 yr by spl147

On 1/9/2025 at 11:17 AM, spl147 said:

@Djoss did you ever figure out why the latest container kills read speed on local files?

 

here is a screenshot from the latest container:

 

 

here is a screenshot from container version: v24.07.1

 

 

So in your case MakeMKV is not reading from an optical drive, but from a file ?

Do you have the same issue with v24.11.1 ?