A couple of observations regarding installation

I’ve now installed Rockstor to two different machines. One an HP Proliant Microserver, the other a Packard Bell small form factor machine. In both instances, the install was fairly easy, though I did have a few problems with setting the disks up in the Microserver - its disks were already partitioned and the installer was a bit confusing regarding blanking the primary disk (I pulled the second disk prior to the install, since it had backup files that I didn’t want to lose).

Two things that could do with improvement - first, even though I selected a UK keyboard layout for both installs, both came through with a US keyboard layout. I had to manually edit /etc/vconsole.conf after install to correct the keyboard layout.

Second, why install plymouth? The machines will run headless most of the time, and even if they are running with a screen and keyboard, they don’t have any X server, so Plymouth seems to be a waste. I would much rather see any boot messages rather than a slow progress bar during boot. If nothing else, just after an install, the boot messages help isolate any problems. I’ve now uninstalled plymouth, but there seems little point in letting it install in the first place.



I confirm the Keyboard Issue.


@toothandnail Thanks for sharing your keyboard issue fix. As for the Plymouth install point I agree, however so that it might be considered specifically I’ve opened an issue in the rockstor-iso GitHub repo entitled “remove graphical boot.” The reason for it’s initial install is most likely down to that being the default for CentOS 7 which is our upstream.

For those wishing to remove plymouth / the graphical boot up animation from Rockstor just execute the following command in a Rockstor root console:-

yum remove plymouth

@henfri I see that you have opened a GitHub issue on the keyboard problem. That’s great thanks.
Linking here to help tie this thread to the issue.

1 Like