Hello
Some time ago I noticed a VERY large number of messages in the log of vmkernel.log similar to:
Partition: 648: Read from primary gpt table failed on "naa.600a...."
Almost all datastore devices(absolutly different datastores and LUNs) are listed in the log.
The output of the "partedUtil getptbl" command is:
Error: The primary GPT table is corrupt, but the backup appears OK, so that will be used. Fix primary table ? diskPath (/dev/disks/naa.600a...) diskSize (23622320128) AlternateLBA (1) LastUsableLBA (23622320094)
I have tried the "partedUtil fixGpt" command and it fixes the GPT.
However, I have questions:
1. How safe is it to use in a production environment?
2. What are the unpredictable consequences of this command?
3. What can happen if you ignore these messages?
4. How can I see what exactly is damaged in the Primary GPT?
Output of the "partedUtil getptbl" command before fixing and after is the same:
gpt
1229833 255 63 19757268992
ps ESXi 6.5 U2, datastores connect to hosts via FC