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

VDI not available on SR Rescan


Ratul Dutta1709160162

Question

I am getting "VDI not available" on  my SR attached to my Xen Server 6.5 pool since last one week. SR is SAN storage of 6TB size, in pool we have 15 HOST. I tried shutting down all VMs in SAN and rebooting the SAN but still same error. 

 

Any help related to this will be very much helpful.

 

Getting below error:

Error code: SR_BACKEND_FAILURE_46
Error parameters: , The VDI is not available [opterr=Error scanning VDI d8a94be7-7975-42fc-a6f3-2b6282b28ce4], 

 

I tried doing below things...

xe vbd-list vdi-uudi=d8a94be7-7975-42fc-a6f3-2b6282b28ce4.

 

showing no VMs attached.. tried running forget VDI but nothing happened

Link to comment

16 answers to this question

Recommended Posts

  • 1

Long pending issue is resolved today....

 

Steps followed:

lvscan

search the uuid=d8a94be7-7975-42fc-a6f3-2b6282b28ce4 due to which SAN was stuck and not reclaiming any space. Got two entries, one was showing Active and one was inactive. Then used below commands to delete the lv as it was not used by any VM..cross checked earlier using xe vdi-list uuid= command ..showing empty

 

lvremove /dev/VG_XenStorage-7154a02f-b64c-a25b-d4a7-f735cda36c4f/VHD-d8a94be7-7975-42fc-a6f3-2b6282b28ce4   (was showing Active)

 

lvremove /dev/VG_XenStorage-7154a02f-b64c-a25b-d4a7-f735cda36c4f/inflate_d8a94be7-7975-42fc-a6f3-2b6282b28ce4_8388608   (was showing inactive)

 

Last command was to resolve rescan error after running above two commands

 

lvrename /dev/VG_XenStorage-7154a02f-b64c-a25b-d4a7-f735cda36c4f/MGT /dev/VG_XenStorage-7154a02f-b64c-a25b-d4a7-f735cda36c4f/MGT.bak

 

All Started working now.. back to Normal.. I was in a state to format the SAN.. saved lot of my time..

 

Thanks a lot to all for your guidance..

  • Like 1
Link to comment
  • 0
15 hours ago, Alan Lantz said:

Were the hosts restarted? Sometimes they can lock a vdi and cause it to not start.

And it could be something corrupted the VDI.

 

--Alan--

 

Hi Alan..No I have not restarted  the HOSTs yet, will do it. Hopefully it will resolve the issue.. few years back same happened. After rebooting all HOSTs issue got resolved.. I was checking if any other options without rebooting the HOST. As its production so trying to avoid downtime.

Link to comment
  • 0
15 hours ago, Tobias Kreidl said:

You might have to find the corresponding VBD and re-plug it. Do you see the VDI at all if you try to list it out and if so, does it have any VBD associated with it?

 

-=Tobias

Its not showing any VBD after running below command...

 xe vbd-list vdi-uudi=d8a94be7-7975-42fc-a6f3-2b6282b28ce4

 

Also tried to forget the VDI but no luck

Link to comment
  • 0
14 hours ago, Ratul Dutta1709160162 said:

Its not showing any VBD after running below command...

 xe vbd-list vdi-uudi=d8a94be7-7975-42fc-a6f3-2b6282b28ce4

 

Also tried to forget the VDI but no luck

I tried below commands... and output given below..

 

[root@XENH1-MKCL ~]# xe sr-scan uuid=7154a02f-b64c-a25b-d4a7-f735cda36c4f
Error code: SR_BACKEND_FAILURE_46
Error parameters: , The VDI is not available [opterr=Error scanning VDI d8a94be7-7975-42fc-a6f3-2b6282b28ce4], 
[root@XENH1-MKCL ~]# xe vbd-list vdi-uuid=d8a94be7-7975-42fc-a6f3-2b6282b28ce4
[root@XENH1-MKCL ~]# xe vdi-forget uuid=d8a94be7-7975-42fc-a6f3-2b6282b28ce4
The uuid you supplied was invalid.
type: VDI
uuid: d8a94be7-7975-42fc-a6f3-2b6282b28ce4
[root@XENH1-MKCL ~]# 

Link to comment
  • 0

xe vdi-list sr-uuid=7154a02f-b64c-a25b-d4a7-f735cda36c4f --minimal

 

Just making sure you see the vdi on the SR. If you do then you must have a corrupted vdi

which really monkeys with an SR. If this is so I would probably create a new SR and migrate

all of the other vdi's to the new one. I've never had very good luck with vdi recovery. You 

will likely need to recover the VM data from a backup. There are some things you can do

to try and recover, but I would do those once my other good data is on another SR.

 

--Alan--

 

Link to comment
  • 0
On 01/10/2018 at 4:49 PM, AshokReddy Bhavanam said:

Seems there is some issue with XS6.5 since I've the same issue happening with my infra.

Just want to check what is the SAN you are using, in my case we are using Dell.

 

Sharing the thread if you wanna check.

https://discussions.citrix.com/topic/398335-vdi-not-available-after-executing-vdi-forget-command/?page=0#comment-2021328

 

AB

Yes I am also using Dell Storage.. MD3200i

Link to comment
  • 0

Try to use vhd-util to check if physical VHD corrupt.

/dev/VG_XenStorage-600e7112-683d-740e-9aa2-33544f4ee83d/VHD-51a4fe60-9e27-4965-93cd-d28889e66f9a 

1. reactive the problematic vhd lv

lvchange -an /dev/VG_XenStorage-7154a02f-b64c-a25b-d4a7-f735cda36c4f/VHD-d8a94be7-7975-42fc-a6f3-2b6282b28ce4

 

lvchange -ay  /dev/VG_XenStorage-7154a02f-b64c-a25b-d4a7-f735cda36c4f/VHD-d8a94be7-7975-42fc-a6f3-2b6282b28ce4

 

2. Read vhd header to see if there is corrupt parameters

vhd-util read -n /dev/VG_XenStorage-7154a02f-b64c-a25b-d4a7-f735cda36c4f/VHD-d8a94be7-7975-42fc-a6f3-2b6282b28ce4 -p

 

 

 

 

Link to comment
  • 0
25 minutes ago, Huaijian Lin said:

Try to use vhd-util to check if physical VHD corrupt.

/dev/VG_XenStorage-600e7112-683d-740e-9aa2-33544f4ee83d/VHD-51a4fe60-9e27-4965-93cd-d28889e66f9a 

1. reactive the problematic vhd lv

lvchange -an /dev/VG_XenStorage-7154a02f-b64c-a25b-d4a7-f735cda36c4f/VHD-d8a94be7-7975-42fc-a6f3-2b6282b28ce4

 

lvchange -ay  /dev/VG_XenStorage-7154a02f-b64c-a25b-d4a7-f735cda36c4f/VHD-d8a94be7-7975-42fc-a6f3-2b6282b28ce4

 

2. Read vhd header to see if there is corrupt parameters

vhd-util read -n /dev/VG_XenStorage-7154a02f-b64c-a25b-d4a7-f735cda36c4f/VHD-d8a94be7-7975-42fc-a6f3-2b6282b28ce4 -p

 

 

 

 

I have done above steps.. given below the outputs..

 

[root@XENH1-MKCL ~]# lvchange -an /dev/VG_XenStorage-7154a02f-b64c-a25b-d4a7-f735cda36c4f/VHD-d8a94be7-7975-42fc-a6f3-2b6282b28ce4
[root@XENH1-MKCL ~]# lvchange -ay  /dev/VG_XenStorage-7154a02f-b64c-a25b-d4a7-f735cda36c4f/VHD-d8a94be7-7975-42fc-a6f3-2b6282b28ce4
[root@XENH1-MKCL ~]# vhd-util read -n /dev/VG_XenStorage-7154a02f-b64c-a25b-d4a7-f735cda36c4f/VHD-d8a94be7-7975-42fc-a6f3-2b6282b28ce4 -p
Failed to open /dev/VG_XenStorage-7154a02f-b64c-a25b-d4a7-f735cda36c4f/VHD-d8a94be7-7975-42fc-a6f3-2b6282b28ce4: -22

/dev/VG_XenStorage-7154a02f-b64c-a25b-d4a7-f735cda36c4f/VHD-d8a94be7-7975-42fc-a6f3-2b6282b28ce4 appears invalid; dumping headers

VHD Footer Summary:
-------------------
Cookie              : 
Features            : (0x00000000) 
File format version : Major: 0, Minor: 0
Data offset         : 2112
Timestamp           : Sat Jan  1 05:30:00 2000
Creator Application : ''
Creator version     : Major: 0, Minor: 0
Creator OS          : Unknown!
Original disk size  : 0 MB (0 Bytes)
Current disk size   : 0 MB (0 Bytes)
Geometry            : Cyl: 0, Hds: 0, Sctrs: 0
                    : = 0 MB (0 Bytes)
Disk type           : Unknown type!

Checksum            : 0x0|0xffffba3b (Bad!)
UUID                : 8004d440-0000-0000-e09a-ee4000000000
Saved state         : No
Hidden              : 0

VHD Header Summary:
-------------------
Cookie              : 
Data offset (unusd) : 0
Table offset        : 0
Header version      : 0x00000000
Max BAT size        : 0
Block size          : 0 (0 MB)
Parent name         : 
Parent UUID         : 00000000-0000-0000-0000-000000000000
Parent timestamp    : Sat Jan  1 05:30:00 2000
Checksum            : 0x0|0xffffffff (Bad!)

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...