VMware Cloud Community
RediMika
Contributor
Contributor

LUNs not visible in storages

Hi,
we have currently (big?) problems after our SAN went down due the disk fail. Now the SAN is again fully up and running after complete rebuilding of its RAID. Problem is that now our ESX servers can see only two out of six LUNs (vml.0200020000600805f3001a0350a10cb7ca973d00044d5341313030 and vml.0200060000600805f3001a0350ace30859127200084d5341313030).
When starting to add new storages, the servers can see also rest of the LUNs and VMFS file systems on mentioned LUNs. Problems is that we don't want to add those again since reformatting happens and that would mean data loss.
Below is a listing of vmfs disks from two of our ESX servers.
Any idea why other server sees some mystical disks (see bolded lines)? Any idea how to fix this?
------------
[root@server4 disks]# ls -la
total 7607272182
drwxr-xr-x    1  root     root          512 Mar 25 08:36 .
drwxr-xr-x    1 root      root          512 Mar 25 08:36 ..
-rw-------    1 root     root      293563949056 Mar 25 08:36 vmhba0:0:0:0
-rw-------    1 root     root      106896384 Mar 25 08:36 vmhba0:0:0:1
-rw-------    1 root     root      5239503360 Mar 25 08:36 vmhba0:0:0:2
-rw-------    1 root     root      285450117120 Mar 25 08:36 vmhba0:0:0:3
-rw-------    1 root     root      2763694080 Mar 25 08:36 vmhba0:0:0:4
-rw-------    1 root     root      567512064 Mar 25 08:36 vmhba0:0:0:5
-rw-------    1 root     root      2089188864 Mar 25 08:36 vmhba0:0:0:6
-rw-------    1 root     root      106896384 Mar 25 08:36 vmhba0:0:0:7
lrwxrwxrwx    1 root     root            58 Mar 25 08:36 vmhba1:0:1:0 ->  vml.0200010000600805f3001a0350adbeb37f8f4b00024d5341313030
lrwxrwxrwx    1  root     root           60 Mar 25 08:36 vmhba1:0:1:1 ->  vml.0200010000600805f3001a0350adbeb37f8f4b00024d5341313030:1
lrwxrwxrwx    1  root     root           58 Mar 25 08:36 vmhba1:0:2:0 ->  vml.0200020000600805f3001a0350a10cb7ca973d00044d5341313030
lrwxrwxrwx    1  root     root           60 Mar 25 08:36 vmhba1:0:2:1 ->  vml.0200020000600805f3001a0350a10cb7ca973d00044d5341313030:1
lrwxrwxrwx    1  root     root           58 Mar 25 08:36 vmhba1:0:3:0 ->  vml.0200030000600805f3001a0350a0dc87e7f33300054d5341313030
lrwxrwxrwx    1  root     root           60 Mar 25 08:36 vmhba1:0:3:1 ->  vml.0200030000600805f3001a0350a0dc87e7f33300054d5341313030:1
lrwxrwxrwx    1  root     root           60 Mar 25 08:36 vmhba1:0:3:2 ->  vml.0200030000600805f3001a0350a0dc87e7f33300054d5341313030:2

lrwxrwxrwx    1  root     root           58 Mar 25 08:36 vmhba1:0:4:0 ->  vml.0200040000600805f3001a0350affd2acacc3600064d5341313030
lrwxrwxrwx    1  root     root           60 Mar 25 08:36 vmhba1:0:4:1 ->  vml.0200040000600805f3001a0350affd2acacc3600064d5341313030:1
lrwxrwxrwx    1  root     root           58 Mar 25 08:36 vmhba1:0:5:0 ->  vml.0200050000600805f3001a0350a0483755c35800074d5341313030
lrwxrwxrwx    1  root     root           60 Mar 25 08:36 vmhba1:0:5:1 ->  vml.0200050000600805f3001a0350a0483755c35800074d5341313030:1
lrwxrwxrwx    1  root     root           58 Mar 25 08:36 vmhba1:0:6:0 ->  vml.0200060000600805f3001a0350ace30859127200084d5341313030
lrwxrwxrwx    1  root     root           60 Mar 25 08:36 vmhba1:0:6:1 ->  vml.0200060000600805f3001a0350ace30859127200084d5341313030:1
-rw-------    1  root     root     899998300160 Mar 25 08:36  vml.0200010000600805f3001a0350adbeb37f8f4b00024d5341313030
-rw-------    1  root     root     899993621504 Mar 25 08:36  vml.0200010000600805f3001a0350adbeb37f8f4b00024d5341313030:1
-rw-------    1  root     root     285426580992 Mar 25 08:36  vml.0200020000600805f3001a0350a10cb7ca973d00044d5341313030
-rw-------    1  root     root     285425375744 Mar 25 08:36  vml.0200020000600805f3001a0350a10cb7ca973d00044d5341313030:1
-rw-------    1  root     root     914570932736 Mar 25 08:36  vml.0200030000600805f3001a0350a0dc87e7f33300054d5341313030
-rw-------    1  root     root     314567542784 Mar 25 08:36  vml.0200030000600805f3001a0350a0dc87e7f33300054d5341313030:1
-rw-------    1  root     root     600001260544 Mar 25 08:36  vml.0200030000600805f3001a0350a0dc87e7f33300054d5341313030:2

-rw-------    1  root     root     299999559680 Mar 25 08:36  vml.0200040000600805f3001a0350affd2acacc3600064d5341313030
-rw-------    1  root     root     299992346624 Mar 25 08:36  vml.0200040000600805f3001a0350affd2acacc3600064d5341313030:1
-rw-------    1  root     root     599998806016 Mar 25 08:36  vml.0200050000600805f3001a0350a0483755c35800074d5341313030
-rw-------    1  root     root     599992984064 Mar 25 08:36  vml.0200050000600805f3001a0350a0483755c35800074d5341313030:1
-rw-------    1  root     root     599998660608 Mar 25 08:36  vml.0200060000600805f3001a0350ace30859127200084d5341313030
-rw-------    1  root     root     599992984064 Mar 25 08:36  vml.0200060000600805f3001a0350ace30859127200084d5341313030:1
[root@server4  disks]#
----
[root@server1 disks]# ls -la
total 3551150729
drwx------    1  root     root          512 Mar 25 05:26 .
drwx------    1 root      root          512 Mar 25 05:26 ..
-rwx------    1 root     root      36385505280 Mar 25 05:26 vmhba0:0:0:0
lrwx------    1 root     root            58 Mar 25 05:26 vmhba1:0:1:0 ->  vml.0200010000600805f3001a0350adbeb37f8f4b00024d5341313030
lrwx------    1  root     root           58 Mar 25 05:26 vmhba1:0:2:0 ->  vml.0200020000600805f3001a0350a10cb7ca973d00044d5341313030
lrwx------    1  root     root           58 Mar 25 05:26 vmhba1:0:3:0 ->  vml.0200030000600805f3001a0350a0dc87e7f33300054d5341313030
lrwx------    1  root     root           58 Mar 25 05:26 vmhba1:0:4:0 ->  vml.0200040000600805f3001a0350affd2acacc3600064d5341313030
lrwx------    1  root     root           58 Mar 25 05:26 vmhba1:0:5:0 ->  vml.0200050000600805f3001a0350a0483755c35800074d5341313030
lrwx------    1  root     root           58 Mar 25 05:26 vmhba1:0:6:0 ->  vml.0200060000600805f3001a0350ace30859127200084d5341313030
-rwx------    1  root     root     899998300160 Mar 25 05:26  vml.0200010000600805f3001a0350adbeb37f8f4b00024d5341313030
-rwx------    1  root     root     285426580992 Mar 25 05:26  vml.0200020000600805f3001a0350a10cb7ca973d00044d5341313030
-rwx------    1  root     root     914570932736 Mar 25 05:26  vml.0200030000600805f3001a0350a0dc87e7f33300054d5341313030
-rwx------    1  root     root     299999559680 Mar 25 05:26  vml.0200040000600805f3001a0350affd2acacc3600064d5341313030
-rwx------    1  root     root     599998806016 Mar 25 05:26  vml.0200050000600805f3001a0350a0483755c35800074d5341313030
-rwx------    1  root     root     599998660608 Mar 25 05:26  vml.0200060000600805f3001a0350ace30859127200084d5341313030
[root@server1  disks]#
Tags (4)
Reply
0 Kudos
1 Reply
Sreejesh_D
Virtuoso
Virtuoso

may the volumes detected as VMFS snapshot or there is a signature issue. Run the following command if ESX/ ESXi is 4.1, it will list if there is a snapshot volume.

esxcfg-volume -l

Follow the steps in following KB to mount the volume if there is any snapshot volume exist.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101138...

Reply
0 Kudos