This was another Xenserver install without Local Storage on the drive after the install completed. I installed new drives to both an HP 1RU server and an HP Blade server. All the drives were 1T SATA and should have formatted identically.
The first server created c0d0 and c0d1 where the c0d1 was the remaining space of the 1Tbyte drive that was installed in an HP server. The /cciss/c0d1 was created with a Xenserver UUID and connecting to it was a simple(ish) process. I wrote up the process I used in another post titled Xenserver has no Local Storage.
So I expected that the other server would be the same issue, but it was different.
This server is a blade server and while the 1Tbyte drive is the same, the installer for some reason created the remaining space as an additional partition, /cciss/c0d0p3, but there was no UUID created.
Using vgs to confirm that the only volume group was the Dom(0) 4G partition:
VG #PV #LV #SN Attr VSize VFree
VG_XenStorage-50423669-52dc-b116-0aae-6cc1545a3013 1 1 0 wz–n- 3.99G 3.98G
Step 1. Create another volume group.
# vgcreate VG-LocalDisk /dev/cciss/c0d0p3
No physical volume label read from /dev/cciss/c0d0p3
Writing physical volume data to disk “/dev/cciss/c0d0p3”
Physical volume “/dev/cciss/c0d0p3” successfully created
Volume group “VG-LocalDisk” successfully created
Step 2. Create the storage repository (SR)
# xe sr-create content-type=”Local SR” host-uuid=bd73aed4-5583-4d3e-94b3-a271c2446d12 type=ext device-config-device=/dev/cciss/c0d0p3 shared=false name-label=”Local Storage”
Noting that I liked the shortcut of host-uuid=<tab key> to get the current host uuid without lookup / copy / paste !
Step 3. Done.
The drive should now be present in the XenCenter details for the server.
The only thing I noted here was an apparent loss of around 14G of storage in the 931G formated drive, less the 8G roughly for Xen Dom(0) should have netted me around 923G but it only reports 909G. I looked at it and decided it was not worth pursuing.
I am also guessing that this may not be an efficient method of using / allocating the disk space, but as with most things I do, it was expedient.