XenServer Local SR: Need another pair of eyes

Kelly

/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

DustinB3403

This system only has two drives in it?

travisdh1

@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?

momurda

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"

Kelly

@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

Kelly

@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

@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.

Kelly

@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.

travisdh1

@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.

momurda

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.

Kelly

@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?

travisdh1

@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.

Kelly

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.

Kelly

And the same command worked on the second host in the pool as well (different uuid).

momurda

curious what the output of 'xe sr-list' shows for content-type on your new SRs since you didnt specify when creating.

Kelly

@momurda said in XenServer Local SR: Need another pair of eyes:

curious what the output of 'xe sr-list' shows for content-type on your new SRs since you didnt specify when creating.

Hmm...

content-type ( RO):

momurda

Hmm indeed. can you use the new SRs? Boot a vm on them, add a disk from one to an existing vm?

Kelly

@momurda said in XenServer Local SR: Need another pair of eyes:

Hmm indeed. can you use the new SRs? Boot a vm on them, add a disk from one to an existing vm?

The pbd was marked as read-only. I'm going to try adding in content-type to my above command.

momurda

I am not clear about this, but i think the results of xe sr-list
0_1465596516689_upload-29cacbab-e373-4f34-945e-86e9e38f0396
the RO/RW parts refer to the parameters themselves, not necessarily the SR.
For instance, you cant change uuid of an sr so it is RO.
You can change the name-label, name-description parameters, so they are RW

Kelly

@momurda said in XenServer Local SR: Need another pair of eyes:

I am not clear about this, but i think the results of xe sr-list

the RO/RW parts refer to the parameters themselves, not necessarily the SR.
For instance, you cant change uuid of an sr so it is RO.
You can change the name-label, name-description parameters, so they are RW

Hmm, perhaps it wasn't read only, but I couldn't install to it. I removed the SR and PBD and then redid it with the content-type defined and I'm now able to install to it.

Final command:

xe sr-create name-label="VM Storage" type=lvm content-type=user host-uuid=uuid device-config:device=/dev/sda