Problem with vcb after Update

[markus_herbert]

After Update from U1 to U2, my vcb won't work anymore.

I use esx 3.5.0 build 113339

VCenter 2.5.0 build 104215

vcb 1.5.0 build 102898

I use a FC-SAN Storage. Before the Update, everything works ok. Any Idea??

-

---

Pre Script log begins----

---

Time Stamp: 10/1/2008 19:25:14:898

vcb_config = C:\Program Files\CA\BrightStor ARCserve Backup\config\cavcb_config1.js

vcb_path = C:\Program

Files\VMware\VMware Consolidated Backup Framework

Backuproot = C:\VMmount

Hostname = vcenter

Username = manager

Password = *******

Port = 443

Processing VM name and valid mount type specified in Configuration file ...

VMname = EVENT

Mount Type = fullvm

No of VMs considered

for Mount operation = 1

Starting VM mounting operation ...

VM name: EVENT & Mount type: fullvm

Current working directory: C:\Program Files\CA\BrightStor ARCserve Backup

HOSTINFO: Seeing Intel CPU, numCoresPerCPU 1 numThreadsPerCore 2.

HOSTINFO: This machine has 1 physical CPUS, 1 total cores, and 2 logical CPUs.

Using system libcrypto, version 90709F

SSLVerifyCertAgainstSystemStore: Subject mismatch: VMware vs vcenter

SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:

• The host name used for the connection does not match the subject name on the host certificate

• A certificate in the host's chain is based on an untrusted root.

SSLVerifyIsEnabled: failed to read registry value. Assuming verification is disabled.

LastError = 0

SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will

proceed despite the error

Copying "[DiskLUN12] Event/Event.vmx":

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

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

Copying "[DiskLUN12] Event/Event.nvram":

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

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

Copying "[DiskLUN12] Event//vmware-13.log":

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

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

Copying "[DiskLUN12] Event//vmware-11.log":

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

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

Copying "[DiskLUN12] Event//vmware-14.log":

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

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

Copying "[DiskLUN12] Event//vmware-9.log":

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

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

Copying "[DiskLUN12] Event//vmware-10.log":

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

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

Copying "[DiskLUN12] Event//vmware-12.log":

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

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

Copying "[DiskLUN12] Event//vmware.log":

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

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

SSLVerifyCertAgainstSystemStore: Subject mismatch: VMware vs vcenter

SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:

• The host name used for the connection does not match the subject name on the host certificate

• A certificate in the host's chain is based on an untrusted root.

SSLVerifyIsEnabled: failed to read registry value. Assuming verification is disabled.

LastError = 0

SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will

proceed despite the error

SSLVerifyCertAgainstSystemStore: Subject mismatch: VMware vs vcenter

SSLVerifyCertAgainstSystemStore: The remote host certificate has these problems:

• The host name used for the connection does not match the subject name on the host certificate

• A certificate in the host's chain is based on an untrusted root.

SSLVerifyIsEnabled: failed to read registry value. Assuming verification is disabled.

LastError = 0

SSLVerifyCertAgainstSystemStore: Certificate verification is disabled, so connection will

proceed despite the error

No path to device LVID:4601479c-b08f636a-6d6a-000423d5f07c/4601479c-a4c39717-303a-000423d5f07c/1

found.

Error: Failed to open the disk: Cannot access a SAN/iSCSI LUN backing this virtual disk.

(Hint: If you are using vcbMounter you can use the option "-m ndb" to switch to network based disk access if this is what you want.) If you

were attempting file-level access, stop the vmount Service by typing "net stop vmount2" on a command prompt to force vmount to re-scan for

SAN LUNs and re-try the command.

An error occurred, cleaning up...

Deleted directory C:\VMmount\EVENT-fullVM

0External command failed. See error above.

Exit Code: 1

VCB Mount/delete operation for this VM (EVENT) has failed

Number of VM failed to mount/export, count is = 1

Error code returned is: 1

Time Stamp: 10/1/2008 19:28:11:745

-

---

Pre Script log ends----

---

[dconvery]

The key error is "No path to device LVID:4601479c-b08f636a-6d6a-000423d5f07c/4601479c-a4c39717-303a-000423d5f07c/1 found."

Try rebooting the VCB server toallow a complete rescan of everything. If that doesn't work run vcbSanDbg andoutput it to a text file and post it here.

Dave

[markus_herbert]

Reboot doesn't solve my problem. So here ist the output.txt from vcbSanDbg:

Current working directory: C:\Program Files\VMware\VMware Consolidated Backup Framework

HOSTINFO: Seeing Intel CPU, numCoresPerCPU 1 numThreadsPerCore 2.

HOSTINFO: This machine has 1 physical CPUS, 1 total cores, and 2 logical CPUs.

Building SCSI Device List...

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&100#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&100#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Reading 32256 bytes from offset 0.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&100#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&100#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Cannot read 32256 bytes from offset 0.

No partitions could be found on this device.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&101#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&101#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Reading 32256 bytes from offset 0.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&101#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&101#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Cannot read 32256 bytes from offset 0.

No partitions could be found on this device.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&102#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&102#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Reading 32256 bytes from offset 0.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&102#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&102#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Cannot read 32256 bytes from offset 0.

No partitions could be found on this device.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&103#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&103#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Reading 32256 bytes from offset 0.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&103#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&103#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Cannot read 32256 bytes from offset 0.

No partitions could be found on this device.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&104#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&104#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Reading 32256 bytes from offset 0.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&104#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&104#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Cannot read 32256 bytes from offset 0.

No partitions could be found on this device.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&105#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&105#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Reading 32256 bytes from offset 0.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&105#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&105#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Cannot read 32256 bytes from offset 0.

No partitions could be found on this device.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&106#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&106#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Reading 32256 bytes from offset 0.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&106#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&106#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Cannot read 32256 bytes from offset 0.

No partitions could be found on this device.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&107#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&107#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Reading 32256 bytes from offset 0.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&107#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&107#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Cannot read 32256 bytes from offset 0.

No partitions could be found on this device.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&108#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&108#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Reading 32256 bytes from offset 0.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&108#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&108#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Cannot read 32256 bytes from offset 0.

No partitions could be found on this device.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&109#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&109#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Reading 32256 bytes from offset 0.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&109#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&109#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Cannot read 32256 bytes from offset 0.

No partitions could be found on this device.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10a#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10a#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Reading 32256 bytes from offset 0.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10a#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10a#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Cannot read 32256 bytes from offset 0.

No partitions could be found on this device.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10b#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10b#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Reading 32256 bytes from offset 0.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10b#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10b#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Cannot read 32256 bytes from offset 0.

No partitions could be found on this device.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10c#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10c#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Reading 32256 bytes from offset 0.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10c#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10c#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Cannot read 32256 bytes from offset 0.

No partitions could be found on this device.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10d#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10d#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Reading 32256 bytes from offset 0.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10d#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10d#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Cannot read 32256 bytes from offset 0.

No partitions could be found on this device.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10e#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10e#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Reading 32256 bytes from offset 0.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10e#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10e#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Cannot read 32256 bytes from offset 0.

No partitions could be found on this device.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10f#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10f#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Reading 32256 bytes from offset 0.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10f#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10f#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Cannot read 32256 bytes from offset 0.

No partitions could be found on this device.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&010010#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&010010#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Reading 32256 bytes from offset 0.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&010010#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&010010#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Cannot read 32256 bytes from offset 0.

No partitions could be found on this device.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&010011#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&010011#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Reading 32256 bytes from offset 0.

Evaluating 1 paths.

Trying to open path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&010011#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Now using Path
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&010011#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}.

Cannot read 32256 bytes from offset 0.

No partitions could be found on this device.

Dumping SCSI Device/LUN List.

**** Begin SCSI Device LIst ****

Found SCSI Device: SERIAL_NUM:37353035303531373030303020202020444636303046/00000

Visible on 1 paths:

Device Name:
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&100#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 1 Target: 0 Lun: 0

Lun does not contain any VMFS/LVM signatures.

Found SCSI Device: SERIAL_NUM:37353035303531373030303120202020444636303046/00001

Visible on 1 paths:

Device Name:
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&101#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 1 Target: 0 Lun: 1

Lun does not contain any VMFS/LVM signatures.

Found SCSI Device: SERIAL_NUM:37353035303531373030303220202020444636303046/00002

Visible on 1 paths:

Device Name:
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&102#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 1 Target: 0 Lun: 2

Lun does not contain any VMFS/LVM signatures.

Found SCSI Device: SERIAL_NUM:37353035303531373030303320202020444636303046/00003

Visible on 1 paths:

Device Name:
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&103#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 1 Target: 0 Lun: 3

Lun does not contain any VMFS/LVM signatures.

Found SCSI Device: SERIAL_NUM:37353035303531373030303420202020444636303046/00004

Visible on 1 paths:

Device Name:
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&104#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 1 Target: 0 Lun: 4

Lun does not contain any VMFS/LVM signatures.

Found SCSI Device: SERIAL_NUM:37353035303531373030303520202020444636303046/00005

Visible on 1 paths:

Device Name:
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&105#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 1 Target: 0 Lun: 5

Lun does not contain any VMFS/LVM signatures.

Found SCSI Device: SERIAL_NUM:37353035303531373030303620202020444636303046/00006

Visible on 1 paths:

Device Name:
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&106#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 1 Target: 0 Lun: 6

Lun does not contain any VMFS/LVM signatures.

Found SCSI Device: SERIAL_NUM:37353035303531373030303720202020444636303046/00007

Visible on 1 paths:

Device Name:
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&107#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 1 Target: 0 Lun: 7

Lun does not contain any VMFS/LVM signatures.

Found SCSI Device: SERIAL_NUM:37353035303531373030303820202020444636303046/00008

Visible on 1 paths:

Device Name:
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&108#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 1 Target: 0 Lun: 8

Lun does not contain any VMFS/LVM signatures.

Found SCSI Device: SERIAL_NUM:37353035303531373030303920202020444636303046/00009

Visible on 1 paths:

Device Name:
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&109#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 1 Target: 0 Lun: 9

Lun does not contain any VMFS/LVM signatures.

Found SCSI Device: SERIAL_NUM:37353035303531373030304120202020444636303046/00010

Visible on 1 paths:

Device Name:
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10a#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 1 Target: 0 Lun: 10

Lun does not contain any VMFS/LVM signatures.

Found SCSI Device: SERIAL_NUM:37353035303531373030304220202020444636303046/00011

Visible on 1 paths:

Device Name:
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10b#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 1 Target: 0 Lun: 11

Lun does not contain any VMFS/LVM signatures.

Found SCSI Device: SERIAL_NUM:37353035303531373030304320202020444636303046/00012

Visible on 1 paths:

Device Name:
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10c#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 1 Target: 0 Lun: 12

Lun does not contain any VMFS/LVM signatures.

Found SCSI Device: SERIAL_NUM:37353035303531373030304420202020444636303046/00013

Visible on 1 paths:

Device Name:
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10d#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 1 Target: 0 Lun: 13

Lun does not contain any VMFS/LVM signatures.

Found SCSI Device: SERIAL_NUM:37353035303531373030304520202020444636303046/00014

Visible on 1 paths:

Device Name:
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10e#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 1 Target: 0 Lun: 14

Lun does not contain any VMFS/LVM signatures.

Found SCSI Device: SERIAL_NUM:37353035303531373030304620202020444636303046/00015

Visible on 1 paths:

Device Name:
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&10f#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 1 Target: 0 Lun: 15

Lun does not contain any VMFS/LVM signatures.

Found SCSI Device: SERIAL_NUM:37353035303531373030313020202020444636303046/00016

Visible on 1 paths:

Device Name:
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&010010#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 1 Target: 0 Lun: 16

Lun does not contain any VMFS/LVM signatures.

Found SCSI Device: SERIAL_NUM:37353035303531373030313120202020444636303046/00017

Visible on 1 paths:

Device Name:
?\scsi#disk&ven_hitachi&prod_df600f&rev_0000#5&abeb12a&0&010011#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}, Bus: 1 Target: 0 Lun: 17

Lun does not contain any VMFS/LVM signatures.

**** End SCSI Device LIst ****

[dconvery]

Lots of "No Partitions found" on the Hitachi LUNs.... Check to make sure they are still being presented properly and are not set to read only. DId you change ANYTHING else on the SAN or VCB server? I have seen issues with newer versions of EMC Powerpath. Mayve there is an issue with the version of MPIO that you are using?

[markus_herbert]

I didn't change anything on my SAN. On my backup proxy I have only one FC-HBA (Emulex).

On the backup proxy I didn't use any multipath software because of only one FC-HBA.

On my HBAnywhere I see all LUNS from LUN00 up to LUN17

Also in MS Diskmanagement System I can see Disk3 to Disk30 with status healty and

as I can see also in the right direction as seen on esx host.

On my bakup proxy all the LUN's are mounted Read/Only (of course) and all my ESX Hosts

are seeing the LUNS with read/write access. All my VM's are working properly.

[dconvery]

Try UNSETTING the read only bit and reboot the VCB Proxy. Then re set the read only once the proxy "sees" the LUNs.

[markus_herbert]

How can I UNSET the read only bit on the VCB Proxy Server ?

[Andy_Imm]

I have had this kind of issue in the past. It had something to do with the VC not seeing all of the vmfs disks. Once the VC was able to see all of the vmfs disks, we were able to proceed with the VCBs.

[dconvery]

You mentioned that the LUNs are mounted read only. Did you set this up in the hitachi array? How did you make it read only? You need to reset that so that the VCB server has write access because winders does not like read only LUNs.

Dave

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

"There is an island of opportunity in the middle of every difficulty. Miss that, though, and you're pretty much doomed."

despair.com

[markus_herbert]

Sorry my explanation wasn't good. So what I mean is that I made the followin on the VCB proxy server:

diskpart

automount disable

automount scrub

exit

-> so the MS Windows OS doen't try to write their signatures on the disks.

The LUN's on the Hitachi SAN Storage are of course read/write.

[dconvery]

Try to uninstall and reinstall VCB. Make a backup copy of config.js and make sure that driver signing is set to "prompt" or "Allow" in the security policy or the vlun driver will not install..

Dave

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

"There is an island of opportunity in the middle of every difficulty. Miss that, though, and you're pretty much doomed."

despair.com

[dconvery]

Here are some screenshots on how to set up driver signing.

Dave

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

"There is an island of opportunity in the middle of every difficulty. Miss that, though, and you're pretty much doomed."

despair.com

[_lpl_]

http://communities.vmware.com/docs/DOC-8332

[Pat_47]

did you take a look at zoning ? i had exactly same problem until i presented LUN hosting VMFS to the VCB Proxy...

Having ESX and VCB Proxy in same SAN zone is not enough !