Maticks

I can ping from unraid to the docker. i managed to fix it through just changed to Host.

I tried this but didnt work still. Still can't ping the Unraid server.

I am hoping its just a setting somewhere i have missed. I have Home Assistant running on a VM as BR0 i have given it an ip on my lan of 10.0.10.248. my unraid server is 10.0.10.252 when i try ping 10.0.10.252 i can't reach it on the VM. I am trying to run the Unraid plugin on HA. I can access the HA server fine on the LAN though.

Not sure if anyone has seen this but since moving to an AM5 7700X Unraid just randomly stops responding. It feels more like the network driver stops working though, because when i boot back up after forcing a reboot i get a UPS Communcations error about it being unreachable. So that tells me the Kernel likely didnt crash the network card stopped working likely. Since I can't get diags downloaded with no network connection ive attached them anyone know what this might be? It's random sometimes its hours sometimes its days. tower-diagnostics-20240729-0017.zip.crdownload

Anyone ever seen these, i moved from an Intel Ethernet Card to another with an Intel Ethernet Card. I tried upgrading but that didn't make any difference. These messages weren't there before switching out the motherboard. Attaching Diagnotics, anyone have any suggestions on how to fix it. Jul 21 05:37:43 Tower kernel: veth7574e5c: renamed from eth0 Jul 21 05:37:43 Tower kernel: eth0: renamed from veth246d9d3 Jul 21 05:38:00 Tower kernel: veth246d9d3: renamed from eth0 Jul 21 05:38:01 Tower kernel: eth0: renamed from veth7257c17 Jul 21 05:38:17 Tower kernel: veth7257c17: renamed from eth0 Jul 21 05:38:18 Tower kernel: eth0: renamed from veth74ebec2 Jul 21 05:38:35 Tower kernel: veth74ebec2: renamed from eth0 Jul 21 05:38:35 Tower kernel: eth0: renamed from vethb478acf Jul 21 05:38:52 Tower kernel: vethb478acf: renamed from eth0 Jul 21 05:38:53 Tower kernel: eth0: renamed from veth6960e55 Jul 21 05:39:10 Tower kernel: veth6960e55: renamed from eth0 Jul 21 05:39:10 Tower kernel: eth0: renamed from veth8ff1cbc Jul 21 05:39:28 Tower kernel: veth8ff1cbc: renamed from eth0 Jul 21 05:39:28 Tower kernel: eth0: renamed from vethbe2c01a Jul 21 05:39:45 Tower kernel: vethbe2c01a: renamed from eth0 Jul 21 05:39:45 Tower kernel: eth0: renamed from vethe11298f Jul 21 05:40:03 Tower kernel: vethe11298f: renamed from eth0 Jul 21 05:40:03 Tower kernel: eth0: renamed from veth470aa43 Jul 21 05:40:19 Tower kernel: veth470aa43: renamed from eth0 Jul 21 05:40:19 Tower kernel: eth0: renamed from vethd2261d5 Jul 21 05:40:36 Tower kernel: vethd2261d5: renamed from eth0 Jul 21 05:40:36 Tower kernel: eth0: renamed from veth23b3f6b Jul 21 05:40:52 Tower kernel: veth23b3f6b: renamed from eth0 Jul 21 05:40:53 Tower kernel: eth0: renamed from veth96c40fb Jul 21 05:41:10 Tower kernel: veth96c40fb: renamed from eth0 Jul 21 05:41:10 Tower kernel: eth0: renamed from veth91b9029 Jul 21 05:41:27 Tower kernel: veth91b9029: renamed from eth0 Jul 21 05:41:27 Tower kernel: eth0: renamed from veth3c239da Jul 21 05:41:44 Tower kernel: veth3c239da: renamed from eth0 Jul 21 05:41:44 Tower kernel: eth0: renamed from veth62b354d Jul 21 05:42:01 Tower kernel: veth62b354d: renamed from eth0 Jul 21 05:42:02 Tower kernel: eth0: renamed from vetha5e03e2 Jul 21 05:42:18 Tower kernel: vetha5e03e2: renamed from eth0 Jul 21 05:42:19 Tower kernel: eth0: renamed from veth009bc2e Jul 21 05:42:36 Tower kernel: veth009bc2e: renamed from eth0 Jul 21 05:42:36 Tower kernel: eth0: renamed from veth705ed30 Jul 21 05:42:53 Tower kernel: veth705ed30: renamed from eth0 Jul 21 05:42:53 Tower kernel: eth0: renamed from veth15e9705 Jul 21 05:43:01 Tower kernel: veth15e9705: renamed from eth0 Jul 21 05:43:13 Tower kernel: eth0: renamed from veth791e18a Jul 21 05:43:30 Tower kernel: veth791e18a: renamed from eth0 Jul 21 05:43:31 Tower kernel: eth0: renamed from veth53e22e4 Jul 21 05:43:47 Tower kernel: veth53e22e4: renamed from eth0 Jul 21 05:43:48 Tower kernel: eth0: renamed from vethcbcc80c tower-diagnostics-20240720-1946.zip

6.12.8 is crashing for me the same way with BTRFS. I will try change out the motherboard, processor and memory see if that fixes it. its weird my main cache drive is fine just my second cache pool is having this issue. but a repair has no errors.

May 5 15:50:51 Tower kernel: BTRFS error (device sde1): parent transid verify failed on logical 13897975595008 mirror 2 wanted 1008412 found 1008417 May 5 15:50:51 Tower kernel: BTRFS error (device sde1): parent transid verify failed on logical 13897975595008 mirror 1 wanted 1008412 found 1008417 May 5 15:50:51 Tower kernel: BTRFS: error (device sde1: state A) in __btrfs_free_extent:3076: errno=-5 IO failure May 5 15:50:51 Tower kernel: BTRFS info (device sde1: state EA): forced readonly May 5 15:50:51 Tower kernel: BTRFS error (device sde1: state EA): failed to run delayed ref for logical 13897975300096 num_bytes 16384 type 176 action 2 ref_mod 1: -5 May 5 15:50:51 Tower kernel: BTRFS: error (device sde1: state EA) in btrfs_run_delayed_refs:2150: errno=-5 IO failure May 5 15:50:51 Tower kernel: BTRFS warning (device sde1: state EA): Skipping commit of aborted transaction. May 5 15:50:51 Tower kernel: BTRFS: error (device sde1: state EA) in cleanup_transaction:1992: errno=-5 IO failure happened a lot quicker this time

lots of people downgraded to 6.11.5 who ran into this but i can't seem to do that anymore? is there a command to force that version to downgrade ?

memtest has also passed

ive tried different sticks and in different slots works fine for 12 hours then starts error again. it's weird behaviour.

since upgrading to 6.12.10 ive had BRFS errors not on my main cache setup but my second cache pool. A reboot always fixes it, rolling back to 6.12.8 seems to stop the BRFS issues, but is there a fix here i can apply? tower-diagnostics-20240503-1654.zip.crdownload

What is the best way to replace my aging cache disks? I have them in a BTRFS Raid 1 Do i run a Balance then power down the server rip out one of the disks and replace it?

Yeah i do notice that, so what you guys are saying apart from a fancy newer LSI card and fresh cables. It won't really make any difference in speed with this many drives and 4T disks still in my system?

8TB around 20-24 hours. a faster LSI card i am assuming will cut that down with faster disk accesses.

Hi Unraid pplz, I have a LSI 9201-16i at the moment total of 15 disks second cache pool included or 2 Parity and 11 Data Drives on just the array. WD Red and Ironwolf 4T and 8T disks. I am looking to move onto a 9305-16i and recable all the SATA disks with the different adaptor type. Anyone have an idea of what speed increase ill see on the array or anyone have a 9305-16i and advise what speeds they see on their disks. Considering moving to 10T or 12T disks but the rebuilt times at the moment are rather long any increase is just going to make that process even longer.