can you share vmkernel.log to do further investigation.
1 person found this helpful
You need to check vmkernel.log according to time when you try to create VMFS datastore.
Usually outdated driver \ firmware for raid controller causes such issues.
If you use server from Dell then try to install ESXi using Dell customized ISO.
1 person found this helpful
What I could think of is that there's something on the LUN (Virtual Disk) that causes the issue, e.g. some dirty bits which are interpreted incorrectly!?
In this case you could try to clear the 10TB virtual disk's partition table. To do this, select Storage in the inventory, then switch to the Devices tab. With the proper device selected, run "Clear partition table" from the Actions menu.
Devices: 1 x 10TB Virtual Disk (Raid 10 x 4 Physical Disks) setup by Dell.
Size to create VMFS datastore: 1 TB
Please remember that VMware supports only a single datasatore per LUN (Virtual Disk)!
16 people found this helpful
I had the same problem and in order to fix it I had to run three commands through an SSH connection. From what I have seen and found this error comes from having disks that were part of different arrays and contain some data on them. When I ran the commands I was then able to connect the data stores with no issues.
1. Show connected disks.
ls -lha /vmfs/devices/disks/
(Verify the disk is seen. You will probably see your disk ID then :1. This is a partition on the disk. We only need to work about the main disk ID.)
2. Show the error on disk.
partedUtil getptbl /vmfs/devices/disks/(disk ID)
(It will probably indicate that the GPT is located beyond the end of the disk.)
3. Wipe disk and rewrite with a basic MSDOS partion.
partedUtil setptbl /vmfs/devices/disks/(disk ID) msdos
(The output from this should be similar to msdos and the next line will be o o o o)
I hope this helps you out.
This post is a bit old but I found it while researching the same error message. My R540 had the exact same message and it ended up being that the newly created array that I was attempted to create a new datastore on was not finished doing a full initialization by the controller. During the array config I opted to do a full initialization instead of a quick. Once I waited it out, the VMFS datastore creation went fine. Even though the iDrac had the array marked as "online" and ready it would fail with the error message.
i have the same problem with an esxi 6.7 and a local ssd Samsung 840 Pro.
esxi 6.7 FSS: 2350: Failed to create FS
(this is a test computer)
I got this error could you help me please
0 0 0 0
Error: Read-only file system during write on /dev/disks/naa.600508b1001c50fcc5654d86b955aa6e
WriteNewPtable: error removing gpt signatures from (/dev/disks/naa.600508b1001c50fcc5654d86b955aa6e)
I was able to fix my issue.
Could you run this ls -lha /vmfs/devices/disks/
and paste image of your disks. thanks
According to the screenshot you are trying to overwrite the system/installation disk on an ESXi 7.0 host!?
Moderator note: Please consider to open a new discussion instead of asking for help on an already 2 years old one. A new discussion you will get much more attention.