fireplex

Just a general query, you seem to have two ways to connect Home Assistant to unRAID, this agent based one and this one solely using the unRAID API https://github.com/ruaan-deysel/ha-unraid Any recommendations which to use and will they both be developed going forward? Thanks.

Just upgraded from 7.1.4, looking good so far

I was trying to work out what was causing one of my disks to keep spinning up so installed File Activity plugin. I noticed I was getting these messages in it's logs and couldn't figure out why: * Downloads ** Aug 30 19:07:34 OPEN => /mnt/disk1/Downloads/ISOs/ubuntu-25.04-desktop-amd64.iso Aug 30 19:07:34 OPEN => /mnt/disk1/Downloads/ISOs/Win11_24H2_EnglishInternational_x64.iso Aug 30 19:07:34 OPEN => /mnt/disk1/Downloads/ISOs/virtio-win-0.1.225-2.iso Aug 30 19:08:14 OPEN => /mnt/disk1/Downloads/ISOs/ubuntu-25.04-desktop-amd64.iso Aug 30 19:08:14 OPEN => /mnt/disk1/Downloads/ISOs/Win11_24H2_EnglishInternational_x64.iso Aug 30 19:08:14 OPEN => /mnt/disk1/Downloads/ISOs/virtio-win-0.1.225-2.iso Aug 30 19:08:23 OPEN => /mnt/disk1/Downloads/ISOs/ubuntu-25.04-desktop-amd64.iso Aug 30 19:08:23 OPEN => /mnt/disk1/Downloads/ISOs/Win11_24H2_EnglishInternational_x64.iso Aug 30 19:08:23 OPEN => /mnt/disk1/Downloads/ISOs/virtio-win-0.1.225-2.iso Aug 30 19:13:43 OPEN => /mnt/disk1/Downloads/ISOs/ubuntu-25.04-desktop-amd64.iso Aug 30 19:13:43 OPEN => /mnt/disk1/Downloads/ISOs/Win11_24H2_EnglishInternational_x64.iso Aug 30 19:13:43 OPEN => /mnt/disk1/Downloads/ISOs/virtio-win-0.1.225-2.iso Aug 30 19:13:55 OPEN => /mnt/disk1/Downloads/ISOs/ubuntu-25.04-desktop-amd64.iso Aug 30 19:13:55 OPEN => /mnt/disk1/Downloads/ISOs/Win11_24H2_EnglishInternational_x64.iso Aug 30 19:13:55 OPEN => /mnt/disk1/Downloads/ISOs/virtio-win-0.1.225-2.iso Turns out each time I navigate to the Dashboard tab in the unRAID GUI it caused this access. I have two VMs configured, not running, and they point at the above files. Disabling VM Manager stops this issue.

The plugin is displaying this message: The Tailscale key will expire in 7 days on Fri, 11 Apr 2025 00:58:53 GMT. Couple of questions/comments: 1. What do I need to do about this? 2. Can the plugin display the answer to question 1 so people don't need to ask Thanks!

I suspect so yes, just wondered if anyone else has seen this or it's just me and I need to dig further.

I am running 7.0.0 but saw this issue with previous releases. I like to configure my dashboard, things like remove the VPN section, move tailscale and GPU readings around, have the main display set to read/write per sec etc etc. This all works fine, but I am finding after a random number of days that things move back, eg tailscale section or GPU move back to default position at bottom of screen, main section changes back to total number reads/writes. I'm running Firefox on Linux, has anyone else experienced this?

OK. Problem is mover will then move it back to array. Would just be good if a modified file on the array is written to cache rather than array but guess it just doesn't work that way,

You mean move owncloud.db to the cache disk ?

I have nextcloud docker installed, it has it's own share Nextcloud that is set to cache -> array File activity plugin is reporting: ** /mnt/user/Nextcloud ** Dec 15 15:20:00 OPEN => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:20:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:20:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:20:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:20:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:20:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:20:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:20:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:20:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:25:00 OPEN => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:25:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:25:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:25:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:25:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:25:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:25:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:25:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Dec 15 15:25:00 MODIFY => /mnt/disk1/Nextcloud/owncloud.db Mover runs every day and moves from cache to array as expected. Nextcloud seems to modify owncloud.db quite frequently even if not used causing array disk1 and parity to spin up. It seems that any modification to a file already present on the array is done straight to array, I was hoping the modified file would be written to my cache disk (SSD) and not the array but that doesn't seem the case - any way around this please to prevent the spin-ups of disk1 and parity?

You sir are a star!! We have a signal, and we have services: Thanks so much for the assistance, my card lives again 😀

Hi, thanks very much! Please don't put yourself out on my behalf, whenever you have time, it is much appreciated 🙂

Hi, https://github.com/tbsdtv/linux_media is the repository where the merge request was made 3 weeks ago. How often do you compile from there? Thanks.

OK thanks. Yes everything is wired correctly, I tried with external power also (although never needed it before), I have tried the mxl58x.mode but that doesn't apply to this card and didn't help. I physically checked my card and it has two ISL6422B chips onboard, I am thinking due to those kernel messages that they are not being driven correctly and producing any output to the LNBs (as per my multimeter testing): 28.494167] DVB: Unable to find symbol isl6422_attach() I found this thread that I don't totally understand but it does seem to imply there is an issue caused by newer kernels https://github.com/ljalves/linux_media/issues/143 , it points to https://github.com/tbsdtv/linux_media/pull/361 Maybe the other users who have downloaded this plugin don't have a DVB-S card with this chip?

I tried LibreELEC but they don't find my card. At some point in the past, did this plugin have another option for TBS cards, eg. closed source ?

I could try and upgrade to 7, are you thinking a newer kernel (presumably) may help?

Tried a Windows box but it couldn't even find the card, so that was a non starter. I've tried everything I can think of in tvheadend, I had previous notes on how to configure it and they didn't work either. Is there anyway I can get dvbscan / dvb-apps installed on unRAID so I could try those at the CLI ?

Just as an update I tried my Plex docker which did tune before, and that's also no longer finding any channels. I'll see if I can try Windows tomorrow.

Thanks for checking, it could be the card has a HW fault as I haven't used it for some time - I will see if I can find a Windows PC to try it in. Yes, this is a fresh install of TVHeadend with a new appdata.

Hi, Wondered if anyone can help? I did have my TBS 6984 quad DVB-S2 card working with this plugin fine a few years ago, recently I have tried installing the card again and using the TBS OpenSource driver option but it looks like there is a problem somewhere, I am seeing: root@Tower:~# dmesg|grep -i dvb [ 0.000000] Command line: BOOT_IMAGE=/bzimage initrd=/bzroot saa716x_tbs-dvb.int_type=1 [ 0.058421] Kernel command line: BOOT_IMAGE=/bzimage initrd=/bzroot saa716x_tbs-dvb.int_type=1 [ 25.266293] dvbdev: DVB: registering new adapter (SAA716x dvb adapter) [ 28.491089] DVB: Unable to find symbol isl6422_attach() [ 28.491666] SAA716x Budget 0000:03:00.0: DVB: registering adapter 0 frontend 0 (TurboSight TBS 6984 DVB-S/S2)... [ 28.491905] dvbdev: DVB: registering new adapter (SAA716x dvb adapter) [ 28.494167] DVB: Unable to find symbol isl6422_attach() [ 28.494722] SAA716x Budget 0000:03:00.0: DVB: registering adapter 1 frontend 0 (TurboSight TBS 6984 DVB-S/S2)... [ 28.494937] dvbdev: DVB: registering new adapter (SAA716x dvb adapter) [ 28.497367] DVB: Unable to find symbol isl6422_attach() [ 28.497925] SAA716x Budget 0000:03:00.0: DVB: registering adapter 2 frontend 0 (TurboSight TBS 6984 DVB-S/S2)... [ 28.498173] dvbdev: DVB: registering new adapter (SAA716x dvb adapter) [ 28.500750] DVB: Unable to find symbol isl6422_attach() [ 28.501310] SAA716x Budget 0000:03:00.0: DVB: registering adapter 3 frontend 0 (TurboSight TBS 6984 DVB-S/S2)... [ 90.605334] SAA716x Budget 0000:03:00.0: DVB: adapter 3 frontend 0 frequency 0 out of range (950000..2150000) [ 90.686522] SAA716x Budget 0000:03:00.0: DVB: adapter 2 frontend 0 frequency 0 out of range (950000..2150000) [ 92.171488] SAA716x Budget 0000:03:00.0: DVB: adapter 1 frontend 0 frequency 0 out of range (950000..2150000) [ 92.238677] SAA716x Budget 0000:03:00.0: DVB: adapter 0 frontend 0 frequency 0 out of range (950000..2150000) Note the isl6422_attach issue. I have measured the voltage out of my DVB-S2 card for the LNBs and it should be between 13 and 18 V DC but I get nothing. A quick google on ISL6422 shows it's responsible to providing power to LNBs so I am guessing this is the issue. Note the card appears under /dev/dvb fine and configures in tvheadend container but a scan finds nothing and reports faint or no signal. Any idea's please? (I tried libreelec driver and that doesn't find the card at all). Thanks 🙂

OK, I see 6.12.8 has just been released so will check that. I do not have the Parity Check Tuning plugin installed, so will have a look at that also. Thanks for the assistance.

Ah that would explain it, thanks. I presume just need to wait for a new release for the bug fix?

Hi, I have had prior warnings of parity errors for a couple of weeks now. Yesterday I replaced the parity drive with a larger drive, the parity rebuild finished this morning but I received a notification notice saying parity errors, this is from /boot/config/plugins/dynamix/notifications/archive (I cleared it from onscreen) :- -rw------- 1 root root 206 Feb 16 07:35 Unraid_Parity_Sync_1708068901.notify <---------------- this morning root@Tower:/boot/config/plugins/dynamix/notifications/archive# cat YD191511891GB cat: YD191511891GB: No such file or directory root@Tower:/boot/config/plugins/dynamix/notifications/archive# cat Unraid_Parity_Sync_1708068901.notify timestamp=1708068901 event=Unraid Parity-Sync subject=Notice [TOWER] - Parity-Sync finished (2591 errors) description=Duration: 18 hours, 33 minutes, 36 seconds. Average speed: 119.8 MB/s importance=normal So the above reports 2591 errors. However, my GUI shows: 0 errors reported. So, why the discrepancy between the notification I received and the GUI? Thanks!

Hmm, that's a bit worrying. OK thanks for letting me know.

Yes I saw that thread and the comment about is this something you installed. Hence my query on this thread, as I have not knowingly installed elogind...

Ok thanks, I'll check for that 👍