VMware wants to format an existing VMFS
We are running two VMware ESXi v4 systems. We access our VMs on a NAS via iSCSI. Recently, we had some issues and had to remove and reconfigure the iSCSI LUN on each server. On one, it came right up. We were able to see the LUN and it mounted just fine and we saw all of our VMs. On the second VMware ESXi box, if we do a Rescan.. it won't auto-mount the LUN (which has VMFS). If we do an Add Storage, we can find the LUN but then we get only the option "Format the disk [create a new datastore]).
Obviously that would be a bad idea. :)
I can't figure out the problem.
BTW, we can mount a second LUN on both VMware servers just fine that we use for some other VMs that we just created.
Obviously that would be a bad idea. :)
I can't figure out the problem.
BTW, we can mount a second LUN on both VMware servers just fine that we use for some other VMs that we just created.
can you mount this LUN on the other ESX servers?
no one has presented this to A Windows source and formatted it?
no one has presented this to A Windows source and formatted it?
Clinical Systems Analyst
Is the option to re-signature available when you go through add storage wizard?
if you can, post a screenshot of what you see during add storage wizard
if you can, post a screenshot of what you see during add storage wizard
if seems that for some reason the signature on the LUN has changed. Hence VMware ESXi, wants to reformat, rather than add.
check at the ESXi console with
esxcfg-volume -l
check at the ESXi console with
esxcfg-volume -l
You can also re-signature existing VMFS volumes through the vSphere client using the "Add Storage" wizard in the host configuration tab storage section.
The wizard detects the existing VMFS volume and lets you choose between:
- Re-signature volume and keep data.
- Keep existing signature and mount the volume.
- Reformat the volume.
The wizard detects the existing VMFS volume and lets you choose between:
- Re-signature volume and keep data.
- Keep existing signature and mount the volume.
- Reformat the volume.
Let's clarify a few things just in case.
The LUN is being exported by a NAS that offers iSCSI.
vm-4 is able to mount the LUN just fine and sees the filesystem and VMs.
vm-3 wants to format the LUN.
I am attaching screenshots to make life easier. :)
vm-3.png
vm-3-formatlun.png
vm-3-selectlun.png
vm-4.png
The LUN is being exported by a NAS that offers iSCSI.
vm-4 is able to mount the LUN just fine and sees the filesystem and VMs.
vm-3 wants to format the LUN.
I am attaching screenshots to make life easier. :)
vm-3.png
vm-3-formatlun.png
vm-3-selectlun.png
vm-4.png
okay. got it.
what output do you get with esxcfg-volume -l
also do you have valid backups of the vms on the lun.
what output do you get with esxcfg-volume -l
also do you have valid backups of the vms on the lun.
on vm-3:
~ # esxcfg-volume -l
VMFS3 UUID/label: 4cc89503-f054d0d4-2865-002
Can mount: Yes
Can resignature: No (the volume is being actively used)
Extent name: naa.600140588e9bab7d2b7ed4
The volume is mounted on vm-4, but that's common practice with vmfs. Or perhaps I'm missing something.
~ # esxcfg-volume -l
VMFS3 UUID/label: 4cc89503-f054d0d4-2865-002
Can mount: Yes
Can resignature: No (the volume is being actively used)
Extent name: naa.600140588e9bab7d2b7ed4
The volume is mounted on vm-4, but that's common practice with vmfs. Or perhaps I'm missing something.
Clinical Systems Analyst
in the gui, do a rescan on all storage, then review the /var/log/vmkernel file for errors.
'less /var/log/vmkernel' will open it, do a capital G to go to the bottom of the file, then use the page-up/page-down keys to navigate. Look for any error messages, especially those that reference that naa id or UUID. post the file up if you can, too. You can download it with winscp or cp it over to a working datastore and then use the datastore browser to download it to your pc.
'less /var/log/vmkernel' will open it, do a capital G to go to the bottom of the file, then use the page-up/page-down keys to navigate. Look for any error messages, especially those that reference that naa id or UUID. post the file up if you can, too. You can download it with winscp or cp it over to a working datastore and then use the datastore browser to download it to your pc.
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION
Wow. Worked perfectly:
# esxcfg-volume -m 4cc89503-f054d0d4-2865-002
There you go. Sometimes the CLI just works better. :)
# esxcfg-volume -m 4cc89503-f054d0d4-2865-002
There you go. Sometimes the CLI just works better. :)
Very helpful and to the point. Took the time to read through my initial question and my responses and gave me the absolute right answer.
We also use the command line, rather than the GUI, because it's more powerful, or I'm I just old fasioned, and not a GUI man!
~ # esxcfg-volume -M VOLUME_LABEL_OR_ID
My issue was slightly different, but for those that wander here and find the above solution doesn't work. Try a capital 'M'.
It is a different command and resolved my issue. Same premise as the OP but nothing else worked.
My issue was slightly different, but for those that wander here and find the above solution doesn't work. Try a capital 'M'.
It is a different command and resolved my issue. Same premise as the OP but nothing else worked.
I have the same problem
I tried with all the option but still i couldnt mount the LUN. I could see the LUN displayed in
/vmfs/devices/disks/naa.60
/vmfs/devices/disks/naa.60
But I couldnt mount this, when i attempt to mount, it says that it is going to format all data.
My ESXi version is 4.0.0, 208167
Check the screenshot for more info,
====================
fdisk -u result
Disk /vmfs/devices/disks/naa.60
255 heads, 63 sectors/track, 58743 cylinders, total 943718400 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/vmfs/devices/disks/naa.60
=====================
There is data I am afraid to proceed further...
vmfs-mount-error.png
I tried with all the option but still i couldnt mount the LUN. I could see the LUN displayed in
/vmfs/devices/disks/naa.60
/vmfs/devices/disks/naa.60
But I couldnt mount this, when i attempt to mount, it says that it is going to format all data.
My ESXi version is 4.0.0, 208167
Check the screenshot for more info,
====================
fdisk -u result
Disk /vmfs/devices/disks/naa.60
255 heads, 63 sectors/track, 58743 cylinders, total 943718400 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/vmfs/devices/disks/naa.60
=====================
There is data I am afraid to proceed further...
vmfs-mount-error.png
Join our community and discover your potential
Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.
*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.