Hello teamsters !!

Update today got shot off at parcel of bash.

Bash ist now de-formed.

After reboot (because Solus Linux was crashed) I cannot
get through to gdm. Linux ist halting with black screen.

How can I repair in emergency mode and reinstall bash, when bash ist broken and wiped off ?

For hints thank you !!
I want to avoid total new installation.

  • DirtyAngel and pomon replied to this.

  • You need to chroot the broken system. Above, @alfisya has already provided a page on how to do it. It looks like you won't be able to handle it, so do as @ReillyBrogan wrote and transfer the data from the old system to the new Solus-4.4. However, if you want to go further, you need to start with lsblk -p describing which system is old and which is new.

    PS. My way to chroot in Solus on an unencrypted drive

    Have you tried these helps here ? If not please try to follow these instructions.

      alfisya

      How could I do this here : ...

      sudo eopkg rebuild-db
      sudo eopkg up
      sudo eopkg check | grep Broken | awk '{print $4}' | xargs
      sudo eopkg it --reinstall

      ... when bash has been wiped at Update, after this Linux crashed ?

        What do you mean by "bash is deformed" ?
        Did you already try to boot rescue using the instruction? Also the instruction is using live environment from usb stick, so your system condition shouldn't matter much ( i think).

        Yes, please actually follow the instructions on the boot rescue documentation.

        I have installed and updated Solus to 4.4 on /dev/sda.
        Want to repair encrypted Solus on /dev/sdb.
        After password of encrypted /dev/sdb is typed.
        How do I type command for /dev/sdb ?
        Is this correct ? :

        sudo eopkg rebuild-db /dev/sdb
        ?

          DirtyAngel
          If there is a black screen when the system starts and we don't know where it stops. The next time it starts up we press, in my case space or F7, you have to check at your place which button. When the boot menu appears

          press e, systemd.show_status=false change to true and enter.

          We will see the services uploaded.

            DirtyAngel Honestly you should just copy off your data to another drive and then reinstall completely. It doesn't sound like you understand the boot recovery instructions and none of us are really interested in walking someone through them step by step.

                ReillyBrogan It doesn't sound like you understand the boot recovery instructions

                When I tried to follow those instructions (the ones involving chroot) I couldn't get anywhere with them. I mentioned that in the Solus Off-topic room at the time, but I don't know if anything was done about it. I didn't enter a bug report because I thought it might be my error, and I wanted to wait and see if anyone else had the same problems.

                Regardless, your idea is probably best. I ended up doing a reinstallation at that time, and it provided an opportunity to improve a number of things in my system. Improvements I wish I'd thought of the first time.

                    WetGeek When I tried to follow those instructions (the ones involving chroot) I couldn't get anywhere with them.

                    it's one of those 'have to do 3-4' times ( I have) til the context sinks in. I understand it now. The tutorial is not intuitive. There are two parts that don't apply to most people (lvm part and part that seems to deviate and go out of chroot then comes back--the ping part? I forget) that just show up and appear as normal steps and sequential steps in the narrative.

                    I thinks it's a sound tutorial, I get it now. I have to remember to skip some parts. They could make that clearer._..but I know how to chroot with success now.

                    long story short if you follow it from beginning to end, I wouldn't exepct success the first time. you have to know what to throw out.

                    That's one of those things I always wanted to take a crack at re-writing. edit/sp

                        brent you have to know what to throw out

                        I thought I did know that. My issue was no mount points available for the mount commands. I went back three or four times and couldn't get it to work with these new instructions, and finally decided a reinstallation was likely to be quicker. And I was able to make it a improved installation.

                        Ironically, I was able to easily chroot following the earlier instructions.

                          I have installed Solus 4.4 on different hard-disk.
                          Now I want to "open" old installation to repair it.
                          Old installation is encrypted LUKS hard-disk. Do I have to type password, when I plug-in
                          the old installation into new installation ? I am asking this, because there is no password-query for
                          LUKS-encryption (when I click on old hard-disk with file-manager nautilus) ... ?!
                          Or can I simply start to repair with Solus 4.4 the old installation after plug-in ?
                          Now I am asking, should I type this :

                          sudo eopkg rebuild-db /dev/sdb
                          ?

                          or do I need number of partition like sdb1 or sdb2 ?

                          You need to chroot the broken system. Above, @alfisya has already provided a page on how to do it. It looks like you won't be able to handle it, so do as @ReillyBrogan wrote and transfer the data from the old system to the new Solus-4.4. However, if you want to go further, you need to start with lsblk -p describing which system is old and which is new.

                          PS. My way to chroot in Solus on an unencrypted drive