XenServer Local SR: Need another pair of eyes
-
I'm trying to create some new local SRs in XS7 and I'm not getting what I am expecting. Here is my command:
xe sr-create host-uuid=[uuid from xe host-list] content-type=user device-config:device=/dev/sda name-label=”VM Storage" shared=false type=ext
When I run that I just get a
>
and no other response. I end up having to hit Ctrl+C to break out. -
Are you trying to use that single sda device or trying to create the SR out of an array?
-
It is a single logical disk built on a hardware RAID 10 array.
-
There are no partitions configured on it either.
-
But it shouldn't be /dev/sda that would (if your running from USB) be the USB drive.
-
@DustinB3403 said in XenServer Local SR: Need another pair of eyes:
But it shouldn't be /dev/sda that would (if your running from USB) be the USB drive.
A possibility for sure. What does the out put of
ls -l /dev/sd*
show?
-
/dev/sda is the right partition according to fdisk -l
Here is the output of the ls -l
brw-rw---- 1 root disk 8, 0 Jun 7 09:55 /dev/sda brw-rw---- 1 root disk 8, 16 Jun 6 16:02 /dev/sdb brw-rw---- 1 root disk 8, 17 Jun 6 16:02 /dev/sdb1 brw-rw---- 1 root disk 8, 18 Jun 6 16:02 /dev/sdb2 brw-rw---- 1 root disk 8, 19 Jun 6 16:02 /dev/sdb3 brw-rw---- 1 root disk 8, 21 Jun 6 16:02 /dev/sdb5 brw-rw---- 1 root disk 8, 22 Jun 6 16:02 /dev/sdb6
-
This system only has two drives in it?
-
@Kelly Ok, so sdb is obviously the system drive. Is the RAID controller a Dell/LSI? Might need to get the LSI megaraid-sas or one of their other utilities installed to get us the actual array status. For now, what does
fdisk -l /dev/sda
show?
-
what does 'pvdisplay' output?
or 'vgdisplay'xe sr-create host-uuid=uuidofhost shared=false type=lvm content-type=user device-config:device=/dev/sda1 name-label="blah"
-
@travisdh1 said in XenServer Local SR: Need another pair of eyes:
@Kelly Ok, so sdb is obviously the system drive. Is the RAID controller a Dell/LSI? Might need to get the LSI megaraid-sas or one of their other utilities installed to get us the actual array status. For now, what does
fdisk -l /dev/sda
show?
Disk /dev/sda: 24001.4 GB, 24001350991872 bytes, 46877638656 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
-
@momurda said in XenServer Local SR: Need another pair of eyes:
what does 'pvdisplay' output?
or 'vgdisplay'xe sr-create host-uuid=uuidofhost shared=false type=lvm content-type=user device-config:device=/dev/sda1 name-label="blah"
No return on either pvdisplay or vgdisplay.
-
-
@travisdh1 said in XenServer Local SR: Need another pair of eyes:
@Kelly So far the drive looks good. This seems silly, be it could be that you'll need to create a partition on the drive for things to work. (Don't ask me why, a raw drive vs a partition shouldn't make much difference.) I'd go with an LVM partition type and use type=lvm like @momurda suggested.
Same response. I just have a > below the command.
-
@Kelly Well, bother.
xe sr-create host-uuid=uuidofhost shared=false type=lvm content-type=user device-config:device=/dev/sda1 name-label="blah"
Should work. You've stumped me for the day at least.
-
Thats weird. pvdisplay/vgdisplay should give you a list of physical devices (pvdisplay) and vgdisplay should show you the logical volumes of your physical disks.
-
@travisdh1 said in XenServer Local SR: Need another pair of eyes:
@Kelly Well, bother.
xe sr-create host-uuid=uuidofhost shared=false type=lvm content-type=user device-config:device=/dev/sda1 name-label="blah"
Should work. You've stumped me for the day at least.
Does the order of the elements after sr-create matter?
-
@Kelly said in XenServer Local SR: Need another pair of eyes:
@travisdh1 said in XenServer Local SR: Need another pair of eyes:
@Kelly Well, bother.
xe sr-create host-uuid=uuidofhost shared=false type=lvm content-type=user device-config:device=/dev/sda1 name-label="blah"
Should work. You've stumped me for the day at least.
Does the order of the elements after sr-create matter?
It shouldn't, but xe can be a bit of an oddball at times. Could be as simple as a space where one shouldn't be.
-
Ok, so I decided to step through xe sr-create until it stopped complaining. It created the SR with just this:
xe sr-create name-label="VM Storage" type=lvm host-uuid=uuid device-config:device=/dev/sda
I only entered a parameter when it specifically asked for it. I'm wondering if there is an undocumented change in one of the parameters.
-
And the same command worked on the second host in the pool as well (different uuid).