Hi all,

I'm hoping someone can point me in the right direction.

I was upgrading the second NVMe slot in my server. I had a 256GB NVMe installed for a passthrough VM, which I removed and replaced with a 1TB drive.

Since doing that, I've run into a strange issue. Unraid is now reporting one failed drive, and it's asking me to mount three drives. I believe these three drives are all connected to my PCIe SATA controller.

My first thought was that the SATA controller had failed, so I replaced it with another one, but I'm seeing exactly the same behaviour.

Has anyone come across anything like this before? Could changing the NVMe have altered the PCIe lane allocation or device ordering, causing the SATA controller drives to appear differently?

Any ideas would be greatly appreciated.

Thanks!

jeeves-syslog-20260626-1758.zip

Attach Diagnostics ZIP to your NEXT post in this thread.

We need the diags to confirm, but based on the description, the device IDs might have changed, and you are now possibly passing through the SATA controller to the VM.

Sorry, please find attached the diags.

I appreciated (disk1) drive defiantly looks to have failed, I just need some help on disk3 and 4 :)

jeeves-diagnostics-20260626-1908.zip

Has anyone got any ideas?

I tried a new config last night, which I know is dangerous with a failed drive. But I had a similar thing in the past, and that fixed it. Also the drive that failed is not very old, so I’m a little sceptical.

After the new config, it now thinks drive 3 has failed and drive 1 is ok 🤷‍♂️

Still loads of drives in unassigned 😕

Edited June 27Jun 27 by davemoreton

Though I'm not seeing the SATA controller being passed through directly, the issue looks connected to the VM, disable the VM service, reboot the server, and post new diags after array start.

Thanks for that, I have got a little further with this.

I think the disk config file got a little messed up, I completely restored the USB boot drive to a few months ago.

It's booted with all its drives, wanted to do a rebuild which its currently doing and all network shares are back online etc.

The only problem I have at the moment is the docker service won't start :( I will wait for the rebuild to finish first, and then take a look.

Thanks

If you need help with the Docker issue later, post new diags after array start

13 minutes ago, JorgeB said:

If you need help with the Docker issue later, post new diags after array start

Thanks JorgeB

Here is the new diags, the rebuild hasn't finished yet. I think the docker image is dead though

root@Jeeves:~# mkdir -p /mnt/docker-recovery
root@Jeeves:~# btrfs restore -v /mnt/user/system/docker/docker.img /mnt/docker-recovery parent transid verify failed on 44892160 wanted 3065530 found 3065542 parent transid verify failed on 44892160 wanted 3065530 found 3065542 parent transid verify failed on 44892160 wanted 3065530 found 3065542 Ignoring transid failure ERROR: child eb corrupted: parent bytenr=30408704 item=0 parent level=1 child bytenr=44892160 child level=1 ERROR: search for next directory entry failed: -5
root@Jeeves:~#

jeeves-diagnostics-20260627-1212.zip

Recreating the docker.img file is normally quite trivial as you can use Apps->Previous apps to reinstall containers using their previous settings.

11 minutes ago, itimpi said:

Recreating the docker.img file is normally quite trivial as you can use Apps->Previous apps to reinstall containers using their previous settings.

Will they remember all the settings? I had some rather custom bits

36 minutes ago, davemoreton said:

Will they remember all the settings? I had some rather custom bits

They will as long as they were installed via the Unraid Apps tab. When you install containers in that way the settings are stored in an XML template on the flash drive and that is used by the Apps->Previous Apps option. If you install containers in another way then you have to remember the settings used.

Sometimes unraid just blows my mind away! all the apps are back with all the configurations.

Thank you for all your help :)