Page 1 of 2 12 LastLast
Results 1 to 10 of 20

Thread: Unable to boot to /home after login

  1. #1

    Default Unable to boot to /home after login

    Hello everyone, using 12.3 32bit version.

    I am unable to boot to my home directory after logjn where it stays idle showi g the opensuse screen. I noticed there are 3 kernels displayed on the splash screen 3.7.10-pae , default, and desktop. Everything went awry when I rebooted after installing a program which stated it neexex to update the kernel (pae I assume).

    I have the rescue cd if its needed and would appreciate any help on the matter.

  2. #2
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    15,684
    Blog Entries
    3

    Default Re: Unable to boot to /home after login

    Quote Originally Posted by fisk_king1 View Post
    Hello everyone, using 12.3 32bit version.

    I am unable to boot to my home directory after logjn where it stays idle showi g the opensuse screen. I noticed there are 3 kernels displayed on the splash screen 3.7.10-pae , default, and desktop. Everything went awry when I rebooted after installing a program which stated it neexex to update the kernel (pae I assume).

    I have the rescue cd if its needed and would appreciate any help on the matter.
    One possibility comes to mind.

    Perhaps you have a separate "/boot". And, with three kernels, it is possibly out of space so that the "initrd" did not build correctly when you added extra kernels.

    (added) You say you have the rescue CD. Booting that to look around would also work.

    If you are not sure, then boot the rescue CD, open a terminal and use "su" to become root. Then run
    Code:
    # fdisk -l
    and post the results here. You can copy/paste the command output to a file that you save on a USB, and later post from there.

    I'm guessing that you installed with the live KDE or live Gnome image. So you probably still have that live media. Are you able to boot it, mount partitions and look around to see if "/boot" is out of space?

    (If you don't know how, it's okay to ask for further help).

    I thought I had added this. Boot your rescue CD, and look around from there. Post the output of "fdisk -l" (run that as root)
    Last edited by nrickert; 07-Apr-2014 at 16:39. Reason: add more
    openSUSE Leap 15.3; KDE Plasma 5.18.6;

  3. #3

    Default Re: Unable to boot to /home after login

    Thanks for the reply. Funny I was trying to figure out how to PM u or Robin lista for help before I made this thread.

    Code:
                               Start.             End.                 Blocks.           ID.   System
    /dev/sda1   *   2048.      321535.              159744.            83.   Linux
    /dev/sda2.       321536.   976773119.     488225792.      8e.    Linux LVM

  4. #4

    Default Re: Unable to boot to /home after login

    Sorry for the errors I'm typing this from my phone.

  5. #5
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    15,684
    Blog Entries
    3

    Default Re: Unable to boot to /home after login

    Quote Originally Posted by fisk_king1 View Post
    Sorry for the errors I'm typing this from my phone.
    It's a bit hard to read, but I could work it out.

    It looks as if you have installed in an LVM. Is that an encrypted LVM?

    Presumably, "/dev/sda1" is mounted as "/boot".

    With three kernels (default, desktop and pae), and with probably two versions of each kernel, you have very likely run out of space on "/boot". It looks to be 160M.

    When I was running 12.3, and using only the desktop kernel, I ran out of space on a 100M "/boot".

    I am assuming that you installed 32-bit (there isn't a PAE kernel for 64-bit). And you probably have 4G or more of memory, and needed the desktop and/or pae kernel to be able to access that memory.

    You are going to need to go into rescue mode to fix this. I'm hoping that your rescue CD ls also 32-bit.

    The general procedure for rescue mode is described in my blog post Rescuing Susie. However, I was solving a slightly different problem, so we will have to do it a little differently. I suggest you start by reading that.

    My tentative suggestion is that you should delete the default kernel and the pae kernel, and keep only the desktop kernel. That will still give access to all of your memory. And it will free up the needed space for "/boot". Once we have freed up space, you will need to run "mkinitrd" to rebuild the "initrd" files.

    Here's a simpler step that you might want to try first:

    1. Boot your rescue disk.
    2. Code:
      # mount /dev/sda1 /mnt
    3. Use "ls -l" to list the "initrd" files in "/mnt" (really your "/boot")
    4. Find the oldest of those "initrd" files (using the file date).
    5. Write down the details of that oldest initrd. In particular, write down the kernel version number and whether default, desktop or pae.
    6. At the grub screen, attempt to boot the kernel corresponding to that oldest "initrd". You might have to explore the grub menu.


    The idea here is that the oldest "initrd" is the one most likely to be correct. If you are able to boot with that, then it will be easier to fix your system from the inside when it is running. In particular, that will be easier than rescue mode.

    I'll wait your response, and then we can go on from there.
    openSUSE Leap 15.3; KDE Plasma 5.18.6;

  6. #6

    Default Re: Unable to boot to /home after login

    After using your advice I see that in /mnt using "ls -l" desktop kernel is the oldest. Can I not remove these files ising the rescue disksimilar to in terminal when booted normally (probably a stupid question).


    Thanks for the help.

  7. #7

    Default Re: Unable to boot to /home after login

    Maybe I shouldn't have bit using the recovery disk I deleted everything pertaining to default & pae. Using ls -l it now displays:

    Code:
    Initrd -> initrd-3.7.10-1.28-default
    
    Vmlinuz -> vmlinuz-3.7.10-1.28-default
    Both of these are highligbted in red ( desktop files still remain). When I try to boot normally it is looking for the pae kernel to boot which I then use Advance Options. Using the the desktop kernel (or recovery option) to boot everything loads to the login afterwhich nothing loads except Teamviewer app and default desktop wallpaper.

    It is encrypted by the way (LVM).

  8. #8
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    15,684
    Blog Entries
    3

    Default Re: Unable to boot to /home after login

    Quote Originally Posted by fisk_king1 View Post
    After using your advice I see that in /mnt using "ls -l" desktop kernel is the oldest. Can I not remove these files ising the rescue disksimilar to in terminal when booted normally (probably a stupid question).
    Yes, you can remove them manually. But that might confuse your system. Your RPM database won't match what is present. But it is okay as a temporary solution. You can fix the rest later, once you are up and running.

    If you do it that way, then delete "initrd" files and "vmlinuz" files for the kernels that you don't want.
    openSUSE Leap 15.3; KDE Plasma 5.18.6;

  9. #9
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    15,684
    Blog Entries
    3

    Default Re: Unable to boot to /home after login

    Quote Originally Posted by fisk_king1 View Post
    Using the the desktop kernel (or recovery option) to boot everything loads to the login afterwhich nothing loads except Teamviewer app and default desktop wallpaper.
    When you boot to that stage, can you use CTRL-ALT-F1 (or perhaps CTRL-ALT-F2) to get to a login prompt?

    If you are able to login there, then login as root and run
    Code:
    # mkinitrd
    then reboot and see if things work a little better.

    If you cannot get to a root prompt, then we will need to go into rescue mode.

    I'll fill in the details for rescue mode, if it turns out that we need that. Waiting for your next response.
    openSUSE Leap 15.3; KDE Plasma 5.18.6;

  10. #10

    Default Re: Unable to boot to /home after login

    Well progress is being made but still having the end result. Normal startup no longer shows the other two kernels (default & pae). When desktop kernel is selected for boot and decrypting the LVM it takes me to the login screen, as normal, where it hangs on the default homescreen still. The TeamViewer Wine application appears on the screen but nothing else. Same result choosing kernel recovery option as well.

Page 1 of 2 12 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
  •