XenServer Local SR: Need another pair of eyes
- 
 @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/sdaI 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). 
- 
 curious what the output of 'xe sr-list' shows for content-type on your new SRs since you didnt specify when creating. 
- 
 @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):
- 
 Hmm indeed. can you use the new SRs? Boot a vm on them, add a disk from one to an existing vm? 
- 
 @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. 
- 
 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
- 
 @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 RWHmm, 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
- 
 Nice. Also Ive only been using XS for a few months, so i could be wrong about the xe sr-list command output 
- 
 @Kelly It doesn't help that most of us have to use the xe sr-create command once every 4-5 years. 

