JorgeB

You have, RAM is running @ 3200MHz, 1st gen Ryzen officially supports 2133Mhz max with 4 SR DIMMs.

Next beta is going to align the partition on SSDs on the 1MiB boundary, like Windows does, this should improve performance, try that that once it's available, you'll need to reformat the cache though.

Only btrfs supports pools, xfs can only be single device.

Lots of ATA errors, looks more like a connection issue, start by replacing both cables.

Any new VM will default to virtio-net, existing VMs need to be updated.

Changed Status to Closed Changed Priority to Other

Overclocked RAM is a know issue with Ryzen, see here, also check the power supply idle control setting, even if before you were overclocking you should stop.

It's very easy to confirm if it's this same issue, the line above always appears when the shares go away.

Please remind me, is this issue mainly when writing to cache SSD/pool or also when writing to array disks?

Main difference it that on the array you have individual data drives each with its own filesystem protected by one or two parity disks, each pool is one btrfs filesystem that can be or not redundant, you can use any of the available btrfs profiles, depending on the number of devices.

Yes, this is an old issue, not related to this release, it appears to be a fuse issue that happens when a file is removed and then moved, I believe it happens mostly when using for example a media processing docker.

Now it wouldn't be able to sync 100% because of the read errors. Correct, parity needs all others disks except one to recover, so a known bad disk should be replaced ASAP or if another one fails you'll be in trouble.

Almost certainly unrelated, if there's nothing logged and it started doing it out of the blue it's most likely a hardware issue, though you can still try safe model without VMs/dockers to rule that out first.

Yes, by default it creates a raid1 pool.

Like mentioned the fist check was non correct, so next one will still encounter the same errors.

Previous one was non correct.

IIRC it also happens with some B450 based boards, it doesn't happens with all Ryzen boards, regardless of chipset, best bet it to use v6.9.

Yep.

I'm not seeing any disk read errors, there are some ATA errors on disk7, and since the disk look healthy it could be the typical SASLP problem, parity was updated after some of those, possibly incorrectly, you can swap that disk with another one using the onboard SATA ports and run another check, also I would recommend replacing the SASLP with an LSI ASAP.

Please post the diagnostics instead: Tools -> Diagnostics

Problem with the onboard SATA controller, this is quite common with Ryzen boards, there are several reports that using the newer kernel on the v6.9 betas fixes the problem.

It should work with the next beta.

Sure: C:\iperf>iperf3 -c 192.168.1.10 Connecting to host 192.168.1.10, port 5201 [ 4] local 192.168.1.6 port 51796 connected to 192.168.1.10 port 5201 [ ID] Interval Transfer Bandwidth [ 4] 0.00-1.00 sec 356 MBytes 2.98 Gbits/sec [ 4] 1.00-2.00 sec 263 MBytes 2.20 Gbits/sec [ 4] 2.00-3.00 sec 474 MBytes 3.98 Gbits/sec [ 4] 3.00-4.00 sec 467 MBytes 3.90 Gbits/sec [ 4] 4.00-5.00 sec 371 MBytes 3.13 Gbits/sec [ 4] 5.00-6.00 sec 464 MBytes 3.89 Gbits/sec [ 4] 6.00-7.00 sec 447 MBytes 3.75 Gbits/sec [ 4] 7.00-8.00 sec 543 MBytes 4.56 Gbits/sec [ 4] 8.00-9.00 sec 619 MBytes 5.19 Gbits/sec [ 4] 9.00-10.00 sec 712 MBytes 5.98 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth [ 4] 0.00-10.00 sec 4.61 GBytes 3.96 Gbits/sec sender [ 4] 0.00-10.00 sec 4.61 GBytes 3.96 Gbits/sec receiver iperf Done. C:\iperf>iperf3 -c 192.168.1.10 -R Connecting to host 192.168.1.10, port 5201 Reverse mode, remote host 192.168.1.10 is sending [ 4] local 192.168.1.6 port 51814 connected to 192.168.1.10 port 5201 [ ID] Interval Transfer Bandwidth [ 4] 0.00-1.00 sec 462 MBytes 3.87 Gbits/sec [ 4] 1.00-2.00 sec 369 MBytes 3.10 Gbits/sec [ 4] 2.00-3.01 sec 378 MBytes 3.15 Gbits/sec [ 4] 3.01-4.00 sec 320 MBytes 2.70 Gbits/sec [ 4] 4.00-5.01 sec 349 MBytes 2.90 Gbits/sec [ 4] 5.01-6.01 sec 384 MBytes 3.22 Gbits/sec [ 4] 6.01-7.00 sec 427 MBytes 3.61 Gbits/sec [ 4] 7.00-8.00 sec 417 MBytes 3.50 Gbits/sec [ 4] 8.00-9.00 sec 443 MBytes 3.72 Gbits/sec [ 4] 9.00-10.00 sec 379 MBytes 3.18 Gbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 3.84 GBytes 3.30 Gbits/sec 7 sender [ 4] 0.00-10.00 sec 3.84 GBytes 3.30 Gbits/sec receiver iperf Done.

Best bet is btrfs restore on the link above, then re-format.

Please post the diagnostics: Tools -> Diagnostics (after trying to format it)