My OS drive (USB thumb drive) was reporting errors so I’m working on getting a new installation up and running. I have a few questions regarding this procedure…
First, after I enable stable updates, is there a good way I can trigger the update via SSH so that I may monitor the process? After my install last night, I started the update process from the GUI. After about 90 minutes, it was still updating. I wasn’t sure if it was hung or not, so I SSH’ed in and issued a “sudo reboot”. My thought was that whatever was happening, it should shut down gracefully. What actually happened is that ‘yum’ was left in a broken state. I “fixed” it manually with yum-utils, but I’m thinking that I should just reinstall again to avoid any potential issues. From looking on the forums, I’m leaning towards the appropriate command (running it via ‘screen’ in case I get disconnected) being something along the lines of
yum update && yum upgrade && yum update rockstor
Second, I think I also read on the forums that when a config is loaded the appropriate rock-ons will be installed. Is this the preferred method of reinstalling the rock-ons? I think I had an old Plex installation active as I think there was a bug that kept it from being easily updated. I’m assuming that the latest docker will be used to reinstall things and not and old one. Is that an accurate assumption?
Lastly, one of my installations failed because the OS drive’s file system was LVM. Is there a way to modify the installer so that LVM cannot be used at all? I briefly considered doing a manual partitioning of the drive, but backed out and did an automatic partitioning instead. However, LVM was used and the GUI through an error when I tried to set the hostname and create the initial user. I haven’t verified that these steps will reproduce the issue, so I haven’t opened a ticket for it. I don’t want to make anyone go off chasing a ghost.