Page 1 of 6 123 ... LastLast
Results 1 to 10 of 58

Thread: Cannot reach login screen due to power failure and stupidity.

  1. #1

    Default Cannot reach login screen due to power failure and stupidity.

    Distribution: OpenSUSE 13.1

    Hello all.

    I'm sorry if this post is a bit long winded, but I've got myself into a bit of a fix.

    I perform Apper recommended updates fairly regularly and usually everything goes fine. On this occasion, after the download phase was over and apper was installing the updates, there was a power failure. My UPS kicked in and so I waited for Apper to complete the installation. Unfortunately there had been several power failures that day and the UPS battery must have got low. The UPS shutoff after a minute or so while the installations were in progress.

    After the power came back on, I restarted Apper and clicked the update button. I got a message box saying that some files related to libpulse0 12.1 needed to be removed. I clicked OK - but this led to the error message that "cannot remove system protected files". So I started YAST searched for libpulse0 files and updated them to the latest version libpulse0 20.1. Went back to Apper and tried again, but got the same message libpulse0 12.1 - needs to be removed - but cannot remove system protected files. This time I checked the error message detail. The detail was to the effect that the libpulse0 12.1 files did not exist. I went back to Yast and restored the libpulse0 files from v 20.1 back to v 12.1. After this the Apper removal worked fine, and the entire update that was interrupted by the power failure completed successfully.

    So far so good. Meanwhile, however, three more updates were available via Apper. I though I might as well install them. One of these updates was for bash and bash-docs. When I tried to update, got the message: bash, bash-docs and readline-docs (all version 12.1) need to be removed. Clicking OK gave the error: "Cannot remove system protected files" with detail to the effect that the files did not exist. I decided to try the same procedure as above. Started YAST and searched for bash. There was no update available. So I just refreshed bash and bash-docs (updated them back to themselves). Went back to Apper and tried to complete the update - same error.

    This is where I decided to get creative and stupid. I started YAST, went to bash and bash-docs - and _downgraded_ them to the previous version (8.1). Yast happily downgraded them. This time when I went back to Apper, the Apper application itself refused to start and YAST refused to start also. I rebooted (more stupidity) and was unable to get to any kind of login.

    As you may have gleaned, I'm relativley new to linux. I tend to only use the command line when there is absolutely no option so my facility with the command line is limited. Nevertheless if there is some set of instructions that can get me back to the login GUI, it would be nice.

    Thank you.

  2. #2
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,740
    Blog Entries
    3

    Default Re: Cannot reach login screen due to power failure and stupidity.

    I suggest that you open a terminal session;
    use the command "su -" to become root.
    Run the command:
    Code:
    # zypper up
    That might not solve your problem, but it is more likely to work than using Apper.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  3. #3
    Join Date
    Nov 2013
    Location
    Canadiana
    Posts
    461

    Default Re: Cannot reach login screen due to power failure and stupidity.

    On 10/26/2014 02:46 PM, emeskay wrote:
    > As you may have gleaned, I'm relativley new to linux. I tend to only use
    > the command line when there is absolutely no option so my facility with
    > the command line is limited. Nevertheless if there is some set of
    > instructions that can get me back to the login GUI, it would be nice.
    >
    > Thank you.


    You can still run YaST from the command line, you will need to use the
    keyboard to navigate though. This of course assumes you have a shell
    installed.


    --
    openSUSE Factory 64 bit
    KDE 4.14.0

  4. #4

    Default Re: Cannot reach login screen due to power failure and stupidity.

    Thanks for the suggestion.

    It does appear that there is no shell. I booted up in recovery mode and tried to log in as root with password. As soon as I enter the root password, I get the error:
    "No shell - no such file or directory"

    I also tried rescue mode using the bootable openSUSE 13.1 CD. The rescue mode allows you to log in as root to a "pseudo system" with no password in which you can mount your real system. Following some instructions I found elsewhere, I entered the following:

    mount /dev/sda6 /mnt
    mount /dev/sda7 /mnt/home
    mount -o bind /dev /mnt/dev
    mount -o bind /proc /mnt/proc
    mount -o bind /sys /mnt/sys
    cd /mnt
    chroot /mnt

    [sda6 is my root partition]
    [sda7 is my data partition]

    This gave an error to the effect that bash was not found.

    Does this mean that I have inadvertently uninstalled bash?
    What can I do now?

  5. #5
    Join Date
    Nov 2013
    Location
    Canadiana
    Posts
    461

    Default Re: Cannot reach login screen due to power failure and stupidity.

    On 10/26/2014 10:06 PM, emeskay wrote:
    >
    > Thanks for the suggestion.
    >
    > It does appear that there is no shell. I booted up in recovery mode and
    > tried to log in as root with password. As soon as I enter the root
    > password, I get the error:
    > "No shell - no such file or directory"
    >
    > I also tried rescue mode using the bootable openSUSE 13.1 CD. The rescue
    > mode allows you to log in as root to a "pseudo system" with no password
    > in which you can mount your real system. Following some instructions I
    > found elsewhere, I entered the following:
    >
    > mount /dev/sda6 /mnt
    > mount /dev/sda7 /mnt/home
    > mount -o bind /dev /mnt/dev
    > mount -o bind /proc /mnt/proc
    > mount -o bind /sys /mnt/sys
    > cd /mnt
    > chroot /mnt
    >
    > [sda6 is my root partition]
    > [sda7 is my data partition]
    >
    > This gave an error to the effect that bash was not found.
    >
    > Does this mean that I have inadvertently uninstalled bash?
    > What can I do now?
    >
    >


    I suspect what happened is for some reason during the "version change"
    bash was removed and the system freaked out. I would probably just back
    up important stuff and reinstall at this point but there may be a way to
    save the system (although I cant think of how).

    --
    openSUSE Factory 64 bit
    KDE 4.14.0

  6. #6
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,740
    Blog Entries
    3

    Default Re: Cannot reach login screen due to power failure and stupidity.

    Quote Originally Posted by alanbortu View Post
    I suspect what happened is for some reason during the "version change"
    bash was removed and the system freaked out. I would probably just back
    up important stuff and reinstall at this point but there may be a way to
    save the system (although I cant think of how).
    This might work.

    Boot the live rescue CD.
    Make sure that you have a network connection.
    Mount the root file system to "/mnt"
    Mount other file systems ("/home", perhaps "/boot")
    Code:
    # mount --bind /dev /mnt/dev  ### not sure if these bind mounts are needed
    # mount --bind /proc /mnt/proc
    # mount --bind /sys /mnt/sys
    And now run zypper on behalf of the mounted system:

    Code:
    # zypper -R /mnt up
    That uses the "zypper" from the rescue system. Hopefully it doesn't require bash from the mounted system.

    I don't know if it will work. I used this method back in June when a half-completed update left zypper broken.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  7. #7
    Join Date
    Nov 2013
    Location
    Kamloops, BC, Canada
    Posts
    3,974

    Default Re: Cannot reach login screen due to power failure and stupidity.

    Quote Originally Posted by emeskay View Post
    Thanks for the suggestion.

    It does appear that there is no shell. I booted up in recovery mode and tried to log in as root with password. As soon as I enter the root password, I get the error:
    "No shell - no such file or directory"

    I also tried rescue mode using the bootable openSUSE 13.1 CD. The rescue mode allows you to log in as root to a "pseudo system" with no password in which you can mount your real system. Following some instructions I found elsewhere, I entered the following:

    mount /dev/sda6 /mnt
    mount /dev/sda7 /mnt/home
    mount -o bind /dev /mnt/dev
    mount -o bind /proc /mnt/proc
    mount -o bind /sys /mnt/sys
    cd /mnt
    chroot /mnt

    [sda6 is my root partition]
    [sda7 is my data partition]

    This gave an error to the effect that bash was not found.

    Does this mean that I have inadvertently uninstalled bash?
    What can I do now?
    ... procedure should be (try):
    Code:
    mount /dev/sda6 /mnt
    mount --bind /dev /mnt/dev
    chroot /mnt
    mount -t proc proc /proc
    mount -t sysfs sysfs /sys
    ... then run zypper.
    -Gerry Makaro
    Fraser-Bell Info Tech
    Solving Tech Mysteries since the Olden Days!
    ~~
    If I helped you, consider clicking the Star at the bottom left of my post.

  8. #8
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,740
    Blog Entries
    3

    Default Re: Cannot reach login screen due to power failure and stupidity.

    Quote Originally Posted by Fraser_Bell View Post
    ... procedure should be (try):
    Code:
    mount /dev/sda6 /mnt
    mount --bind /dev /mnt/dev
    chroot /mnt
    mount -t proc proc /proc
    mount -t sysfs sysfs /sys
    ... then run zypper.
    I don't think that would work if the shell is missing. The "chroot" will try to start that shell and fail.

    Maybe:
    Code:
    # chroot /mnt /usr/bin/zsh
    would work with the "zsh" which is probably still there.

    My suggestion in the previous reply was to run "zypper" at the top level without doing a "chroot", but use the "-R" option for that zypper so that it acts on the mounted system.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  9. #9

    Default Re: Cannot reach login screen due to power failure and stupidity.

    Thanks nrickert and Fraser_Bell.

    I tried both your suggestions, but no luck.

    I can't chroot to /mnt - bash is not found.
    If I try running zypper from the rescue command line - zypper not found.

    I also located yast and yast2 in /mnt/sbin, changed to this directory and tried ./yast, but this gives a list of errors, ending with - "something is wrong with the yast installation".
    Located zypper in mnt/usr/bin, changed to this directory and tried running ./zypper -help, but get an error.

    I didn't make note of the exact error messages, but I could do it again and post them here if that would help.

    I could probably reinstall without any problems, but it would be a quite a pain as I would have to make a note of all the non-default software and reinstall all of them.
    Hopefully I wouldn't lose my settings as they they should be in my home partition - am I right?

    State Electricity Board morons. The forum emoticons are too gentle. Isn't there a "sharp kick on the nuts" icon?

  10. #10
    Join Date
    Feb 2009
    Location
    Spain
    Posts
    25,547

    Default Re: Cannot reach login screen due to power failure and stupidity.

    On 2014-10-27 13:46, emeskay wrote:
    >
    > Thanks nrickert and Fraser_Bell.
    >
    > I tried both your suggestions, but no luck.
    >
    > I can't chroot to /mnt - bash is not found.
    > If I try running zypper from the rescue command line - zypper not found.
    >
    > I also located yast and yast2 in /mnt/sbin, changed to this directory
    > and tried ./yast, but this gives a list of errors, ending with -
    > "something is wrong with the yast installation".
    > Located zypper in mnt/usr/bin, changed to this directory and tried
    > running ./zypper -help, but get an error.


    IF you don't have the BIG DVD installation DVD, download it now, for the
    same version as you have currently installed. Get it into a DVD or a USB
    stick.

    Boot it. Choose "upgrade installed system" when asked. Follow your nose.

    Ie: upgrade 13.1 to 13.1

    When finished, try booting. If it works, text mode or graphical mode
    does not matter, run YaST Online Update (not Apper, drat the thing), and
    let it finish. Alternatively, use "zypper patch" (not zypper up).

    Then reboot.

    On issues, report back here. I'll light a candle for you ;-) :-p

    --
    Cheers / Saludos,

    Carlos E. R.
    (from 13.1 x86_64 "Bottle" at Telcontar)

Page 1 of 6 123 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •