I have an ASUS Prime Z370-A motherboard and just added an IO crest 2 port SATA card (Asmedia chipset) to the PCIe x16_3 slot. Upon boot up I noticed that my parity drive (still plugged into the motherboard) was now shows as sdc and my drive 1 (also connected to motherboard) is now sdb. Not sure why this occurred as all my drives used to be in order sdb-sdg.
Additionally, I had my Windows 10 VM configured to pass through a USB controller for my keyboard mouse etc while my other Asmedia USB controller on the motherboard remained and has the unraid USB stick and UPS plugged into it. After adding the SATA card, I attempted to boot the VM and I got no video or anything. I look at the unraid web GUI and it's complaining about loss of connectivity to the UPS and I also notice a lot of screens are now blank with errors. It looked like unraid couldn't see the USB stick anymore.
So I shut down the system, booted it back up again and tried to boot the VM without passing the USB controller (even though it still said Intel and not Asmedia where unraid is). That worked. So I went through the process of removing the USB controller from the VM config then re-adding it and now it's working again. I also had to re-add my PCIe x1 sound card to the VM config as it now showed none for audio.
My Windows 10 VM has worked for months prior to adding this SATA card. I had a Marvell SATA card which had to go because of issues but that one never caused anything weird to happen with my devices.
Just very odd that these things happened when I moved sdf and sdg drives from the onboard ports to the new SATA card that now other drives are showing different device names.
Attaching diagnostics if you need them. Perhaps it's not a bug or something the motherboard did because I put the SATA card in PCIe x16_3 slot. No idea...
Recommended Comments
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.