s.Oliver

i've only tested briefly one tune/channel and that worked. my card is a Digital Devices Max A8i (cable). has 8-tuners and was heavily used in the past.

well, couldn't wait and tried my luck – and... it looks good! needs a bit more time to see the longevity/stability of all services, but well, for now, i'm happy.

i can't and don't want to say no. it's only my understanding of drivers for interfaces. well, someone with more knowledge of available drivers needs to chime in. but firewire is old and since a long time depreciated. i loved it back in the day, but alas not always the best technology wins in the long run.

i would imagine, that firewire support needs kernel drivers to be present for that I/O interface.

so basically this means i could move from 6.8.3 (with Unraid DVB PlugIn and so the custom kernel) to v6.9 out of the box and use this DVB-Drivers PlugIn (from ich777) and get my Digital Devices card for TVHeadend up-and-running in no time?! just want to be sure to have a fully supported solution.

looks good. all calm again. thx.

i've seen this behavior once by myself, but several times by others. in any case it wasn't necessary to start over. but i just remember it can be a hassle, to get it recognized again. latest case: friend couldn't use firefox to sign in locally to his server. it always used the plex.tv site to login in. after fidling around we used chrome browser and it worked immediately. you could also try to use this url once: http://[ip]:32400/manage maybe some of it helps

hey Maciej, i can report: it works! thanks alot! 😃

thx. mciekb! 🙂 i'll try out whenever i find a few minutes for the downtime

here runs unRAID 6.8.1 now as VM under Proxmox. all is fine so far, but i admit, i don't use VMs inside unRAID (as that can be very tricky with performance). using quite a few dockers and plug-ins, all runs fine. Proxmox as the hypervisor uses KVM/QEMU itself to run VMs. so it would be great to have QEMU Agent support for unRAID as being run as VM (the QEMU agent would then report some informations back to the hypervisor). there's one guy, which did a VMware Tools build for his ESXi as hypervisor. but (and that's fine) he won't/can't do it for the QEMU Agent. so if

hi Steven, i do run unRAID as VM under Proxmox v6.x and it uses a qemu-agent to talk to the hypervisor. so my question would be: do you see a way of compiling the necessary QEMU-Agent for unRAID, or is this out of question? a quick search for slackware based QEMU agent showed this for example: https://slackbuilds.org/repository/14.2/system/qemu-guest-agent/ that would be really great and very much appreaciated – and it would offer one more integration of unRAID into another great hypervisor (which is free and has no artifical limitations). and

thx., but i did that from beginning on. it never booted automatically from the USB stick – it entered the EFI shell. when intercepted while initializing BIOS and selecting the proper shown boot device (unRAID USB stick) it boots and everything is fine. not sure, why it doesn't automatically choose it. i'm running on Proxmox v6 and use UEFI/EFI boot because of passthrough'ing serveral PCI devices.

so today was the day for PROXMOX installation and virtualizing unRAID again. most of the stuff works as expected, but some things aren't up to expectations: a) booting unRAID (directly from USB stick) brings me every time into the EFI shell, even though i set all the right boot options in the PROXMOX BIOS. so with every reboot i need to enter the BIOS, set the USB stick as boot option and then it boots unRAID. looks like PROXMOX doesn't save the changes into the EFI partitions or so. b) even though i enabled nested virtualization (PROXMOX) my macOS VM (under unRAID

hey siwat, thanks for sharing this Adguard Home docker! i had PiHole running before, but this one has some nice features. two things popped up and i wanted to let you know about (docker has a dedicated IP): 1) the template shows 2 entries for the Web GUI (ports 6052 [it's under the Icon URL] and port 3000 [under the working directory setup]) – but none of them works. ONLY port 80 does. 2) whenever i try to connect to it via a fqdn (like adguard.mydomain.whatever) it only shows a blank page (this works for all my other dockers, so i could image, that some

i didn't want to go into deep of the concept of unRAIDs parity algorithm. so you're right, unRAID needs to be strict in writing the same sector to data/parity drive(s) at (more or less) at the same time (given how fast different drives are completing the request). so the slowest drive in the mix (which is in the data writing cycle – doesn't matter if parity or data) is responsible for the time needed (or how fast that write cycle will be completed). but, unRAID is not immune against data loss because of not finished write operations (whatever reason) and has no concept of a journal