I have a Home Lab with 1 host that I recently setup to study for my VCP and hope you can help me with this issue.
I upgraded the VCSA via the Install updates in the VCSA. The upgrade was from 5.5.0.10000 Build 1624811 to 5.5.0.10200 Build 1891314.
1) Received this error when I booted up the ESXi Server & attempted to logon to the web client;
Failed to verify the SSL certificate for one or more vCenter Server Systems: https://vCenterServerFQDN:443/sdk
To Fix this I followed KB 2033338 and enabled Certificate regeneration then rebooted the VCenter appliance. Please note I have not got SSO Enabled
After this I was able to logon to the Web client all the data stores were showing as inaccessible. I rebooted the ESXi Host ( Only running 1 host at present) but the data stores still showing as inaccessible.
I disconnected the ESXi host and have not been able to reconnect. I get the following error;
Datastore 'SATA_NoRAID_01' conflicts with an existing datastore in the datacenter that has the same URL (ds:///vmfs/volumes/535f0166-cd19b3f2-8d9f-a0369f390962/), but is backed by different physical storage.
I found KB 2036481, Connected to the ESXi Host via Putty and ran the esxcfg-scsidevs -m command ( Output attached) and then ran the ls -lrth /vmfs/devices/disks | grep -i naa Command but nothing output.
I have disconnected the hard disks that contain the Datastores & reconnected them to different SATA ports but this has not resolved the issue.
Please let me know how I can Connect my ESXi Host again to the VCenter and make the DataStore active again.
Regards
David
hi -- seems like grepping for naa will only return SAN devices .. so do ls -lrth /vmfs/devices/disks | grep mpx -- if that too does not return much just paste the whole of ls -lrth /vmfs/devices/disks -- we can work from there
~Sai Garimella
Hi,
The output of the two commands is below;
~ # ls -lrth /vmfs/devices/disks | grep mpx
lrwxrwxrwx 1 root root 22 Jul 7 07:20 vml.0000000000766d6862613 3323a303a30:8 -> mpx.vmhba32:C0:T0:L0:8
lrwxrwxrwx 1 root root 22 Jul 7 07:20 vml.0000000000766d6862613 3323a303a30:7 -> mpx.vmhba32:C0:T0:L0:7
lrwxrwxrwx 1 root root 22 Jul 7 07:20 vml.0000000000766d6862613 3323a303a30:6 -> mpx.vmhba32:C0:T0:L0:6
lrwxrwxrwx 1 root root 22 Jul 7 07:20 vml.0000000000766d6862613 3323a303a30:5 -> mpx.vmhba32:C0:T0:L0:5
lrwxrwxrwx 1 root root 22 Jul 7 07:20 vml.0000000000766d6862613 3323a303a30:4 -> mpx.vmhba32:C0:T0:L0:4
lrwxrwxrwx 1 root root 22 Jul 7 07:20 vml.0000000000766d6862613 3323a303a30:1 -> mpx.vmhba32:C0:T0:L0:1
lrwxrwxrwx 1 root root 20 Jul 7 07:20 vml.0000000000766d6862613 3323a303a30 -> mpx.vmhba32:C0:T0:L0
-rw------- 1 root root 286.0M Jul 7 07:20 mpx.vmhba32:C0:T0:L0:8
-rw------- 1 root root 110.0M Jul 7 07:20 mpx.vmhba32:C0:T0:L0:7
-rw------- 1 root root 250.0M Jul 7 07:20 mpx.vmhba32:C0:T0:L0:6
-rw------- 1 root root 250.0M Jul 7 07:20 mpx.vmhba32:C0:T0:L0:5
-rw------- 1 root root 4.0M Jul 7 07:20 mpx.vmhba32:C0:T0:L0:4
-rw------- 1 root root 896.0M Jul 7 07:20 mpx.vmhba32:C0:T0:L0:1
-rw------- 1 root root 7.5G Jul 7 07:20 mpx.vmhba32:C0:T0:L0
~ # ls -lrth /vmfs/devices/disks
totTotal 5870198368
lrwxrwxrwx 1 root root 73 Jul 7 07:23 vml.010000000020202020202 02020202020205a31463530593256535432303030 -> t10.ATA_____ST2000DM0012D1CH164____ ______________________________Z1F50Y2V
lrwxrwxrwx 1 root root 75 Jul 7 07:23 vml.010000000020202020202 02020202020205a3145374c573832535432303030:1 -> t10.ATA_____ST2000DM0012D1CH164__ ________________________________Z1E7LW82:1
lrwxrwxrwx 1 root root 73 Jul 7 07:23 vml.010000000020202020202 02020202020205a3145374c573832535432303030 -> t10.ATA_____ST2000DM0012D1CH164____ ______________________________Z1E7LW82
lrwxrwxrwx 1 root root 22 Jul 7 07:23 vml.0000000000766d6862613 3323a303a30:8 -> mpx.vmhba32:C0:T0:L0:8
lrwxrwxrwx 1 root root 22 Jul 7 07:23 vml.0000000000766d6862613 3323a303a30:7 -> mpx.vmhba32:C0:T0:L0:7
lrwxrwxrwx 1 root root 22 Jul 7 07:23 vml.0000000000766d6862613 3323a303a30:6 -> mpx.vmhba32:C0:T0:L0:6
lrwxrwxrwx 1 root root 22 Jul 7 07:23 vml.0000000000766d6862613 3323a303a30:5 -> mpx.vmhba32:C0:T0:L0:5
lrwxrwxrwx 1 root root 22 Jul 7 07:23 vml.0000000000766d6862613 3323a303a30:4 -> mpx.vmhba32:C0:T0:L0:4
lrwxrwxrwx 1 root root 22 Jul 7 07:23 vml.0000000000766d6862613 3323a303a30:1 -> mpx.vmhba32:C0:T0:L0:1
lrwxrwxrwx 1 root root 20 Jul 7 07:23 vml.0000000000766d6862613 3323a303a30 -> mpx.vmhba32:C0:T0:L0
-rw------- 1 root root 1.8T Jul 7 07:23 t10.ATA_____ST2000DM0012D 1CH164__________________________________Z1F50Y2V
-rw------- 1 root root 1.8T Jul 7 07:23 t10.ATA_____ST2000DM0012D 1CH164__________________________________Z1E7LW82:1
-rw------- 1 root root 1.8T Jul 7 07:23 t10.ATA_____ST2000DM0012D 1CH164__________________________________Z1E7LW82
-rw------- 1 root root 286.0M Jul 7 07:23 mpx.vmhba32:C0:T0:L0:8
-rw------- 1 root root 110.0M Jul 7 07:23 mpx.vmhba32:C0:T0:L0:7
-rw------- 1 root root 250.0M Jul 7 07:23 mpx.vmhba32:C0:T0:L0:6
-rw------- 1 root root 250.0M Jul 7 07:23 mpx.vmhba32:C0:T0:L0:5
-rw------- 1 root root 4.0M Jul 7 07:23 mpx.vmhba32:C0:T0:L0:4
-rw------- 1 root root 896.0M Jul 7 07:23 mpx.vmhba32:C0:T0:L0:1
-rw------- 1 root root 7.5G Jul 7 07:23 mpx.vmhba32:C0:T0:L0
Appreciate the help.
Regards
David
thanks - how many datastores were here prior to the upgrade ? was it just one ?
There were 2 Datastores prior to the Upgrade. The Server also has 3 x SATA Drives, two containing the 2x Data stores and the 3rd disk not in use yet.
Regards
David
just searched thru the archives -- this seems more relevant as you have only one ESX host -- my suggestion according to that would be to disconnect the drives - reinstall ESXi and connect them back
Cannot add host to vCenter server because datastore is shared with an existing vCenter host
~Sai Garimella