Link to home
Start Free TrialLog in
Avatar of janhoedt
janhoedt

asked on

LUNs not recognized during scan (new esxi 5 in existing cluster)

Hi,

I reinstalled one of my 3 ESX-servers. Everything works fine but it sees only 2 of it's (ISCSI) LUNS, the others it doesn't see. If I "add storage", there they are, but adding them there will destroy the content .... Other ESX-es see the luns correctly (they are cur rentlyrunnig vm's on it).
User generated image
Please advise what to do.
J.
ASKER CERTIFIED SOLUTION
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of janhoedt
janhoedt

ASKER

-ash: esxcfg-volume: not found
Are we sure?

what build of ESXi 5.x ?

it's there in VMware ESXi 5.0.0 build-768111 and ESXi 5.1 just checked


User generated image

User generated image
Ok, I ll check again.
Ok, I cannot access the console, as mentioned I don't have a RAC-card and it's really hard to attach a screen, only via putty.
Version of ESXi 5.0.0, 623860
Must have typed something wrong, copy/pasted your commandline, output is there now:

VMFS UUID/label: 4fa0fe84-f6fc8a94-0448-001b785d9b0a/VMFS_DS1511_RAID5_02
Can mount: Yes
Can resignature: Yes
Extent name: naa.600140506b4c07fd03f0d3a9bda85dd9:1     range: 0 - 409343 (MB)

VMFS UUID/label: 4f91c961-e42f3832-0daa-001b785d850a/VMFS5_DS1511_RAID5_01
Can mount: Yes
Can resignature: Yes
Extent name: naa.6001405b92566d0d7fd1d3358dd8116d7:1     range: 0 - 409343 (MB)

VMFS UUID/label: 4f91ca05-1b80abc1-4050-001697885d9b0a/VMFS5_DS1511_RAID1
Can mount: Yes
Can resignature: Yes
Extent name: naa.600140558284fbedd43d36893a76db0f6d3:1     range: 0 - 409343 (MB)
Great, seams to work.
Lifesaver, thanks!
Lifesaver!
No problems, I don't know why it is, but ESX/ESXi has been doing that issue for years, some days, a LUN will not mount, on a server automatically!

but bookmark this, or add to your knowledgebase, because one day it will happen again!
It was -M for persistent mount.