vcbMounter: "Error: failed to open the disk: One LUN could not be opened"

[PauliPinguin]

Hello all,

We're encountering a problem with vcb and could not find a solution. We have two ESX3.0 and one Server for vcb with access to the vmfs-Storage. On the vcb-server alle paths except one to the LUN are disabled as described in the knowledge-base.

Everytime we run vcbMounter, the snapshot is being created and some files (*.log, .vmx) are being copied to the destination path. Then vcbMopunter runs at an error:

vcbMounter: "Error: failed to open the disk: One LUN could not be opened"

Could anyone help?

Many thanks

[kix1979]

Ran into a similar problem, but it turned out to be my VM. I had to power it off and reboot it. Try turning your logging up to 6 and see if it gives any more details on the issue. Worst case a reboot of the host would probably fix it.

[PauliPinguin]

Hello,

thanks for your tips, but nor rebooting the VMs nor rebooting the Hosts or the VCs did help. Following is the output of vcbmounter created with -L 6:

any ideas?

\[2006-09-04 14:42:57.843 'App' 2856 info] Current working directory: C:\Programme\VMware\VMware Consolidated Backup Framework

\[2006-09-04 14:42:57.843 'vcbMounter' 2856 trivia] Initializing SSL context

\[2006-09-04 14:42:57.843 'BaseLibs' 2856 info] Using system libcrypto, version 90703F

\[2006-09-04 14:42:58.140 'vcbMounter' 2856 info] Connecting to host v000011.streck on port 902

\[2006-09-04 14:42:58.359 'vcbMounter' 2856 verbose] Connected to stream: \[class Vmacore::Ssl::SSLStreamImpl:01674F00]

\[2006-09-04 14:42:58.359 'BaseLibs' 2884 warning] \[Vmdb_Unset] Unsetting unknown path: /vmomi/

\[2006-09-04 14:42:58.390 'vcbMounter' 2856 info] Authenticating user administrator

\[2006-09-04 14:42:58.625 'vcbMounter' 2856 info] Logged in!

\[2006-09-04 14:42:59.531 'App' 2856 info] IpAddrVmFilter: VM does not report an IP addresss.

\[2006-09-04 14:42:59.546 'vcbMounter' 2856 info] Got VM MoRef

\[2006-09-04 14:43:02.203 'vcbMounter' 2856 info] Got access method

\[2006-09-04 14:43:02.203 'vcbMounter' 2856 info] Got coordinator object

\[2006-09-04 14:43:02.203 'vcbMounter' 2856 info] Attempting data access.

\[2006-09-04 14:43:02.343 'vcbMounter' 2856 info] Scanning snapshot Consolidate Helper

\[2006-09-04 14:43:02.343 'vcbMounter' 2856 info] Creating snapshot

\[2006-09-04 14:43:17.875 'vcbMounter' 2856 info] Snapshot created, ID: snapshot-191

\[2006-09-04 14:43:17.875 'vcbMounter' 2856 info] Mount operation created snapshot.

\[2006-09-04 14:43:18.046 'vcbMounter' 2856 verbose] Found a device: vim.vm.device.VirtualLsiLogicController

\[2006-09-04 14:43:18.046 'vcbMounter' 2856 verbose] Found a device: vim.vm.device.VirtualDisk

\[2006-09-04 14:43:18.109 'vcbMounter' 2856 info] Mount operation obtained backup info.

\[2006-09-04 14:43:18.109 'vcbMounter' 2856 info] Creating export directory

\[2006-09-04 14:43:18.109 'vcbMounter' 2856 info] Writing restore config file

\[2006-09-04 14:43:23.125 'vcbMounter' 2856 info] Exporting VM config files

Copying "\[vmfs_san] s101954-vm2/winNetStandard.vmx":

0%=====================50%=====================100%

**************************************************

Copying "\[vmfs_san] s101954-vm2/winNetStandard.nvram":

0%=====================50%=====================100%

**************************************************

Copying "\[vmfs_san] s101954-vm2//vmware-1.log":

0%=====================50%=====================100%

**************************************************

Copying "\[vmfs_san] s101954-vm2//vmware-2.log":

0%=====================50%=====================100%

**************************************************

copying "\[vmfs_san] s101954-vm2//vmware-3.log":

0%=====================50%=====================100%

**************************************************

Copying "\[vmfs_san] s101954-vm2//vmware.log":

0%=====================50%=====================100%

**************************************************

\[2006-09-04 14:44:48.375 'vcbMounter' 2856 info] Exporting disks

\[2006-09-04 14:44:48.375 'vcbMounter' 2856 info] Filenames: blklst://snapshot-191\[vmfs_san] s101954-vm2/s101954-vm2-000004.vmdk@v000011.streck?administrator/**** --> c:\mnt\s101954-vm2-fullVM\scsi0-0-0-s101954-vm2.vmdk

\[2006-09-04 14:44:48.437 'blocklist' 2856 trivia] Initializing SSL context

\[2006-09-04 14:44:48.437 'blocklist' 2856 info] Connecting to host v000011.streck on port 902

\[2006-09-04 14:44:48.656 'blocklist' 2856 verbose] Connected to stream: \[class Vmacore::Ssl::SSLStreamImpl:016ABE10]

\[2006-09-04 14:44:48.656 'BaseLibs' 2892 warning] \[Vmdb_Unset] Unsetting unknown path: /vmomi/

\[2006-09-04 14:44:48.687 'blocklist' 2856 info] Authenticating user administrator

\[2006-09-04 14:44:48.875 'blocklist' 2856 info] Logged in!

\[2006-09-04 14:44:53.218 'vcbMounter' 2856 error] Error: Failed to open the disk: One LUN could not be opened

\[2006-09-04 14:44:53.218 'vcbMounter' 2856 error] An error occured, cleaning up...

\[2006-09-04 14:44:55.000 'vcbMounter' 2856 warning] Snapshot deletion failed. Attempting to clean up snapshot database...

\[2006-09-04 14:44:55.015 'vcbMounter' 2856 info] Scanning snapshot Consolidate Helper

\[2006-09-04 14:44:55.015 'vcbMounter' 2856 info] Found match: snapshot-190

\[2006-09-04 14:44:55.015 'vcbMounter' 2856 info] Scanning snapshot \_VCB-BACKUP_

\[2006-09-04 14:44:57.093 'App' 2856 verbose] Got vmdb error -14 (Pipe connection has been broken) when invoking \[logout] on \[vim.SessionManager:SessionManager]

\[2006-09-04 14:44:57.093 'vcbMounter' 2856 info] Error on logout (ignored): vmodl.fault.HostNotReachable

\[2006-09-04 14:44:57.093 'vcbMounter' 2856 verbose] Shutting down VMDB service...

\[2006-09-04 14:44:57.093 'vcbMounter' 2856 verbose] Unregistering callback...

\[2006-09-04 14:44:57.093 'vcbMounter' 2856 verbose] ...done

[howl]

I encounter this problem too!

[jiaxu2000]

I encounter this problem too! help me!

\[2006-09-09 19:53:41.894 'App' 3220 info] Current working directory: C:\Program

Files\VMware\VMware Consolidated Backup Framework

\[2006-09-09 19:53:42.515 'BaseLibs' 2328 warning] \[Vmdb_Unset] Unsetting unknown

path: /vmomi/

Copying "\[Edi3000] /New Virtual Machine/New Virtual Machine.vmx":

0%=====================50%=====================100%

**************************************************

Copying "\[Edi3000] /New Virtual Machine/New Virtual Machine.nvram":

0%=====================50%=====================100%

**************************************************

Copying "\[Edi3000] /New Virtual Machine/vmware-7.log":

0%=====================50%=====================100%

**************************************************

Copying "\[Edi3000] /New Virtual Machine/vmware-2.log":

0%=====================50%=====================100%

**************************************************

Copying "\[Edi3000] /New Virtual Machine/vmware.log":

0%=====================50%=====================100%

**************************************************

Copying "\[Edi3000] /New Virtual Machine/vmware-3.log":

0%=====================50%=====================100%

**************************************************

Copying "\[Edi3000] /New Virtual Machine/vmware-6.log":

0%=====================50%=====================100%

**************************************************

Copying "\[Edi3000] /New Virtual Machine/vmware-4.log":

0%=====================50%=====================100%

**************************************************

Copying "\[Edi3000] /New Virtual Machine/vmware-5.log":

0%=====================50%=====================100%

**************************************************

\[2006-09-09 19:53:50.687 'BaseLibs' 3192 warning] \[Vmdb_Unset] Unsetting unknown

path: /vmomi/

\[2006-09-09 19:53:51.207 'vcbMounter' 3220 error] Error: Failed to open the disk

: One LUN could not be opened

\[2006-09-09 19:53:51.207 'vcbMounter' 3220 error] An error occured, cleaning up.

..

\[2006-09-09 19:53:51.658 'vcbMounter' 3220 warning] Snapshot deletion failed. At

tempting to clean up snapshot database...

Message was edited by:

jiaxu2000

[jiaxu2000]

I know.

Esx Server and VCB host need connect a SAN.

[joepje]

just use one path to the LUN you want to connect. Multipathing is not supported with VCB at the moment.

[Schorschi]

Who or whom do we SHOOT for this? You have got to be kidding... 1 path?

[rmigfr]

I got exactly the same error log. We have only one path from the proxy server to the SAN.

After the failure, we cannot delete the snapshot with the machine online. We need to poweroff the VM, delete the snapshot. Sometime we also need to reboot the host to get ride of the snapshot.

The fact that VCB and VC are on the same server could it be the cause ?

[rmigfr]

Ok it was simply a LUN visibility problem. But we still have the snapshot problem. A snashot created by VCB cannot be deleted with the VM power on. So vcbmount or pre-backup.bat failed when they try to delete the helper snapshot.

The errors are differents: locked files, other operation running, or object do not exist anymore.

We need to stop the VM before deleting the vcb helper snapshot.

[sachin_achavan]

Hello,

Can anybody tell me how to check that both esx server and proxy see the same LUN :

I m tring ...

On ESX :

esxcfg-mpath -l

which gives me

Disk vmhba3:0:4 /dev/sdf (10240MB) has 1 paths and policy of Fixed

FC 12:7.0 210000e08b02dc03<->[b]50001fe150071ca8 vmhba3:0:4 On active preferred

And on Proxy I used SANSurferFC_CLI

which gives me

port Name as 50001FE150071CAD[/b]

I think BOLD entries are not matched means LUN is not same .....only Last letter diffrence 8------D

Is it correct or tell me hoe to check LUN on both esx & proxy is same ....

I have got error on vcbMounter cmd that disk open error :One LUN is not opened

So that I m checking LUN on both esx and proxy

Thnax In Advaned

Message was edited by:

sachin_achavan

[jhp7395]

Could you explain what you mean by "LUN visibility problem"? I have the exact same error, and am hoping that whatever you did will also fix my problem.

[sachin_achavan]

I had just set same LUN number of virtual array disk to both VCB proxy and esx-server from HP Storage Management . and It work finnally

[dcampbel]

I am also getting the same 'ONE LUN could not be opened' error

\[2006-10-25 11:26:10.890 'vcbMounter' 2404 error] Error: Failed to open the disk: One LUN could not be opened[/b]

I get the following when running esxcfg-mpath -l

Disk vmhba1:1:0 (558006MB) has 2 paths and policy of Most Recently Used

FC 3:3.0 210000e08b8a1888 <-> 200500a0b821ae92 vmhba1:1:0 Standby preferred

FC 9:2.0 210000e08b8f9584 <-> 200400a0b821ae92 vmhba2:1:0 On active

Am I to understand that you cannot use VCBMounter if you have 2 paths to the SAN? Could it be that the ESX server is not currently using the 'Preferred path'?

Any suggestions would be appreciated. Have ESX 3.0 and IBM SAN. Both ESX and VCB Proxy see as volume as LUN 0.

[jeffslapp]

One thing that also needs to happen on the VCB Proxy is the LDM (Logical Disk Manager) needs to be able to see the VMFS LUN. If you go to the LDM and you don't see an "Unknown Partition" in the list of disk objects then you need to do a Disk Rescan by right clicking the Disk Management object on the left-hand side.

Once the partition(s) appear then the vcbMounter command should run properly.

[sharvey2]

Same error but some of my policies are working. I have a farm and I can VCB backup Linux, and Win 2003 VMs, I get this error on all my Windows XP VMs. Very confused by all this lun visibility talk. What exactly do you mean by "go to the LDM"? I have an LDM service but not a view like the one you describe.

[Justin_King]

The fact that VCB and VC are on the same server could

it be the cause ?

FYI that will cause problems when you start deploying templates. VC and VCB use different methods to open up and mount a VMDK for editing that are strictly incompatible. You'll need to move VCB to a different box than VC at one point or wait until they patch it.

[zhangfred_vm]

How to solve this issue, I also get the problem, when I run the commends

\-------

C:\Program Files\VMware\VMware Consolidated Backup Framework>vcbMounter -h 192.168.2.211 -u root -p 123456 -a uuid:5001dc10-2a19-d98c-adf4-27119a82f3f3 -r F:\vmb

ackup\VP2001 -t fullvm

\[2007-03-23 11:59:17.218 'App' 5292 info] Current working directory: C:\Program

Files\VMware\VMware Consolidated Backup Framework

\[2007-03-23 11:59:17.968 'BaseLibs' 6972 warning] \[Vmdb_Unset] Unsetting unknown

path: /vmomi/

Copying "\[storage1] P2v_2003_01/P2v_2003_01.vmx":

0%=====================50%=====================100%

**************************************************

Copying "\[storage1] P2v_2003_01/P2v_2003_01.nvram":

0%=====================50%=====================100%

**************************************************

Copying "\[storage1] P2v_2003_01/vmware-1.log":

0%=====================50%=====================100%

**************************************************

Copying "\[storage1] P2v_2003_01/vmware-2.log":

0%=====================50%=====================100%

**************************************************

Copying "\[storage1] P2v_2003_01/vmware-3.log":

0%=====================50%=====================100%

**************************************************

Copying "\[storage1] P2v_2003_01/vmware.log":

0%=====================50%=====================100%

**************************************************

\[2007-03-23 11:59:27.296 'BaseLibs' 5676 warning] \[Vmdb_Unset] Unsetting unknown

path: /vmomi/

\[2007-03-23 11:59:28.093 'BlockList' 5292 warning] Could not log out (16.157.66.

84:root)

\[2007-03-23 11:59:28.093 'vcbMounter' 5292 error] Error: Failed to open the disk

: One LUN could not be opened

\[2007-03-23 11:59:28.093 'vcbMounter' 5292 error] An error occured, cleaning up.

[beneddt]

Bump....

I'm also getting the same error...and I've unplugged one path to my SAN to ensure Multipathing is not the problem.

In disk management, I see the correct SAN Luns that have been mapped to my host.

Any ideas? This thing was working a month ago.

dean

[pcomo]

Hi,

same problem.

I share LUN (vmfs ) between ESX server and VCB server (Netbackup server) with the same LUN id.

I only use multipathing on esx server for this LUN and not on VCB.

It's strange because all log files from VM directory could be export by VCB but the error appears when vmdk files are accessed.

At this time all VM are VM which are migrate from VMware server.

I will try to create a VM from ESX and see the difference.

If someone have information.

thanks.