BackupAddict

Thank-You for the advice. Was on my list of possibles but helps to not be randomly trying stuff if more experienced folk can point one the right direction. Server was a little grumpy shutting down as it hung trying to unmount my cache, had to get monitor direct on server and powerdown from cli. no biggie needed to drag monitor in there anyway for the memtest. Running now will see what it finds, if no errors on first pass how many passes do people think rules out mem problems? edit. nvm, within 40 mins of memtest got a fail error, now to isolate bios settings, what stick or mobo/slot or if need to re-seat. Some backup RAM that should be good, but dropping from 32GB to 16GB hurts lol Thank-you, assuming I don't have two things true at once likely resolved :)

Been running this server for close to 5 years problem free only a few reboots a year, so as with anything working a little rusty on setup and how things work. While I was at work today got reports from family plex was down, got home and found all my dockers not loaded and seems the cache has gone read only. Cache is a two SSD BTRFS RAID. Running short and extended SMART tests on both cache drives passing with no errors. Lots of space on cache available and Vdisk is only 51% used. Not an expert at scanning diagnostics but looks like around 7:44 this morning the BTRFS had a error and switched to read only <Aug 9 07:44:01 REMOTE kernel: BTRFS error (device sdb1): block=3999596822528 write time tree block corruption detected Aug 9 07:44:01 REMOTE kernel: BTRFS: error (device sdb1) in btrfs_commit_transaction:2537: errno=-5 IO failure (Error while writing out transaction) Aug 9 07:44:01 REMOTE kernel: BTRFS info (device sdb1 state E): forced readonly Aug 9 07:44:01 REMOTE kernel: BTRFS warning (device sdb1 state E): Skipping commit of aborted transaction./> Would really appreciate if anyone could point me in the right direction on this or point out any issues they see in attached diagnostics file I just exported. Lucky it is my Friday today so can try to get this sorted. Setup this server close to 5 years ago using Spaceinvader One video's and besides adding a few HDD's and cleaning dust it's just worked. Have to refresh memory and get back up to speed on Unraid configuration :D remote-diagnostics-20250810-0012.zip

Just been trying to fix this for the last hour. Came here and see I'm not alone, same as above screenshots. I will stop mucking around and check back tomorrow

Awesome thank-you for the details, all sorted now notifications arriving in my alert channel now. Easy once one know how but that said a simple chatid field in the UnRAID notification agent GUI for Telegram would sure be more user friendly than having to use terminal

Hmmm thx for the info, Just tried "apikey:chatid" but test didn't work, perhaps a day delay again.... not sure as the APIkey for my bot has a " : " in it perhaps that mucks things up. Nov 25 10:14:34 REMOTE ool www[5445]: /usr/local/emhttp/plugins/dynamix/scripts/agent 'test' 'Telegram.sh' Nov 25 10:14:51 REMOTE ool www[25433]: /usr/local/emhttp/plugins/dynamix/scripts/agent 'enable' 'Telegram.sh' Nov 25 10:14:54 REMOTE ool www[25433]: /usr/local/emhttp/plugins/dynamix/scripts/agent 'test' 'Telegram.sh' first test listed in log above worked, then I add chatid with apikey using ":" in between and get no test message popup, to my eyes no error on either not sure why no results again once chatid added. Where do you put this file? As I am just using the built in agent not a custom user script and an UnRAID nOOb still I will wait and see if it starts working later with "apikey:chatid" if I patiently wait again, but another way if this fails would be welcome. Not sure why its so easy cut and dry with other dockers, but built in UnRAID usage has been difficult for me

Well I am not sure why but after throwing my hands in the air and leaving it alone for a day, notifications starting coming in on my UnRAID notification bot. Now if I press the test button I get an instant message on telegram bot, yay But odd cause I didn't change anything just took a day to start working. Only thing I can't get sorted is how to get unRAID bot to post in my custom telegram channel I have that all the other bots for various dockers and other stuff post in to keep telegram cleaner. In Radarr docker for instance I can add the chat ID of my Notification channel into a field beside my bots API key and then they post in my unified notification channel instead of each bot posting in their own thread.

I am having issues as well setting up telegram agent in UnRAID. I can make the same bot work in Radarr and Sonarr where the GUI lets me add the "chatID" in a field. But the Unraid notification agent settings GUI doesn't have this. I get results in log and no error but nothing pops up on Telegram.... Nov 23 13:18:20 REMOTE ool www[9010]: /usr/local/emhttp/plugins/dynamix/scripts/agent 'enable' 'Telegram.sh' Nov 23 13:18:23 REMOTE ool www[9010]: /usr/local/emhttp/plugins/dynamix/scripts/agent 'test' 'Telegram.sh' Nov 23 13:20:27 REMOTE ool www[14897]: /usr/local/emhttp/plugins/dynamix/scripts/agent 'test' 'Telegram.sh' But setting up in a bot with Radarr docker on same UnRaid server works instantly, what am I missing? Found this in my searching and trying to figure this out is it related - https://github.com/limetech/webgui/pull/512