Jump to content

Tergo247

Members
  • Content Count

    19
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Tergo247

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I appreciate it, I bet it's the quotes. I'll give it a shot when I'm within VPN range.
  2. New question, I'm getting an unexpected character error with line 62, the one where admins are listed. I just put my steam username in the brackets, is that not the syntax?
  3. Thanks gents, I knew there must be a method outside of windows. I couldn't figure out nano, but the Config Editor worked like a champ. The more you know...
  4. I'm trying to spin up a Factorio server docker. I can't wait to get this going, but I've hit a snag. I anticipate this being a noob move, but I was trying to modify the settings.conf file with Notepad++ in Windows and am completely unable to save it. Even being an admin on my box, I can't change the permissions of that file or anything in the Factorio folder to allow my edits. It's how I typically adjust anything from NGINX to subdomains, this is the first time I've had a problem. Any help is appreciated.
  5. root@GowingNAS:~# docker exec MakeMKV lsscsi -g -k [0:0:0:0] disk SanDisk Cruzer Fit 1.00 /dev/sda /dev/sg0 [1:0:0:0] disk ATA WDC WD40EFRX-68N 0A82 /dev/sdb /dev/sg1 [2:0:0:0] disk ATA WDC WD40EFRX-68N 0A82 /dev/sdc /dev/sg2 [3:0:0:0] cd/dvd ASUS BC-12B1ST b 3.00 /dev/sr0 /dev/sg3 [4:0:0:0] disk ATA Samsung SSD 840 4B0Q /dev/sdd /dev/sg4 root@GowingNAS:~# docker exec MakeMKV env HOME=/config s6-applyuidgid -u 99 -g 100 -G 19 /opt/makemkv/bin/makemkvcon -r --cache=1 info disc:9999 MSG:1005,0,1,"MakeMKV v1.14.4 linux(x64-release) started","%1 started","MakeMKV v1.14.4 linux(x64-release)" MSG:5042,0,0,"The program can't find any usable optical drives.","The program can't find any usable optical drives." DRV:0,256,999,0,"","","" DRV:1,256,999,0,"","","" 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:5010,0,0,"Failed to open disc","Failed to open disc" Here's what I got. I ordered an external 5.25 enclosure. I'll be able to test the drive on another computer when it arrives.
  6. Yes, I've ripped in something to the tune of 50 discs with it.
  7. Hey Guys, I've been using this container for some time now and have a pretty sizable media library, so thanks for your efforts. Recently however, I've lost my ability to rip discs. The hard stop seems to be that it doesn't recognize my fairly new optical drive with the auto ripper (nothing shows up) and in the GUI (says no optical drives), despite this being in the log on start up: 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/sg3], 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. Now there are tons of errors related to fontconfigs that I assume are unrelated as I have been ripping despite them without issue until now. Thanks for any help you can provide.
  8. 5.10.24 is a thing... wink wink. I just got my first Ubiquiti gateway/ap and foolishly set it up on my laptop. In retrospect, I'm not sure how I would have accessed my server to configure it from there, but at any rate it sure would be nice to migrate my site over to your awesome docker. Nudge nudge.
  9. Given how little discussion there is on passthrough drives, I figured it best to ask a related question here. I've mapped a BD drive to MakeMkV for ripping in discs, but a new thing has started happening. The drive automatically ejects when done ripping a disc as it always has, but now it automatically closes after a few minutes as well. Then it re-rips continually automatically opening and closing until I manually stop it. I could shut off automatic ejecting at MakeMKV, and just use the status light on the drive to tell quickly if it's done, but I like the eject to prompt a new disc insert. Any way you guys see of stopping automatic closing?
  10. Just to put this issue to bed, it was the drive. The replacement is ripping happily. Thanks for hanging out in the weeds with me. Cheers.
  11. Same behavior in handbrake. I can try temping it into another computer before I buy a new one. I'll let you know how it goes..
  12. I tried setting the minimum length to 0, still doesn't see the disc. I tried setting the authentication key to UNSET, and it still doesn't behave any differently, although the log looks slightly different. Nothing shows up in the web gui asking for a key. Anything else to try or is it likely a bad optical drive?
  13. I see v1.12.2 in MakeMKV. If I add :v1.9.0 to the repository line and force the update, it seems to install that version but the about page in the gui shows otherwise. If I understand you correctly, I do have it set to only rip titles more than an hour and a half long, but in my experience it will still see all the titles on the disc regardless of that setting. It just won't bother to rip in the short ones. My output directory is definitely different from the storage directory. Thanks for the snappy assistance Djoss. Hopefully we're nearing the cause, even if that means buying a new optical drive.
  14. I passed through the drive to handbrake and it behaves exactly the same way. No title. I tried rolling back the version but it still reports using the new one, is there anything to do besides changing the repository line and restarting the container? It certainly seems that way, although there is nothing in the logs that would indicate that. I don't recall having to grant special permissions during the install, where would one do that?
  15. I encountered some notable odd behavior. I removed the sr0 device line and the log was unchanged after restarting the container. I deleted everything in extra parameters and encountered no difference in function or log. I uninstalled MakeMKV, deleted all files from the appdata folder, and reinstalled it. I then got the following in the log sans extra parameters: 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/sg3], but it is not usable because: [cont-init.d] 95-check-optical-drive.sh: --> the host device /dev/sr0 is not exposed to the container. [cont-init.d] 95-check-optical-drive.sh: --> the host device /dev/sg3 is not exposed to the container. [cont-init.d] 95-check-optical-drive.sh: no usable optical drive found. [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: no usable optical drive available. [cont-init.d] 96-install-autodiscripper-srv.sh: exited 0. [cont-init.d] done. I added back in the original lines and am right back where I started. It sees the drive but not the disc. The only difference is this time when I remove the sr0 line, it calls for it in the log. Weird behavior aside, how long do optical drives last? It's pretty coincidental if this drive happened to fail within a day of container updates.