VM not a bootable disk

jackDante

New Member
Jul 8, 2024
2
0
1
Hi, thanks in advance.
I made a VM's clone from one node to another one (in my cluster).

  • The process created a new logical volume in my node, however my VM does not boot correclty as you can see in the image (posted).
  • I have my logical volume /dev/main/vm-303-disk-0, but I cannot understand what's wrong.
  • I can make it available using >lvchange -ay /dev/main/vm-303-disk-0, but this does not solve my VM'booting problem!

    Thanks

The new node situation is::
Code:
root@SCADA-SRV03:~# lsblk
NAME               MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda                  8:0    0 223.5G  0 disk
├─sda1               8:1    0  1007K  0 part
├─sda2               8:2    0     1G  0 part /boot/efi
└─sda3               8:3    0 222.5G  0 part
  ├─pve-swap       252:0    0     8G  0 lvm  [SWAP]
  ├─pve-root       252:1    0  65.6G  0 lvm  /
  ├─pve-data_tmeta 252:2    0   1.3G  0 lvm
  │ └─pve-data     252:4    0 130.2G  0 lvm
  └─pve-data_tdata 252:3    0 130.2G  0 lvm
    └─pve-data     252:4    0 130.2G  0 lvm
sdb                  8:16   0   1.8T  0 disk

root@SCADA-SRV03:~# lvs
  LV            VG   Attr       LSize    Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  vm-303-disk-0 main -wi-------  500.00g                                                 
  data          pve  twi-a-tz-- <130.22g             0.00   1.22                         
  root          pve  -wi-ao----   65.62g                                                 
  swap          pve  -wi-ao----    8.00g                                                 
root@SCADA-SRV03:~# vgs
  VG   #PV #LV #SN Attr   VSize   VFree
  main   1   1   0 wz--n-  <1.82t  1.33t
  pve    1   3   0 wz--n- 222.50g 16.00g
 
  root@SCADA-SRV03:~# lvdisplay main
  --- Logical volume ---
  LV Path                /dev/main/vm-303-disk-0
  LV Name                vm-303-disk-0
  VG Name                main
  LV UUID                fAPOqq-mHMI-jifx-N4iZ-hc45-8KYe-u6c2OT
  LV Write Access        read/write
  LV Creation host, time SCADA-SRV03, 2025-02-06 13:09:06 +0100
  LV Status              NOT available
  LV Size                500.00 GiB
  Current LE             128000
  Segments               1
  Allocation             inherit
  Read ahead sectors     auto

root@SCADA-SRV03:~# lvchange -ay /dev/main/vm-303-disk-0
 

Attachments

  • notabootableDisk.png
    notabootableDisk.png
    62.6 KB · Views: 6
Last edited:
Hi,

please share the configuration of the vm by either screenshot of Hardware and Options or by running qm config 303 in the PVE cli
 
Mmh, don't know if the following would help but you are missing the thin-pool ... compare to orig path with shown by "lvs" the "t" for Attr :
pv: real disk -> vg: pve -> lv: data -> vdisk: vm-103-disk-0
pv: real disk -> vg: main -> lv: % -> vdisk: vm-303-disk-0
 
Here the VM 303 configuration (see image "5"):
Code:
boot: order=scsi0;ide2;net0
cores: 16
cpu: x86-64-v2-AES
ide2: none,media=cdrom
memory: 16384
meta: creation-qemu=8.1.5,ctime=1734364410
name: 4A-uel03
net0: virtio=BC:24:11:6B:94:4C,bridge=vmbr1,firewall=1
numa: 0
ostype: l26
scsi0: main:vm-303-disk-0,iothread=1,size=500G
scsihw: virtio-scsi-single
smbios1: uuid=0199234a-a435-4ba8-8c35-539f658d1237
sockets: 1
vmgenid: 26f5294f-ed25-479a-8fbf-6a5920fce708

I followed this steps, maybe it's not the best one:
  1. I have a Cluster with 4 Nodes.
    1. First of all, I creted Volume Group "main" on /dev/sda (See image "2")
  2. First I created Node1, VM101 (ubuntu) and then I cloned VM101 (renamed in VM202) to the new Node2.
  3. Then I cloned VM202 to Node3 and so on.
  4. At the end of the story, only the VMs in Node1 and 2 are able to boot correctly...and I didn't understand why yet. :mad::eek:
I'm not using the thin-pool.


Thanks
 

Attachments

  • 5.png
    5.png
    99.6 KB · Views: 6
  • 2.png
    2.png
    66.3 KB · Views: 5
  • 3.png
    3.png
    82.7 KB · Views: 4
  • 4.png
    4.png
    63 KB · Views: 6