Scott I eventually just wiped it and started fresh but I learned a lot. At home I have been spending more time on the CLI with XenServer, no so much @ work as I only have 1 Raid array and normally don 't have to deal with CLI as much.
What I eventually did was nuked the raid, started fresh, changed it to a RAID 0 (for giggles), reinstalled XS. XS is installed to a 64 GB
@scottalanmiller it's my old server. It works fine, not the greatest lol but works. Battery back up is in place. Cache and flash 
you already know the answer.
Are there any RAID Cards that are more modern that will fit the old server? Non Dell Perc obviously.
Any suggestions as this one has my mind boggled.
@scottalanmiller Yes it is my Dell H200
@dbeato hey bro! I was already using it last year 
I actually like it. Pretty decent.
This is basically a fresh install. I installed XenServer from DVD to USB Flash Drive. I also have a freshly created Raid 1 volume (which is my intended target) and Dell disk backup drive.
xe sr-create content-type=user device-config:device=/dev/sda host-uuid=30b317b1-01bc-4eaa-9eb1-a43f16ebdbd8 name-label="SSDR1" shared=false type=ext
The SR operation cannot be performed because a device underlying the SR is in use by the host.
fdisk -l
Disk /dev/sda: 239.4 GB, 239444426752 bytes, 467664896 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
WARNING: fdisk GPT support is currently new, and therefore in an experimental phase. Use at your own discretion.
pvscan
PV /dev/sda VG XSLocalEXT-4958af2e-9aa2-3032-c814-5e5c6e8c1ffd lvm2 [222.99 GiB / 0 free]
PV /dev/sdc VG XSLocalEXT-4958af2e-9aa2-3032-c814-5e5c6e8c1ffd lvm2 [465.75 GiB / 242.76 GiB free]
Total: 2 [688.73 GiB] / in use: 2 [688.73 GiB] / in no VG: 0 [0 ]
UPDATE
Nuked host, rebuilt it from scratch and got around the problem. However I'm just interested in figuring out how to do the low level drive management from the CLI. I was able to get through it on my own by the seat of my pants. Just want some clarity.
Not that I like Windows way better (sometimes it's good sometimes it's bad) but I swear, someone needs to take a look at the way these systems are designed!
I did try to just install Xen Tools like I would normally do the windows version, by right clicking on the vm and Install the tools. But when that didn't do anything on screen, that's what raised a flag like oh shit I need to do something CLI.
Had it been something on screen to tell me or better guide me it would have been a smoother experience. Hence me saying, a UX Engineer needs to be around!
@dustinb3403 Please school me brother as Linux isn't my OS of fun but I tend to prefer it over windows!
I installed the vm, putty'd in because I thought that was the right thing! If I did it from the Xen Console I was greeted with the menu for the app and how to navigate to the IP's for it.
@dustinb3403 SSH into it via Putty.
I swear just one decent UX engineer! Just one!
Dustin one day I strive to be proficient like you and SAM If I see ya beer's on me bro!
What they say now is!
Installing XenServer Tools on Linux VMs
Select the VM in the Resources pane, right-click, and then click Install XenServer Tools on the shortcut menu. Alternatively, on the VM menu, click Install XenServer Tools.
Click Install XenServer Tools on the message dialog to go to the VM's console.
As the root user, mount the image into the VM:
mount -o ro,exec /dev/disk/by-label/XenServer\x20Tools /mntNote: If mounting the image fails, you can locate the image by running the command
blkid -t LABEL="XenServer Tools"Execute the installation script as the root user:
/mnt/Linux/install.shUnmount the image from the guest by running the command:
umount /mnt If the kernel has been upgraded, or the VM was upgraded from a previous version, reboot the VM now.
Note that CD-ROM drives and ISOs attached to Linux VMs appear as /dev/xvdd(or /dev/sdd in Ubuntu 10.10 and later), rather than /dev/cdrom. This is because they are not true CD-ROM devices, but normal devices. When the CD is ejected by XenCenter, it hot-unplugs the device from the VM and the device disappears. This is different from Windows VMs, where the CD remains in the VM in an empty state
Ok so I found out the installation instructions changed for Linux after a few releases!
Installing XenServer Tools on Linux VMs
Select the VM in the Resources pane, right-click, and then click Install XenServer Tools on the shortcut menu. Alternatively, on the VM menu, click Install XenServer Tools.
Click Install XenServer Tools on the message dialog to go to the VM's console.
As the root user, mount the image into the VM:
mount /dev/xvdd /mnt
Execute the installation script as the root user:
/mnt/Linux/install.sh
If the kernel has been upgraded, or the VM was upgraded from a previous version, reboot the VM now.
Note that CD-ROM drives and ISOs attached to Linux VMs appear as /dev/xvdd rather than /dev/cdrom. This is because they are not true CD-ROM devices, but normal devices. When the CD is ejected by XenCenter, it hot-unplugs the device from the VM and the device disappears. This is different from Windows VMs, where the CD remains in the VM in an empty state
For the love of GOD if I wasn't happy with finding an answer that would have turned me off! Like it isn't helpful. Maybe I'm wrong but a UX engineer would be like, ummmm FIX THAT!
mount -o ro,exec /dev/disk/by-label/XenServer\x20Tools /mnt
It fails when we point to the "DISK"
That is the exact same error I got!
So let me get this straight, I could have actually piped another command into that?
@scottalanmiller said in XenTools installation error for Linux:
mount /dev/cdrom /mnt/
mount /dev/cdrom /mnt/
So SCOTT am I wrong in reading this? Im telling the system to mount a dev called cdrom but turn around and "RE" mount it? WTF and WTH?!?!?!