JKunraid

Seems to have worked. Thanks so much.

I created a new USB key using the Unraid software utility. The system boots but of course the drive mappings and everything else isn't configured or a valid license.. Are you saying this can all be fixed by simply overwriting the /config folder on the new USB by copying over the /config folder on the old USB key?

Unraid server stopped booting after a cold restart. When looking at the boot sequence locally it does see the Unraid USB key but gets stuck during boot process (tried with GUI, without, and safe mode). I pulled out the USB key and put it in an Ubuntu machine to run a checkdisk using the built-in Disk app. It did flag a dirty bit. I ran the repair and it seemed to work but when I try to boot with it I once again get stuck during the boot process. I have a flash key config backup but it's out of date and I've updated the array with additional drives and done other changes since the old backup. Fortunately, I was able to copy all the files of the USB key to another computer. What would be the steps to recover to another USB key using the files from the old key?

I have a bunch of HDDs in a Netapp disk shelf. I'd like to passthrough one of them to a PopOS VM. I can see them in unassigned disk devices (able to mount and unmount it). I was able to passthrough a GPU and a couple of M.2 SSD drives by binding them in Unraid's system devices but I don't see this particular HDD in the list. How would I do the passthrough?

UPDATE: I did of search of devices with bus 43 (and 44) as you suggested using the broken XML. As the XML was nested I assumed the parent lines of XML were also required. I added these lines to working XML config just above the <memballon model='none'/> line. It booted and showed the two drives. I need to spend a bit of time making sure I haven't broken anything but as it stands it seems to be working.. I'll update as soon as I know for sure. <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x43' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x44' slot='0x00' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> </hostdev>

Yes. A virtio vdisk is set to "1" on boot field. It has a working OS. The m.2 drives are for secondary drives not operating system... I have nearly the same setup on the simpler VM and i have no issue using the form view to add them in. It's the manually modified xml VM that has the issue. I could start from scratch again but I took hours to get the VM working for my particular configuration. It would be a lot simpler if I could add the lines into the xml manually.

Thanks again for reply Simon. Not following you though. I've already done the vfio bind in system devices and confirmed I can add the m.2 drives to another basic VM using Unraids VM template GUI. That VM boots fine and adds the drives. The issue is if I use the VM template tool in form view to add the m.2 drives to another VM that has a manually modified XML config template. My second VM boots fine. When I use to VM template form view to modify the config (rather than the config directly using the "xml text" toggle) it messes up my manually modified XML config. The system won't boot then. In other words, what I'm trying to figure out is what text lines do I need to add to my VM's XML configuration to get the two m.2 drives to do the passthrough? (i.e. rather than using the form view) (Edit:" The devices below are available as an option in the VM's form view but if I check the boxes and click update the VM doesn't boot. I have to repaste a backup of the xml config to get it to boot again) Other PCI Devices: AMD RAID Bottom Device | Non-Volatile memory controller (43:00.0) AMD RAID Bottom Device | Non-Volatile memory controller (44:00.0)

I want to passthrough a couple of M.2 SSDs. I am able to do the passthrough with a simple Linux VM configuration using the UI (confirmed with testing). When I try to do the passthrough to another Linux VM though, one that has some manual modifications done to its XML configuration file, it messes up the XML configuration and VM won't boot. I've seen this Unraid bug before where if you switch back to UI mode and save after manually modifying VM's XML config it can mess it up. So I backed it up and was able to recover but I'm stuck as to how to add the passthrough for the m.2s manually to my xml file.

Got it. Thanks again.

I opened up the fsab file with nano. I've never done this before so I'm not sure what the exact line I should add looks like.

I just realized I have one more related question. How would I keep the connection to share persistent across reboots?

Perfect. Thanks.

Setup following virtiofs settings when I created a PopOS VM (settings selected from dropdown). Unraid Share Mode: Virtiofs Mode Unraid Share: user: vmShare Unraid Source Path: /mnt/user/vmShare Unraid Mount Tag: vmShare The VM boots fine but I can't see the share named "vmShare". either in locations, VM's mnt folder, or using Disks utility. Is there some step I'm missing or is there a problem?

Unraid Share Mode: Virtiofs Mode Unraid Share: user: vmShare Unraid Source Path: /mnt/user/vmShare Unraid Mount Tag: vmShare

Success! My existing Ubuntu VM still doesn't see it. And I tried with multiple new templates of Ubuntu but I tried with your suggested PopOS VM and it recognizes the GPU. Thanks so much for the help.