Hello, I need some help since I cannot see my datastore anymore.
I have a server Dell Poweredge with PERC H310 controller. This server had three SATA 4Tb configured as RAID5. This virtual disk was being seen from ESXi as a datastore named "DATI".
A couple of weeks ago one of these disk being degraded. I had some trouble finding SATA replacement, so I decide to move to SAS disks.
I bought 3 SAS Dell disk (4Tb). These are the operation I did in order to migrate the VM from the old datastore to a new datastore.
-put the defective SATA disk offline
-remove all SATA disks
-insert the three new SAS disks
-restart the server
-create a new virtual disk with SATA RAID SAS named DATA1
-put one of the SAS disks offline and remove it (so two bay are available)
-insert the two SATA disks still OK, accepted as foreign
-now I can see two virtual disks (SATA and SAS) both 7Tb
-start ESXi and create a new datastore with the new SAS virtual disk
-copy 5 VM machines to the new datastore (lot of time spent here...)
-unregister VM from old datastore DATI and register these VM on datastore DATA1
-start these 5 VM: all VM (Windows server, some 2008 one 2012 with Veeam Backup&Replication Suite) started an successfully working
Now I was ready to complete the migration from SATA to SAS, so I decided to remove these old SATA drives. So I:
- shutdown ESXi server
- removed the two old SATA disk and mounted the third SAS disk (so this RAID5 can be completed)
- power on server, enter in PERC controller and put this third disk online
- restarted the server and started ESXi
Now the trouble: datastore DATA1 disappeared in web console. I can see the disk as storage:
In the output of the command esxcli storage filesystem list I can see the disk:
unknown.vmhba1-unknown.2:0-naa.6b083fe0e9e63c0023b10b410d2f4655
UID: unknown.vmhba1-unknown.2:0-naa.6b083fe0e9e63c0023b10b410d2f4655
Runtime Name: vmhba1:C2:T0:L0
Device: naa.6b083fe0e9e63c0023b10b410d2f4655
Device Display Name: Local DELL Disk (naa.6b083fe0e9e63c0023b10b410d2f4655)
Adapter: vmhba1
Channel: 2
Target: 0
LUN: 0
Plugin: NMP
State: active
Transport: parallel
Adapter Identifier: unknown.vmhba1
Target Identifier: unknown.2:0
Adapter Transport Details: Unavailable or path is unclaimed
Target Transport Details: Unavailable or path is unclaimed
Maximum IO Size: 131072
When I enter in the /vmfs/volume directory I see something but I'm not sure what is this link:
I don't want to do it all over again. Please could you tell me how can I have this datastore available in the ESXi ?
Thanks a lot.
Riccardo
So, your issue is that you can't see a Datastore?
If this is a local Datastore (not very convenient), did you move the data before removing it physically?
What the command is showing to you is a symbolic link of the name of your old Datastore and the device which points to.
Are you sure that your datastore wasn't hosted in one of your old SATA drives?
Yes I cannot see the new datastore. I don't think that the new datastore is hosted by old sata drives since I created it pointing to the new virtual disk.
The command that show me this symbolic link is "ls -l" done in /vmfs/volumes directory.
This is the output of the same command when both virtual disk are mounted (two SATA + two SAS)
Here I can see only the datastore "DATA":
But here I can see both devices:
I'm afraid that it's only a mess on symbolic links, the disk is online in the Devices pane but not on datastore.
thank you and Merry Xmas to all!
Does the following command return something?
esxcli storage vmfs snapshot list
André
Hello, the command shows nothing:
[root@esxi:~] esxcli storage vmfs snapshot list
[root@esxi:~]
Is it bad?
In /dev/disks it seems that the new raid disk is there (naa.6b083fe0e9e63c0023b10b410d2f4655) but is not mounted.
What may help to find out what's causing the issue is to do a rescan, and then download the ESXi host's vmkernel.log to see whether it contains useful information.
Since the partition ssems to be ok, I think that an ESXi reinstall with preserving the VMFS datastore may also resolve the issue.
André
Ok thank you for your help. I'll let you know some news as soon as I'll try to make a new ESXi server installation (I will do a VM total backup before...)
Riccardo