XenServer installation SR issue
-
It wouldn't hurt to just turn off RAID, bypass everything, stick in just one drive and try to install to it. Use your newest drive.
If you must RAID, do something simpler and just mirror two newest drives.
It would seem on the surface that XS simply can't configure the way it needs, which means perhaps hardware incompatibility?
If it were me, I feel I have to rule out the RAID and RAID hardware and drives entirely. If a drive works by itself, then try a simple RAID mirror. If that works, try the 10 again with 4 drives. I could be one of the physical drives just isn't matching all the rest in some sense.
Like you said, grasping at straws.
-
Have you tried it without enabling the thin provisioning?
-
@fuznutz04 said in XenServer installation SR issue:
My thought was that something wasn't being properly cleared during a quick initialization.
Recreating RAID blows absolutely everything away. Anything "left over" would cause total data corruption.
-
So next steps this weekend is:
Try the install again on a disk by itself. If that works, Then try it on another set of disks in a Raid 1 array. Then go from there.
-
@Danp said in XenServer installation SR issue:
Have you tried it without enabling the thin provisioning?
No, I haven't. Will try that also.
-
@fuznutz04 said in XenServer installation SR issue:
@Danp said in XenServer installation SR issue:
Have you tried it without enabling the thin provisioning?
No, I haven't. Will try that also.
That removes the EXT3 layer.
-
Finally, a win this week. Tried many things including just using one disk for the install. Still no dice. Then as suggested I tried an install NOT using thin provisioning. It worked the first time. So why?
-
@fuznutz04 said in XenServer installation SR issue:
Finally, a win this week. Tried many things including just using one disk for the install. Still no dice. Then as suggested I tried an install NOT using thin provisioning. It worked the first time. So why?
That's very strange indeed. So you are using thick (LVM) on the RAID array now?
-
My current guess, but I don't see enough lvs output, is that LVM is creating only one LV and there is nowhere for the ext3 to go.
-
@fuznutz04 You could try to change from LVM to EXT --
http://xmodulo.com/how-to-change-xenservers-local-storage.html
-
@scottalanmiller said in XenServer installation SR issue:
@fuznutz04 said in XenServer installation SR issue:
Finally, a win this week. Tried many things including just using one disk for the install. Still no dice. Then as suggested I tried an install NOT using thin provisioning. It worked the first time. So why?
That's very strange indeed. So you are using thick (LVM) on the RAID array now?
Yes, I chose the default install option, without checking the Thin Provisioning box.
-
@fuznutz04 said in XenServer installation SR issue:
@scottalanmiller said in XenServer installation SR issue:
@fuznutz04 said in XenServer installation SR issue:
Finally, a win this week. Tried many things including just using one disk for the install. Still no dice. Then as suggested I tried an install NOT using thin provisioning. It worked the first time. So why?
That's very strange indeed. So you are using thick (LVM) on the RAID array now?
Yes, I chose the default install option, without checking the Thin Provisioning box.
My only guess at this point is an LVing error.
-
@scottalanmiller
I'm going to make another raid array, separate from the one that XS is currently installed on, and then see if I can create an SR on that new array. Lets see if that works.What are the main disadvantages to NOT having thin provisioning for XS?
-
@fuznutz04 said in XenServer installation SR issue:
What are the main disadvantages to NOT having thin provisioning for XS?
Thin provisioning just gives you more flexibility with making big datastores and not having to worry about designing your storage before it is needed to the same degree.
-
So I was able to make another array, and was also able to make an SR on that array. It's still strange that I'm not able to use thin provisioning by default on install, but for now, it's working.
