So I installed the latest updates from 3/26 and installed the newest version of Citrix Workspace 2103 this morning. Went to reboot and I'm greeted with a screen that shows [!!] Failed to execute /sbin/init So I went to boot rescue, and ran into more problems. Rather than put the whole log in the forum, it's on pastebin. I'm met with a few different issues, first /target: unknown filesystem type LVM2_member and the second Could not find platform independent libraries <prefix>
Could not find platform dependent libraries <exec_prefix>
Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
ImportError: No module named site
I've done some Googling and found some different issues, nothing specific to Solus or that has provided any assistance so far. I was able to chroot /target but my luck seems to stop there. So I thought I'd ask here to see if there's any way to salvage this mess before I just nuke and pave.

    Brucehankins
    https://getsol.us/articles/troubleshooting/boot-rescue/en/
    I think you know this one well.

    I've had the LVM error before in this (boot rescue)circumstance and google did take me to a terminal command that made the root lvm accessible (Sorry I really should save my fixes. Or was it a permission thing or a flag thing in gparted? I don't know). I've gotten past that obstacle somehow.

    I wonder if your flatpak (guessing) update python package conflicted with one in Solus? Never saw that python warning before.
    Hope someone gives you more value then this. I hate nuke and pave.

        brent not sure, I feel like for some reason it was related to the Citrix 2103 install, but unsure.

        I have Citrix 2103 running on another machine using Plasma and Lubuntu 20.10

          I'm curious. Since it's not a flatpak or snap, then you compiled citrix yourself? How does an update work for a compiled package? Uninstall old one then install the new one?

          no tty?

            brent no tty, and no compiling. It installs via script from a .targz file. I was just upgrading from 2010 or 2009, whatever the previous version was, which was working fine before.

                Brucehankins
                for workspace app it show the new version is the perplexingly-named '2103' and in its linux subsets the tarballs etc all are called '2012' as you said.
                This is their 'changelog' for the new 2012: https://docs.citrix.com/en-us/linux-virtual-delivery-agent/current-release/whats-new.html
                --read it twice, I see no clues but maybe you might.

                I don't know why this thing mangled your solus boot. if you could get past the stage you are stuck at in the Live ISO then you could fix packages. I know you know this. Been on this end more than twice. Frustrating.

                  a year later

                  hello, the simplest and safest solution is to use a live with solus os, and within the live of solus os look for the sbin folder

                  Already inside it look for the init file, copy it and in the file manager look for the partition of your solus os, not the live one, look for the one you have installed on your pc (hard disk), already inside the root partition of your solus looks for the sbin folder and pastes the file you copied into it, if it doesn't let you paste it, open the terminal and execute sudo nautilus and enter your password, now paste it according to the above.

                  Step 2: now go back to the root folder of your live solus os and enter the usr folder in which inside you will notice a folder called lib which you have to copy everything and move it to the usr folder located in the root folder of your pc where your solus os (hard disk) is installed, if it asks you to overwrite accept everything.

                  Everything would be repaired, just restart your system.

                  Note: this error occurs because during the installation or configuration of a program the init of the system is changed or the lib folder of usr is deleted, with this it is solved, if you want I will create an explanatory video for you though it's just that.

                    Brandon-pc Hi there! Please don't copy&paste the same reply into every old thread about this topic. I'll leave this comment as is, but won't admit the others (in even older threads, 2 years at least). In general please try not to "necro" old topics like this. The user most likely has solved their problem by now. If new problems occur, a new thread should be created.