It seems te problem ist the harddrive naming under Xen. The harddrives are named /dev/xvd* instead of /dev/sd*
Problem is, I can not override this, because the linux kernel recognises that it is running under xen hypervisor an automatic uses the paravirt drivers for the disc. Even if I configure the vm to show sata drives. So this results in the devices called /dev/xvd*
With KVM there is an easy workaround.
Create a dummy virtual disk (1 GB for example). Add it to the VM definition as SATA disk sda. All other disks remain virtio.
Then install rockstor to the virtio disk you want. The installation will start without any problems, because there is the dummy disk as sda.
After instlltion is done, you can remove the dummy sata disk from the VM definition.
With xen the case is somewhat different. Linux guests with newer kernels recognize, that they are starting under Xen hypervisor and do automatically load the paravirtual drivers. No matter what is configured in the VM definition. So every virtual disk will become /dev/xvd*. So the installtion will not work out of the box.
Same here (“Specified non existant disk sda in ignore disk command”). Has anyone managed to install Rockstor as a XenServer VM on a non VT-d system (ie no passthrough workaround)? Tried pressing tab at the splash screen and removing the ks=hd… just get a white underscore in the top left as if it can’t find any boot device.
The most relevant forum topic seems to be this, but it’s about a hardware RAID device, and I’m just trying to make it install with the onboard SATA, so not sure what the references to “magic kernel options” would be in my case. I tried adding “hpsa.hpsa_allow_any=1” to the end of the Rescue command line, but upon pressing “Next” it says “You don’t have any Linux partitions”, so that can’t be right.
I’ll have a crack at installing vanilla CentOS next, but suggestions welcome.
Cracked it. I pressed tab at the “Install Rockstor in basic graphics mode” stage, then removed the ks= part of the string per Suman’s suggestion. Then it proceeded to ask whether I’d like to install using VNC or text mode. Launched VNC and…
I tried installing using the GUI. But I ended up with no luck.
If you use auto partitioning, this results in LVM instead of BTRFS for the root partition. In the result rockstor complains about the root partition not being BTRFS and does not work.
So I tried to partition the disk by hand and using BTRFS instread of LVM. But also no luck.
After installation completed, rockstor complained about a not parsable string 17.5
I realized that 17.5 was exakt the size of my root partition.
So I tried to make the size an integer value of gigabytes. In ths case 17 GB. This worked. After installation rockstor did not complain about this and worked so far.
But after adding my data disks, it complained again about a non parsable value of 2.74 (or something like this). And this was the exact size of my data disks in TB.
So, after all, I ended up in an not usable installation. This was the point, where I temporarely passend thru my SATA controller to the VM with one hard drive connected. This leads to an existing /dev/sda. The normal installation works and I installed to /dev/xvda. After installation the passed thru controller can be removed and rockstor is up and running.
Yes I had no luck with GUI (via VNC) either. Trying text install instead.
The problem is caused by the kickstart file on the root of the Rockstor ISO: ks.conf. Line 13 (unlucky for some) is:
I’ve tried commenting this out or replacing with xvda, and then saving into the ISO (using WinISO), but then the installer says:
dracut-initqueue: Warning: failed to fetch kickstart from hd:LABEL=Rockstor\x203\x20x86_64:/ks.cfg
and eventually boots to a command prompt (no web UI). I’m guessing that my changing the ISO has broken some checksum, so it no longer sees this as a valid ISO image, and “fails to fetch”.
I’ve just used the text installer instead of VNC, and it seems to have completed the install okay, and I’m now in the webui. I’m concerned that I’m missing something crucial in the kickstart file that wasn’t loaded. This is below for reference. Is there any way to post-instate these kickstart options? Eg "services --enabled=“chronyd”? I have prefixed the commented lines with a ’ because hashes are made into titles in this forum editor:
’# System authorization information
auth --enableshadow --passalgo=sha512
‘# Use CDROM installation media
’# Run the Setup Agent on first boot
’#this may not be necessary. look at rockstor vm’s anaconda and decide.
‘# probably not necessary. this can be upto the user to decide.
’# Keyboard layouts
keyboard --vckeymap=us --xlayouts=‘us’
'# System language
‘# Network information
’# probably not necessary. users can configure interactively. Or should we leave dhcp as the default?
network --bootproto=dhcp --onboot=yes --hostname=Rockstor
‘# Root password
’#rootpw --iscrypted $6$F3v.RAjU…pGqpAf$ItkRJpJdKjZExy0rMG/ZDotQdAn65LO59iG/CPF/ql9MFHiMl1RzUW0aQXRHO94IgdBMBUrJ7mzJBv2rx1zPY1
’# System services
’# System timezone
’#timezone America/Los_Angeles --isUtc
’# X Window System configuration information
’# System bootloader configuration
bootloader --location=mbr --boot-drive=sda
’# Partition clearing information
clearpart --none --initlabel
No it will not, unfortunately. We should probably create a short installation video for this scenario. You’ll need to (1) choose BTRFS for the partitioning layout (2) Select Rockstor environment in the package selection (3) make sure network connection is up.
Just a note that might help here. To reproduce what the ‘appliance’ auto install options do partition wise there is a picture of them in the docs inside the Reinstalling Rockstor howto.
And from parted we have:-
Model: ATA TS32GMSA370 (scsi)
Disk /dev/sdc: 32.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 1049kB 525MB 524MB primary ext4 boot
2 525MB 3728MB 3202MB primary linux-swap(v1)
3 3728MB 32.0GB 28.3GB primary btrfs
Might be relevant to those doing advanced DIY partitioning, either out of necessity or curiosity.
My understanding is that the rockstor_rockstor pool name is important but I think there are plans to alter this requirement.
Just to update the situation on installing Rockstor as a XenServer VM. “ignoredisk --only-use=sda” is still in ks.cfg on the latest ISO, and perhaps this won’t be changed. While removing would ease installing on XenServer, some might say it’s not worth the cost of giving users a list of disks from which to choose where to install Rockstor, which might confuse.
Perhaps better to find a workaround for installing Rockstor in Xen. Removing ks.cfg from boot options won’t work because both the GUI & text installer won’t continue without something in the Software Selection section. Hence continuing down the path of installing with ks.cfg specified, I’ve got past the “Specified nonexistent disk sda in ignoredisk command” error by:
Changing the following lines in ks.cfg:
bootloader --location=mbr --boot-drive=xvda
Saving the new ks.cfg to the ISO using ISO editor software,
Booting off the ISO, choosing Troubleshooting, pressing tab key on the Install Rockstor in Basic Graphics Mode and changing boot options to:
vmlinuz initrd=initrd.img inst.stage2=cdrom xdriver=vesa nomodeset quiet ip=dhcp ks=cdrom:/ks.cfg
Choosing option 1. VNC.
I then run through the GUI install wizard as normal, but the progress bar gets about a third of the way and fails:
Are you sure about this? I just tried. You can click on software selection and you’ll see Rockstor listed under base environment. In fact, that’s the only one listed. Can you try again using vanilla Rockstor-3.8-9.02 ISO?
File System: swap
File System: btrfs
Size: remaining (17gb in my case as I had a 20GB disk)
File System: btrfs
Size: remaining (17gb in my case as I had a 20GB disk)
So to summarise installing in a Xen VM:
Boot off the vanilla, original Rockstor ISO.
Choose Troubleshooting, press tab key on Install Rockstor in Basic Graphics Mode and change boot string to: vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Rockstor\x203\x20x86_64 xdriver=vesa nomodeset quiet ip=dhcp
in other words, simply remove this from the end of the string: ks=hd:LABEL=Rockstor\x203\x20x86_64:/ks.cfg
Either choose VNC or Text interface when prompted. Fill in the options as required, changing the disk partitioning as above.
I think this is a simple enough workaround to warrant closing this issue about removing references to sda from ks.cfg.