Guillaurent

Hi folks I'm looking to upgrade my struggling current setup (Pentium G620 2 cores, 2 threads @2.6GHz from 2011) on the cheap. I have a 100€ second hand setup in the crosshairs I'd like to run by you: i3-10100 Gigabyte Z490M 16GB DDR4 The server is used by me and the wife with a workload consisting of: Serving file (obviously) over SMB Shares Nextcloud: I'd like to enable face recognition which my current setup struggles too much now Jellyfin: ideally with some 4k to 1080p transcoding, current setup has a hard time to do it Home Assistant which is no issue I was wondering is the integrated Intel UHD Graphics 630 would be up to the task. My goal is to have a low idle power setup, if you have inputs about that, it would be appreciated. Cheers

Finally finished the operations. I stopped every service running on the server (Docker, SMB, mover and parity check schedules...). I mounted a new 12TB disk with Unassigned Disk, copied everything in /mnt/user0 into that mount point using the File Manager in the unraid webgui. It took a while. Then did a check of all the data with diff: diff -rq --no-dereference /mnt/user0 /mnt/disks/diskIDIt took another while but no difference were found. Then powered down the system, removed all the HDD, installed the two new 12TB drives and powered up. Used New Config, configured the disk with the data as Disk 1, the other as Parity. Parity operation is still running but everything works like a charm. Thank you for the help. I love unraid :)

Thanks all, I should be receiving the new disks today. I'll try that. Actually I went over the docs (again again) and might have found the solution (although it's in the Legacy documentation): https://docs.unraid.net/legacy/FAQ/replacing-multiple-data-drives/#faster-method Looks a lot like the procedure @ConnerVT was suggesting. I'll disable everything besides the array during the procedure to avoid conflicts (SMB, Docker, mover and parity schedules). Thanks, while powered off, I'll change the SATA cables to be on the safe side. The disks have been showing warnings for a few months now.

That's a neat idea. Could I copy everything from the array to a 12TB disk and then use this disk as a data disk in a new config with the other 12TB disk as parity?

Hi Basically, all my data disks in the unraid array are failing. They've had a good life (over 65k hours for the younger) but it's time to become e-waste I think. I decided to replace all the disks in the array (Parity and data) with two 12TB disks (one for parity, the other as data). I'm using the Basic licence so 6 disks maximum (I'm using a cache disk as well), so I have 1 extra slot. Downtime on the array is not an issue. What would be the best way to do the switch? I would like to avoid too much stress on the data disks that are about to fail.

Hi Is there a way to configure Mover Tuning to move newer files from the Array to the Cache (Secondary > Primary) ? In conjunction with using MTIME, it would allow for frequently modified files to live in the Cache instead of spinning up the drive(s) each time. Am I missing the option? Edit: I think I've found what I was looking for. Rebalance shares: Yes

I haven't used anything else than 1 cache pool named cache so far. I though it would be named cache cache1 like disks are... If anyone knows how to identify cache mounting points, I (or someone else) could modify the script.

diskmv is such a lifesaver! I was going to make the exact same script myself and you saved me the trouble Since I coded it, I'm offering my contribution with the diskdu script. It checks the size of /mnt/user/ files or directories in each /mnt/disk*/ and /mnt/cache*/ where it is present. Do what you will with this. It comes with no waranty. #!/bin/bash # diskdu - Summarize disk usage of the set of unRAID user share directories # and/or files # # usage: diskdu [options] file... # # A du operation is made for every disk and every file given as parameters. usage(){ cat << EOF usage: diskdu [options] file... file... The set of files or directories. They can be specified as an absolute or relative path and can be relative to the current directory or the /mnt/user/ directory. Options: --help help, print this help message All other options from the du command can be used. See du --help EOF } [ ${DEBUG:=0} -gt 0 ] && set -x -v shopt -s extglob # Basically the only option understood by this script is --help. The rest is # passed down to du. ARGS=() while [[ $# -gt 0 ]]; do case "$1" in --help) usage exit 0 ;; *) # Default case: add to array of arguments to pass down to du. if [ -e "$1" ] then # File or directory, replace /mnt/user/... with /mnt/disk*/... FULLNAME=$(readlink -e "$1") # Handle relative path MERGEDIR="${FULLNAME#/mnt/*/}" # Remove any /mnt/*/ prefix if [ ! -e "/mnt/user/$MERGEDIR" ] then echo "'$1' is not a valid user share file or directory." >&2 usage >&2 exit 1 fi ARGS+=(/mnt/@(disk*|cache*)/"$MERGEDIR") else # Something for du to figure out ARGS+=("$1") fi ;; esac shift done du "${ARGS[@]}"

Hi there I'm happily running an unRAID box for quite a while now with an Win10 VM attached to the monitor. The Win10 VM has a 2TB vdisk mounted for user data "local" storage (Documents, Images...). I would like to back the content of this vdisk to a remote site but uploading the 2TB img file every time is way too much, a simple rsync would be plenty enough. Is it possible to mount (read only) the vdisk img file directly on the server (say in /mnt/temp/vdisk) while the VM is running in order to back the content up? I wanted to give it a shot but I don't really want to mess the vdisk image...

I've found the issue I was having. The incoming UDP traffic could not get through to the tvheadend container in Network type bridge (or custon bridge). Switching Network type to Host did the trick but I don't know if there's another way around it.

Hi I've configured tvheadend, antennas and Plex and I'm having the following error in Plex when playing the only channel I've configured yet (testing): I've put all three Docker container in host network mode and did not set any password in tvheadend for now: Antennas's config: I can play live TV (IPTV) from the tvheadend interface on my desktop (Win10 VM machine), I've added antennas to Plex LiveTV and Plex has found the channel, downloaded the Guide but cannot play it. Any ideas?

Thanks for the tip. I gave it a go and did some further testing and it seems that the problem is with codec parameters: root@Tower:~# docker exec tvheadend ffmpeg -i "rtsp://mafreebox.freebox.fr/fbxtv_pub/stream?namespace=1&service=201&flavour=sd" ffmpeg version 4.3.1 Copyright (c) 2000-2020 the FFmpeg developers built with gcc 9.3.0 (Alpine 9.3.0) configuration: --prefix=/usr --enable-avresample --enable-avfilter --enable-gnutls --enable-gpl --enable-libass --enable-libmp3lame --enable-libvorbis --enable-libvpx --enable-libxvid --enable-libx264 --enable-libx265 --enable-libtheora --enable-libv4l2 --enable-libdav1d --enable-postproc --enable-pic --enable-pthreads --enable-shared --enable-libxcb --enable-libssh --disable-stripping --disable-static --disable-librtmp --enable-vaapi --enable-vdpau --enable-libopus --enable-libaom --disable-debug libavutil 56. 51.100 / 56. 51.100 libavcodec 58. 91.100 / 58. 91.100 libavformat 58. 45.100 / 58. 45.100 libavdevice 58. 10.100 / 58. 10.100 libavfilter 7. 85.100 / 7. 85.100 libavresample 4. 0. 0 / 4. 0. 0 libswscale 5. 7.100 / 5. 7.100 libswresample 3. 7.100 / 3. 7.100 libpostproc 55. 7.100 / 55. 7.100 [rtsp @ 0x154c3d28e5c0] UDP timeout, retrying with TCP [rtsp @ 0x154c3d28e5c0] method PAUSE failed: 551 Option Not Supported rtsp://mafreebox.freebox.fr/fbxtv_pub/stream?namespace=1&service=201&flavour=sd: could not find codec parameters Fixed the UDP timeout, did not change much: root@Tower:~# docker exec tvheadend ffmpeg -f rtsp -rtsp_transport udp -i "rtsp://mafreebox.freebox.fr/fbxtv_pub/stream?namespace=1&service=201&flavour=sd" ffmpeg version 4.3.1 Copyright (c) 2000-2020 the FFmpeg developers built with gcc 9.3.0 (Alpine 9.3.0) configuration: --prefix=/usr --enable-avresample --enable-avfilter --enable-gnutls --enable-gpl --enable-libass --enable-libmp3lame --enable-libvorbis --enable-libvpx --enable-libxvid --enable-libx264 --enable-libx265 --enable-libtheora --enable-libv4l2 --enable-libdav1d --enable-postproc --enable-pic --enable-pthreads --enable-shared --enable-libxcb --enable-libssh --disable-stripping --disable-static --disable-librtmp --enable-vaapi --enable-vdpau --enable-libopus --enable-libaom --disable-debug libavutil 56. 51.100 / 56. 51.100 libavcodec 58. 91.100 / 58. 91.100 libavformat 58. 45.100 / 58. 45.100 libavdevice 58. 10.100 / 58. 10.100 libavfilter 7. 85.100 / 7. 85.100 libavresample 4. 0. 0 / 4. 0. 0 libswscale 5. 7.100 / 5. 7.100 libswresample 3. 7.100 / 3. 7.100 libpostproc 55. 7.100 / 55. 7.100 rtsp://mafreebox.freebox.fr/fbxtv_pub/stream?namespace=1&service=201&flavour=sd: could not find codec parameters I tried to specify the input codec (h264) to no avail: root@Tower:~# docker exec tvheadend ffmpeg -f rtsp -rtsp_transport udp -codec h264 -i "rtsp://mafreebox.freebox.fr/fbxtv_pub/stream?namespace=1&service=201&flavour=sd" ffmpeg version 4.3.1 Copyright (c) 2000-2020 the FFmpeg developers built with gcc 9.3.0 (Alpine 9.3.0) configuration: --prefix=/usr --enable-avresample --enable-avfilter --enable-gnutls --enable-gpl --enable-libass --enable-libmp3lame --enable-libvorbis --enable-libvpx --enable-libxvid --enable-libx264 --enable-libx265 --enable-libtheora --enable-libv4l2 --enable-libdav1d --enable-postproc --enable-pic --enable-pthreads --enable-shared --enable-libxcb --enable-libssh --disable-stripping --disable-static --disable-librtmp --enable-vaapi --enable-vdpau --enable-libopus --enable-libaom --disable-debug libavutil 56. 51.100 / 56. 51.100 libavcodec 58. 91.100 / 58. 91.100 libavformat 58. 45.100 / 58. 45.100 libavdevice 58. 10.100 / 58. 10.100 libavfilter 7. 85.100 / 7. 85.100 libavresample 4. 0. 0 / 4. 0. 0 libswscale 5. 7.100 / 5. 7.100 libswresample 3. 7.100 / 3. 7.100 libpostproc 55. 7.100 / 55. 7.100 rtsp://mafreebox.freebox.fr/fbxtv_pub/stream?namespace=1&service=201&flavour=sd: could not find codec parameters I'm at lost now...

Hello I'm trying to get an IPTV RTSP mux to work. My Internet provider allows to stream local (French) TV channels from the "router box" (called Freebox). They provide a .m3u from which I extracted one stream for testing purposes: rtsp://mafreebox.freebox.fr/fbxtv_pub/stream?namespace=1&service=201&flavour=sd This URL works when opening in VLC. I created a IPTV network and a mux with the URL: And scan fails: 2021-07-30 00:00:40.901 epggrab: rtsp://mafreebox.freebox.fr/fbxtv_pub/stream?namespace=1&service=201&flavour=sd in Freebox TV - registering mux for OTA EPG 2021-07-30 00:00:40.904 subscription: 0010: "scan" subscribing to mux "rtsp://mafreebox.freebox.fr/fbxtv_pub/stream?namespace=1&service=201&flavour=sd", weight: 5, adapter: "IPTV", network: "Freebox TV", service: "Raw PID Subscription" 2021-07-30 00:00:55.900 mpegts: rtsp://mafreebox.freebox.fr/fbxtv_pub/stream?namespace=1&service=201&flavour=sd in Freebox TV - scan no data, failed 2021-07-30 00:00:55.900 subscription: 0010: "scan" unsubscribing I tried to use the local IP of the router (192.168.0.1) and I have the same error (works as well with VLC). I tested and the Docker container seems to access the port with no problem: root@Tower:~# docker exec -it tvheadend bash root@21234e9f20e5:/# nc -vz 192.168.0.1 554 192.168.0.1 (192.168.0.1:554) open root@21234e9f20e5:/# nc -vz mafreebox.freebox.fr 554 mafreebox.freebox.fr (212.27.XXX.XXX:554) open Here is what VLC has to say about the stream: Any idea why this wouldn't work? Using linuxserver/tvheadend:release-4.2

As said by metalchad, have you set the Outpur Dir parameter in the Unraid Docker Container to where you want rips to go?

Yep, reverting to 1.16.4 did it for me as well. No need to tinker with /ripper/settings.conf as well. I'll go back with lastest as soon as the problem is resolved. @rix I'll be happy to test things out if you need someone to.

Are you able to rip DVDs and such after this? I tried and I'm not. From what I gathered, MakeMKV is actually looking at ~/.MakeMKV/settings.conf

Here is what I've just tested. First, I removed everything related to ripper from my system (Docker containers, appdata folders and /out directory): Then, I reinstalled Ripper from CA: For the first test, I've put the Network Type to None and changed the Output Dir: Install log: Start log: I inserted a DVD and: For the second test, I left the Network Type to None and added my MakeMKV key to settings.conf: And restarted the container: And re-inserted the DVD: For the third and last test, I changed the Network Type to Host (as default): And re-re-inserted the DVD: As you can see, I didn't do anything fancy. The last test should be the same as a default install with the MakeMKV key in settings.conf. Hope this helps.

I did some testing and I don't think it checks anyting online: I tried installing a brand new instance with Network set as none and I'm having the same issue (with or without the key entered).

Hi I'm trying to rip a DVD using Ripper (fantastic container btw) and I'm having the same issue: /mnt/user/appdata/ripper/Ripper.log: MSG:1005,0,1,"MakeMKV v1.16.3 linux(x64-release) started","%1 started","MakeMKV v1.16.3 linux(x64-release)" MSG:5074,0,0,"Automatic checking for updates is enabled, you may disable it in preferences if you don't want MakeMKV to contact web server.","Automatic checking for updates is enabled, you may disable it in preferences if you don't want MakeMKV to contact web server." DRV:0,2,999,1,"BD-RE HL-DT-ST BD-RE BH16NS40 1.00","STUDIO_ONE_PAL","/dev/sr0" 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:5021,131332,1,"This application version is too old. Please download the latest version at http://www.makemkv.com/ or enter a registration key to continue using the current version.","This application version is too old. Please download the latest version at %1 or enter a registration key to continue using the current version.","http://www.makemkv.com/" Docker container log extract: *** Running /etc/my_init.d/ripper.sh... Using this daily? Please sponsor me at https://github.com/sponsors/rix1337 - any amount counts! Found settings.conf. Replacing beta key file. 27.07.2021 09:38:05 : Starting Ripper. Optical Discs will be detected and ripped within 60 seconds. 27.07.2021 09:38:09 : DVD detected: Saving MKV renamed '/out/Ripper/DVD/STUDIO_ONE_PAL' -> '/out/Ripper/DVD/finished/' 27.07.2021 09:38:10 : Done! Ejecting Disk I did buy a MakeMKV key and pasted in /mnt/user/appdata/ripper/settings.conf: app_Key = "M-yXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX_wpR2sl1" I also restarted the docker container and checked inside the container that the settings.conf was grabbed by /etc/my_init.d/ripper.sh: root@Tower:~# docker exec -i -t Ripper bash root@Tower:/# ls -al /root/.MakeMKV/ total 12 drwxr-xr-x 1 root root 82 Jul 27 09:26 . drwx------ 1 root root 92 Jul 27 09:09 .. -rw-rw-rw- 1 root root 2048 Jul 27 09:17 _private_data.tar -rw-r--r-- 1 root root 81 Jul 27 09:17 settings.conf -rw-rw-rw- 1 root root 194 Jul 27 09:19 update.conf I can't figure out why MakeMKV is still not working (it was working with this DVD a few weeks ago). Any idea?