I'm running xcp-ng 8.2.1 on a Proctetli box.

My actual partitions on the hardware are as follows:

NAME                       MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sdb                          8:16   0 931.5G  0 disk
└─XSLocalEXT--99f0de78--37cb--ead5--0c56--bd5e341416aa-99f0de78--37cb--ead5--0c56--bd5e341416aa
                           253:0    0   1.8T  0 lvm  /run/sr-mount/99f0de78-37cb-ead5-0c56-bd5e341416aa
tdc                        254:2    0    10G  0 disk
tda                        254:0    0   100G  0 disk
sda                          8:0    0 931.5G  0 disk
├─sda4                       8:4    0   512M  0 part
├─sda2                       8:2    0    18G  0 part
├─sda5                       8:5    0     4G  0 part /var/log
├─sda3                       8:3    0   890G  0 part
│ └─XSLocalEXT--99f0de78--37cb--ead5--0c56--bd5e341416aa-99f0de78--37cb--ead5--0c56--bd5e341416aa
                           253:0    0   1.8T  0 lvm  /run/sr-mount/99f0de78-37cb-ead5-0c56-bd5e341416aa
├─sda1                       8:1    0    18G  0 part /
└─sda6                       8:6    0     1G  0 part [SWAP]
tdd                        254:3    0 834.2M  1 disk
tdb                        254:1    0   721M  1 disk

Within the actual xcp-ng host I'm using local storage which is the LVM 1.8T partition.
I have a number of VMs on the host, however at the most I had either 4/5 running.
VMs on the host are either Arch Linux, Ubuntu Linux or pfsense. Currently I'm having a problem with all the Ubuntu and Arch VMs.

I believe most of the VMs that were created were created with partition scheme of /dev/xvda1 --> boot partition, /dev/xvda2 ---> root partition, /dev/xvda3 ---> swap partition.

When attempting to boot the Arch or Ubuntu VM's, I'm getting i/o errors when trying to mount the /dev/xvda2 or the root partition.

Although I haven't troubleshooted every VM, I've tried the following:

1. VM boots to recovery or busybox shell, try fsck /dev/xvda2 however process doesn't work
2. Boot a rescue CD (such as an Arch Install Disk), and then try fsck /dev/xvda2.
   When trying such an approach I'm seeing the following:

# lsblk                                                                                                  :(
NAME    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0     7:0    0 607.1M  1 loop /run/archiso/sfs/airootfs
sr0      11:0    1   721M  0 rom  /run/archiso/bootmnt
xvda    202:0    0   100G  0 disk
├─xvda1 202:1    0     1M  0 part
└─xvda2 202:2    0   100G  0 part

# fsck -yv /dev/xvda2
fsck from util-linux 2.34
e2fsck 1.45.4 (23-Sep-2019)
/dev/xvda2: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway? yes

fsck.ext4: Input/output error while recovering journal of /dev/xvda2
fsck.ext4: unable to set superblock flags on /dev/xvda2


/dev/xvda2: ********** WARNING: Filesystem still has errors **********

I've seen similar error when working with physical disk, however xvda represents virtual partitions.
I'm I just totally hosed here in terms of recovery?? I'm a little stumped how to recover.