We got all the way down to plugging in the PBD. At that point it fails with the aforementioned error.
So with this being the end result, we searched through the rest of the support forums and found a couple more articles and possible workarounds... and no matter what scan we launched on the lvm we just couldn't plug it in.

One of the questions we have is, why does the name of the VG change. Meaning, it is now being called XSLocalEXT-<UUID> when it is normally addressed VG_XenStorage-<UUID>. This questions comes to mind because the SR_BACKEND_FAILURE_47 error also states the following: =no such volume group: VG_XenStorage-<UUID> when my SR-UUID reads something like this "XSLocalEXT-<UUID>"..?

With some suggestions from folks in the Citrix community we also attempted to reverse the introduction process and unplug, forget, and destroy the PBD so we could recreate the PBD and plug it in. All still with NO JOY!

By no means am I linux/xenserver expert and I know that there should be some way to get to that data so it can be accessed.