Enthusiast
Enthusiast

Add existing LUN to new Host ESX 3.0.1

Jump to solution

I've got 2 hosts connected to a LUN. All of our vms are stored on this LUN. I have created a 3rd host and want to

attach that LUN to it. When I try, I get the error

Warning: The current disk layout will be destroyed. All filesystems and data will be lost permanently.

What is the best way to attach this LUN without destroying the data?

Thanks,

Scott

0 Kudos
1 Solution

Accepted Solutions

If things are setup correctly, it'll be sufficient to just do a rescan in Storage Adapters and the datastore will then be listed in Storage. You might want to check that the LUN has been assigned to this server with the same LUN ID as the other hosts.

View solution in original post

0 Kudos
12 Replies
Commander
Commander

Sounds like you are using 'Add Storage' from the 'storage' window, this is used to create new VMFSs - not what you want. If you click on the 'Storage adapters' link, then select the 'rescan' link in the top right corner this will make your server go to the san and discover the LUN and the VMFS. If the LUN is still not visible after this then you will need to check to ensure the LUN is being presented to your server.

See how you go on and repost.

Champion
Champion

Can you post:

"esxcfg-vmhbadevs -q" from one of the old hosts and from the new one

0 Kudos
Enthusiast
Enthusiast

That's right. I'm doing it from Add Storage.

I've rescanned the adapters and I can see the LUN. It's just not listed under "Storage".

Don't I need to have it available under Storage in order to add vms to it from this host?

0 Kudos
Virtuoso
Virtuoso

have you added the WWN to your switch/SAN for that new host so the new host can talk to your san?

-- Kyle "RParker wrote: I guess I was wrong, everything CAN be virtualized "
0 Kudos
Enthusiast
Enthusiast

Here is the output from esxcfg-hbadevs -q

New Server:

vmhba4:0:0 /dev/sda

vmhba5:0:0 /dev/cciss/c0d0

Existing Server:

vmhba0:2:0 /dev/sda

vmhba6:0:0 /dev/cciss/c0d0

0 Kudos
Champion
Champion

Here is the output from esxcfg-hbadevs -q

New Server:

vmhba4:0:0 /dev/sda

Is that san lun ??

vmhba5:0:0 /dev/cciss/c0d0

Existing Server:

vmhba0:2:0 /dev/sda

Is that san lun, but not the same as above?

vmhba6:0:0 /dev/cciss/c0d0

>

Enthusiast
Enthusiast

Yes. The SAN looks good. I can see the LUN from the new host. It just hasn't been added as new storage yet on this host

0 Kudos

If things are setup correctly, it'll be sufficient to just do a rescan in Storage Adapters and the datastore will then be listed in Storage. You might want to check that the LUN has been assigned to this server with the same LUN ID as the other hosts.

View solution in original post

0 Kudos
Enthusiast
Enthusiast

I did rescan, but it doesn't appear under storage, unless I try to manually add it, which then tells me all data will be destroyed.

The EMC is not set up for LUN masking or selective presentation. Everything should be able to see the LUN by default.

You might want to check that the LUN has been assigned to this server with the same LUN ID as the other hosts.

Do you mean in Virtual Center or on the EMC?

0 Kudos
Enthusiast
Enthusiast

Very bizarre. The LUN finally showed up. I'm not sure why it took so long, but at least it's there.

I'm going to take a look at the SAN.

Thanks for all your help.

0 Kudos
Virtuoso
Virtuoso

Sometimes it takes a couple re-scans for everything to show up properly, we usually have to rescan ~2 times if we want to add LUN storage to a host

-- Kyle "RParker wrote: I guess I was wrong, everything CAN be virtualized "
0 Kudos
Virtuoso
Virtuoso

We had one customer who I think had in their procedures to rescan twice after adding a LUN to a host for it to show up properly.

www.thevirtualheadline.com www.liquidwarelabs.com
0 Kudos