Truenas Scale ZFS pool unreliable and disks write errors

I have a server with TrueNAS Scale 25.10.6 as a Proxmox VM, and I’m having issues with write errors on the disks in the main pool. These almost always occur on weekends, presumably during backups. The strange thing is that if I turn the server off and on again, the disks may not show any errors for months, but when I perform updates and restart the TrueNAS VM or even the Proxmox server, errors can appear on the disks in the pool over the next few days (it usually targets one disk and gives errors only to that one until it disconnects and degrades the pool).

The disks aren’t faulty, and these errors appear randomly, sometimes on one disk, sometimes on another. Since I’m used to these errors, one of these disks failed in the past few months, and I mistook it for the usual problem, cleaning up the ZFS pool and crashing the TrueNAS VM because the disk had been set to read-only mode. (i usually wait until week end to shut down and power back on the server in this cases)

I’ve tried everything, and at this point I no longer know how to achieve a stable and reliable configuration.

The pool consists of four 10TB ST10000NM013G drives in RAIDZ2 with a log vdev

of two U.2 drives, with the controller passed to the VM by Proxmox (I used to do disk passthrough with the same result.).

My configuration is as follows:

CPU – A-EPYC9004-2G5

Motherboard – MBD-H13SSL-NT latest BIOS

RAM – 128GB

HBA Controller – AOC-S3816L-16IT latest firmware

Drives – RAIDZ2 4x ST10000NM013G Log 2x U.2-NVME-TLC-4TB-ST-G4

The drives do not have any active power management options, either in the BIOS or TrueNAS.

These write errors when I reboot the VM can appear after a few hours, days, or weeks, or they can go away for months until the next reboot for updates. Sometimes, when I power on or reboot the VM or the newly started TrueNAS server, I find it already has some disk errors, so I shut down the server again until it boots without errors. When it works, it runs smoothly for months without errors.

this problem arose before I even added a vdev log if that helps.

Can anyone point me in the right direction?

truenas vm conf.txt (817 Bytes)

Did you confirm this with LONG SMART tests ?

How did you identify the disc ? By the sdX name or by serial number ? The sdX naming can change after each reboot.

If you have a spare boot device I would install Truenas bare metal as a test - to rule out any shenanigans that proxmox might be up to.

1 Like

this is almost never the disks. write errors that jump from drive to drive after a vm reboot is the hba/passthrough, not the ST10000s dying.

passing the whole AOC-S3816L-16IT is the right idea but you still need:

  • clean iommu group (nothing else in that group)
  • disk cache off on the vm
  • no virtio scsi mixed in for those drives
  • APM actually off on the seagates. “disabled in bios” is not enough, they still spin down under proxmox. smartctl -l scterc / hdparm -B 255 on the running tn vm

slog on virtualized u.2 is another footgun. if those nvmes share the reset path with the hba, a vm reboot can leave the log vdev half-dead and zfs starts throwing writes at the spinning disks. try importing without the slog once (zpool import -m) and see if the hopping errors stop.

post zpool status -v plus the currently “bad” disk smartctl -a and the proxmox cpu/machine type. q35 + host cpu, not i440fx.

and stop power cycling until the errors “go away”. that just hides the controller reset. zfs already marked the pool degraded.

I didn’t do a long test because I’m sure they’re fine because it’s been doing it since I bought the server on one of the 4 random disks and I find it difficult to have 4 failed disks since these errors, when on one or the other, appeared on all the disks.

If I had the possibility to put truenas on bare metal I would have already done it but unfortunately I need proxmox and I have other VMs on the server that all work perfectly.

In the kernel logs i found this error:
[Mon Aug 31 02:45:48 2026] sd 2:0:4:0: [sdg] tag#1906 FAILED Result: hostbyte=DID_SOFT_ERROR driverbyte=DRIVER_OK cmd_age=0s
[Mon Aug 31 02:45:48 2026] I/O error, dev sdg, sector 941747712 op 0x1:(WRITE) flags 0x0 phys_seg 15 prio class 2
[Mon Aug 31 02:45:48 2026] zio pool=Main-pool vdev=/dev/disk/by-partuuid/2b142e8b-3136-11ee-a874-992e5664a07f error=5 type=2 offset=480027279360 size=106496 flags=2148533376

Again, how did you identify them ? You can only be sure its a different disc after a reboot if you track them by serial number.

New discs fail. Even brand new ones. Especially brand new ones.

Not saying its a dying disc. So also look at the tips from @nite_route

1 Like

Sorry, I forgot to reply at this point. I check the serial numbers of each disk. I manually changed the two you see in the configuration file to X and Y so I don’t have to paste the serial numbers of my disks, but they only relate to the vdev. For the main pool, there’s HBA controller passthrough. Long tests are run monthly on all disks, and there are no errors in the smarlog for any of the disks.

This is the smart report for the last disk that gave errors:

smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.99-production+truenas] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Vendor: SEAGATE
Product: ST10000NM013G
Revision: E002
Compliance: SPC-5
User Capacity: 10,000,831,348,736 bytes [10.0 TB]
Logical block size: 512 bytes
Physical block size: 4096 bytes
LU is fully provisioned
Rotation Rate: 7200 rpm
Form Factor: 3.5 inches
Logical Unit id: 0x5000c500d9b7738f
Serial number: ZRT0GTT80000CXXXXXX
Device type: disk
Transport protocol: SAS (SPL-4)
Local Time is: Mon Aug 31 16:59:53 2026 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Temperature Warning: Enabled
Read Cache is: Enabled
Writeback Cache is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART Health Status: OK

Grown defects during certification
Total blocks reassigned during format
Total new blocks reassigned
Power on minutes since format
Current temperature = 33
Lifetime maximum temperature = 37
Lifetime minimum temperature = 31
Maximum temperature since power on = 36
Minimum temperature since power on = 32
Relative humidity = 255
Lifetime maximum relative humidity = 255
Lifetime minimum relative humidity = 255
Maximum relative humidity since power on = 255
Minimum relative humidity since power on = 255
Manufactured in week 24 of year 2022
Specified cycle count over device lifetime: 50000
Accumulated start-stop cycles: 90
Specified load-unload count over device lifetime: 600000
Accumulated load-unload cycles: 21772
Elements in grown defect list: 0

Vendor (Seagate Cache) information
Blocks sent to initiator = 1784895960
Blocks received from initiator = 1551464296
Blocks read from cache and sent to initiator = 932191696
Number of read and write commands whose size <= segment size = 21257887
Number of read and write commands whose size > segment size = 724994

Vendor (Seagate/Hitachi) factory information
number of hours powered up = 26919.70
number of minutes until next internal SMART test = 38

Seagate FARM log supported [try: -l farm]

Error counter log:
Errors Corrected by Total Correction Gigabytes Total
ECC rereads/ errors algorithm processed uncorrected
fast | delayed rewrites corrected invocations [10^9 bytes] errors
read: 0 0 0 0 0 5311.913 0
write: 0 0 0 0 0 3005.367 0

Non-medium error count: 0

Pending defect count:0 Pending Defects

[GLTSD (Global Logging Target Save Disable) set. Enable Save with ‘-S on’]
SMART Self-test log
Num Test Status segment LifeTime LBA_first_err [SK ASC ASQ]
Description number (hours)

1 Background short Completed - 26220 - [- - -]

2 Background short Completed - 893 - [- - -]

Long (extended) Self-test duration: 51615 seconds [14.3 hours]

Background scan results log
Status: no scans active
Accumulated power on time, hours:minutes 26919:42 [1615182 minutes]
Number of background scans performed: 0, scan progress: 0.00%
Number of background medium scans performed: 0
Device does not support General statistics and performance logging

Protocol Specific port log page for SAS SSP
relative target port id = 1
generation code = 0
number of phys = 1
phy identifier = 0
attached device type: SAS or SATA device
attached reason: power on
reason: hard reset
negotiated logical link rate: phy enabled; 12 Gbps
attached initiator port: ssp=1 stp=1 smp=1
attached target port: ssp=0 stp=0 smp=0
SAS address = 0x5000c500d9b7738d
attached SAS address = 0x5003048025704a05
attached phy identifier = 3
Invalid DWORD count = 8564496
Running disparity error count = 8297064
Loss of DWORD synchronization count = 7371
Phy reset problem count = 0
relative target port id = 2
generation code = 0
number of phys = 1
phy identifier = 1
attached device type: no device attached
attached reason: unknown
reason: unknown
negotiated logical link rate: phy enabled; unknown
attached initiator port: ssp=0 stp=0 smp=0
attached target port: ssp=0 stp=0 smp=0
SAS address = 0x5000c500d9b7738e
attached SAS address = 0x0
attached phy identifier = 0
Invalid DWORD count = 0
Running disparity error count = 0
Loss of DWORD synchronization count = 0
Phy reset problem count = 0

Do you see errors at the same time on both sides ? Proxmox and Truenas VM ?

dmesg -T | tail -200 ?

i don’t see any error proxmox side: (on the 29th i’ve made some changes to the passthrough settings if u see something strange on the logs. i’ve changed machine: q35 and added pcie=1 on hostpci0 and latest disk error are on 30th at 2:49)

[Sat Aug 29 18:41:21 2026] sd 1:0:3:0: [sdd] Synchronizing SCSI cache
[Sat Aug 29 18:41:21 2026] mpt3sas_cm0: clearing sas_address from hba_port entry: 0000000047f0abcd port: 0 from hba_port list
[Sat Aug 29 18:41:21 2026] mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x5000c500d9b78219)
[Sat Aug 29 18:41:21 2026] mpt3sas_cm0: removing handle(0x0017), sas_addr(0x5000c500d9b78219)
[Sat Aug 29 18:41:21 2026] mpt3sas_cm0: enclosure logical id(0x3003048025114a02), slot(0)
[Sat Aug 29 18:41:21 2026] mpt3sas_cm0: enclosure level(0x0000), connector name( C0.0)
[Sat Aug 29 18:41:21 2026] mpt3sas_cm0: remove hba_port entry: 0000000021bb5b96 port: 3 from hba_port list
[Sat Aug 29 18:41:21 2026] mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x5000c500d9b77bad)
[Sat Aug 29 18:41:21 2026] mpt3sas_cm0: removing handle(0x001a), sas_addr(0x5000c500d9b77bad)
[Sat Aug 29 18:41:21 2026] mpt3sas_cm0: enclosure logical id(0x3003048025114a02), slot(1)
[Sat Aug 29 18:41:21 2026] mpt3sas_cm0: enclosure level(0x0000), connector name( C0.0)
[Sat Aug 29 18:41:21 2026] mpt3sas_cm0: remove hba_port entry: 000000009646c628 port: 1 from hba_port list
[Sat Aug 29 18:41:21 2026] mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x5000c500f4450f69)
[Sat Aug 29 18:41:21 2026] mpt3sas_cm0: removing handle(0x0018), sas_addr(0x5000c500f4450f69)
[Sat Aug 29 18:41:21 2026] mpt3sas_cm0: enclosure logical id(0x3003048025114a02), slot(2)
[Sat Aug 29 18:41:21 2026] mpt3sas_cm0: enclosure level(0x0000), connector name( C0.0)
[Sat Aug 29 18:41:21 2026] mpt3sas_cm0: remove hba_port entry: 000000002c379e22 port: 2 from hba_port list
[Sat Aug 29 18:41:21 2026] mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x5000c500d9b7738d)
[Sat Aug 29 18:41:21 2026] mpt3sas_cm0: removing handle(0x0019), sas_addr(0x5000c500d9b7738d)
[Sat Aug 29 18:41:21 2026] mpt3sas_cm0: enclosure logical id(0x3003048025114a02), slot(3)
[Sat Aug 29 18:41:21 2026] mpt3sas_cm0: enclosure level(0x0000), connector name( C0.0)
[Sat Aug 29 18:41:21 2026] mpt3sas_cm0: remove vphy entry: 00000000eb3eb181 of port:0000000047f0abcd,from 0 port’s vphys list
[Sat Aug 29 18:41:21 2026] mpt3sas_cm0: remove hba_port entry: 0000000047f0abcd port: 0 from hba_port list
[Sat Aug 29 18:41:21 2026] mpt3sas_cm0: mpt3sas_transport_port_remove: removed: sas_addr(0x3002048025704a02)
[Sat Aug 29 18:41:21 2026] mpt3sas_cm0: removing handle(0x0011), sas_addr(0x3002048025704a02)
[Sat Aug 29 18:41:21 2026] mpt3sas_cm0: enclosure logical id(0x3003048025114a02), slot(16)
[Sat Aug 29 18:41:21 2026] mpt3sas_cm0: enclosure level(0x0000), connector name( C1.1)
[Sat Aug 29 18:41:21 2026] mpt3sas_cm0: sending message unit reset !!
[Sat Aug 29 18:41:21 2026] mpt3sas_cm0: message unit reset: SUCCESS
[Sat Aug 29 18:41:21 2026] vfio-pci 0000:01:00.0: resetting
[Sat Aug 29 18:41:22 2026] vfio-pci 0000:01:00.0: reset done
[Sat Aug 29 18:41:22 2026] tap101i0: entered promiscuous mode
[Sat Aug 29 18:41:22 2026] vmbr0: port 3(fwpr101p0) entered blocking state
[Sat Aug 29 18:41:22 2026] vmbr0: port 3(fwpr101p0) entered disabled state
[Sat Aug 29 18:41:22 2026] fwpr101p0: entered allmulticast mode
[Sat Aug 29 18:41:22 2026] fwpr101p0: entered promiscuous mode
[Sat Aug 29 18:41:22 2026] vmbr0: port 3(fwpr101p0) entered blocking state
[Sat Aug 29 18:41:22 2026] vmbr0: port 3(fwpr101p0) entered forwarding state
[Sat Aug 29 18:41:22 2026] fwbr101i0: port 1(fwln101i0) entered blocking state
[Sat Aug 29 18:41:22 2026] fwbr101i0: port 1(fwln101i0) entered disabled state
[Sat Aug 29 18:41:22 2026] fwln101i0: entered allmulticast mode
[Sat Aug 29 18:41:22 2026] fwln101i0: entered promiscuous mode
[Sat Aug 29 18:41:22 2026] fwbr101i0: port 1(fwln101i0) entered blocking state
[Sat Aug 29 18:41:22 2026] fwbr101i0: port 1(fwln101i0) entered forwarding state
[Sat Aug 29 18:41:23 2026] fwbr101i0: port 2(tap101i0) entered blocking state
[Sat Aug 29 18:41:23 2026] fwbr101i0: port 2(tap101i0) entered disabled state
[Sat Aug 29 18:41:23 2026] tap101i0: entered allmulticast mode
[Sat Aug 29 18:41:23 2026] fwbr101i0: port 2(tap101i0) entered blocking state
[Sat Aug 29 18:41:23 2026] fwbr101i0: port 2(tap101i0) entered forwarding state
[Sat Aug 29 18:41:24 2026] vfio-pci 0000:01:00.0: resetting
[Sat Aug 29 18:41:25 2026] vfio-pci 0000:01:00.0: reset done
[Sat Aug 29 18:41:25 2026] vfio-pci 0000:01:00.0: resetting
[Sat Aug 29 18:41:25 2026] vfio-pci 0000:01:00.0: reset done
[Sat Aug 29 18:45:10 2026] zd80: p1 p2
[Sat Aug 29 18:45:10 2026] nvme1n1: p1
[Sat Aug 29 18:45:10 2026] nvme0n1: p1
[Sat Aug 29 18:45:10 2026] tap101i0: left allmulticast mode
[Sat Aug 29 18:45:10 2026] fwbr101i0: port 2(tap101i0) entered disabled state
[Sat Aug 29 18:45:10 2026] fwbr101i0: port 1(fwln101i0) entered disabled state
[Sat Aug 29 18:45:10 2026] vmbr0: port 3(fwpr101p0) entered disabled state
[Sat Aug 29 18:45:10 2026] fwln101i0 (unregistering): left allmulticast mode
[Sat Aug 29 18:45:10 2026] fwln101i0 (unregistering): left promiscuous mode
[Sat Aug 29 18:45:10 2026] fwbr101i0: port 1(fwln101i0) entered disabled state
[Sat Aug 29 18:45:10 2026] fwpr101p0 (unregistering): left allmulticast mode
[Sat Aug 29 18:45:10 2026] fwpr101p0 (unregistering): left promiscuous mode
[Sat Aug 29 18:45:10 2026] vmbr0: port 3(fwpr101p0) entered disabled state
[Sat Aug 29 18:54:20 2026] nvme1n1: p1
[Sat Aug 29 18:54:20 2026] nvme0n1: p1
[Sat Aug 29 18:54:20 2026] vfio-pci 0000:01:00.0: resetting
[Sat Aug 29 18:54:20 2026] vfio-pci 0000:01:00.0: reset done
[Sat Aug 29 18:54:21 2026] tap101i0: entered promiscuous mode
[Sat Aug 29 18:54:21 2026] vmbr0: port 3(fwpr101p0) entered blocking state
[Sat Aug 29 18:54:21 2026] vmbr0: port 3(fwpr101p0) entered disabled state
[Sat Aug 29 18:54:21 2026] fwpr101p0: entered allmulticast mode
[Sat Aug 29 18:54:21 2026] fwpr101p0: entered promiscuous mode
[Sat Aug 29 18:54:21 2026] vmbr0: port 3(fwpr101p0) entered blocking state
[Sat Aug 29 18:54:21 2026] vmbr0: port 3(fwpr101p0) entered forwarding state
[Sat Aug 29 18:54:21 2026] fwbr101i0: port 1(fwln101i0) entered blocking state
[Sat Aug 29 18:54:21 2026] fwbr101i0: port 1(fwln101i0) entered disabled state
[Sat Aug 29 18:54:21 2026] fwln101i0: entered allmulticast mode
[Sat Aug 29 18:54:21 2026] fwln101i0: entered promiscuous mode
[Sat Aug 29 18:54:21 2026] fwbr101i0: port 1(fwln101i0) entered blocking state
[Sat Aug 29 18:54:21 2026] fwbr101i0: port 1(fwln101i0) entered forwarding state
[Sat Aug 29 18:54:21 2026] fwbr101i0: port 2(tap101i0) entered blocking state
[Sat Aug 29 18:54:21 2026] fwbr101i0: port 2(tap101i0) entered disabled state
[Sat Aug 29 18:54:21 2026] tap101i0: entered allmulticast mode
[Sat Aug 29 18:54:21 2026] fwbr101i0: port 2(tap101i0) entered blocking state
[Sat Aug 29 18:54:21 2026] fwbr101i0: port 2(tap101i0) entered forwarding state
[Sat Aug 29 18:54:23 2026] vfio-pci 0000:01:00.0: resetting
[Sat Aug 29 18:54:23 2026] vfio-pci 0000:01:00.0: reset done
[Sat Aug 29 18:54:23 2026] vfio-pci 0000:01:00.0: resetting
[Sat Aug 29 18:54:24 2026] vfio-pci 0000:01:00.0: reset done
[Sat Aug 29 18:56:48 2026] tap100i0: entered promiscuous mode
[Sat Aug 29 18:56:48 2026] vmbr0: port 4(fwpr100p0) entered blocking state
[Sat Aug 29 18:56:48 2026] vmbr0: port 4(fwpr100p0) entered disabled state
[Sat Aug 29 18:56:48 2026] fwpr100p0: entered allmulticast mode
[Sat Aug 29 18:56:48 2026] fwpr100p0: entered promiscuous mode
[Sat Aug 29 18:56:48 2026] vmbr0: port 4(fwpr100p0) entered blocking state
[Sat Aug 29 18:56:48 2026] vmbr0: port 4(fwpr100p0) entered forwarding state
[Sat Aug 29 18:56:48 2026] fwbr100i0: port 1(fwln100i0) entered blocking state
[Sat Aug 29 18:56:48 2026] fwbr100i0: port 1(fwln100i0) entered disabled state
[Sat Aug 29 18:56:48 2026] fwln100i0: entered allmulticast mode
[Sat Aug 29 18:56:48 2026] fwln100i0: entered promiscuous mode
[Sat Aug 29 18:56:48 2026] fwbr100i0: port 1(fwln100i0) entered blocking state
[Sat Aug 29 18:56:48 2026] fwbr100i0: port 1(fwln100i0) entered forwarding state
[Sat Aug 29 18:56:48 2026] fwbr100i0: port 2(tap100i0) entered blocking state
[Sat Aug 29 18:56:48 2026] fwbr100i0: port 2(tap100i0) entered disabled state
[Sat Aug 29 18:56:48 2026] tap100i0: entered allmulticast mode
[Sat Aug 29 18:56:48 2026] fwbr100i0: port 2(tap100i0) entered blocking state
[Sat Aug 29 18:56:48 2026] fwbr100i0: port 2(tap100i0) entered forwarding state
[Sat Aug 29 18:56:50 2026] tap102i0: entered promiscuous mode
[Sat Aug 29 18:56:50 2026] vmbr0: port 5(fwpr102p0) entered blocking state
[Sat Aug 29 18:56:50 2026] vmbr0: port 5(fwpr102p0) entered disabled state
[Sat Aug 29 18:56:50 2026] fwpr102p0: entered allmulticast mode
[Sat Aug 29 18:56:50 2026] fwpr102p0: entered promiscuous mode
[Sat Aug 29 18:56:50 2026] vmbr0: port 5(fwpr102p0) entered blocking state
[Sat Aug 29 18:56:50 2026] vmbr0: port 5(fwpr102p0) entered forwarding state
[Sat Aug 29 18:56:50 2026] fwbr102i0: port 1(fwln102i0) entered blocking state
[Sat Aug 29 18:56:50 2026] fwbr102i0: port 1(fwln102i0) entered disabled state
[Sat Aug 29 18:56:50 2026] fwln102i0: entered allmulticast mode
[Sat Aug 29 18:56:50 2026] fwln102i0: entered promiscuous mode
[Sat Aug 29 18:56:50 2026] fwbr102i0: port 1(fwln102i0) entered blocking state
[Sat Aug 29 18:56:50 2026] fwbr102i0: port 1(fwln102i0) entered forwarding state
[Sat Aug 29 18:56:50 2026] fwbr102i0: port 2(tap102i0) entered blocking state
[Sat Aug 29 18:56:50 2026] fwbr102i0: port 2(tap102i0) entered disabled state
[Sat Aug 29 18:56:50 2026] tap102i0: entered allmulticast mode
[Sat Aug 29 18:56:50 2026] fwbr102i0: port 2(tap102i0) entered blocking state
[Sat Aug 29 18:56:50 2026] fwbr102i0: port 2(tap102i0) entered forwarding state
[Sat Aug 29 18:56:50 2026] sd 19:0:0:0: [sde] Synchronizing SCSI cache
[Sat Aug 29 18:56:50 2026] sd 19:0:0:0: [sde] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[Sat Aug 29 18:57:02 2026] usb 6-1: reset SuperSpeed USB device number 2 using xhci-pci-renesas
[Sat Aug 29 18:57:02 2026] debugfs: ‘stream_id’ already exists in ‘ep02’
[Sat Aug 29 18:57:02 2026] debugfs: ‘stream_context_array’ already exists in ‘ep02’
[Sat Aug 29 18:57:02 2026] debugfs: ‘stream_id’ already exists in ‘ep03’
[Sat Aug 29 18:57:02 2026] debugfs: ‘stream_context_array’ already exists in ‘ep03’
[Sat Aug 29 18:57:02 2026] debugfs: ‘stream_id’ already exists in ‘ep06’
[Sat Aug 29 18:57:02 2026] debugfs: ‘stream_context_array’ already exists in ‘ep06’
[Sat Aug 29 18:57:02 2026] usb 5-2.1: reset full-speed USB device number 3 using xhci-pci-renesas
[Sat Aug 29 18:57:03 2026] usb 5-2.2: reset full-speed USB device number 4 using xhci-pci-renesas
[Sat Aug 29 18:57:03 2026] usb 5-2.3: reset full-speed USB device number 5 using xhci-pci-renesas
[Sat Aug 29 18:57:03 2026] usb 5-2.4: reset full-speed USB device number 6 using xhci-pci-renesas
[Sun Aug 30 05:08:48 2026] tap104i0: entered promiscuous mode
[Sun Aug 30 05:08:49 2026] vmbr0: port 8(fwpr104p0) entered blocking state
[Sun Aug 30 05:08:49 2026] vmbr0: port 8(fwpr104p0) entered disabled state
[Sun Aug 30 05:08:49 2026] fwpr104p0: entered allmulticast mode
[Sun Aug 30 05:08:49 2026] fwpr104p0: entered promiscuous mode
[Sun Aug 30 05:08:49 2026] vmbr0: port 8(fwpr104p0) entered blocking state
[Sun Aug 30 05:08:49 2026] vmbr0: port 8(fwpr104p0) entered forwarding state
[Sun Aug 30 05:08:49 2026] fwbr104i0: port 1(fwln104i0) entered blocking state
[Sun Aug 30 05:08:49 2026] fwbr104i0: port 1(fwln104i0) entered disabled state
[Sun Aug 30 05:08:49 2026] fwln104i0: entered allmulticast mode
[Sun Aug 30 05:08:49 2026] fwln104i0: entered promiscuous mode
[Sun Aug 30 05:08:49 2026] fwbr104i0: port 1(fwln104i0) entered blocking state
[Sun Aug 30 05:08:49 2026] fwbr104i0: port 1(fwln104i0) entered forwarding state
[Sun Aug 30 05:08:49 2026] fwbr104i0: port 2(tap104i0) entered blocking state
[Sun Aug 30 05:08:49 2026] fwbr104i0: port 2(tap104i0) entered disabled state
[Sun Aug 30 05:08:49 2026] tap104i0: entered allmulticast mode
[Sun Aug 30 05:08:49 2026] fwbr104i0: port 2(tap104i0) entered blocking state
[Sun Aug 30 05:08:49 2026] fwbr104i0: port 2(tap104i0) entered forwarding state
[Sun Aug 30 05:11:49 2026] zd160: p1
[Sun Aug 30 05:11:49 2026] tap104i0: left allmulticast mode
[Sun Aug 30 05:11:49 2026] fwbr104i0: port 2(tap104i0) entered disabled state
[Sun Aug 30 05:11:49 2026] fwbr104i0: port 1(fwln104i0) entered disabled state
[Sun Aug 30 05:11:49 2026] vmbr0: port 8(fwpr104p0) entered disabled state
[Sun Aug 30 05:11:49 2026] fwln104i0 (unregistering): left allmulticast mode
[Sun Aug 30 05:11:49 2026] fwln104i0 (unregistering): left promiscuous mode
[Sun Aug 30 05:11:49 2026] fwbr104i0: port 1(fwln104i0) entered disabled state
[Sun Aug 30 05:11:49 2026] fwpr104p0 (unregistering): left allmulticast mode
[Sun Aug 30 05:11:49 2026] fwpr104p0 (unregistering): left promiscuous mode
[Sun Aug 30 05:11:49 2026] vmbr0: port 8(fwpr104p0) entered disabled state
[Sun Aug 30 06:01:07 2026] hrtimer: interrupt took 6329 ns
[Mon Aug 31 05:03:53 2026] tap104i0: entered promiscuous mode
[Mon Aug 31 05:03:53 2026] vmbr0: port 8(fwpr104p0) entered blocking state
[Mon Aug 31 05:03:53 2026] vmbr0: port 8(fwpr104p0) entered disabled state
[Mon Aug 31 05:03:53 2026] fwpr104p0: entered allmulticast mode
[Mon Aug 31 05:03:53 2026] fwpr104p0: entered promiscuous mode
[Mon Aug 31 05:03:53 2026] vmbr0: port 8(fwpr104p0) entered blocking state
[Mon Aug 31 05:03:53 2026] vmbr0: port 8(fwpr104p0) entered forwarding state
[Mon Aug 31 05:03:53 2026] fwbr104i0: port 1(fwln104i0) entered blocking state
[Mon Aug 31 05:03:53 2026] fwbr104i0: port 1(fwln104i0) entered disabled state
[Mon Aug 31 05:03:53 2026] fwln104i0: entered allmulticast mode
[Mon Aug 31 05:03:53 2026] fwln104i0: entered promiscuous mode
[Mon Aug 31 05:03:53 2026] fwbr104i0: port 1(fwln104i0) entered blocking state
[Mon Aug 31 05:03:53 2026] fwbr104i0: port 1(fwln104i0) entered forwarding state
[Mon Aug 31 05:03:53 2026] fwbr104i0: port 2(tap104i0) entered blocking state
[Mon Aug 31 05:03:53 2026] fwbr104i0: port 2(tap104i0) entered disabled state
[Mon Aug 31 05:03:53 2026] tap104i0: entered allmulticast mode
[Mon Aug 31 05:03:53 2026] fwbr104i0: port 2(tap104i0) entered blocking state
[Mon Aug 31 05:03:53 2026] fwbr104i0: port 2(tap104i0) entered forwarding state
[Mon Aug 31 05:06:53 2026] zd160: p1
[Mon Aug 31 05:06:53 2026] tap104i0: left allmulticast mode
[Mon Aug 31 05:06:53 2026] fwbr104i0: port 2(tap104i0) entered disabled state
[Mon Aug 31 05:06:53 2026] fwbr104i0: port 1(fwln104i0) entered disabled state
[Mon Aug 31 05:06:53 2026] vmbr0: port 8(fwpr104p0) entered disabled state
[Mon Aug 31 05:06:53 2026] fwln104i0 (unregistering): left allmulticast mode
[Mon Aug 31 05:06:53 2026] fwln104i0 (unregistering): left promiscuous mode
[Mon Aug 31 05:06:53 2026] fwbr104i0: port 1(fwln104i0) entered disabled state
[Mon Aug 31 05:06:53 2026] fwpr104p0 (unregistering): left allmulticast mode
[Mon Aug 31 05:06:53 2026] fwpr104p0 (unregistering): left promiscuous mode
[Mon Aug 31 05:06:53 2026] vmbr0: port 8(fwpr104p0) entered disabled state

I don’t have much experience with SAS drives, but wouldn’t this be (per my googlefu) similar to CRC errors on a SATA drive?

Thoughts on this being a cabling issue?