![]() ![]() I enabled iscsi on all 3 hosts and then went to the SAN to see if it found the IQNs. The second NIC on the hosts and the SAN are plugged into a dedicated switch. The second NIC on each host is in the 192.168.100.0 network as is the second NIC on the SAN server. I created a VMkernal port on each host that uses the second NIC for iSCSI. The first NICs are used for the VMnetwork. The hosts were all using local storage for the VMs so I was assigned to implement iscsi so that eventually we will buy Vcenter and start using Vmotion. ![]() I'll try to answer each of your questions as best I can.ġ. is there any error there ? do you see any fs3, lvm error?Ħ) did you check the following KB from the download page : extract it from a linux machine and look at the var/log/vmkernel for rescan even. SO DO NEVER CHANGE LVM.ENABLERESIGNATURING TO 1 UNLESS YOU KNOW WHY IT NEED TO BE RESIGNATURED AND THERE NO OTHER OPTION AND NO OTHER LUN ARE GOING TO BE RESINGNATURED.ĥ) collect from the vi client a support bundle (file>export>diagnostic bundle.). I know by experience that many peopel do that change first as it seems to be the obvious way out of a vmfs not mounting, but really it should only considered as a lats resort as it can corrupt your data and is an operation which generate a really heavy administrative work to be completed. do you see the lun in the storage adapter screen ?Ģ) also an important point to know is what was the version of ESX you were using before (version number adn build number) and what bis the current one.ģ) as you suggest, it seems this is due to the upgrade, did you try to rool back the install to the previous version ? (reinstall one of the esx with the previous version anc check)Ĥ) if you have followed the advivce of changimng LVM resignaturing please reverte teh change ASAP! while this change is handy and a good tip, it is Extremely dangerous option that should be changed only as last resort when the issue is diagnosed already which is not the case. so do you see the datastore in the datastore screen? i believe not because you are posting here. I am not sure if you have still the problem, how evrr to help resolving the issue i have few question to ask :ġ)to detrmine wher we fail we need to confirm if the problem is with the vmfs not mounting, the lun not being seen or the target not seen. Sorry about that - got a little carried away. My experience with their support people has been very positive. If you're not willing to wait for the answer in the forum or the next free version of ESXi to come out, or you're not willing to downgrade to an earlier firmware revision, then grab your credit card and pay for a single support call with VMware to resolve the issue - they can probably tell you in half an hour what may take you a few days on this forum to figure out. VMware may have messed up the latest build of their software a little bit - there seem to be a few people with similar issues - but if they did, trust me, they will fix it. I can certainly understand frustration with it, especially when it works in one version and stops working after an "upgrade," but have a little patience. Oh, c'mon - It drives me nuts when people, after encountering an error setting something up, immediately get ticked off at the company who produces the product - especially when the product is licensed for free.
0 Comments
Leave a Reply. |