- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I have recently received two Lenovo SR650 servers both with M.2 discs and ESXi 7.0. I am having difficulty seeing the two data stores defined below in XClarity when trying to add them in ESXi 7.0 and they do not seem to be available as shown in the following screen shot.
I have tried deleting them in XCLARITY and recreated them with different named but have had no joy
I have even tried navigating in the CLI and seen that the two DataStores seem available so I am not sure why the “New DataStore” wizard cannot see them or what I need to do to try to access and configure them in ESXi 7.0
SERVER ONE
SERVER TWO
Any assistance would be most grateful.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Could this be my issue?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Definitely nothing to do with evaluation mode, which is fully functional.
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Although I am a VMware employee I contribute to VMware Communities voluntarily (ie. not in any official capacity)
VMware Training & Certification blog
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did you install ESXi yourself, or did the hosts come with ESXi pre-installed?
Anyway, as a first step please run ls -lisa /dev/disks to find out whether, and how the RAID-LUNs are listed.
André
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks André
The ESXI was preinstalled with the system
These are the DataStore_SSD and DataStore_HDD respectively.
No sure why there are two files for each DataStore and why there are slightly different in size. What does the :1 mean at the end of the LUN?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
One entry is for the device (LUN), and the other one (with the ":1") represents partition 1 on that LUN.
Please run
partedUtil getptbl "/vmfs/devices/disks/DeviceName"
for both devices to see what this command reports for the partition.
In case that the command returns VMFS partitions (GUID: "AA31E02A400F11DB9590000C2911D1B8"), then run
esxcli storage vmfs snapshot list
to see whether the LUNs are detected as so called Snapshot LUNs. If so follow the steps in the "Command Line" section of https://kb.vmware.com/s/article/1011387 to try an mount the datastores.
André
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi André
I see what, seems to have happened I originally name these DataStores HDD_DISK_VOL and SSD_DISK_VOL and were able to mount them. I then changed their names to DataSore_SSD and DataStore_HDD to conform to our other Server Naming Convention.
As these data stored no longer exist (With their name change) I assume I need to remove these Snapshots and mount the new Disk Names?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Andre
Using
# esxcli storage vmfs snapshot mount -n -l "SSD_DISK_VOL"
and
# esxcli storage vmfs snapshot mount -n -l "HDD_DISK_VOL"
I was able to mount the volumes and just rename them Many thanks for your help ![]()