DizzyWeb

If I were to do that, I'd probably use a separate controller, so that wouldn't be an issue. I'm asking this since I've read Unraid relies on the disk's ID's. When I pass them through individually, those ID's aren't visible to the VM (as you can see).

Currently running Unraid in a Proxmox VM, which works fine. I have my disks passed through individually, since they're all just connected to the motherboard and at the time of installation I wasn't sure if I needed any SATA drives anywhere else (and I had no idea if I could actually passthrough the onboard SATA controller in the first place). This works fine, however, looks weird in Unraid. Disks are called something like this: 0QEMU_QEMU_HARDDISK_drive-scsi0 Instead of this: ata-Crucial_CT128MX100SSD1_14440DA9B9DF If I were to some day move to a passed through SATA controller, for whatever reason, will that work if I make a new config and put the disks in the exact same order (but with very different names)? Or would I need to start from scratch? I mean, I could pass a controller through and just go disk by disk and let it repair every time, but that would take weeks, while the data is just right there on the disks.

Right, for anyone who has a similar issue... the solution (for me) where snippets. I made a snippet that unmounts and disables the share in the "pre-stop" phase (and because it'll only enter that phase if you shut the VM down from within Proxmox, not from within the VM itself, I do it again in "post-stop" just to be sure), and it enables and mounts the share again in the post-start phase. Solved the massive delays, but it's not perfect. It doesn't always see the mount, so sometimes I'm left with a share in Proxmox that it can't use. Simply disabling and re-enabling fixes that. Not entirely sure how to fix that yet, I'm guessing it happens because the snippet runs because the VM has started, but Unraid hasn't completely booted yet, so the share isn't available yet.

I'm currently running Unraid in a Proxmox VM and it works flawlessly. Was a bit of a hassle to get working and not having a PCI SATA card to pass through, just individual drives will prove an absolute nightmare if a drive fails, but... that's not my issue. I have a share setup on Unraid where Proxmox saves it's backups. So, Unraid runs in a VM in Proxmox and Proxmox has a CIFS share on Unraid for backups. Works fine, except for one thing. Whenever I shutdown or reboot the machine, it takes forever. Turns out... it's waiting for the share to unmount. Which obviously takes forever: the Unraid VM has already shutdown! All in all, this makes a shutdown of my Proxmox machine take around 10 minutes, if not more. Does anyone perhaps have an elegant solution?