January 31, 20224 yr Hi I have a number (8) of data prepopulated ntfs drives in Unassigned devices that I am pushing through to a VM by assigning them manually using by-id and passing through. It all works fine but for troubleshooting later I want to be able to see the serial number or other exact identifying way of which disk is which, not QM0001, 2 ,3 as the serial etc. The Disk Label is visible in the particular VM I am using which is helpful as I can see the old Drive name that it had in Windows but i'd really like to be able to see the actual disk id, especially as I wont be able to access the disk label if the drive dies. I've had a good look around but can't seem to locate the info I'm looking for. I feel like there might be something I can add to the xml in the form view of the VM that might get passed through and do what I want but don't have the knowledge or skill to work it out. Can anyone please point me in the right direction if this is at all possible. I am aware that if a disk failed I'd be able to see it in the actual unassigned devices section and work backwards but for my intentions I'd really love to ID my disks properly in the VM. Although I ran Unraid in a vm for ages in virualbox on a windows machine (to run pretty much one app) I've decided to use it properly now on baremetal and 'really' use it so I am still technically quite new to this so I apologies if I'm asking a stupid already answered question. Thank you
February 1, 20224 yr Not sure if it's possible at all by passing the disks by by-id, but if you have a second sata controller, pass it through with all the disks attached and they will be seen as native. This is an example of my disk in a mac os vm with a sata controller passed through:
February 1, 20224 yr Author hmm that's interesting. I dont have any space pci slots for another hba but I seem to recall a video where the card was stubbed out and then unstubbed after creation if my memory serves me correctly. Thanks I will investigate down this path.
February 1, 20224 yr Author actually I found a post somewhere else that references using <serial> in the xml and that has given me the opportunity to arbitrarily identify the disks with what serial I want which will definitely help me.. Cheers again for the hba isolation idea too though
February 1, 20224 yr 7 minutes ago, markymark said: but I seem to recall a video where the card was stubbed out and then unstubbed after creation Yes, it should be possible to attach to vfio "on the fly", simply don't attach it to vfio, and setup the sata controller in the xml with vfio; by this way (hopefully), the controller will detach when the vm will start, and it will attach again after the vm is shutdown. This worked on my box with my sata controller, however if possible, I prefer to attach to vfio at boot all that I can. Obviously, make sure to not have other devices you need in the host attached to the same sata controller.
February 1, 20224 yr Author yeah i hang ppretty much everyting off that controller and sas expander so that will be too difficult wihtout adding another hba. I'll have to tuse the serial xml instead which is enough for what I need. cheers again
February 2, 20224 yr Author I just realised the custom xml is overwritten every time i change something in the template so maybe I will have to go down your route.
February 14, 20233 yr On 2/1/2022 at 7:08 AM, markymark said: actually I found a post somewhere else that references using <serial> in the xml and that has given me the opportunity to arbitrarily identify the disks with what serial I want which will definitely help me.. Cheers again for the hba isolation idea too though I'm having a similar issue but I can't find the post your referencing anywhere. Can you tell me exactly how you typed it into the xml to let you give the disks a serial number? Thanks a lot!
February 14, 20233 yr Community Expert 4 minutes ago, FoxBytes said: I'm having a similar issue but I can't find the post your referencing anywhere. Can you tell me exactly how you typed it into the xml to let you give the disks a serial number? Thanks a lot! On the disk in the xml. <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Unraid-VM/vdisk2.img'/> <target dev='hdd' bus='virtio'/> <serial>vdisk2</serial> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </disk> It has been added to the GUI for 6.12 Edited February 14, 20233 yr by SimonF
February 15, 20233 yr 6 hours ago, SimonF said: On the disk in the xml. <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Unraid-VM/vdisk2.img'/> <target dev='hdd' bus='virtio'/> <serial>vdisk2</serial> <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/> </disk> It has been added to the GUI for 6.12 Ohh perfect! Thanks so much! That was actually my initial thought but then when I went to do it all the other parameters were inside the < >, so I second guessed myself and didn't want to screw things up haha. Thank you! Oh and I didn't even think to check the gui! Thanks so much! EDIT: Oh apparently I'm still on 6.11 haha Edited February 15, 20233 yr by FoxBytes
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.