escapem2
Enthusiast
Enthusiast

LUN dissapeared from 2 out of 3 ESX 4

Jump to solution

hi guys

I got 3 servers ESX 4.0 today doing some maintenance stuff (updating packages for my ESXs) I updated 2 of 3 ESX but when I tried to update node03 I found the LUNs where not there...

what I mean is node01 shows LUN let's say LUN-Dev in Storage Section but what happens my other 2 nodes they don't show me the LUN-DEV (this LUN was added like 1 month ago)

the weird thing is the LUN ID on Storage Adapters Section is recognized by the other 2 nodes that do not show me the LUN-Dev in Storage Section

How can recover this LUN-Dev to my these 2 nodes?

I already did rescan - refresh and nothing....

any other idea?

oh by the way when I click Add storage on the nodes that do not show me the LUN-Dev it shows me this LUN as an option to add...which I don't want to do.... I will lost all

thanks a lot

0 Kudos
1 Solution

Accepted Solutions
a_p_
Leadership
Leadership

You may want to take a look at Mounting VMFS Datastores with Existing Signatures in VMware's Fibre Channel SAN Configuration Guide

André

View solution in original post

0 Kudos
11 Replies
golddiggie
Champion
Champion

Need to know what the storage actually is... Is it local (to the host) datastores, iSCSI, NFS, etc.? What build of ESX/ESXi are you running? If the storage is a SAN, what make and model is it? Have you checked with the manufacturer for any possible updates to the SAN to resolve any issues?

VMware VCP4

Consider awarding points for "helpful" and/or "correct" answers.

Hosted Systems Engineer IV (VMware environment)
Brewing beer again!
escapem2
Enthusiast
Enthusiast

+Need to know what the storage actually is... Is it local (to the host)

datastores, iSCSI, NFS, etc.? What build of ESX/ESXi are you running? If

the storage is a SAN, what make and model is it? Have you checked with

the manufacturer for any possible updates to the SAN to resolve any

issues?+

it is Fiber Channel, SAN, IBM 4700

0 Kudos
JoJoGabor
Expert
Expert

Check for any differences in hardware between the hosts, in particular the HBAs, their firmware version and/or NICs if you are using iSCSI and their firmware versions. Then check all this hardware in on the Hardware COmpatibilty List for ESX 4

Double check the LUN presentation on the SAN also and verify the WWIDs of the HBAs match up to what is in the SAN

a_p_
Leadership
Leadership

Is the LUN in question presented to all hosts using the same LUN-ID ?

André

kopper27
Hot Shot
Hot Shot

wrong post

0 Kudos
escapem2
Enthusiast
Enthusiast

yeah on storage adapters it says LUN ID 6 for the host that recognizes

the LUN-Dev on Storage Section.

as well as the 2 host that does not show the LUN-Dev on Storage

Section they recognize the LUN ID 6 on Storage Adapters Section

0 Kudos
a_p_
Leadership
Leadership

You may want to take a look at Mounting VMFS Datastores with Existing Signatures in VMware's Fibre Channel SAN Configuration Guide

André

View solution in original post

0 Kudos
escapem2
Enthusiast
Enthusiast

a.p. thanks for pointing me to that article

now my question I kinda confused with the procedure what should I do?

should I remove the recognized storage from node01 and Add the Storage with the Existing Signature option? or assign a new Signature?

I think what happens I don't the snapshot(Keep Signature) and copy LUN (New Signature)

Or maybe I leave node01 like that and add Datastores to the other 2 nodes as Keep existing signature....

thanks a lot

0 Kudos
a_p_
Leadership
Leadership

Or maybe I leave node01 like that and add Datastores to the other 2 nodes as Keep existing signature....

What I meant was to mount the datastore without resignaturing. It looks like the datastore - for any reason - has been unmounted from 2 of you hosts.

Make sure you have a backup of the LUN/VM's, in case something goes wrong.

André

0 Kudos
kopper27
Hot Shot
Hot Shot

we tried mounting the existing VMFS

Procedure

1 - Log in to the vSphere Client and select the server from the inventory panel.

2 - Click the Configuration tab and click Storage in the Hardware panel.

3 - Click Add Storage.

4 - Select the Disk/LUN storage type and click Next.

5 - From the list of LUNs, select the LUN that has a datastore name displayed in the VMFS Label column and

click Next.

The name present in the VMFS Label column indicates that the LUN is a copy that contains a copy of an

existing VMFS datastore.

6 - Under Mount Options, select Keep Existing Signature.

7 - In the Ready to Complete page, review the datastore configuration information and click Finish.

but we get theerror

*_Cannot change the host configuration._ *

and I found this

will it be safe to try what is says in the KB article?

Thanks a lot

note: I am escapem2 friend Smiley Happy working on the same thing

0 Kudos
escapem2
Enthusiast
Enthusiast

thanks a lot a.p

it was

Workaround

To mount the

VMFS volume on each of the other ESX 4.0 hosts, use one of these

options:

By connecting to

the ESX host with vSphere Client:

  1. Connect vSphere Client directly to the second ESX host as root.

  2. Click the Configuration tab.

  3. Click Storage.

  4. Click Add Storage....

  5. Complete the wizard to force mount the appropriate VMFS volume which is being detected as a Snapshot LUN.

  6. Keep the existing signature Smiley Happy

0 Kudos