I had a regularly scheduled parity check. I had to add another m.2 drive so once it was finished I installed it. I don't recall seeing any errors once I started it back up but I just did a quick glance. This morning, I noticed some disks were disabled and some in standby. I shut it down, checked the cables and such. There are no disks in standby but I still have some disks disabled. The parity check was fine. I'm not sure what the issue is. I've included my diagnostics.

tower-diagnostics-20250108-1007.zip

Diags are after rebooting, at least twice, since the disks were already disabled in the syslog-previous, so we can't see what happened, disks look healthy, so most likely a different issue, if the emulated disks are mounting and contents look correct, you can rebuild on top, if it happens again, save the diags before rebooting.

5 minutes ago, JorgeB said:

Diags are after rebooting, at least twice, since the disks were already disabled in the syslog-previous, so we can't see what happened, disks look healthy, so most likely a different issue, if the emulated disks are mounting and contents look correct, you can rebuild on top, if it happens again, save the diags before rebooting.

That's what I thought. Shoot, should have saved it before rebooting but I just figured I knocked a cable. 

Well, the rebuild finished and shortly after, the disk were disabled again and a few others went on standby. I made sure and grabbed the diagnostics first. I'm not sure how to unmark this as resolved.

tower-diagnostics-20250109-0924.zip

This SATA controller is being passed through to a VM:

 

44:00.0 SATA controller [0106]: JMicron Technology Corp. JMB58x AHCI SATA controller [197b:0585]
    Subsystem: JMicron Technology Corp. Device [197b:0000]
    Kernel driver in use: vfio-pci
    Kernel modules: ahci

 

So when the VM starts, all 5 disks connected there will drop, and Unraid will disable the first two that give a write error.

 

Note that when you add/remove hardware, the device IDs will typically change, so you need to recheck any devices being passed through.

OMG, how did I miss that?!

Actually, now that I look at it, there might be a UI bug. I added a new m.2 drive and a heatsink to the other m.2 drive. Because my stupid motherboard has a big fat capacitor in the way of the m.2 slot, I had to swap it with a SATA controller because the drive no longer fits with the heatsink. The SATA controller is now were the passed-through drive used to be. I did check the hardware and made sure both drive controllers were passthrough but I did not check to see if the SATA controller was passed through.

Now I have two VMs, each using a passed-through m.2 drive. I don't recall which VM it was, but when I was making sure the correct m.2 drive controller was assigned to the correct VM, I also made sure the boot order was set to 1 but surprisingly, it gave me an error saying there was already another device with the boot order set to 1. I checked the form and there wasn't, even searched for "boot" to make sure. So I think the SATA controller was there and the form was just not showing it. I'm positive there was only the two drives showing in the "other devices". Going back to the VMs, one shows both drive controllers under "other devices" and the other additionally shows the SATA controller. I checked and the SATA controller is not configured to be passed through. But I'm just glad it isn't bad news.