Quick one here. Create a new logical disk via RAID5, after an old logical unit failed from only a single bad disk.
No issues deleting the old logical disk, and creating a new one via HP storage controller commands.
However was greeted with this nice error.
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.”
Looks like it worked… Thanks Cookie04!