username34793

Anyone have any further input regarding Makemkv profiles/conversion profiles? It seems the MakeMKV profile/conversion profiles have to be placed in the .MakeMKV directory and then the ripper settings/arm.yaml file needs to be updated to have MKV_ARGS: use /home/arm/.MakeMKV/insert profile name... So in my case it looks like this "--profile=/home/arm/.MakeMKV/pcmflac.mmcp.xml" After correcting a conversion profile series of errors I can confirm ARM will use a proper MakeMKV conversion profile. Only issue I noticed is the app_DefaultSelectionString= parameter within the profile was ignored. I had to add it back to the settings.conf file. By doing this, the logs indicate this profile is being used however, everything I want this profile to do is not working. This is either a profile issue or ARM/ARM's installation of MakeMKV doesn't process these profiles correctly. I will test this profile and other profiles further to attempt to determine what is or isn't working and where/why. I have the profile located in the same directory as the abcde.conf. I have pointed to it with the MKV_ARGS option and nothing seems to work. I have used --profile=/etc/arm/config/pcmflac.mmcp.xml and "--profile=/etc/arm/config/pcmflac.mmcp.xml" as the MKV_ARGS: option. There's a separate settings.conf file located in the.MakeMKV directory which absolutely respects anything added to app_DefaultSelectionString= However, I do not know if or how to populate the settings.conf with MakeMKV profile/conversion profile info as the profiles use XML and a specific structure... apparently. From what I can tell, the profile needs to be in MakeMKVs data directory which is the .MakeMKV folder/directory within ARM but I have no idea how to point to it with the MKV_ARGS yaml option,

Now that I have a working ARM container, can anyone tell me how to go about adding custom Makemkv profiles to it? I can't figure out what directory the custom xml file should be in. I was/am expecting to find the default.mmcp.xml file somewhere within the ARM container files but I cannot. I'm not sure if I just need to create the profile and appropriately reference it via the MKV_ARGS: option via the webui ripper settings / arm.yaml file. Thanks in advance

Well, actually this turned out to be a pretty easy fix. It only took somewhere around 16 hours of trial and error to find... It seems the Music / music folder thing can cause problems during the container creation. If there's a music folder already in the directory the scripts will halt because it cannot delete the folder... I don't know exactly how to explain it but I was able to replicate it a whole lot with a virtual machine. It was actually in the log I posted below from the beginning but it took me far to long to realize that was the problem. I'm not too good at this here Linux stuff. I cannot get this to work at all. I left the container config at default except for removing the nvidia runtime and adjusting the cd/dvd/bd drive parameters. Everything appears to be successful and the container will start but I cannot get to the webui no matter what ports I try and inserting a dvd doesn't do anything. ARM log below: text error warn system array login *** Running /etc/my_init.d/10_syslog-ng.init... *** Running /etc/my_init.d/arm_user_files_setup.sh... rm: cannot remove '/home/arm/music': Is a directory *** /etc/my_init.d/arm_user_files_setup.sh failed with status 1 *** Killing all processes... *** Running /etc/my_init.d/10_syslog-ng.init... *** Running /etc/my_init.d/arm_user_files_setup.sh... rm: cannot remove '/home/arm/music': Is a directory *** /etc/my_init.d/arm_user_files_setup.sh failed with status 1 *** Killing all processes... Dec 7 01:39:29 b82e733c525e syslog-ng[13]: syslog-ng starting up; version='3.25.1' Updating arm user id from 1000 to 99... Updating arm group id from 1000 to 100... Adding arm user to 'render' group Dec 7 01:39:30 b82e733c525e syslog-ng[13]: syslog-ng shutting down; version='3.25.1' Dec 7 01:39:35 b82e733c525e syslog-ng[12]: syslog-ng starting up; version='3.25.1' Updating arm user id from 1000 to 99... usermod: no changes Updating arm group id from 1000 to 100... Adding arm user to 'render' group Dec 7 01:39:36 b82e733c525e syslog-ng[12]: syslog-ng shutting down; version='3.25.1' ** Press ANY KEY to close this window **

@JorgeB Thank you for the reply and insight. I am barely a novice when it comes to understanding Linux. Do you have any further information regarding this general protection fault or perhaps you can point me to some resources to better understand Linux/UNRAID general protection faults? My assumption is this has something to do with the SAS drives I added and the way SAS drives handle and report SMART info but I am pretty much just guessing. I do not have the required understanding to do anything other than guess. I'll take your advice and not worry for now but I would love to understand more about these faults.

Recently I've been seeing general protection faults regarding smartctl. The two most recent examples are: Nov 30 18:56:01 UNRAID kernel: traps: smartctl[12156] general protection fault ip:1467c84358e4 sp:7ffe9bf86558 error:0 in libc-2.37.so[1467c8373000+169000] Dec 1 00:45:05 UNRAID kernel: traps: smartctl[18759] general protection fault ip:14b9dd2d28e4 sp:7ffe6616ed48 error:0 in libc-2.37.so[14b9dd210000+169000] I added two 20TB SAS drives as my parity drives and I think these general protection faults started around that time. I have checked all cables for proper connection and function and cannot identify any issues with cables. As far as I can tell, everything is working fine but seeing these errors in the log is a bit concerning. Diagnostics attached. Thanks in advance. unraid-diagnostics-20231201-0448.zip