eric90000

Thank you very much, that is great to know a combination of SATIP and tuner cards works well for you. I will check out those devices you mentioned. From what I gather from reading online, the general consensus seems to be that the SATIP approach is the easiest, as it rules out driver issues with physical PCIe cards. I had been trying to find a Digibit R1 SATIP device, which could be paired with something like a HDHomeRun for DVB-T. I really appreciate the screenshot of your setup - it will be handy when I come to setting mine up.

Thank you for the info appreciate it. Apologies if my post on the TVheadend thread appeared as a double post, I didn't intend that, as I had different questions in mind and tried my best to write different posts. I will continue researching, thanks again.

Hi! I am just researching at the moment before I purchase equipment. Is it possible to use a combination of tuners with TVheadend in Unraid - e.g. a PCIe DVB-S2 tuner alongside a networked DVB-T2 HDHomeRun quad tuner? Does anyone know if the TBS 6981 card (DVB-S2 Dual Tuner) is a known working card and would integrate with TVheadend with minimal issues? If anyone has a recommendation for a DVB-S2/DVB-T2combo tuner for Freeview & Freesat that is compatible with this TVheadend docker image (Unicable compatible for the satellite would be a big bonus) I would greatly appreciate the steer in the right direction! Thanks

Hey! I'm just getting into setting up TV on my Unraid server, and I have the chance to grab an older TBS 6981 card (DVB-S2 Dual Tuner) at the low price of €10. I just wanted to double check if this is a known working card and would integrate with TVheadend with minimal issues? I saw mention of this card a few years back in this thread, and I think someone was having issues with older drivers. It also mentions here that the card is Unicable compatible, however it specifically mentions the Windows driver for this so I am not 100% sure if Unicable would work with this card in Unraid? For the price I think it's probably worth the gamble regardless, but any help would be great. Thanks!

OK awesome, this is what I needed to hear! Thanks for the link. Looks like I can do it with the single built in NIC right? Just a case of setting up the VLAN on the server and on my network. I'll do some more digging into this to figure it out! Thanks again

Hey guys, I would like to run a game server on my UnRaid machine (Binhex Minecraft Server Docker container), and open it up to the internet via port forwarding so that friends outside of my network can join. The fear I have currently is that my server is on my main network VLAN, which has all of my other computers, mobile devices and other important things on it. The server itself also has other Docker containers and file shares, which share the same physical NIC connection and IP address to my router. This main VLAN can also speak to other VLANs I have in my home such as security cameras, IoT devices etc. Obviously anything exposed to the internet via open ports on a router is a risk in itself, and if something were to go wrong such as an intrusion or attack, then I could find myself in a situation where they have access to my home network right?.....at least I think this could happen? I had thought about building a dedicated machine for exposed services such as game servers, and making a separate VLAN for it with rules to isolate it from the main network so it can speak ONLY to the internet and nothing else. However this involves extra cost that I would rather not have to do considering I have a perfectly working UnRaid server as it is. I have been reading up on Docker networks and various NIC setups etc, and it seems like I could potentially segregate the Minecraft Docker container without having to spend too much money. I think this would mean even if someone managed to get in, they wouldn't be able to access anything else on the server/network right? With this in mind, would it be possible to install a separate NIC in the server, and connect it to my network via a separate physical cable (assigning it with a separate VLAN and isolating that network in the process), or could I potentially achieve this with the single onboard NIC I am currently using, and utilise some sort of VLAN tag that is only used by that container? I am in the Ubiquiti Unifi ecosystem, and I currently already have this server on a VLAN. Please let me know if I am completely overthinking this safety/paranoia wise - I have a habit of going over the top unnecessarily with security. If there's a better way to open up a docker container to the internet, while keeping the server and network safe I am all ears! Thanks guys

Finished successfully this time! Thanks for all the help. 12TB EMFZ WD Elements Drive - 'Preclear: total elapsed time: 62:16:06'

Great thank you gfjardim, I have updated the plugin and I am restarting the pre-clear on the same disk now. I will let you know how it goes.

Sent! Thank you for the assistance

Hi guys, Having some issues in the last few hours even since updating the Preclear Disk plugin. before the update it failed at 99% zeroing, now it is giving an error during the pre-read stage. I've attached the full log file but this jumps out at me: Dec 13 23:58:00 preclear_disk_9RKHVUBD_15516: Low memory detected, aborting... Dec 13 23:58:01 preclear_disk_9RKHVUBD_15516: S.M.A.R.T.: Error: Not sure why that would be the case as I have 16gb RAM and very little running on the server (a Plex RAM transcode could be an issue but the ram usage rarely goes above 15/20%). Any help greatly appreciated! It's a new 12TB drive. I could potentially try the alternative script, up to now I've just been using the default plugin settings. preclear_disk_9RKHVUBD_15516(1).txt

Today I had the exact same thing happen on my new shucked 12TB WD drive. It reached 99% writing zero then halted with an error. I noticed both Preclear Disk & Unassigned Devices plugins had updates available - I've now updated both and started a new pre-clear using the default script. Fingers crossed!

Hi guys, I'm brand new to Unraid and just started using my first trial key. I left a pre-clear disk running overnight and when I logged back on today I noticed it was no longer running. When I clicked start again it told me I can resume the previous instance, and it did indeed resume at approx 82% pre-read. For info this is a 12tb WD Elements drive connected via USB and using the included PSU. Once it passes pre-clear I will be shucking it and connecting it internally via SATA. Can anyone tell me why this stopped in the first place? Looks like the first error was a 'tower kernel: Sleep', so I'm thinking maybe it was an issue with the drive going to sleep? Here is the relevant section from the log. Error messages highlighted in red. Jun 6 10:47:12 Tower preclear_disk_38434A5542424C45[13553]: Pre-Read: progress - 20% read @ 183 MB/s Jun 6 12:39:46 Tower preclear_disk_38434A5542424C45[13553]: Pre-Read: progress - 30% read @ 175 MB/s Jun 6 14:37:44 Tower preclear_disk_38434A5542424C45[13553]: Pre-Read: progress - 40% read @ 165 MB/s Jun 6 16:41:37 Tower preclear_disk_38434A5542424C45[13553]: Pre-Read: progress - 50% read @ 159 MB/s Jun 6 18:53:05 Tower preclear_disk_38434A5542424C45[13553]: Pre-Read: progress - 60% read @ 150 MB/s Jun 6 21:14:05 Tower preclear_disk_38434A5542424C45[13553]: Pre-Read: progress - 70% read @ 136 MB/s Jun 6 23:47:43 Tower preclear_disk_38434A5542424C45[13553]: Pre-Read: progress - 80% read @ 128 MB/s Jun 7 00:36:36 Tower kernel: sleep[18933]: segfault at 1457c2431802 ip 00001457c2431802 sp 00007fff38420840 error 14 Jun 7 00:36:36 Tower kernel: Code: Bad RIP value. Jun 7 00:36:36 Tower kernel: bash[13544]: segfault at 1487f369f802 ip 00001487f369f802 sp 00007fffadf09000 error 14 Jun 7 00:36:36 Tower kernel: Code: Bad RIP value. Jun 7 00:36:36 Tower kernel: tmux: server[13543]: segfault at 14b9cc95f802 ip 000014b9cc95f802 sp 00007ffeb3b38500 error 14 Jun 7 00:36:36 Tower kernel: Code: Bad RIP value. Jun 7 06:03:57 Tower preclear_disk_38434A5542424C45[13921]: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --load-file /tmp/.preclear/38434A5542424C45.resume /dev/sdb Jun 7 06:03:57 Tower preclear_disk_38434A5542424C45[13921]: Preclear Disk Version: 1.0.16 Jun 7 06:03:57 Tower preclear_disk_38434A5542424C45[13921]: Restoring previous instance of preclear Jun 7 06:03:57 Tower preclear_disk_38434A5542424C45[13921]: S.M.A.R.T. info type: default Jun 7 06:03:57 Tower preclear_disk_38434A5542424C45[13921]: S.M.A.R.T. attrs type: default Jun 7 06:03:57 Tower preclear_disk_38434A5542424C45[13921]: Disk size: 12000105070592 Jun 7 06:03:57 Tower preclear_disk_38434A5542424C45[13921]: Disk blocks: 2929713152 Jun 7 06:03:57 Tower preclear_disk_38434A5542424C45[13921]: Blocks (512 bytes): 23437705216 Jun 7 06:03:57 Tower preclear_disk_38434A5542424C45[13921]: Block size: 4096 Jun 7 06:03:57 Tower preclear_disk_38434A5542424C45[13921]: Start sector: 512 Jun 7 06:03:58 Tower preclear_disk_38434A5542424C45[13921]: Continuing disk read from byte 9957313347584 Jun 7 06:03:58 Tower preclear_disk_38434A5542424C45[13921]: Pre-Read: dd if=/dev/sdb of=/dev/null bs=2097152 skip=9957313347584 count=2042791723008 conv=notrunc,noerror iflag=nocache,count_bytes,skip_bytes System Spec: Model: Custom M/B: MSI Z87-G45 GAMING (MS-7821) Version 1.0 - s/n: To be filled by O.E.M. BIOS: American Megatrends Inc. Version V1.9. Dated: 07/21/2014 CPU: Intel® Core™ i5-4670K CPU @ 3.40GHz HVM: Enabled IOMMU: Disabled Cache: 1024 KiB, 256 KiB, 6144 KiB Memory: 16 GiB DDR3 (max. installable capacity 32 GiB) Network: bond0: fault-tolerance (active-backup), mtu 1500 eth0: 100 Mbps, full duplex, mtu 1500 Kernel: Linux 4.19.107-Unraid x86_64 OpenSSL: 1.1.1d Uptime: 1 day, 01:33:45