flokason

Thank you for the help Yes that activity is no more, it looks normal now I will look up that pool monitoring, thank you

Thank you JorgeB I would appreciate any advice so I can prevent this happening again, and perhaps knowing how to fix it if it happens again Best regards tower-diagnostics-20240330-1052.zip

I got kind of depressed, google something Though I should delete everything from both of my cache drives and then restore it with appdata backup Did those commands shown on screenshot Dockers started to work And hevy read/write on my cahce drive I have literally know idea what it happening

I think I have to format and start from scratch on my cahce drives root@Tower:~# btrfs dev stats /mnt/cache [/dev/nvme0n1p1].write_io_errs 296591154 [/dev/nvme0n1p1].read_io_errs 454910 [/dev/nvme0n1p1].flush_io_errs 1525783 [/dev/nvme0n1p1].corruption_errs 16434475 [/dev/nvme0n1p1].generation_errs 13247 [/dev/nvme1n1p1].write_io_errs 0 [/dev/nvme1n1p1].read_io_errs 0 [/dev/nvme1n1p1].flush_io_errs 0 [/dev/nvme1n1p1].corruption_errs 0 [/dev/nvme1n1p1].generation_errs 0

I do have the appdata backup plugin and backed up last time 25th of Mars Should I restore that?

I can only do it on Cache, not Cache 2 (they are mirror) I get this: [1/7] checking root items [2/7] checking extents [3/7] checking free space tree [4/7] checking fs roots [5/7] checking only csums items (without verifying data) [6/7] checking root refs [7/7] checking quota groups skipped (not enabled on this FS) Opening filesystem to check... Checking filesystem on /dev/nvme0n1p1 UUID: 7928d4a8-c447-4027-8952-2e27c43e51a9 found 511549218816 bytes used, no error found total csum bytes: 401640012 total tree bytes: 1649328128 total fs tree bytes: 993787904 total extent tree bytes: 166559744 btree space waste bytes: 372308360 file data blocks allocated: 1470746066944 referenced 495950946304

Like topic says, I updated from 6.12.8 to 6.12.9 and now I get this message on my dockers: Docker Service failed to start. Attached is my diognostics I would appreciate all help tower-diagnostics-20240329-2118.zip

Thank you that worked, Now forexample Dockers don't work But I do have access to a weeks old backup of my old flash drive. Do I gain anything on recreating my usb flashdrive from that backup?

Thanks for your help Should I just click "delete pool". And then I can start the array up again

Well that does sound good, I can't imagine that something crucial was on it So what should I do now. That is, how do I start my array without it correctly Thank you

Thanks for your replys I checked BIOS, did not see the drive. Took the drive out, in again. Power on, did not see in the BIOS There has been for some time 1 error on it in SMART, don't remember which one. I kind of thought it was no big deal. So if this drive is dead, what are we talking about. Can I restore everything without it? I think I was using it as cache for every 24 hours

So my usb flash drive died. And all my backups of it are on on my array, and encrypted rclone gdrive I was able to DMDE to restore my config file, or hopefully all of it. So I made a new USB drive with unraid, and c/p my recovered config file to the new USB I have gotten my licence to work on the new USB drive But it says my cache drive is missing. It is a 1TB m2 SSD. So there are no cables to connect/reconnect Now I am a afraid to do something wrong so destroy my data. So I will appreciate all help tower-diagnostics-20231215-1737.zip

Appears to be working! I deleted eth2 from the network-rules Thank you so much https://imgur.com/HpiOjBq Now I don't have a multiple MAC address Pretty strange problem though

Hi I'm pretty sure this file is now called "network-rules.cfg" See mine here: # PCI device 0x8086:0x15b8 (e1000e) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="e0:d5:5e:0d:a9:af", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" -- # PCI device 0x15b3:0x6750 (mlx4_core) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:02:c9:10:ee:ec", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" # PCI device 0x15b3:0x6750 (mlx4_core) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:02:c9:10:ee:ed", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2" # PCI device 0x15b3:0x6750 (mlx4_core) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:02:c9:10:ee:ed", ATTR{dev_id}=="0x0", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3" I tried deleting the network-rules.cfg and reboot. Did not work, came back like this. Aslo tried deleting the duplicate line of eth3 and rebooting. Did not work, came back like this Any more ideas? My diagnostics file is attached edit: Is it possible that the conflict is that it is sharing an IOMMO group with the PCI bridge? IOMMU group 1: [8086:1901] 00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 07) [15b3:6750] 01:00.0 Ethernet controller: Mellanox Technologies MT26448 [ConnectX EN 10GigE, PCIe 2.0 5GT/s] (rev b0) tower-diagnostics-20210519-0051.zip

I'll try that But right now the mellanox card is not installed, as I gave up on installing it yesterday, because it made it impossible to use eth0 as my old nic to get internet to my Unraid server I do have 4port i340 card installed, but it is bounded to pfsense VM, so perhaps thats the reason why i have no interface-rules.cfg Thanks for your help