December 16, 20241 yr I have a win11 vm that has a mapping to a physical hdd. <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-Hitachi_HUS724040ALE641_SERIAL#' index='1'/> <backingStore/> <target dev='hdd' bus='sata'/> <serial>vdisk2</serial> <boot order='2'/> <alias name='sata0-0-3'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> When the machine boots up it has a c drive and two cd-rom drives one for os and one for virtio drivers. The d drive mapped above does not show up. If you open the windows drive manager it shows as drive 1 but you cannot assign a letter to it. It will not show up in disk part. I take it this is normal functionality due to the drive being formatted in XFS. This did work for serval month and just stopped when I had to fix a drive in the array. Drive works fine in Unraid.
December 16, 20241 yr Community Expert 5 minutes ago, dodgeman said: No, its a pool device. You should only pass thru a device in this manner if the disk is unassigned. The drive is mounted to the host hence you cannot see the partitions.
December 19, 20241 yr Author Not sure how that would have occurred, so I changed it to a nvme that is unassigned and it now show the nvme drive in the vm drive manager but not in explorer. Any ideas?
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.