VMware Cloud Community
spiffeluringen
Contributor
Contributor

New datastore using old partition

Is it still possible to create a new datastore in the same place without destroying the files present, if you use the same name and partitioning options? This is esxi 6.7

I remember having done this in esxi 5 (maybe 5.5), after a reboot the datastore was missing and I could not see it anyware, after giving up regaining the datastore I decided to just create a new datastore and use the backups, but afterwords all files where there and working..

As you can see the device is visible.

datastore1.PNG

 

 

Reply
0 Kudos
27 Replies
spiffeluringen
Contributor
Contributor

Yes I havent given upp, my guess is that this is from the faulty disk that is still present in the machine.

Should I remove it and we go from there?

Reply
0 Kudos
spiffeluringen
Contributor
Contributor

Is this something that is possible to work with?

 

esxcli storage vmfs extent list
[root@VMESXi6:~] esxcli storage vmfs extent list
Volume Name VMFS UUID Extent Number Device Name Partition
----------- ----------------------------------- ------------- ------------------------------------------------------------------------- ---------
DATA2 5b645277-8d5e92a9-8bf8-40f2e9a61a78 0 naa.600605b00d1e455022827e6e1572e990 1
DATASTORE1 551b50cd-4562d988-2331-40f2e9a61a78 0 t10.ATA_____ST8000DM0042D2CX188__________________________________ZCT3DDHT 1
[root@VMESXi6:~]


#
ls -alh /vmfs/devices/disks
[root@VMESXi6:~] ls -alh /vmfs/devices/disks
total 17186018537
drwxr-xr-x 2 root root 512 Mar 8 10:48 .
drwxr-xr-x 16 root root 512 Mar 8 10:48 ..
-rw------- 1 root root 1.9G Mar 8 10:48 mpx.vmhba32:C0:T0:L0
-rw------- 1 root root 4.0M Mar 8 10:48 mpx.vmhba32:C0:T0:L0:1
-rw------- 1 root root 250.0M Mar 8 10:48 mpx.vmhba32:C0:T0:L0:5
-rw------- 1 root root 250.0M Mar 8 10:48 mpx.vmhba32:C0:T0:L0:6
-rw------- 1 root root 110.0M Mar 8 10:48 mpx.vmhba32:C0:T0:L0:7
-rw------- 1 root root 286.0M Mar 8 10:48 mpx.vmhba32:C0:T0:L0:8
-rw------- 1 root root 3.3T Mar 8 10:48 naa.600605b00d1e455022827e6e1572e990
-rw------- 1 root root 3.3T Mar 8 10:48 naa.600605b00d1e455022827e6e1572e990:1
-rw------- 1 root root 7.3T Mar 8 10:48 t10.ATA_____ST8000DM0042D2CX188__________________________________ZCT3DDHT
-rw------- 1 root root 2.2T Mar 8 10:48 t10.ATA_____ST8000DM0042D2CX188__________________________________ZCT3DDHT:1
lrwxrwxrwx 1 root root 20 Mar 8 10:48 vml.0000000000766d68626133323a303a30 -> mpx.vmhba32:C0:T0:L0
lrwxrwxrwx 1 root root 22 Mar 8 10:48 vml.0000000000766d68626133323a303a30:1 -> mpx.vmhba32:C0:T0:L0:1
lrwxrwxrwx 1 root root 22 Mar 8 10:48 vml.0000000000766d68626133323a303a30:5 -> mpx.vmhba32:C0:T0:L0:5
lrwxrwxrwx 1 root root 22 Mar 8 10:48 vml.0000000000766d68626133323a303a30:6 -> mpx.vmhba32:C0:T0:L0:6
lrwxrwxrwx 1 root root 22 Mar 8 10:48 vml.0000000000766d68626133323a303a30:7 -> mpx.vmhba32:C0:T0:L0:7
lrwxrwxrwx 1 root root 22 Mar 8 10:48 vml.0000000000766d68626133323a303a30:8 -> mpx.vmhba32:C0:T0:L0:8
lrwxrwxrwx 1 root root 73 Mar 8 10:48 vml.01000000002020202020202020202020205a43543344444854535438303030 -> t10.ATA_____ST8000DM0042D2CX188__________________________________ZCT3DDHT
lrwxrwxrwx 1 root root 75 Mar 8 10:48 vml.01000000002020202020202020202020205a43543344444854535438303030:1 -> t10.ATA_____ST8000DM0042D2CX188__________________________________ZCT3DDHT:1
lrwxrwxrwx 1 root root 36 Mar 8 10:48 vml.0200000000600605b00d1e455022827e6e1572e990536572766552 -> naa.600605b00d1e455022827e6e1572e990
lrwxrwxrwx 1 root root 38 Mar 8 10:48 vml.0200000000600605b00d1e455022827e6e1572e990536572766552:1 -> naa.600605b00d1e455022827e6e1572e990:1


esxcli storage vmfs snapshot list
nada

esxcli storage filesystem list
[root@VMESXi6:~] esxcli storage filesystem list
Mount Point Volume Name UUID Mounted Type Size Free
------------------------------------------------- ----------- ----------------------------------- ------- ------ ------------- -------------
/vmfs/volumes/5b645277-8d5e92a9-8bf8-40f2e9a61a78 DATA2 5b645277-8d5e92a9-8bf8-40f2e9a61a78 true VMFS-6 3597840416768 837812224
/vmfs/volumes/551b50cd-4562d988-2331-40f2e9a61a78 DATASTORE1 551b50cd-4562d988-2331-40f2e9a61a78 true VMFS-5 2397933928448 1877172289536
/vmfs/volumes/7b6be5e5-70263cea-fe0e-fb11006cb6fe 7b6be5e5-70263cea-fe0e-fb11006cb6fe true vfat 261853184 93880320
/vmfs/volumes/551b45e8-eebaf810-c3c1-40f2e9a61a78 551b45e8-eebaf810-c3c1-40f2e9a61a78 true vfat 299712512 80486400
/vmfs/volumes/5acf16e0-a706c55d-e17d-a153153dfbb5 5acf16e0-a706c55d-e17d-a153153dfbb5 true vfat 261853184 113680384

#
esxcli storage vmfs extent list
[root@VMESXi6:~] esxcli storage vmfs extent list
Volume Name VMFS UUID Extent Number Device Name Partition
----------- ----------------------------------- ------------- ------------------------------------------------------------------------- ---------
DATA2 5b645277-8d5e92a9-8bf8-40f2e9a61a78 0 naa.600605b00d1e455022827e6e1572e990 1
DATASTORE1 551b50cd-4562d988-2331-40f2e9a61a78 0 t10.ATA_____ST8000DM0042D2CX188__________________________________ZCT3DDHT 1

Reply
0 Kudos
spiffeluringen
Contributor
Contributor

With the ATA disk in the machine I found something interesting.

 

Reply
0 Kudos
spiffeluringen
Contributor
Contributor

I tryed with the clone in place and got this

[root@VMESXi6:~] esxcli storage filesystem list
Mount Point Volume Name UUID Mounted Type Size Free
------------------------------------------------- ----------- ----------------------------------- ------- ------ ------------- -------------
/vmfs/volumes/5b645277-8d5e92a9-8bf8-40f2e9a61a78 DATA2 5b645277-8d5e92a9-8bf8-40f2e9a61a78 true VMFS-6 3597840416768 835715072
/vmfs/volumes/551b50cd-4562d988-2331-40f2e9a61a78 DATASTORE1 551b50cd-4562d988-2331-40f2e9a61a78 true VMFS-5 2397933928448 1877171240960
/vmfs/volumes/551b45e8-eebaf810-c3c1-40f2e9a61a78 551b45e8-eebaf810-c3c1-40f2e9a61a78 true vfat 299712512 80486400
/vmfs/volumes/5acf16e0-a706c55d-e17d-a153153dfbb5 5acf16e0-a706c55d-e17d-a153153dfbb5 true vfat 261853184 113680384
/vmfs/volumes/7b6be5e5-70263cea-fe0e-fb11006cb6fe 7b6be5e5-70263cea-fe0e-fb11006cb6fe true vfat 261853184 93880320
[root@VMESXi6:~]
[root@VMESXi6:~] esxcli storage vmfs snapshot list
[root@VMESXi6:~]
[root@VMESXi6:~]

Reply
0 Kudos
spiffeluringen
Contributor
Contributor

Also would it help finding the error if I installed an new host on a new USB.media (keeping the old one intact) in the same machine?

Reply
0 Kudos
continuum
Immortal
Immortal

Yes - install a fresh ESXi to USB.
That sometimes helps

 

Ulli


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
spiffeluringen
Contributor
Contributor

OK installed a new host on new USB and it looks the same as far as I can tell so far.

The bigger storage was found automaticaly and it contains a vmdk file among some other things.

It also detcted the other device with the same UUID. but not as a datastore.

The parameters is also the same, it claims to be a VMFS(5) volume and the size is correct, see pic

I´m not sure what the next step would be?

I have a disk with UBUNTU 20xx in the machine I that is possible to boot from aswell

 

 

 

Reply
0 Kudos
spiffeluringen
Contributor
Contributor

Some things I dont understand,
one is the size of the content, on the device the amount of data claimed as used is much less than what I expect, the drive in the VM contained more than double the dataamount before?
The amount of data that I can see is less than what it claims to contain.
What is on the rest?


A question about .sdd.sf, is this created by the host on start or is it persistent on the datastore/devise?

 

 

Reply
0 Kudos