Building Out XenServer 6.5 with USB Boot and Software RAID 10
-
@Romo said:
@DustinB3403 I am actually trying to do exactly that just right now on my test setup. It thought that with this command:
xe sr-create type=ext device-config:device=/dev/md10 shared=false host-uuid:fba59a9c7e6db5a2d21e40343b415cfd name-label="Array storage"It would get added as local storage to xencenter, but I am getting this error :
The SR operation cannot be performed because a device underlying the SR is in use by the host.Don't really know why, I haven't used xenserver before. Any ideas @scottalanmiller
The reason your target device is in use is you have it mounted. Try dismounting the array and try again.
-
Romo when you run
xe sr-list
What's listed?
-
The array is now properly seen as storage in xencenter, I did have to unmount it first @DustinB3403
-
What process did you run to unmount it.
-
umount /dev/md10
-
So you ran
umount /dev/md10
and then
xe sr-create type=ext device-config:device=/dev/md10 shared=false host-uuid:fba59a9c7e6db5a2d21e40343b415cfd name-label="Array storage"
Correct?
-
Yes, @DustinB3403 .
This is xe sr-list output with the array added as storage
-
@DustinB3403 sorry I did add content-type=user to the sr-create command. The final command was
xe sr-create type=ext device-config:device=/dev/md10 shared=false host-uuid:fba59a9c-7e6db5a2-d21e4034-3b415cfd content-type=user name-label="Array storage"
-
OK so after saving the RAID Array (in my wall of text) he then would have to run
umount /dev/raid10
and then
xe sr-create type=ext device-config:device=/dev/raid10 shared=false host-uuid:<HOST-UUID> content-type=user name-label="Array storage"
-
I'm guessing the system auto-mounted the array when you built it, and can now see it in XenCenter.
Correct?
-
It is automounting since we added it to our fstab
-
After adding the array as storage xenserver , the output of df -Th changes to this
-
I removed the /dev/md10 entry from fstab so it doesn't automount and causes conflict with xenserver handling storage
-
Xencenter after reboots properly automounts our new array
-
We need to get the UUID out of the proposed script, that much I know won't work.
-
@Romo said:
I removed the /dev/md10 entry from fstab so it doesn't automount and causes conflict with xenserver handling storage
Ah, good catch. I'm updating the OP with a finalized script. Please review.
-
I got the uuid using this:
madadm --detail /dev/md10 | grep UUID
-
We don't need to install mdadm, its there already
-
-
@Romo said:
I got the uuid using this:
madadm --detail /dev/md10 | grep UUID
What is the raw output of that command? Did you need to clean it up? I want this scripted, not manual, if possible.