восстановление LVM и xfs в файле img

[14:45, 14.9.2017] +7 962 680-46-98: mount -t xfs -o loop /dev/vdb2 /mnt/test
mount: wrong fs type, bad option, bad superblock on /dev/loop1,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so                        
[14:45, 14.9.2017] +7 962 680-46-98: dmesg | tail  
pci 0000:00:0a.0: using default PCI settings
virtio-pci 0000:00:0a.0: enabling device (0000 -> 0003)
virtio-pci 0000:00:0a.0: PCI INT A -> Link[LNKB] -> GSI 11 (level, high) -> IRQ 11
virtio-pci 0000:00:0a.0: irq 35 for MSI/MSI-X
virtio-pci 0000:00:0a.0: irq 36 for MSI/MSI-X
 vdb: vdb1 vdb2
SGI XFS with ACLs, security attributes, large block/inode numbers, no debug enabled
SGI XFS Quota Management subsystem
XFS (loop1): bad magic number
XFS (loop1): SB validate failed 

fdisk -l
Disk /dev/vda: 161.1 GB, 161061273600 bytes
16 heads, 63 sectors/track, 312076 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00036690

   Device Boot      Start         End      Blocks   Id  System
/dev/vda1   *           3        1018      512000   83  Linux
Partition 1 does not end on cylinder boundary.
/dev/vda2            1018      312077   156773376   8e  Linux LVM

Disk /dev/vdb: 161.1 GB, 161061273600 bytes
16 heads, 63 sectors/track, 312076 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000a1f87

           1018      312077   156773376   8e  Linux LVM
   Device Boot      Start         End      Blocks   Id  System
/dev/vdb1   *           3        1018      512000   83  Linux
Partition 1 does not end on cylinder boundary.
/dev/vdb2            1018      312077   156773376   8e  Linux LVM
Partition 2 does not end on cylinder boundary.

xfs_check /dev/vdb
xfs_check: /dev/vdb is not a valid XFS filesystem (unexpected SB magic number 0xeb639010)
xfs_check: size check failed
xfs_check: WARNING - filesystem uses v1 dirs,limited functionality provided.
xfs_check: read failed: Invalid argument
xfs_check: data size check failed
cache_node_purge: refcount was 1, not zero (node=0x26ffb10)
xfs_check: cannot read root inode (22)
cache_node_purge: refcount was 1, not zero (node=0x26ffca0)
xfs_check: cannot read realtime bitmap inode (22)
xfs_check: size check failed
xfs_check: WARNING - filesystem uses v1 dirs,limited functionality provided.
xfs_check: read failed: Invalid argument
xfs_check: data size check failed
bad superblock magic number eb639010, giving up

xfs_repair -n  /dev/vdb1
Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - scan filesystem freespace and inode maps...
        - found root inode chunk
Phase 3 - for each AG...
        - scan (but don't clear) agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
        - traversing filesystem ...
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify link counts...
No modify flag set, skipping filesystem flush and exiting.