LoyalScotsman

I don't this but it wouldn't fix them so moved everything off and formatted cache then copied bakc over So not sure if same issue but issue contuine see below Plexed started giving errors when trying to watch something so I rebooted plex docker to then not work at all, then I shut plex down and started it up again no change my server was down, turned docker off then back on and then said docker failed to start then stopped array for reboot and it got stuck at unmounting disk so found this forum ran commands on it but no luck see screenshot so I rebooted to see if this would bring docker back up but now I have the following on my cache disks they are showing as incorrect format but some dockers are working but not all. I have attached below daigs and syslogs before I rebooted see below will create another comment with fresh daigs and logs after reboot please help me on this one I have not yet formatted the cahce disk awaiting your responce vault101-syslog-20231015-1913.zip vault101-diagnostics-20231015-2013.zip

thank you this is probley why it didn't move the last corpted files, mover has just completed and by the looks of it the only files left is a some appdata files for drop box, the last time it corpted it was my plex DB which i managed to save so followed your sprit guide and now run a backup of this daily

also any idea on how to work out what files are corpted ?

hello not a problem i will do that in a min and then update this upon the next crash this might not be for days but i will quote you so you get a notification

ever since i upgrade to 6.12 on wards i have been experiencing random crashes where everything is completely unassessable when it crashes there is no display on a montior and also no access via url or putty, it will ping but that's about all it will do which this then results in me having to force a power down, last time i done this the cache drive got corpted but i was able to run some command and find out what folder was the problem but for some reason this time i am not able to do so can someone please review the daigs logs and sys logs to provide input to what has caused this ? current unraid version is 6.21.2 i can try upgrade to the next version but need to find out where the corrpted file is on my cache so i can do this so if anyone is able to work this out or provide a command to locate this corpted files that would be great this is the check cache spript i created and info it provided FYI the below is the first run of the spript after boot up there scan is done hourly so didn't want to upload it since its the same input each time Script Starting Oct 11, 2023 22:47.01 Full logs for this script are available at /tmp/user.scripts/tmpScripts/checkcachedrives/log.txt [/dev/sde1].write_io_errs 0 [/dev/sde1].read_io_errs 0 [/dev/sde1].flush_io_errs 0 [/dev/sde1].corruption_errs 0 [/dev/sde1].generation_errs 0 [/dev/sdg1].write_io_errs 0 [/dev/sdg1].read_io_errs 0 [/dev/sdg1].flush_io_errs 0 [/dev/sdg1].corruption_errs 16 [/dev/sdg1].generation_errs 0 Script Finished Oct 11, 2023 22:47.04 I have just disabled docker so i can run mover to remove everything from my cache drives cause last time it left the corpted files on cache please any assistance would be great this random crash is very random sometimes it can run for days some times weeks and then month or to before a crash vault101-diagnostics-20231013-0905.zip vault101-syslog-20231013-0804.zip

no problem starting to copy stuff from the pool over to array just now, and re-format the pool and copy back over, hopefully all goes sucesffully cause alot more errors in the logs this morning

sorry delayed response i went down the good old linux command route and CD into the dir then removed the dir that way

found how to do it please see results and fresh logs, hope to here from you soon UUID: 95913f78-fc8f-491e-b13a-789a9383ef8a Scrub started: Sat Sep 2 21:19:17 2023 Status: aborted Duration: 0:29:00 Total to scrub: 127.51GiB Rate: 70.81MiB/s Error summary: csum=34 Corrected: 33 Uncorrectable: 1vault101-diagnostics-20230902-2131.zip Unverified: 0

can you please confirm the progress to do this ? doing a google found the following command to get cache stats and i think that dont look good. think one of my cache disks has dropped off but not sure root@Vault101:~# btrfs dev stats /mnt/cache [devid:1].write_io_errs 37728126 [devid:1].read_io_errs 25990032 [devid:1].flush_io_errs 0 [devid:1].corruption_errs 232473 [devid:1].generation_errs 0 [/dev/sdg1].write_io_errs 1763 [/dev/sdg1].read_io_errs 1996297 [/dev/sdg1].flush_io_errs 0 [/dev/sdg1].corruption_errs 2 [/dev/sdg1].generation_errs 0 [/dev/sde1].write_io_errs 243721484 [/dev/sde1].read_io_errs 231592189 [/dev/sde1].flush_io_errs 0 [/dev/sde1].corruption_errs 335203 [/dev/sde1].generation_errs 0

logs attached, daigs attached Sep 2 19:12:58 Vault101 kernel: BTRFS warning (device sdg1): checksum verify failed on logical 158164238336 mirror 2 wanted 0x2a076ccd found 0x69294921 level 1 ran this to locate file when i go to the location its empty root@Vault101:~# find /mnt/cache -inum 158164238336 find: ‘/mnt/cache/appdata/plex/Library/Application Support/Plex Media Server/Metadata/TV Shows/3/495d21813339e6542d1713ccc0ed51d7c636e14.bundle/Contents/_stored/seasons/3/episodes/11’: Input/output error did a scrub check currently still running i think, first time so no sure if correct command for cache as found another forum on similar issue - root@Vault101:~# /usr/local/emhttp/plugins/dynamix/scripts/btrfs_scrub 'start' '/mnt/cache' '-r' but i have nothing to delete could i please have assistance and input on this please? his issue caused docker to crash and then had to force a re boot on my server so currently it is doing a parity check. vault101-diagnostics-20230902-1922.zip vault101-syslog-20230902-1829.zip Edit this appears to be spamming my syslogs now Sep 2 19:49:08 Vault101 kernel: BTRFS error (device sdg1: state EA): bdev /dev/sdg1 errs: wr 1763, rd 1994530, flush 0, corrupt 2, gen 0 Sep 2 19:49:08 Vault101 kernel: BTRFS error (device sdg1: state EA): bdev /dev/sdg1 errs: wr 1763, rd 1994531, flush 0, corrupt 2, gen 0 Sep 2 19:49:08 Vault101 kernel: BTRFS error (device sdg1: state EA): bdev /dev/sdg1 errs: wr 1763, rd 1994532, flush 0, corrupt 2, gen 0

So when i first set up this it was failing so i now have a selection of failed backups that i cannot delete, i have tried to delete them via kurseder but it refuses to delete any advice on how to delete the failed one because taking up unnessaray space

I have an other q

yes the oen from Squids i still have it installed but finally got around to updating to your one as per his notes when accessed his one

just seen this so i have excluded this from the next backup what contents is this excluding ? i suspect this will exclude users watched data ? which if i am correct the metadata only reason i question it is cause the old appdata backup ran fine and i don't want to completely remove the old one until i know this is working correctly

please can i get some assistance with this

Hello looking to see if can get assistance on this error please just set this up can see that the backup has failed on it within the DIR 18.07.2023 11:26:56][Main][info] Done! [18.07.2023 11:26:56][Main][warning] An error occurred during backup! RETENTION WILL NOT BE CHECKED! Please review the log. If you need further assistance, ask in the support forum. [18.07.2023 11:26:56][Main][info] DONE! Thanks for using this plugin and have a safe day [18.07.2023 11:26:56][Main][info] ❤️ ab.debug.log ab.log

thank you very much issue now resolved

Hello can i please have some assistance my delugevpn has been working perfect with nordvpn for years, but recently getting the below within the deluge logs and delugevpn wont launch with VPN enabled, but if disabled it allows me to access the web interface. i have tried several OVPN files, have rebooted unraid itself no change you can see the current OVPN files i am using and the credentials.conf file within the OVPN path recently updated to unraid 6.12.1 - originally was working rolled back to 6.11.5 and restore appdata from a backup on same day i upgraded and still doing this can someone please advice on how to fix this if you need anything else let me know

Hello so the working one is not on a custom network it runs through the basic bt home hub the none working one which was working prior to this issue occurring is on a customer network with Ubiquiti hardware i suspect the issue is with virgin because cannot access the sites required for prowlarr to work. so wonder if anyone is having this issue with virgin and how did they get around it ? does anyone know how to set up a indexer proxie to work with VPN ?

anyone able to assist ?

setting up prowlarr and flaresolverr the reason for setting up this is because Jackett was failing and looking up this i found prowlarr to be a better solution set this up on 2 systems one works one does not copied all settings from working unriad box to the one none working unraid box working box is on BT full fibre 1gb none working is on virgin 500mbs when adding an indexer i am getting the below error "Unable to connect to indexer, please check your DNS settings and ensure IPv6 is working or disabled. The SSL connection could not be established, see inner exception." the virgin box does not support ipv6 i have pulled the log files and event logs from prowlarr and also the logs from unraid can someone review and assist me please logs from unriad prolarr.txt event logs.txt log files.txt

@ljm42 i am getting the same can you let me know when sorted

thank you i will take this notes on but managed to resolved it by binning my current config file and DB and inputted the backup config file and DB and its now resolved

I have tried reverting back a backup on my server but when i go back 7 or 14 days the issue still persists. When i mean reverting a backup i am referring to the Radarr and appdata only. If possible what is the best steps on how to revert the Radarr version back its self and then i will test and if no go i will then move the backup DB over to see if this helps. I have had a google on how to revert the radarr version back but not having much luck do you have the steps on how to do it ?

Hello did you get a solution for this because mines has done the same i did revert back a week from backups to make no difference