vSAN1

I was playing around VSAN and it failed so I decided not to use VSAn and want to get my local datastores back

From the GUi I can not erase partitions.

running from cli

partedUtil mklabel /vmfs/devices/disks/naa.5000000000000000 gpt

Error: Read-only file system during write on /dev/disks/naa.5000000000000000

WriteNewPtable: Unable to commit to device /vmfs/devices/disks/naa.5000000000000000

This is a list of my disks

vml.0000000000766d68626133323a303a30 -> mpx.vmhba32:C0:T0:L0

vml.0000000000766d68626133323a303a30:1 -> mpx.vmhba32:C0:T0:L0:1

vml.0000000000766d68626133323a303a30:5 -> mpx.vmhba32:C0:T0:L0:5

vml.0000000000766d68626133323a303a30:6 -> mpx.vmhba32:C0:T0:L0:6

vml.0000000000766d68626133323a303a30:7 -> mpx.vmhba32:C0:T0:L0:7

vml.0000000000766d68626133323a303a30:8 -> mpx.vmhba32:C0:T0:L0:8

vml.0000000000766d68626133323a303a30:9 -> mpx.vmhba32:C0:T0:L0:9

vml.01000000003531333330303030303030303030433955534220466c -> mpx.vmhba33:C0:T0:L0

vml.01000000003531333330303030303030303030433955534220466c:1 -> mpx.vmhba33:C0:T0:L0:1

vml.020000000050000000000000004e4653303231 -> naa.5000000000000000

vml.020000000050000000000000004e4653303231:1 -> naa.5000000000000000:1

vml.020000000050000000000000004e4653303231:2 -> naa.5000000000000000:2

vml.02000000005000c500b2d98a97535431303030 -> naa.5000c500b2d98a97

vml.02000000005000c500b2d98a97535431303030:1 -> naa.5000c500b2d98a97:1

vml.02000000005000c500b2d98a97535431303030:2 -> naa.5000c500b2d98a97:2

vml.02000000005000c500b5f0e3fe535431303030 -> naa.5000c500b5f0e3fe

vml.02000000005000c500b5f0e3fe535431303030:1 -> naa.5000c500b5f0e3fe:1

vml.02000000005000c500b5f0e3fe535431303030:2 -> naa.5000c500b5f0e3fe:2

vml.02000000005000c500b6873eaa535431303030 -> naa.5000c500b6873eaa

vml.02000000005000c500b6873eaa535431303030:1 -> naa.5000c500b6873eaa:1

vml.02000000005000c500b6873eaa535431303030:2 -> naa.5000c500b6873eaa:2

any ideas on how to get my local disks back?

Thank you

Tom

Discussion moved from VMware vCenter™ to VMware vSAN

This is not possible to format the read only disk using partedutil. If you are using usb disk then you need to remove the disk and connect to any windows server and format it using third party Rufus tool to format it. https://rufus.ie/

Nawals

The drives are SSD and ATA 1 SSD and ATA drives all 2.5 format.

So I need to remove all the drives and reformat them ???

The rufus tool create a bootable usb  will it point to the internal drives if I boot the esxi host

I got this working I had to remove the drives from the host I have a portable sata drive usb  device plugged into my computer and the started disk management

Was able to delete all active volumes on drive put but on esxi host

Ran next commands

partedUtil getUsableSectors /dev/disks/naa.5000000000000000

34 500118158

partedUtil setptbl /dev/disks/naa.5000000000000000  gpt "1 2048 500118158 AA31E02A400F11DB9590000C2911D1B8 0"

gpt

0 0 0 0

1 2048 500118158 AA31E02A400F11DB9590000C2911D1B8 0

vmkfstools -C vmfs6 -S TGCSESXI-15-Datastore-SSD /dev/disks

/naa.5000000000000000:1

create fs deviceName:'/dev/disks/naa.5000000000000000:1', fsShortName:'vmfs6', fsName:'TGCSESXI-15-Datastore-SSD'

deviceFullPath:/dev/disks/naa.5000000000000000:1 deviceFile:naa.5000000000000000:1

ATS on device /dev/disks/naa.5000000000000000:1: not supported

.

Checking if remote hosts are using this device as a valid file system. This may take a few seconds...

Creating vmfs6 file system on "naa.5000000000000000:1" with blockSize 1048576, unmapGranularity 1048576, unmapPriority default and volume label "TGCSESXI-15-Datastore-SSD".

Successfully created new volume: 5e74020a-d41ce4bc-c56d-000af77acb40

Now have local datastores

Thank you,

Tom

Hello Tom,

What was the nature of the failure?

Generally devices only become read-only if there are severe issues with them (or other things such as the controller they are attached to having issues).

Also, did you edit/obfuscate the naa number or is it actually naa.5000000000000000? I ask as that doesn't look right and maybe it is not being detected correctly.

Try rebooting the host and if still in that state then look in the vmkernel.log for messages relating to that device and/or the controller it is attached to (e.g. SCSI sense codes).

Bob

I ran into the same issue as I was attempting to get vSAN up and running the first time.

Sign into the ESXI host client (not vcenter)

Go to Storage -> Devices

Highlight the disk in question.

Actions -> Clear Partition Table

Much easier than pulling disks.