Problem passing through disks to VM

N

NickH

Active Member
Aug 13, 2020
33
1
28
64
I have a VM which currently has 2 disks passed through to it. I would like to pass another 2 disks through to it. However, when I try
Code: 
qm set 117 -scsi3 /dev/disk/by-id/ata-TOSHIBA_MG09ACA18TE_62X0A100FJDH
It just sits there forever. If I change -scsi3 to -scsi5, it works. Do you know what is going on? Could scsi3 be in use somewhere? if so, where? It is not mentioned in any conf file in /etc/pve/nodes/pve/qemu-server.
 
Last edited:
is the vm running? what does 'qm config 117' say?
 
I tried multiple times with the VM running and not running and every time it hung, but when I tried scsi4 it worked for the other disk (even with the VM running). I then tried scsi5 with this disk and it worked immediately.
Code: 
root@pve:~# qm config 117
boot: order=scsi0;ide2;net0
cores: 2
ide2: local:iso/ClearOS-7.9.1.342252-DVD-x86_64.iso,media=cdrom
memory: 32768
meta: creation-qemu=6.1.0,ctime=1644334629
name: Sia
net0: virtio=4E:53:C4:ED:BB:1F,bridge=vmbr0,firewall=1
numa: 0
onboot: 1
ostype: l26
scsi0: nvme_2g_01:vm-117-disk-0,size=100G
scsi1: /dev/disk/by-id/ata-TOSHIBA_MG09ACA18TE_Y1X0A26JFJDH,size=16764G
scsi2: /dev/disk/by-id/ata-TOSHIBA_MG09ACA18TE_Z1B0A02KFJDH,size=16764G
scsi4: /dev/disk/by-id/ata-TOSHIBA_MG09ACA18TE_62X0A0Q9FJDH,size=16764G
scsi5: /dev/disk/by-id/ata-TOSHIBA_MG09ACA18TE_62X0A100FJDH,size=16764G
scsihw: virtio-scsi-pci
smbios1: uuid=2b4177e1-6604-4ef2-a661-a6888d80807f
sockets: 4
vmgenid: 985f571d-4f41-452c-8e86-1ca6a18620d5
 
what does the host syslog say (e.g. with 'journalctl -b') ? any disk (or other) errors?
 
I can see where it worked:
Code: 
Sep 12 15:01:38 pve pvedaemon[1884]: <root@pam> end task UPID:pve:00006547:000DF6E2:631F3BC0:qmstart:117:root@pam: OK
Sep 12 15:05:24 pve qm[26772]: <root@pam> update VM 117: -scsi4 /dev/disk/by-id/ata-TOSHIBA_MG09ACA18TE_62X0A0Q9FJDH
Sep 12 15:05:24 pve kernel:  sdb: sdb1
Sep 12 15:06:13 pve qm[26933]: <root@pam> update VM 117: -scsi5 /dev/disk/by-id/ata-TOSHIBA_MG09ACA18TE_62X0A100FJDH
Sep 12 15:06:13 pve kernel:  sda: sda1
It looks like the VM was running when I did this and there is no mention of scsi3 (so where it hung):
Code: 
root@pve:~# journalctl -b | grep scsi
Sep 12 12:30:16 pve kernel: scsi host0: ahci
Sep 12 12:30:16 pve kernel: scsi host1: ahci
Sep 12 12:30:16 pve kernel: scsi host2: ahci
Sep 12 12:30:16 pve kernel: scsi host3: ahci
Sep 12 12:30:16 pve kernel: scsi host4: ahci
Sep 12 12:30:16 pve kernel: scsi host5: ahci
Sep 12 12:30:16 pve kernel: scsi host6: ahci
Sep 12 12:30:16 pve kernel: scsi host7: ahci
Sep 12 12:30:16 pve kernel: scsi host8: ahci
Sep 12 12:30:16 pve kernel: scsi host9: ahci
Sep 12 12:30:16 pve kernel: scsi 0:0:0:0: Direct-Access     ATA      TOSHIBA MG09ACA1 0104 PQ: 0 ANSI: 5
Sep 12 12:30:16 pve kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Sep 12 12:30:16 pve kernel: scsi 4:0:0:0: Direct-Access     ATA      TOSHIBA MG09ACA1 0104 PQ: 0 ANSI: 5
Sep 12 12:30:16 pve kernel: sd 4:0:0:0: Attached scsi generic sg1 type 0
Sep 12 12:30:16 pve kernel: scsi 5:0:0:0: Direct-Access     ATA      TOSHIBA MG09ACA1 0104 PQ: 0 ANSI: 5
Sep 12 12:30:16 pve kernel: sd 5:0:0:0: Attached scsi generic sg2 type 0
Sep 12 12:30:16 pve kernel: scsi 6:0:0:0: Direct-Access     ATA      TOSHIBA MG09ACA1 0104 PQ: 0 ANSI: 5
Sep 12 12:30:16 pve kernel: sd 6:0:0:0: Attached scsi generic sg3 type 0
Sep 12 12:30:16 pve kernel: scsi 7:0:0:0: Direct-Access     ATA      ST1000DM010-2EP1 CC43 PQ: 0 ANSI: 5
Sep 12 12:30:16 pve kernel: sd 7:0:0:0: Attached scsi generic sg4 type 0
Sep 12 12:30:20 pve kernel: iscsi: registered transport (tcp)
Sep 12 12:30:20 pve kernel: iscsi: registered transport (iser)
Sep 12 12:30:17 pve systemd-modules-load[759]: Inserted module 'iscsi_tcp'
Sep 12 12:30:22 pve smartd[1500]: Device: /dev/sda, type changed from 'scsi' to 'sat'
Sep 12 12:30:22 pve smartd[1500]: Device: /dev/sdb, type changed from 'scsi' to 'sat'
Sep 12 12:30:22 pve smartd[1500]: Device: /dev/sdc, type changed from 'scsi' to 'sat'
Sep 12 12:30:22 pve smartd[1500]: Device: /dev/sdd, type changed from 'scsi' to 'sat'
Sep 12 12:30:22 pve smartd[1500]: Device: /dev/sde, type changed from 'scsi' to 'sat'
Sep 12 12:30:25 pve systemd[1]: Starting iSCSI initiator daemon (iscsid)...
Sep 12 12:30:25 pve iscsid[1635]: iSCSI logger with pid=1667 started!
Sep 12 12:30:25 pve systemd[1]: Started iSCSI initiator daemon (iscsid).
Sep 12 12:30:25 pve iscsiadm[1675]: iscsiadm: No records found
Sep 12 12:30:26 pve iscsid[1667]: iSCSI daemon with pid=1668 started!
Sep 12 15:05:24 pve qm[26772]: <root@pam> update VM 117: -scsi4 /dev/disk/by-id/ata-TOSHIBA_MG09ACA18TE_62X0A0Q9FJDH
Sep 12 15:06:13 pve qm[26933]: <root@pam> update VM 117: -scsi5 /dev/disk/by-id/ata-TOSHIBA_MG09ACA18TE_62X0A100FJDH
Sep 12 15:30:13 pve smartd[34554]: Device: /dev/sda, type changed from 'scsi' to 'sat'
Sep 12 15:30:13 pve smartd[34554]: Device: /dev/sdb, type changed from 'scsi' to 'sat'
Sep 12 15:30:13 pve smartd[34554]: Device: /dev/sdc, type changed from 'scsi' to 'sat'
Sep 12 15:30:13 pve smartd[34554]: Device: /dev/sdd, type changed from 'scsi' to 'sat'
Sep 12 15:30:13 pve smartd[34554]: Device: /dev/sde, type changed from 'scsi' to 'sat'
 
You must log in or register to reply here.
Top Bottom