I figured out the solution to the problem.
There seems to be a bug (or several bugs?) in ESXi 5.5.0 and/or the vSphere 5.5.0b Client when trying to create a 4TB datastore using the vSphere Client.
Whenever I would try to create a VMFS-5 Datastore on a 4TB disk, it would come back with the following error:
A Specified parameter was not correct.
Vim.Host.DiskPartitionInfo.Spec
Call "HostStorageSystem.ComputeDiskPartitionInfo" for object "storageSystem" on ESXi "x.x.x.x" failed.
I found the following article that describes this ESXi 5.5 Installation Error here: https://communities.vmware.com/message/2294919#2294919
and here: https://communities.vmware.com/thread/457982
It seems that the problem is caused by any disk that has existing partitions on it.
It seems that the problem is that ESXi 5.5.0 is not properly wiping the disk (unable to delete the partitions).
More information can be found here: http://blog.the-it-blog.co.uk/2013/10/10/cant-add-a-storage-device-to-vmware-esxi-5-5/
If you manually delete all the partitions (logged in as root), then try to go back and create a VMFS-5 datastore, it should work and fix the problem.
The EASIEST solution to fixing the problem for me was to simply use the vSphere client and create the datastore using VMFS-3 first (which I did) and after a VMFS-3 datastore is created, just go back and delete the new VMFS-3 datastore and then go back and create a new VMFS-5 datastore and it should be able to wipe the disk and create the VMFS-5 datastore and it should work (which it did for me).
I'm not exactly sure what the problem/bug with ESXi5.5.0 (or vSphere Client 5.5.0b) is, or why ESXi 5.5.0 is unable to delete existing partitions, but by creating a 2TB VMFS-3 datastore on the new 4TB drive first (be sure to choose "Use all available partitions" under current disk layout), and then after that 2TB VMFS-3 datastore is created, then simply go back and delete that new 2TB datastore, and then after deleting that 2TB datastore and attempting to create a new 4TB (3.64TB) datastore using VMFS-5 seemed to fix all the problem(s), and I was able to create the 3.64TB VMFS-5 datastore.
I had to do this for each and every 4TB drive that was installed in the system. It seems to be a strange bug with ESXi 5.5.0 being unable to delete existing drive partition information.
It seems that there is a bug in ESXi 5.5.0 with the VMFS-5 datastore installer being unable to delete the existing partitions on a drive. Other users seem to have experienced the problem here, and here, and here, and here and here and here. It seems to be a problem with ESXi 5.5.0 being unable to delete the existing partition data on the drive.
It seems to be a reproduceable error/bug and I can reproduce this error/bug with every single 4TB drive that I add to the system.
Hopefully this solution will help future users who might have the same exact problem, or stumble upon this post via Google Search.