Jump to content


Photo

PVS 6.1 vDisk is locked. 0xffff8017

Started by Adam Kamali , 10 April 2012 - 07:33 PM
23 replies to this topic

Adam Kamali Members

Adam Kamali
  • 429 posts

Posted 10 April 2012 - 07:33 PM

Hello Everyone;

I don't know if it's me or it's just a bad luck.

My image is ON STANDALONE mode and no one touched it. All the sudden it's not accessible and when I checked the boot process on one VM I see it's pointing to my PVS TFTP 172.27.102.10 and it's trying to stream the image but get status Vdisk is locked. 0xffff8017.

I have seen this behavior when you set the machine on private mode* and you try to connect more than one target device to it. but not when the image is set *on stand alone mode (Read only).

Lucky I had a little older backup image that I kept, so published it to all client devices and it worked.

The question is why my image was working for a week then all the sudden died without a warning?.

2 DDC 5.6
2 PVS 6.1
NetScaler (TFTP load balance).
XenServer 5.6

Please note that I have turned off 1 DDC and 1 PVS just to eliminate any other possibilities that could contribute to this problem.

FACT: I have rebooted the machines (PVS) servers this morning before this issue start happening, could this be the reason why this happened?

- I have rebooted the first machine, then waited until it came back online then rebooted the second box.

I did not try to stop streaming service or close any open connections on the server before rebooting, could this damage the vDisk image? Although it's in Read Only mode?

Thanks;

Adam

Edited by: Adam Kamali on Apr 10, 2012 3:34 PM

Attached Files



Adam Kamali Members

Adam Kamali
  • 429 posts

Posted 11 April 2012 - 04:17 AM

Finally managed to fix the issue without opening an SR Hooray!

- I deleted the vDisk from PVS console
- Went and deleted the .lok file.
- Added the vDisk again to my PVS store
- Now the vDisk start showing it's set to "Private" very weird, set it back to standard and it started woking again.

If you ever face this problem, drop a line here!



Jeroen Kompier Members

Jeroen Kompier
  • 20 posts

Posted 16 April 2012 - 11:07 PM

Yes. Just had the exact same issue and using your method of deleting and re-adding resolve it for me as well.

Experienced the same with the vdisk being marked as private although it should have been Standard Mode on the re-add.

Perhaps we are using the same method to load balance?

1. Create a new non-load ballanced vdisk and xenconverted into the vdisk.
2. Copy the file across to the second PVS.
3. Mark the vdisk for Load Balancing with No Subnet Affinity.

Cheers
Jeroen



David Figueroa-jessica Members

David Figueroa-jessica
  • 26 posts

Posted 17 April 2012 - 07:54 PM

I had the same issue and the same resolution.

David F.



Bryan Kirschenman Members

Bryan Kirschenman
  • 99 posts

Posted 18 April 2012 - 03:12 PM

Yeah I was having the same issues. When using servers that were load balanced to create an image. As a work around I have just a separate server with no load balancing to create/edit the images. Then I copy the vhd and pvp down to the other servers. Then I add the existing vhd after I have copied it over to both servers.



Adam Kamali Members

Adam Kamali
  • 429 posts

Posted 18 April 2012 - 03:20 PM

Sorry guys I was a bit busy to reply, yes we are load balancing via local disk (make a copy manually).

The cause of the issue still unknown.



Jeroen Kompier Members

Jeroen Kompier
  • 20 posts

Posted 18 April 2012 - 10:18 PM

I have done a bit more investigation into this.

PVS 6 seems to have some new features around version and replication that checks for consistency in vdisks. If you go to your store, pick a vdisk and right click - Replication Status you will get a status of the vdisks on your PVS boxes.

In my case one of the copies of the vdisk was not the same. A manual copy of the correct vdisk to the PVS box that was not in sync fixed my issues.

Hope this helps.

Cheers
JK



David Figueroa-jessica Members

David Figueroa-jessica
  • 26 posts

Posted 18 April 2012 - 10:40 PM

I had tried that, and it did not work for me. :-\

David F.



Robert Posey Members

Robert Posey
  • 78 posts

Posted 01 May 2012 - 06:02 PM

I have tried both resolutions with no luck. 8(



Adam Kamali Members
  • #10

Adam Kamali
  • 429 posts

Posted 01 May 2012 - 06:10 PM

There must be a reason why the image is getting locked up.

Either it's an issue with console, or configuration problem.

It would be better to list a description of the environment you are using to see what caused it.

Edited by: adamtigris on May 1, 2012 2:10 PM



David Figueroa-jessica Members
  • #11

David Figueroa-jessica
  • 26 posts

Posted 01 May 2012 - 07:17 PM

I don't think it's a configuration issue, or a console problem per-se. It appears to be a bug in the system, an it is definitely not the first one I have found in the new PVS 6.1 environment.

In my environment, I have

2 PVS 6.1 servers (vmware)
2 XD 5.6 servers (vmware)

David F.



Preston Gallwas Members
  • #12

Preston Gallwas
  • 91 posts

Posted 09 May 2012 - 03:33 PM

I'm getting this too.

2 PVS 6.1 servers on the same subnet (Hyper-V)
Load balancing no subnet affinity
using DFSR to replicate images
Per eDocs, replicating all files (including LOK) <-- I wonder if this shouldnt be.

Since I can't take my image offline I've found a (really terrible) workaround is to create a new version, promote it, then boot...until the next time. oy.



CHRIS SCOTTO Members
  • #13

CHRIS SCOTTO
  • 45 posts

Posted 25 May 2012 - 12:10 PM

You can add me to this as well. Experiencing the same thing with PVS 6.1.



CHRIS SCOTTO Members
  • #14

CHRIS SCOTTO
  • 45 posts

Posted 25 May 2012 - 12:44 PM

I removed the original VDisk. Made a copy of it and appended the name with _Update1. Assigned it to the devices and booted them up. I then copied the new one over to the second PVS server and enabled default Load Balancing and they boot up from both. Hopefully it will stay working.



Jarian Gibson Members
  • #15

Jarian Gibson
  • 6,421 posts

Posted 05 June 2012 - 08:29 PM

Seeing this with 6.1 as well after upgrading from 5.6.x.



Jarian Gibson Members
  • #16

Jarian Gibson
  • 6,421 posts

Posted 05 June 2012 - 08:52 PM

I was able to get past without deleting the lok file.

What I did
Unassigned from all target devices
Deleted vDisk from console and left delete VHD unchecked
Reimported to console
Changed it back to Standard Mode (After import it changed to Private Mode even though it was Standard Mode before I deleted from console)
Assigned back to vDisks



Robert Posey Members
  • #17

Robert Posey
  • 78 posts

Posted 08 June 2012 - 05:39 PM

Jarian,
Dealing with this issue right now. I tried both methods (deleting and not deleting the lok file) and it did not work.
I set the vdisk to boot from a single provisioning server, removed it from PVS console, deleted lok file, then reimported. No dice, still got the vdisk locked error. I have a couple more things to try, just FYI incase you have seen anything new.

Robert



Adam Kamali Members
  • #18

Adam Kamali
  • 429 posts

Posted 12 June 2012 - 06:25 PM

I had this issue today;

Again in my case; I'm replicating disks manually between PVS servers.

I think the best practice should be:

1. Ensure that the vDisk is deleted from the Store.
2. Delete all LOK and PVP files associated with the VHD disk.
2. Make a copy of vDisk file to the second PVS box (make sure they have the same size).
3. Import the existing vDisk into the Store and have the option "Enable Load balancing for these vDisks" checked.
4. Configure the vDisk properties as they were set before.
5. Set the vDisk to Standard mode.



Robert Posey Members
  • #19

Robert Posey
  • 78 posts

Posted 19 June 2012 - 05:35 PM

Adam,
I think you are right. That procedure seems to be working for me also. Thanks!



Kailas Sanathanan Members
  • #20

Kailas Sanathanan
  • 451 posts

Posted 20 June 2012 - 12:47 PM

Hi..

yes i had faced the same issue.. in my scenario i have 8 PVS.

The steps i have follwed to get rid of from the issue.

1)From Stores i slected particular Vdisk where i have the problem and removed all locks manually.

2) deleted the v disk from store through pvs console.

also make sure its been deleted( PVP,LOK and VHD) from System Disk ( where you have assigned the place to vdisk).

also i have verified all the 7 pvs whether the vdisk has been removed.

3) Later i copied the vdisk to first PVS and maide all changes
4) Then i copied the vdisk including PVP to rest of the PVS.
5)Checked the vdisk replication status..

wowwww.. all are green..............

problem resolved.. let have a drink