Host is disabled

olivierlambert

And are you sure this UUID was the PBD UUID? (and not the SR UUID)

gawlo

It was the false UUID....sorry! With the correct UUID it took about 3-4 hours and I ended up with this error:

xe pbd-unplug force=true uuid=44e9e1b7-5a7e-8e95-c5f1-edeebbc6863c
Another operation involving the object is currently in progress
class: SR
object: b7b541e7-a44d-61b7-0db4-55a0f9ce78bb (NAS2 ISO)
<extra>: plug

olivierlambert

I edited your post to use markdown syntax

Anyway, you have something blocking the mount or umount, try to find the process, kill him. Alternatively, lazy umount.

That's what happening when you remove physically a SR before removing it from XAPI

gawlo

Many thanks for the help!!

Unfortunately I still could not solve the problem. Is it advisable to restart the host completely?

EDIT: Found this in the xensource.log:
PBD.destroy locking failed: caught transient failure OTHER_OPERATION_IN_PROGRESS: [ SR; OpaqueRef:d4815da4-f7ca-40b0-ab21-f67411a7abf3; plug ]

I already checked all SRs and PBDs but the UUID can not be found.

Could this be the problem?

olivierlambert

Yes, there's a lock somewhere on the missing SR.

gawlo

But how can i find and break the lock?

I searched every uuid (pbd, sr, vdi, host, ..) but cannot find anything.

olivierlambert

No I mean in the dom0 system, check if there's specific process on the mountpoint

tony

@gawlo to check mountpoint as olivier suggested

lsof +D /mountpoint

gawlo

@tony Where is the Mountpoint? i can not find antyhing to the uuid

Or can i just reboot the xen server?

tony

@gawlo if you can reboot then you can try, but if the process is started after the reboot, it will still block your mountpoint.

And the mountpoint is the result of this command

xe pbd-param-get param-name=device-config uuid=44e9e1b7-5a7e-8e95-c5f1-edeebbc6863c

gawlo

I tried to get the mountpoint with the command from @tony but the result always was "The uuid you supplied was invalid."

To get a new/live log i restarted the toolstack (the 100th time..) and now everything is working again. I dont know why but okay..

Thank you very, very much @olivierlambert and @tony for your help!!!!