January 28, 20215 yr First why: In the last two years we did setup several big Unraid servers with attached "Direct Attached Storage" enclosures. Usually the bare metal server did host several HBAs and every attached "Direct Attached Storage" enclosure was one individual Unraid array with it's own license stick and it's own HBA passed thru to every Unraid VM. With this setup we could drive several Unraid arrays (22 data drives, 2 parity drives each) as one server. Using the 36/45 drive enclosures from Supermicro now we would like to change that: Only one HBA per bare metal, using the expander feature of the bigger backplane, driving two arrays. In this setup we can't passthru a second HBA for the Unraid VM. E.g. for the 45 drive this would result in one Unraid array of 24 drives and one Unraid array of 21 drives. All attached to one HBA using the expander feature of the 24-drive backplane. This means: We need to passthru 21 drives to the Unraid VM. Question(s): After reading lots of information I'm confused now about the correct syntax and keywords I need to use: 1.) virsh manual? virsh attach-disk TowerVM01 /dev/disk/by-id/ata-TOSHIBA_MG07ACA12TE_3010A09AF96G --serial TOSHIBA_MG07ACA12TE_3010A09AF96G --type disk virsh attach-disk TowerVM01 /dev/disk/by-id/ata-WDC_WD60EFRX-68L0BN1_WD-WX11D469YZL4 --serial WDC_WD60EFRX-68L0BN1_WD-WX11D469YZL4 --type disk 2.) XML? <disk type='block' device='disk'> <driver name='qemu' type='raw'/> <source dev='/dev/disk/by-id/ata-TOSHIBA_MG07ACA12TE_3010A09AF96G'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw'/> <source dev='/dev/disk/by-id/ata-WDC_WD60EFRX-68L0BN1_WD-WX11D469YZL4'/> </disk> Would these work? Any help is highly appreciated.
Archived
This topic is now archived and is closed to further replies.