September 28, 2025Sep 28 Diagnostics attached. Some very odd stuff going on, and I'm concerned I may have lost all my data. In the event log, I have continuous errors:Sep 28 09:05:43 citadel kernel: XFS: metadata IO error: 6697 callbacks suppressedSep 28 09:05:43 citadel kernel: XFS (md1p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS (md1p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS (md1p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS (md1p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS: metadata IO error: 452 callbacks suppressedSep 28 09:05:43 citadel kernel: XFS (md3p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS (md1p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS (md3p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS (md1p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS (md3p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS (md1p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS (md3p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS (md1p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS (md3p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS (md1p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS (md3p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS (md1p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS (md3p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS (md3p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS (md3p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS (md3p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS: metadata IO error: 533 callbacks suppressedSep 28 09:05:43 citadel kernel: XFS (md2p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS (md2p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS (md2p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS (md2p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS (md2p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS (md2p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS (md2p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS (md2p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS (md2p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5Sep 28 09:05:43 citadel kernel: XFS (md2p1): metadata I/O error in "xfs_buf_ioend+0x10d/0x380" at daddr 0x80 len 32 error 5\When i stop the array to try to do a filesystem check, it loses all the disks in the array:On a reboot, I can get them back, but when i go to stop it for maintenance mode, same thing happens. Rebooting into safe mode works, at which point I can enter maintenence mode. Upon doing file system checks, I get this:I run a file system check on the failed at random disk (it was Disk 11, which I successfully rebuilt in full, then it was parity 1, then it was disk 12) and they do have errors, which repair.I have checked all my cabling, and this is occurring across multiple cables, multiple backplanes. The only thing changed was the pcie slot i put my HBA in, and it was working well in the previous PCIe slot (PCIe x16 5.0 slot (working), vs PCIe 4.0 x16 slot (errors) citadel-diagnostics-20250928-0906.zip
September 28, 2025Sep 28 Author Repaired the filesystem on all disks in maintenance mode. Mounted disks in normal mode, entire machine froze.At this point, I want to recover any data I can and copy it to a different system.... best way to do that? Edited September 28, 2025Sep 28 by jbrukardt
September 29, 2025Sep 29 Community Expert The HBA is being passed through to the Windows VM, so when it starts, Unraid loses contact with all the disks. Correct that, and it should resolve the issue.
September 29, 2025Sep 29 Community Expert Good idea to verify iommu group vfio binds after any hw config changes as the group number can change.
October 3, 2025Oct 3 Author On 9/29/2025 at 3:19 AM, JorgeB said:The HBA is being passed through to the Windows VM, so when it starts, Unraid loses contact with all the disks. Correct that, and it should resolve the issue.That makes perfect sense, as the video card that used to be on that slot was passed to the VM.You are awesome.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.