Warning 1 on item /dev/rdsk/c5t1d2: Device file '/dev/rdsk/c5t1d2' in use by server.

[Gene Laoyan]

I am getting the following error...
Warning 1 on item /dev/rdsk/c5t1d2: Device file '/dev/rdsk/c5t1d2' in use by server.

I am trying to assign it to a Virtual Machine in Integrity Virtual MAchine but it keeps saying it is in use. I verified that it is not assign to any other Virtual Machines and I also checked SAM and it showed it is unused.

Is there anywhere else I should check?

Thanks

[Jannik]

If this machine is part of a RAC cluster it may be used by another machine.. But are more commen thing is that the disk is a more than one parth disk.
So i if you have secure parth or as it is called today you could use commands like:
autopath display /dev/rdsk/c5t1d2
to get its other names and se in the lvmtab where it is used:
strings /etc/lvmtab
or if you have EMC storage you would have a product like powerparth installed:
powermt display dev=c5t1d2
and then
cat /etc/lvmtab

[Gene Laoyan]

What's RAC? I gues that answers your question.....lol

We are using Serviceguard and HP Integrity Virtual Machine.

The LUN's in question do have multipaths. This is a fiber LUN and all the other nPartitions can see the same lun. I verified that none of the nPars have a VM assigned to the LUN and powered on. I also shutdown all Virtual machines on all nPars. Also for kicks I powered down the other nPars leaving only the one I am having problems with and I got the same thing.
Something in UNIX thinks it has it's grip on it.

Any help is very appreciated. Gettin kindof desperate here.

Thanks

[Prashanth.D.S]

Hi Gene,

Similar issue faced by us here is what we found out check if it works out for you.

We had presented alternate links to the same disk to multiple guests. When
trying to start both guests, the second one would fail. The config was changed to present a single physical disk to a single guest..

Best Regards,
Prashanth

[Gene Laoyan]

I have already isolated this particular nPar by turning off all the other nPars to eliminate anything connecting to that LUN. At that point I only have one nPar but two LUN's which go to the same disk. Of course there are other LUN's but there are no problems with those. Theoretically if I only have this one nPar up and there are only two virtual machines on it and neither VM's are assigned the same LUN's there should be no problem. The LUN assigned to one VM is totally different from the other yet I still get this error.

I'm about ready to re-ignite.