s.Oliver

anyway, i would try to make a change to the setup, to see if there's a change in the process. maybe you could create a new share, point it to the array (without cache drive involved) and see, if you experience a change/success.

is that destination share setup to use a cache drive – if so, i would check, that on the cache drive there's enough free space, to store the complete ripped file. just a thought.

solved – this time it succeeded starting up and updating the version; i guess it was because of problems downloading the update files. puh

well, doesn't make any difference i even think, that it did search only for latest on it's own – at least i had a glimpse while starting it this time. but i set it explicitly to latest – nada, same. anyway, at which version are you yourself? do you updated to this one: 1.1.3.2700-6f64a8d and did it succeed?

strange thing happened today here, needed to restart the machine and afterwards tried to start the plex docker and nothing… docker log only shows these lines: [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] 10-adduser: executing... ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We do accept donations at: https://www.linuxserver.io/donations ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-dbus: executing... [cont-init.d] 30-dbus: exited 0. [cont-init.d] 40-chown-files: executing... [cont-init.d] 40-chown-files: exited 0. [cont-init.d] 50-plex-update: executing... Atempting to upgrade to: 1.1.3.2700-6f64a8d it never gets any further, so plex-server is dead for me. no plex = wife unhappy! VERSION = plexpass (i'm a lifetime pass owner) also tried to delete all references to plex (only appdata left) and re-installed it, but same errors in the log. anyone with the same errors (and possibly any solution)?

in my case, the format of the added string for the "Extra Parameters" needs to look like "--device=/dev/sr0" and not "--device=/dev/sr0:/dev/sr0"

yeah, know that! i try to disable it, whenever possible and whenever i don't forget to do it

saarg, do you plan to update to the new version?

needs a space between "ls " and optional parameters like "-la", so make it look like this: ls -la

steps necessary: 1) goto Tools / System Devices you'll see all devices in the section USB-/SCSI Devices. normally a dvd-drive will be recognized as a SCSI-device. look here for your drive (it has after the []-part it's label as cd/dvd noted). if you can't figure it out a hint: disconnect the drive, come back to this section, or reload your web-browser and make a screenshot of the USB-/SCSI area. now connect the drive again, come back again (or reload the page) and compare it with the screenshot. you should see at last one more device listed – that should be your dvd-drive. 2) device-address for docker container if you found your device (see above) then note (or copy & paste) the exact device address; it usually begins with /dev/srX (where X = 0 for first device, and subsequent higher for additional devices). so in my case it is /dev/sr0 3) goto Docker menu single click on the listed docker entry (e.g. MakeMKV-RDP) and choose "Edit". 3a) Volume Mappings you need to populate paths for the preconfigured container volumes for /config and /unRaid. /config is mostly the destination, where the docker (or program therein) saves it's own configuration files. if you have a cache drive, then enter it's path in the host path field right from the /config field. for example with a cache ssd drive it looks like: "/mnt/cache/appdata/MakeMKV-RDP" the /unRaid container volume needs to mapped to a writeable share. for example, if you have setup before a share called "Movies" and you want to rip directly into it, you would define it as "/mnt/user/Movies/" 3b) Port Mappings don't touch the container port fields, they stay like they are setup. for the host port it depends, if you have either other docker, which use the same port, or install more than one docker instance of MakeMKV. if you haven't installed much and this is your 1st MakeMKV docker, then probably you leave these ports as listed. 4) starting the docker again, goto to Docker and single click on the docker icon for MakeMKV. choose "Start" if it isn't started already, or if you changed settings in step 3a/3b then click on "Restart". give it a short moment of time to start up, then again single click on it and this time choose "WebUI". your browser opens into a RDP-session and you see a login panel; simply click on "OK"-button and boom, you see the program and can start to configure it for use. 5) MakeMKV & destination folder setup you don't want to blow up your docker image file, so you need to setup MakeMKV's destination path. goto preferences and enter there exactly "/unRaid" (of course without ""). apply/save changes and you should be good to go.

hey guys, i want to move makemkv activities also to the unraid box. now i have an old dvd/bluray combo-drive, but it reads blu-rays with only 1.6x (6.8 MB), so one disc takes around ~60 mins. does anybody have suggestions for an external usb-drive (can be a dvd-writer/bluray-reader, or even dvd-/bluray-writer combination)? would be perfect, if those are tested/known to work with makemkv-rdp container. would appreciate any ideas, thx.

well, well, i'll most probably rearrange my drives, so in the end the samsung will end up on a sata port of the MB. so it's then not connected any longer to the LSI and probably TRIM will then work.

Looking at your mb manual this is the problem, SAS3 is onboard LSI, when we say onboard controller we mean the PCH ports, connect the SSD to one of those and trim should work. just wanted to post back, that the SSD is connected to the LSI Logic SAS3008 chip – but you beat me well, i've choosen the faster SAS3 ports and usually passthrough of 3rd party controllers is easier than the MB-ports. well, i'll probably need to reconsider how to utilize all ports of the board. i've passthrough'ed another LSI Logic SAS2008 pci card to unRAID as well. but it seems then same game for these LSI controllers.

No, default BTRFS supports TRIM, you usually get that error when the controller doesn't support it, looks like you're virtualizing unRAID, so maybe that's the cause (if you're using the mb controller). you're right, i do virtualize unRAID, in that hardware controllers are passthrough completely to unRAID. all (to me) known/used hardware features (esp. such as sleep function of hdd) do work properly. even all operations, which do change the boot usb-stick – so no tricks used/necessary here. the SSD is on the same controller (SAS3 from MB) as other HDDs. not an TRIM expert here, but my reading showed, that they use the fstrim command on mountpoints of filesystems and not on devices directly. well, i tried that too, but same result.

>> bonienl is it maybe because the cache device is using (the defaulted) BTRFS? reading up a bit reveals, that BTRFS should support TRIM, but (might) dependent on used mount options. maybe the only quick solution is to format the SSD with EXT4? this page might shed some light on my issue: https://kb.plesk.com/en/122080 using the command on the mountpoint of the cache drive "/mnt/cache" shows the exact same output (also for the discard_max_bytes).

well, i know usually it is sent by sendmail. i thought, that unRAID uses it's own script or small proggy, which is sending out the email with regard to the settings in the "SMTP Settings". but, it seems we have two different use cases here: 1st for sending out only the specified in "Notification Settings" and 2nd for all system generated output. strange in use case two is, that unRAID is already using all defined parameters of "SMTP Settings", but only replaces the sender address with the "root@"-part. in my opinion it seems to be a small step from here to using the specified "from" sending address.

no, 6.1.9 as per signature. but why is the cron job then ignoring the settings for smtp? it is using root@ instead of the setup email-address.

First thing to check is if your SSD supports trim # hdparm -I /dev/sdX | grep TRIM (X = reference to your cache disk) root@unRAID:~# hdparm -I /dev/sdb | grep TRIM * Data Set Management TRIM supported (limit 8 blocks) Second question: is your disk directly connected to your motherboard or do you use an adapter? it is directly connected and does support trim (Samsung Evo 850). thx. for looking into it.

yes, gives this error: root@unRAID:~# /sbin/fstrim -v /mnt/cache fstrim: /mnt/cache: FITRIM ioctl failed: Operation not supported

first off, a great thank you to bonienl for these wonderful suite of plug-ins. a few days ago i installed the SSD TRIM plug-in (i somehow managed to ignore it for quite a while, beside running other Dynamix plug-ins ) and set it to fire at 8am every day. the very next day i checked the logs of unRAID to look for (maybe) any entries belonging to the plug-in. low and behold i found this one (removed private informations): Jun 23 08:00:02 unRAID sSMTP[20482]: Creating SSL connection to host Jun 23 08:00:02 unRAID sSMTP[20482]: SSL connection using XXXX Jun 23 08:00:02 unRAID sSMTP[20482]: Authorization failed (535 5.7.8 https://support.google.com/mail/answer/14257 u64sm2150802wmd.8 - gsmtp) ok, a bit confused (for a moment) – what has caused this? out of nowhere (and never before) something tried to send an email via google. the next second i remembered, ey i got the new plug-in installed – maybe it has any defaults to send reports automatically. checked the "Notification Settings" in unRAID, but they where like i had them set up: no eMail-Notifications, only in browser; no email-account informations in the "SMTP Settings" area. so i went ahead and configured the "SMTP Settings" with my account informations (with different sending/receiving addresses). i verified the setup by using the "Test"-button and immediately received the test-email – all well i thought. and the very next day log-check showed this: 08:00:01 unRAID sSMTP[x]: RCPT TO:<[email protected]> (553 5.7.1 <[email protected]>: Sender address rejected: not owned by user email-account) this error says that something (most probably the plug-in, because didn't happen before) tried to use the sender email-address "[email protected]" to send an email to the (correctly) specified "[email protected]"-address. but now, it correctly did try to use the google email-servers, instead it used the specified one. after re-checking all settings and test-sending emails from the "SMTP Settings" tab i came to the conclusion, that (maybe) the plug-in (or any used parts of unRAID for sending emails) has a hard coded sending email-address (root@) and ignores the specified one. now, you could ask, why then not use the [email protected]. because of security concerns. this email-server checks the sending email-address against the provided email-account; and if it can't verify that it is allowed, it denies it, hence the error in the log. wrap up: had no log entries up to now which are email related (and nothing configured for it) and just exactly one second after the (since then) newly installed SSD_TRIM plug-in fired, i'm pretty much confident, that it is caused by it. maybe some things play together here (functions of unRAID which are used for sending the actual email, or combinations of Dynamix plug-ins) but i think it can be fixed to work as expected. sorry for the long post, but it (hopefully) helps much better to track down this bug. greets, oliver

ok, just had 2 runs and both times the DVB Adapter Drivers didn't get detected. i went this way: updated the plug-in to 2016.06.19a, then choose the new tbs-build, installed (over my previous install - should i've 1st need to deinstalled or install vanilla build?). rebooted: DVB Adapter Drivers not recognized. then updated to the now newer 2016.06.19b plug-in, installed TBS DVB-C 6.1.9 build, rebooted, same error – not recognizing the DVB Adapter Drivers. btw. i do see a line when booting up, shortly before the end, which writes: "File '/boot/config/plugins/UnraidDVB/ddbridge.conf' already there; not retrieving." want me to try something else? New build for you to test. Overwrite your existing one. just as a quick reply: installed, tuner got detected as DVB-C and TVHeadend also recognized it so this looks alreday pretty good! thank you. i probably will go on later today/tonight and will report back then.

ok, just had 2 runs and both times the DVB Adapter Drivers didn't get detected. i went this way: updated the plug-in to 2016.06.19a, then choose the new tbs-build, installed (over my previous install - should i've 1st need to deinstalled or install vanilla build?). rebooted: DVB Adapter Drivers not recognized. then updated to the now newer 2016.06.19b plug-in, installed TBS DVB-C 6.1.9 build, rebooted, same error – not recognizing the DVB Adapter Drivers. btw. i do see a line when booting up, shortly before the end, which writes: "File '/boot/config/plugins/UnraidDVB/ddbridge.conf' already there; not retrieving." want me to try something else?

thx. alot mate for your time/effort! ;-)

ok, back with news... i've setup my test machine with the new TBS-6205 card. unRAID DVB build 6.1.9 TBS installed and when verified via settings it shows: unRAID Version: 6.1.9 DVB Version: TBS Driver Version: 160219 DVB Kernel: Detected DVB Adapter Drivers: Detected for the docker i've choosen saargs "Tvheadend-Unstable-DVB-Tuners" which installed 4.1-2125~g2d15eca so all seems well ;-) but... in the network-setup wizard i see my tuner (card) identified as TBS 6205 DVBT/T2, so there's no mentioning of DVB-C (it supports both DVB T(2)/C-standards). this is also the only choice i get to choose from the drop-down menus "DVB-T Network". so clearly i can't setup/use it. searching the web brought me to this url: https://www.linuxtv.org/wiki/index.php/TBS6205 there the section "Driver" writes: "A switch between DVB T/T2 and DVB-C requires a recompile." so it seems that there needs to be made a choice of network-typ support at compile time. this brings me back to you guys and probably more precisly to CHBMB i kindly ask for help. thx. guys.

That looks like a good plan The 4.1 beta is in my opinion stable enough for normal use and have a wizard for setting up tvheadend. I try to update my unstable container about once a week, but if it's working you don't have to update When you install my container you will have to choose the one with tuners in the end of the name. If you don't, you will have no tuners available for tvheadend. I think the difference between mine and binhex is that his is based on arch Linux and mine on phusion base image. I'm not sure if he have incorporated the xmltv package in his container, in case that is needed for EPG. Maybe he will chime in. thx. saarg for clearing some things up i would then go with 4.1 unstable, cause i need epg-data (hopefully i can find a good source for german cable tv). :-)