How to restore Xen Storage?

Question

Hard disks

There were three HDDs in the server, xen server was on one, storage was on the other two.
The boot drive is dead. There are no backups. There are two disks left with storage in LVM2 format, in which virtual machines (of this kind VHD-7bd542fb-34a3-475c-9cab-94819c4f6aa8).
Is it possible to restore virtual machines?
PS I
connected the storage like this https://www.schirmacher.de/display/INFO/How+to+rea...
I tried to change the virtual group, but xen manager does not see the machines in the storage.
pvdisplay
pastebin.com/hXJMnsML
vgdisplay
pastebin.com/Af56mVig
lvdisplay
pastebin.com/MxQn2Ct9

Answer 1

there were three HDDs, one had a xen server, the other two had storage.

The pvdisplay listing explicitly states that you had three terabyte disks and all three had some data.
Then that you lost 2 out of 3 volumes. At the same time, just the one on which there was free space remained alive.
Specify the status of these two disks.
What can be pulled out in theory - run pvdisplay -m
Which logical disks completely fit into the surviving physical one - you can restore them. Not completely fit - accordingly, the disk will be severely damaged in the virtual machine. Possibly to the point of being inoperable.
How to restore the survivors - google. I haven't tried. In theory (and my superficial research says yes, this is possible) initialize new LVM volumes with old UUIDs, then restore the LVM configuration (it is backed up in metadata by default), then it will be possible to start vg normally and subtract data from normal LV.

Answer 2

It was the case last year. The disk is dead. Both disks were in MD RAID1. I tried to boot from a live one, but xapi db was damaged during loading - this is a file lying in /var/xapi/state.db
As a result, I had to demolish it, otherwise the server would not exit emergency mode. All metadata on virtual machines was also lost - fortunately there were only 2 of them.
I used google to add storage. Maybe this article will help you .
There is no metadata for anyone, so you will have to create new cars and map disks with pens.
one more moment. You write that PV name - unknown device
This happens when your disk names change.
Suppose you had a storage disk /dev/sdb, and then you connected a new disk and the naming changed - maybe you connected it to the wrong ports - I xs. Either you had a raid, but now there is no raid.
Figure it out. Give another output of fdisk -l
PS:
after discussion with Argenon (below), it is clear from the listings that VG was spread over 3 disks (what the hell?!)
one disk crashed, which means the group is now inconsistent. Perhaps your LV is not recoverable at all. Try to restore.
For the future: do RAID1, and on top of it you already roll storage.

Answer 3

yes, just create a virtual machine config and send it to these images