Jump to content
Welcome to our new Citrix community!
  • 0

Error code: SR_BACKEND_FAILURE_202


Sherwin Gefferie

Question

Hi Guys, I am totally new to this. After simply upgrading a standalone server from Xenserer 8.1. to 8.2 one of the LVM disk will not come online.

As this is totally new for I am stuck on troubleshooting.

I did managed to get forget and re-introduce the SR disk. But when I try to establish the PBD I am getting an error.

 

When I perform the following, i get

 

ls -l /dev/disk/by-id
total 0
lrwxrwxrwx 1 root root 10 Aug 15 01:34 dm-name-VG_XenStorage--01510652--a5e0--3e8d--4bb7--479aa9007a40-MGT -> ../../dm-0
lrwxrwxrwx 1 root root 10 Aug 15 01:34 dm-uuid-LVM-9ZaraRNqwG4tpcWhBcgei5w2wlPouxS5lSyWtsOACkXvhGGTjUYJPgXDOfL3J5i2 -> ../.                                                                   ./dm-0
lrwxrwxrwx 1 root root  9 Aug 15 02:11 scsi-3600508e0000000001ea535fb5aa45004 -> ../../sdb
lrwxrwxrwx 1 root root  9 Aug 15 02:23 scsi-3600508e000000000c98a795805ca1608 -> ../../sda
lrwxrwxrwx 1 root root  9 Aug 15 01:33 usb-SanDisk_Ultra_01016de98026311042e31da1f2e7e47f258be9d4e079f13aff4cefbc6a0a7a1cc5                                                                   3d0000000000000000000000f9cdc5ff0a400081558107c1a7480f-0:0 -> ../../sdc
lrwxrwxrwx 1 root root 10 Aug 15 01:33 usb-SanDisk_Ultra_01016de98026311042e31da1f2e7e47f258be9d4e079f13aff4cefbc6a0a7a1cc5                                                                   3d0000000000000000000000f9cdc5ff0a400081558107c1a7480f-0:0-part1 -> ../../sdc1
lrwxrwxrwx 1 root root 10 Aug 15 01:33 usb-SanDisk_Ultra_01016de98026311042e31da1f2e7e47f258be9d4e079f13aff4cefbc6a0a7a1cc5                                                                   3d0000000000000000000000f9cdc5ff0a400081558107c1a7480f-0:0-part2 -> ../../sdc2
lrwxrwxrwx 1 root root 10 Aug 15 01:33 usb-SanDisk_Ultra_01016de98026311042e31da1f2e7e47f258be9d4e079f13aff4cefbc6a0a7a1cc5                                                                   3d0000000000000000000000f9cdc5ff0a400081558107c1a7480f-0:0-part3 -> ../../sdc3
lrwxrwxrwx 1 root root 10 Aug 15 01:33 usb-SanDisk_Ultra_01016de98026311042e31da1f2e7e47f258be9d4e079f13aff4cefbc6a0a7a1cc5                                                                   3d0000000000000000000000f9cdc5ff0a400081558107c1a7480f-0:0-part5 -> ../../sdc5
lrwxrwxrwx 1 root root 10 Aug 15 01:33 usb-SanDisk_Ultra_01016de98026311042e31da1f2e7e47f258be9d4e079f13aff4cefbc6a0a7a1cc5                                                                   3d0000000000000000000000f9cdc5ff0a400081558107c1a7480f-0:0-part6 -> ../../sdc6
lrwxrwxrwx 1 root root  9 Aug 15 02:11 wwn-0x600508e0000000001ea535fb5aa45004 -> ../../sdb
lrwxrwxrwx 1 root root  9 Aug 15 02:23 wwn-0x600508e000000000c98a795805ca1608 -> ../../sda

 

 

 xe pbd-list
uuid ( RO)                  : 74cc00b1-b36f-1c65-0ac2-b1637678b45e
             host-uuid ( RO): 837c14f7-8730-4cd4-b2b4-6eb02f824e4b
               sr-uuid ( RO): 52fa0de8-002a-a70a-902a-f3c1fe325efe
         device-config (MRO): device: /dev/disk/by-id/scsi-3600508e000000000c98a795805ca1608
    currently-attached ( RO): false


uuid ( RO)                  : 717b89bb-e8a5-30bb-c604-5ebdb6f90539
             host-uuid ( RO): 837c14f7-8730-4cd4-b2b4-6eb02f824e4b
               sr-uuid ( RO): be3df3db-dc0f-a839-75e5-f8770fed5630
         device-config (MRO): location: /dev/xapi/cd
    currently-attached ( RO): true


uuid ( RO)                  : a604df3f-dceb-948d-21dc-140e33fd4a94
             host-uuid ( RO): 837c14f7-8730-4cd4-b2b4-6eb02f824e4b
               sr-uuid ( RO): 01510652-a5e0-3e8d-4bb7-479aa9007a40
         device-config (MRO): device: /dev/sdb
    currently-attached ( RO): true


uuid ( RO)                  : 63b85a6b-4880-be41-8b96-083cdd7d5269
             host-uuid ( RO): 837c14f7-8730-4cd4-b2b4-6eb02f824e4b
               sr-uuid ( RO): 9b029c27-4504-d932-5a45-076ad2eee162
         device-config (MRO): legacy_mode: true; location: /mnt/ISOs
    currently-attached ( RO): true


uuid ( RO)                  : 801316c0-9dbd-ed5f-463f-6d702fe8641a
             host-uuid ( RO): 837c14f7-8730-4cd4-b2b4-6eb02f824e4b
               sr-uuid ( RO): 2a50fadf-37b6-a863-b163-08fae7572f1f
         device-config (MRO): location: /dev/xapi/block
    currently-attached ( RO): true

 

[root@PROD00 ~]# pvdisplay
  --- Physical volume ---
  PV Name               /dev/sdb
  VG Name               VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40
  PV Size               <3.64 TiB / not usable 12.00 MiB
  Allocatable           yes
  PE Size               4.00 MiB
  Total PE              953725
  Free PE               753220
  Allocated PE          200505
  PV UUID               qMaced-9mdB-eQ5e-z6Ed-Xwqz-ITBM-rHzLvI

  Couldn't find device with uuid WaReyV-MB9q-68xB-IpU9-E3QD-1Icw-cGWnzG.
  --- Physical volume ---
  PV Name               [unknown]
  VG Name               VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe
  PV Size               <144.25 GiB / not usable 14.98 MiB
  Allocatable           yes
  PE Size               4.00 MiB
  Total PE              36924
  Free PE               29222
  Allocated PE          7702
  PV UUID               WaReyV-MB9q-68xB-IpU9-E3QD-1Icw-cGWnzG

  --- Physical volume ---
  PV Name               /dev/sda
  VG Name               VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe
  PV Size               <3.64 TiB / not usable 12.00 MiB
  Allocatable           yes
  PE Size               4.00 MiB
  Total PE              953725
  Free PE               398539
  Allocated PE          555186
  PV UUID               edmqna-Ej5r-DnYi-ZBrU-llxf-G7Vt-vjK2pK

 

 

[root@PROD00 ~]# lvscan
  ACTIVE            '/dev/VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40/MGT' [4.00 MiB] inherit
  inactive          '/dev/VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40/VHD-c8f3900d-c45a-4384-ad82-2a75cc89057a' [100.20 GiB] inherit
  inactive          '/dev/VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40/VHD-48367a74-acbb-4ccb-aa00-45e29873c2de' [81.99 GiB] inherit
  inactive          '/dev/VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40/ISOs' [100.00 GiB] inherit
  inactive          '/dev/VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40/VHD-aff6654d-6f68-4dfd-82da-b20c9aed0776' [<200.40 GiB] inherit
  inactive          '/dev/VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40/VHD-de82f711-541e-446e-9875-4e6fdf8f05fc' [100.20 GiB] inherit
  inactive          '/dev/VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40/VHD-d71aa5c5-2ad7-4c5f-9a0a-96cce0597c55' [<200.40 GiB] inherit
  inactive          '/dev/VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40/VHD-f286a575-93e3-4159-a0bb-0387bc82ab73' [8.00 MiB] inherit
  inactive          '/dev/VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40/VHD-78e3e9e7-8b9a-46c1-b668-d0bdaf76ea51' [16.00 MiB] inherit
  Couldn't find device with uuid WaReyV-MB9q-68xB-IpU9-E3QD-1Icw-cGWnzG.
  inactive          '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/MGT' [4.00 MiB] inherit
  inactive          '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-68689237-b700-46c5-ae75-d633e6ac3f34' [100.20 GiB] inherit
  inactive          '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-3798bfaa-b512-4ada-a0bb-603e2a275eb9' [<10.03 GiB] inherit
  inactive          '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-3ea8ccad-f7fe-49a6-b5e6-ee4c6009f5cb' [<250.50 GiB] inherit
  inactive          '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-e958bbbe-a799-4f87-9956-ef560b4aeeae' [<50.11 GiB] inherit
  inactive          '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-478d4c7b-9ea0-4ecc-82e7-b5005c6f3bb4' [<10.03 GiB] inherit
  inactive          '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-1fd4edf7-9fb1-458a-afcc-beeb57de15cf' [80.16 GiB] inherit
  inactive          '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-f01cf7b2-f159-4cdf-adfc-6c9039a1a6fe' [<50.11 GiB] inherit
  inactive          '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-f8edb8ca-486b-49c8-be49-0c9d31ef64c7' [<10.03 GiB] inherit
  inactive          '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-4b2d042d-4947-480d-9f9b-0fdd66f9675a' [150.30 GiB] inherit
  inactive          '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-9a92a9aa-96d9-4299-8076-36b91c5b43f8' [<34.45 GiB] inherit
  inactive          '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-ea2ca023-e506-43ae-a93b-6b0e140df995' [100.20 GiB] inherit
  inactive          '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-bd26c452-e699-4b59-acf2-4ba0676dfd43' [500.98 GiB] inherit
  inactive          '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-c6ef0b5e-3d93-4463-a079-cc8a52faaa23' [<651.28 GiB] inherit
  inactive          '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-77028f32-c907-41ca-8d8f-28b6a1cd079a' [100.20 GiB] inherit
  inactive          '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-6c7651d5-0635-4d55-8104-2e99a03452a2' [100.20 GiB] inherit
[root@PROD00 ~]# xe pbd-plug uuid=8f8d667c-0fbd-bcca-d47b-e6e71433cd23
Error code: SR_BACKEND_FAILURE_46
Error parameters: , The VDI is not available [opterr=Error scanning VDI 478d4c7b-9ea0-4ecc-82e7-b5005c6f3bb4],
[root@PROD00 ~]# lvremove /dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-478d4c7b-9ea0-4ecc-82e7-b5005c6f3bb4
  Couldn't find device with uuid WaReyV-MB9q-68xB-IpU9-E3QD-1Icw-cGWnzG.
  Logical volume "VHD-478d4c7b-9ea0-4ecc-82e7-b5005c6f3bb4" successfully removed
[root@PROD00 ~]# xe pbd-plug uuid=8f8d667c-0fbd-bcca-d47b-e6e71433cd23
Error code: SR_BACKEND_FAILURE_46
Error parameters: , The VDI is not available [opterr=Error scanning VDI f8edb8ca-486b-49c8-be49-0c9d31ef64c7],
[root@PROD00 ~]# xe pbd-plug uuid=8f8d667c-0fbd-bcca-d47b-e6e71433cd23
Error code: SR_BACKEND_FAILURE_46
Error parameters: , The VDI is not available [opterr=Error scanning VDI f8edb8ca-486b-49c8-be49-0c9d31ef64c7],
[root@PROD00 ~]# lvremove /dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-f8edb8ca-486b-49c8-be49-0c9d31ef64c7
  Couldn't find device with uuid WaReyV-MB9q-68xB-IpU9-E3QD-1Icw-cGWnzG.
  Logical volume "VHD-f8edb8ca-486b-49c8-be49-0c9d31ef64c7" successfully removed
[root@PROD00 ~]# xe pbd-plug uuid=8f8d667c-0fbd-bcca-d47b-e6e71433cd23
Error code: SR_BACKEND_FAILURE_46
Error parameters: , The VDI is not available [opterr=Error scanning VDI 3798bfaa-b512-4ada-a0bb-603e2a275eb9],
[root@PROD00 ~]# lvremove /dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-3798bfaa-b512-4ada-a0bb-603e2a275eb9
  Couldn't find device with uuid WaReyV-MB9q-68xB-IpU9-E3QD-1Icw-cGWnzG.
  Logical volume "VHD-3798bfaa-b512-4ada-a0bb-603e2a275eb9" successfully removed
[root@PROD00 ~]# xe pbd-plug uuid=8f8d667c-0fbd-bcca-d47b-e6e71433cd23
Error code: SR_BACKEND_FAILURE_202
Error parameters: , General backend error [opterr=Command ['/sbin/lvchange', '-ay', '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/MGT'] failed (Couldn't find device with uuid WaReyV-MB9q-68xB-IpU9-E3QD-1Icw-cGWnzG.
  Refusing activation of partial LV VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/MGT.  Use '--activationmode partial' to override.): Input/output error], Exception AttributeError: "LVMMetadataHandler instance has no attribute 'fd'" in <bound method LVMMetadataHandler.__del__ of <srmetadata.LVMMetadataHandler instance at 0x7f01adca9050>> ignored

[root@PROD00 ~]#

 

The SR I rebuild is VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe.

 

My question is how do i remove the uuid that is missing and what are the consequences?

As this is a productionserver I can not lose any data.

 

PLEASE HELP.

Thankss In advance.

 

Sherwin

Link to comment

6 answers to this question

Recommended Posts

  • 0

You might try destroying and re-creating the PBD for the SR in question. Did you first try a "vgchange -ay" to see if any inactive volumes were reactivated?

As to the 46 error (VDI not found), you might also try this: https://support.unitrends.com/ReliableDR/s/article/000005347

 

The failure 202 has to do with a host not being able to be ejected from a pool which seems out of context here.

Link to comment
  • 0

Thank you for repsonding Tobias.

 

Destroying the PBD will that lose all the info on the disk, like the VM's?

If not, what are the consequences doing that?

 

vgscan reports an error

 

# vgscan -ay
vgscan: invalid option -- 'a'
  Error during parsing of command line

 

without parameter i get

 

# vgscan
  Reading all physical volumes.  This may take a while...
  Found volume group "VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40" using metadata type lvm2
  Couldn't find device with uuid WaReyV-MB9q-68xB-IpU9-E3QD-1Icw-cGWnzG.
  Found volume group "VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe" using metadata type lvm2

 

How can I remove the faulty uuid which is reported alos above in previous errors?

Is "vgremove" the solution here?

 

Also what I am curious about. is the following.

The UUID below is ca not be found, but this same UUID is see below. How do i need to see this?

 

Couldn't find device with uuid WaReyV-MB9q-68xB-IpU9-E3QD-1Icw-cGWnzG.
  --- Physical volume ---
  PV Name               [unknown]
  VG Name               VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe
  PV Size               <144.25 GiB / not usable 14.98 MiB
  Allocatable           yes
  PE Size               4.00 MiB
  Total PE              36924
  Free PE               29222
  Allocated PE          7702
  PV UUID               WaReyV-MB9q-68xB-IpU9-E3QD-1Icw-cGWnzG

Link to comment
  • 0

Oke. I performed that and now all say "ACTIVE" except one.

 

# vgchange -ay
  9 logical volume(s) in volume group "VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40" now active
  Couldn't find device with uuid WaReyV-MB9q-68xB-IpU9-E3QD-1Icw-cGWnzG.
  Refusing activation of partial LV VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/MGT.  Use '--activationmode partial' to override.
  12 logical volume(s) in volume group "VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe" now active
# lvscan
  ACTIVE            '/dev/VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40/MGT' [4.00 MiB] inherit
  ACTIVE            '/dev/VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40/VHD-c8f3900d-c45a-4384-ad82-2a75cc89057a' [100.20 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40/VHD-48367a74-acbb-4ccb-aa00-45e29873c2de' [81.99 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40/ISOs' [100.00 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40/VHD-aff6654d-6f68-4dfd-82da-b20c9aed0776' [<200.40 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40/VHD-de82f711-541e-446e-9875-4e6fdf8f05fc' [100.20 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40/VHD-d71aa5c5-2ad7-4c5f-9a0a-96cce0597c55' [<200.40 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40/VHD-f286a575-93e3-4159-a0bb-0387bc82ab73' [8.00 MiB] inherit
  ACTIVE            '/dev/VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40/VHD-78e3e9e7-8b9a-46c1-b668-d0bdaf76ea51' [16.00 MiB] inherit
  Couldn't find device with uuid WaReyV-MB9q-68xB-IpU9-E3QD-1Icw-cGWnzG.
  inactive          '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/MGT' [4.00 MiB] inherit
  ACTIVE            '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-68689237-b700-46c5-ae75-d633e6ac3f34' [100.20 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-3ea8ccad-f7fe-49a6-b5e6-ee4c6009f5cb' [<250.50 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-e958bbbe-a799-4f87-9956-ef560b4aeeae' [<50.11 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-1fd4edf7-9fb1-458a-afcc-beeb57de15cf' [80.16 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-f01cf7b2-f159-4cdf-adfc-6c9039a1a6fe' [<50.11 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-4b2d042d-4947-480d-9f9b-0fdd66f9675a' [150.30 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-9a92a9aa-96d9-4299-8076-36b91c5b43f8' [<34.45 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-ea2ca023-e506-43ae-a93b-6b0e140df995' [100.20 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-bd26c452-e699-4b59-acf2-4ba0676dfd43' [500.98 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-c6ef0b5e-3d93-4463-a079-cc8a52faaa23' [<651.28 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-77028f32-c907-41ca-8d8f-28b6a1cd079a' [100.20 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-6c7651d5-0635-4d55-8104-2e99a03452a2' [100.20 GiB] inherit

I have performed the steps in the article, but still no luck.

What I find strange is the following below.

How can the highlighted PV's have the same VG? How do i remove the "[unknown]" PV?

doesnot this conflict when creating the SR?

 

PV /dev/sdb with UUID qMaced-9mdB-eQ5e-z6Ed-Xwqz-ITBM-rHzLvI    VG VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40   lvm2 [<3.64 TiB / 2.87 TiB free]
  Couldn't find device with uuid WaReyV-MB9q-68xB-IpU9-E3QD-1Icw-cGWnzG.
  PV [unknown] with UUID WaReyV-MB9q-68xB-IpU9-E3QD-1Icw-cGWnzG   VG VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe   lvm2 [144.23 GiB / 144.23 GiB free]
  PV /dev/sda with UUID edmqna-Ej5r-DnYi-ZBrU-llxf-G7Vt-vjK2pK    VG VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe   lvm2 [<3.64 TiB / 1.52 TiB free]

 

As forcing it would work.

 

# pvremove PV WaReyV-MB9q-68xB-IpU9-E3QD-1Icw-cGWnzG -t --force
  TEST MODE: Metadata will NOT be updated and volumes will not be (de)activated.
  Couldn't find device with uuid WaReyV-MB9q-68xB-IpU9-E3QD-1Icw-cGWnzG.
  Device PV not found.
  Device WaReyV-MB9q-68xB-IpU9-E3QD-1Icw-cGWnzG not found.
  

 

Link to comment
  • 0

Oke. I now performed a --activationmode partial and all are "ACTIVE"

 

# vgchange -ay --activationmode partial
  PARTIAL MODE. Incomplete logical volumes will be processed.
  9 logical volume(s) in volume group "VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40" now active
  Couldn't find device with uuid WaReyV-MB9q-68xB-IpU9-E3QD-1Icw-cGWnzG.
  13 logical volume(s) in volume group "VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe" now active
  

# lvscan
  ACTIVE            '/dev/VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40/MGT' [4.00 MiB] inherit
  ACTIVE            '/dev/VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40/VHD-c8f3900d-c45a-4384-ad82-2a75cc89057a' [100.20 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40/VHD-48367a74-acbb-4ccb-aa00-45e29873c2de' [81.99 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40/ISOs' [100.00 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40/VHD-aff6654d-6f68-4dfd-82da-b20c9aed0776' [<200.40 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40/VHD-de82f711-541e-446e-9875-4e6fdf8f05fc' [100.20 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40/VHD-d71aa5c5-2ad7-4c5f-9a0a-96cce0597c55' [<200.40 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40/VHD-f286a575-93e3-4159-a0bb-0387bc82ab73' [8.00 MiB] inherit
  ACTIVE            '/dev/VG_XenStorage-01510652-a5e0-3e8d-4bb7-479aa9007a40/VHD-78e3e9e7-8b9a-46c1-b668-d0bdaf76ea51' [16.00 MiB] inherit
  Couldn't find device with uuid WaReyV-MB9q-68xB-IpU9-E3QD-1Icw-cGWnzG.
  ACTIVE            '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/MGT' [4.00 MiB] inherit
  ACTIVE            '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-68689237-b700-46c5-ae75-d633e6ac3f34' [100.20 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-3ea8ccad-f7fe-49a6-b5e6-ee4c6009f5cb' [<250.50 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-e958bbbe-a799-4f87-9956-ef560b4aeeae' [<50.11 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-1fd4edf7-9fb1-458a-afcc-beeb57de15cf' [80.16 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-f01cf7b2-f159-4cdf-adfc-6c9039a1a6fe' [<50.11 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-4b2d042d-4947-480d-9f9b-0fdd66f9675a' [150.30 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-9a92a9aa-96d9-4299-8076-36b91c5b43f8' [<34.45 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-ea2ca023-e506-43ae-a93b-6b0e140df995' [100.20 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-bd26c452-e699-4b59-acf2-4ba0676dfd43' [500.98 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-c6ef0b5e-3d93-4463-a079-cc8a52faaa23' [<651.28 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-77028f32-c907-41ca-8d8f-28b6a1cd079a' [100.20 GiB] inherit
  ACTIVE            '/dev/VG_XenStorage-52fa0de8-002a-a70a-902a-f3c1fe325efe/VHD-6c7651d5-0635-4d55-8104-2e99a03452a2' [100.20 GiB] inherit

 

# xe pbd-plug uuid=62621c26-f9f4-bce9-c55b-42a355ec985c
The server failed to handle your request, due to an internal error. The given message may give details useful for debugging the problem.
message: Storage_error ([S(Backend_error);[S(SR_BACKEND_FAILURE_181);[S();S(Error in Metadata volume operation for SR. [opterr=Failed to read file with params [5, 0, 512, 512]. Error: 5]);S()]]])
 

I still got the error above, but the PBD is connected and enable to connect and start the VM's again.

I will migrate the VM's to a newly create SR and destroy the problematic one.

 

Thanks again Tobias.

 

Link to comment
  • 0

Sherwin,

Oh, that's encouraging! Once you have successfully migrated the VMs. I'd suggest destroying and re-creating that SR from scratch as it may still be partially corrupted. You are wise not to trust its integrity. If it re-initializes OK, you are probably good to go with using it.

 

I'd also make a backup pf your :VM metadata if one didn't created on its own. There are both /etc/lvm/backup and /etc/lvm/archive subdirectories.

 

As will all data, have regular backups of VMs, metadata, configuration settings, is always a good practice. Best is to put all this on some totally external storage to increase sfety.

 

Best,

--Tobias

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...