XCP-NG Upgrade to 8.0 issues

So i just upgrade to XCP-NG 8.0 from 7.5, and i having this issues where 1/2 of my VMs seem to have lost there Hardisk mappings.

Im just using local storage for the VMs then pass NFS shares to the VMs for additional storage as required.

I’m not that well versed with the XCP-NG and the way it presents the storage, i have used Vmware most of my working life i i know how to fix this in Vmware.

So if anyone can help me with some commands to find an reattched the disk would be nice, Linux isn’t i’m not as stong in as i used to be either.

So these are VMs ( 4 in total)


Storage they live on

Is that storage device showing under “Storages”?

Yes
So this is the full output shown in Xen Orchestra

If i lis the Disks by ID this is the output

[09:53 xcp-ng ~]#   ll /dev/disk/by-id
total 0
lrwxrwxrwx 1 root root 10 Aug  3 17:33 dm-name-VG_XenStorage--d8cedb95--4be3--65c2--7af5--09864cc7f5b2-MGT -> ../../dm-0
lrwxrwxrwx 1 root root 10 Aug  3 17:34 dm-name-VG_XenStorage--d8cedb95--4be3--65c2--7af5--09864cc7f5b2-VHD--15765228--d9a6--45fb--aca0--93be90185404 -> ../../dm-2
lrwxrwxrwx 1 root root 10 Aug  3 17:35 dm-name-VG_XenStorage--d8cedb95--4be3--65c2--7af5--09864cc7f5b2-VHD--19e55499--69ed--493b--8f2a--b1a8d5e14bac -> ../../dm-4
lrwxrwxrwx 1 root root 10 Aug  3 17:35 dm-name-VG_XenStorage--d8cedb95--4be3--65c2--7af5--09864cc7f5b2-VHD--389f1649--3dce--45fe--a99a--ee808f985af4 -> ../../dm-5
lrwxrwxrwx 1 root root 10 Aug  4 09:48 dm-name-VG_XenStorage--d8cedb95--4be3--65c2--7af5--09864cc7f5b2-VHD--929c2f86--c7c7--4e34--8aff--ef90dc642b9a -> ../../dm-1
lrwxrwxrwx 1 root root 10 Aug  3 17:34 dm-name-VG_XenStorage--d8cedb95--4be3--65c2--7af5--09864cc7f5b2-VHD--9a57b225--d0e4--44d6--8ed2--ac4c7004b936 -> ../../dm-3
lrwxrwxrwx 1 root root 10 Aug  3 17:35 dm-name-VG_XenStorage--d8cedb95--4be3--65c2--7af5--09864cc7f5b2-VHD--e8a54123--58c6--4558--9894--c9d41f806d55 -> ../../dm-6
lrwxrwxrwx 1 root root 10 Aug  3 17:35 dm-uuid-LVM-SvWbXYHyc5AegKlXqCxLPw2SmicR9ibF12Krhe4jKAORB5kzIcyo5xmSwvBE5y6r -> ../../dm-6
lrwxrwxrwx 1 root root 10 Aug  3 17:34 dm-uuid-LVM-SvWbXYHyc5AegKlXqCxLPw2SmicR9ibFDofDHA0t4YsfwJuWEDtkoqgztzYVsezc -> ../../dm-2
lrwxrwxrwx 1 root root 10 Aug  3 17:34 dm-uuid-LVM-SvWbXYHyc5AegKlXqCxLPw2SmicR9ibFe7fmz08sDtoIoC2vFOPiPzJCC1txgJyc -> ../../dm-3
lrwxrwxrwx 1 root root 10 Aug  3 17:35 dm-uuid-LVM-SvWbXYHyc5AegKlXqCxLPw2SmicR9ibFfCGh9QNAKWT3cOanuVSggNAjoUWCQ6p6 -> ../../dm-5
lrwxrwxrwx 1 root root 10 Aug  4 09:48 dm-uuid-LVM-SvWbXYHyc5AegKlXqCxLPw2SmicR9ibFGoc7pNn9uX7eJQlQLNPakYfLcQqVsNGJ -> ../../dm-1
lrwxrwxrwx 1 root root 10 Aug  3 17:33 dm-uuid-LVM-SvWbXYHyc5AegKlXqCxLPw2SmicR9ibFTR9dNRnh5sR8khS5PKlO8zdPenTeigfn -> ../../dm-0
lrwxrwxrwx 1 root root 10 Aug  3 17:35 dm-uuid-LVM-SvWbXYHyc5AegKlXqCxLPw2SmicR9ibFXsprYjvdW3L0gB0KOw6ZNdTKJGAMXpCU -> ../../dm-4
lrwxrwxrwx 1 root root  9 Aug  3 17:32 scsi-3600508b1001c21b608c562698be6deab -> ../../sdb
lrwxrwxrwx 1 root root 10 Aug  3 17:32 scsi-3600508b1001c21b608c562698be6deab-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 Aug  3 17:32 scsi-3600508b1001c21b608c562698be6deab-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 10 Aug  3 17:32 scsi-3600508b1001c21b608c562698be6deab-part3 -> ../../sdb3
lrwxrwxrwx 1 root root 10 Aug  3 17:32 scsi-3600508b1001c21b608c562698be6deab-part5 -> ../../sdb5
lrwxrwxrwx 1 root root 10 Aug  3 17:32 scsi-3600508b1001c21b608c562698be6deab-part6 -> ../../sdb6
lrwxrwxrwx 1 root root 10 Aug  3 17:32 scsi-3600508b1001c21b608c562698be6deab-part7 -> ../../sdb7
lrwxrwxrwx 1 root root 10 Aug  3 17:32 scsi-3600508b1001c21b608c562698be6deab-part8 -> ../../sdb8
lrwxrwxrwx 1 root root 10 Aug  3 17:32 scsi-3600508b1001c21b608c562698be6deab-part9 -> ../../sdb9
lrwxrwxrwx 1 root root  9 Aug  3 17:32 scsi-3600508b1001c384b521d0b3ba8850b49 -> ../../sda
lrwxrwxrwx 1 root root 10 Aug  3 17:32 scsi-3600508b1001c384b521d0b3ba8850b49-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Aug  3 17:32 scsi-3600508b1001c384b521d0b3ba8850b49-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Aug  3 17:39 scsi-3600508b1001c384b521d0b3ba8850b49-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Aug  3 17:32 scsi-3600508b1001c384b521d0b3ba8850b49-part4 -> ../../sda4
lrwxrwxrwx 1 root root 10 Aug  3 17:32 scsi-3600508b1001c384b521d0b3ba8850b49-part5 -> ../../sda5
lrwxrwxrwx 1 root root 10 Aug  3 17:32 scsi-3600508b1001c384b521d0b3ba8850b49-part6 -> ../../sda6
lrwxrwxrwx 1 root root  9 Aug  3 17:32 usb-SRT_USB_3.0_JET_32G_025113111616092878000052-0:0 -> ../../sdc
lrwxrwxrwx 1 root root  9 Aug  3 17:32 wwn-0x600508b1001c21b608c562698be6deab -> ../../sdb
lrwxrwxrwx 1 root root 10 Aug  3 17:32 wwn-0x600508b1001c21b608c562698be6deab-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 10 Aug  3 17:32 wwn-0x600508b1001c21b608c562698be6deab-part2 -> ../../sdb2
lrwxrwxrwx 1 root root 10 Aug  3 17:32 wwn-0x600508b1001c21b608c562698be6deab-part3 -> ../../sdb3
lrwxrwxrwx 1 root root 10 Aug  3 17:32 wwn-0x600508b1001c21b608c562698be6deab-part5 -> ../../sdb5
lrwxrwxrwx 1 root root 10 Aug  3 17:32 wwn-0x600508b1001c21b608c562698be6deab-part6 -> ../../sdb6
lrwxrwxrwx 1 root root 10 Aug  3 17:32 wwn-0x600508b1001c21b608c562698be6deab-part7 -> ../../sdb7
lrwxrwxrwx 1 root root 10 Aug  3 17:32 wwn-0x600508b1001c21b608c562698be6deab-part8 -> ../../sdb8
lrwxrwxrwx 1 root root 10 Aug  3 17:32 wwn-0x600508b1001c21b608c562698be6deab-part9 -> ../../sdb9
lrwxrwxrwx 1 root root  9 Aug  3 17:32 wwn-0x600508b1001c384b521d0b3ba8850b49 -> ../../sda
lrwxrwxrwx 1 root root 10 Aug  3 17:32 wwn-0x600508b1001c384b521d0b3ba8850b49-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Aug  3 17:32 wwn-0x600508b1001c384b521d0b3ba8850b49-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Aug  3 17:39 wwn-0x600508b1001c384b521d0b3ba8850b49-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Aug  3 17:32 wwn-0x600508b1001c384b521d0b3ba8850b49-part4 -> ../../sda4
lrwxrwxrwx 1 root root 10 Aug  3 17:32 wwn-0x600508b1001c384b521d0b3ba8850b49-part5 -> ../../sda5
lrwxrwxrwx 1 root root 10 Aug  3 17:32 wwn-0x600508b1001c384b521d0b3ba8850b49-part6 -> ../../sda6
[09:53 xcp-ng ~]#               

I’m guessing /dm-2 to /dm-6 related to the the VMs that are already running?

If the storage that contains the VM is up and running, then I am not sure what is wrong. Might want to try their forums.

Yea, i thought it was aswell.
Least i have back ups of the VMs i care about.

this is Strange I can export the VHD

Update.
You have to Recreate the VM and them import the VDI content.
you can’t just recreate the Disk and import the VDI content.

1 Like

Thanks for providing the resolution.

1 Like

No Problem, Just in case someone else has a similar issue it might help them.

Yea there wasn’t a lot of information on XCP-NG forms about this one.

There was on from 7.4 - 7.5 where they were able to boot the machine in via recovery create a snapshot then remove it and that fixed it for them.

But while waiting from my account to be approved i decide to try and export the VDI and see if that could work.

So the issue doesn’t seam to be related to the storage pools, as i found out one of the VMs was on one the NFS pools. It Seems related to the VM metadata.