Hi,
I had an issue booting a host from USB due to corruption so re imaged the USB stick. On booting I had to manually mount one datastore (the server has 3 local HDDs, 2 in a mirrored pair and one not in an array) but the second datastore will not mount. The datastore is not visible in the webclient, but I can see it as a snapshot (oddly) via CLI:
[root@localhost:~] esxcli storage vmfs snapshot list
59beb848-9069b44e-64b3-00fd45fd5450
Volume Name: DATA
VMFS UUID: 59beb848-9069b44e-64b3-00fd45fd5450
Can mount: false
Reason for un-mountability: duplicate extents found
Can resignature: false
Reason for non-resignaturability: duplicate extents found
Unresolved Extent Count: 2
And again as a volume:
[root@localhost:~] esxcfg-volume -l
VMFS UUID/label: 59beb848-9069b44e-64b3-00fd45fd5450/DATA
Can mount: No (duplicate extents found)
Can resignature: No (duplicate extents found)
Extent name: t10.ATA_____WDC_WD20EZRX2D00DC0B0_________________________WD2DWCC1T1033575:1 range: 0 - 1907455 (MB)
Extent name: t10.ATA_____WDC_WD20EZRX2D00DC0B0_________________________WD2DWCC1T1090546:1 range: 0 - 1907455 (MB)
When I try mount the "snapshot" I get:
[root@localhost:~] esxcli storage vmfs snapshot mount -l DATA
Unable to mount this VMFS volume due to duplicate extents found
I can't try and mount the datastore as a volume as I get:
[root@localhost:~] esxcli storage filesystem mount -u 59beb848-9069b44e-64b3-00fd45fd5450
No volume with uuid '59beb848-9069b44e-64b3-00fd45fd5450' was found
I've read various posts online addressing similar issues, usually to do with SAN storage as apposed to local, some suggesting to resignature the volume but I also get an error around duplicate extents when I attempt that.
Does anyone have any ideas how to resolve the issue? I'm at a dead end.
Thanks.
Bumping a really old thread, but for a good reason...
I have the same issue, and I am completely unable to find any kind of a solution...
If this happens to anyone else...
For me the issue was because latest ESXi offline update bundle released by HP did not have valid driver for FakeRAID controller (B140i in my case for 9Gen ProLiant ML30).
If you get an error like this it is because there are two drives with same VMFS signature.
In my case, FakeRAID was setup as RAID1 which completely mirrored drives.
After ESXi was updated with wrong driver it was not able to recognize drives as one array, so they were found by ESXi as two drives with same signature.
My solution was manual driver update.
After driver was updated everything started working as it should.