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

Thread: VBOX OpenSuse Guest Will No Longer Boot

  1. #1

    Default VBOX OpenSuse Guest Will No Longer Boot

    I have/had a working OpenSuse(13.1) VBOX(4.3.8) guest running in a 32-bit Windows 7 host. It will not longer boot.


    I had been cloning it successfully, and using the clone as my working machine and keeping the original as a backup.


    Today, I shut down the working machine and made a clone as usual.


    Neither the clone nor the working machine would start completely. They showed the exact same symptoms, so it appears the problem occurred in the working machine during shutdown.


    A previous clone, from two weeks ago boots up without issues.


    The symptoms seem related to the display. During bootup, we eventually see a black/green chameleon desktop, but then the display enlarges and goes black. An "X" cursor appears, and that is it.. That is were the bootup process hangs. In a normal bootup process, after the chameleon desktop appears, the next viewable step would be for hardrive icons and others to up near the center of the screen. This does not happen.


    I have tried changing the display settings (from two displays to one, and video memory allocation, but that does not help.)


    Any idea what is causing this, how to troubleshoot it and how to fix it?


    Thanks

  2. #2
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    13,295
    Blog Entries
    2

    Default Re: VBOX OpenSuse Guest Will No Longer Boot

    Have you tried booting to Recovery Mode?
    If you are able to do that, it would further suggest a display issue related to the installed display driver.
    You could then try
    Re-installing VBox Guest extensions.
    Removing VBox Guest extensions.

    HTH,
    TSU

  3. #3

    Default Re: VBOX OpenSuse Guest Will No Longer Boot

    Thanks for your suggestion. Under advanced, I do not see "Recovery Mode". What I do see is a list with 4 entries -- all the same: "OpenSUSE 13.1 with Linux 3.11".

    Is there another way to get into recovery mode?

    I can get into "Rescue" mode from the CD, but I that does not get me access to the file system, it seems.

    Thanks

  4. #4

    Default Re: VBOX OpenSuse Guest Will No Longer Boot

    Slight progress: I was able to mount the file system in Recovery mode accessed by booting the DVD iso.
    (I changed the boot order in Vbox, Settings).

    I used these commands to mount the file system:
    fdisk -l
    mount /dev/sda2 /mnt <-- i knew from my notes this was the root partition
    mount /dev/sda3 /mnt/ home <--- likewise.


    At this point I am trying to do some damage control to move some non-backed-up files from
    the VM to my host file system.

    The guest additions are not working so I am stuck at the moment with that.

    I would like some help in diagnosing and fixing the boot problem.

    thanks

  5. #5

    Post Re: VBOX OpenSuse Guest Will No Longer Boot

    Here is an update for anyone else having similar problems.

    I was able to boot my suse guest in text mode. I still have not solved the X display problem.

    The guest utils are working, and I was able to mount my shared windows directories.

    So now I can at least copy the files I had not yet backed up from the suse guest to the windows 7 host.

    Next I need to find out why the X display failed....


    For what it is worth, to start the suse guest in text mode, I did this:

    1) As soon as the machine starts booting, type "esc e".That will get you into the grub loader "mode".

    2) If you are in the grub loader mode you should see a text box containing a boot script.

    Scroll down almost to the bottom of the script, to the line starting "linux /boot/vmlinuz-....".

    Immediately after this kernel name, add "3", for run level three. It will look something like this "linux /boot/vmlinuz-3.11.10-7-default 3 root=UUID...." you can also remove the words "quiet" and "silent" from the end of the line. "F10" to boot. That should get you to a login prompt it level 3 (text mode).

    I still need some help troubleshooting the X-display blackout that occurs right before the KDE icons usually appear.

  6. #6

    Default Re: VBOX OpenSuse Guest Will No Longer Boot

    I wish I could edit my previous post(s), but this forum won't allow it.

    And so, when in text mode (3) (as described above) I am able to execute "sudo startx",
    and the display is working.

    What I need now is to figure out why the bootup does not continue past
    a blacked-out screen, and yet the display seems to work.

    Can anyone help me with that?

  7. #7
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    13,295
    Blog Entries
    2

    Default Re: VBOX OpenSuse Guest Will No Longer Boot

    Answering various questions (BTW - all your issues appear to be not likely related to Virtualization)

    - The current default openSUSE Grub graphic isn't wide enough to display the entire line for each kernel entry. IMO is a faulty decision favoring style over functionality. You can fix with the script I created which includes a revised graphic, but will likely be overwritten with every update to Plymouth. So, just keep the package on your system where you can re-run the script as needed. Although my graphic is 12.3, it can be modified in GIMP to display 13.1.
    Hmmmm... Maybe I'll create a graphic and modify the script so the right graphic is installed for the OS.
    http://en.opensuse.org/User:Tsu2/12....fied_GRUB_Menu

    When you can't see the entire Grub entry, a good guess is that every second entry is the Recovery Mode for the kernel immediately preceding.

    - A starting point troubleshooting display issues is to see what is behind the graphic by pressing ESC. You should do this immediately when the graphic first appears, when the system eventually reaches a STOP, the ESC key won't work. You should note what the last few lines indicate before no longer proceeding.

    - Recommend you clone your existing system and just run your DVD "repair" mode. Or, if you have a command line in the Guest, run a "zypper dup" (assuming you haven't touched your repositories). Either method will force a re-install of your OS from whatever sources are configured. IMO either should fix any damage in your system if the cause was an improper shutdown. If you suspect the cause might have been some update, then the DVD will return your system to the packages released when openSUSE 13.1 was first released (assume that would be working). Then follow that up with updating (or patching if you want to be very conservative). Since the openSUSE 13.1 VBox Guests I'm running seem to be OK, I doubt it's a widespread issue caused by something like an update.

    HTH,
    TSU

  8. #8

    Default Re: VBOX OpenSuse Guest Will No Longer Boot

    Thanks Tsu, I have tried your suggestions and am still stuck.

    From the text (level 3) prompt, I successfully ran 'sudo zypper dup', and then rebooted. I am now on a different kernel. Rebooting hangs on a black screen -- this time without an "X" prompt.

    From the text prompt, though, I can still run "sudo startx" and get to a KDE destktop.

    If i reboot again, and break into the GNU GRUB menu (by typing "e" right away after a reset), I can modify the "linux /boot/vmlinz.... " line by removing "quiet silent" from the end of the line. Then I can see the console messages stream past rather than the graphic.

    The last thing I can clearly see on this 'normal' reboot is "Started LSB X Display Manager" before the screen blacks out.

  9. #9
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    13,295
    Blog Entries
    2

    Default Re: VBOX OpenSuse Guest Will No Longer Boot

    I probably should have asked earlier,
    Pls post the repos you have configured
    Code:
    zypper lr
    It could be why you experienced your problems in the first place and why "zypper dup" didn't fix your system. Also, "startx" should not have started KDE successfully.

    TSU

  10. #10

    Post Re: VBOX OpenSuse Guest Will No Longer Boot

    Guest additions copy/paste is not functional when I bring up the KDE desktop using startx.
    So I can not copy/paste the output of "zyppr lr".

    So here goes:

    Name, Enabled, Refresh
    google-chrome, yes, yes
    openSuse-13.1-1.10 yes, no
    openSuse-13.1-Debug, no, yes
    openSuse-13.1-1-Update-Debug, yes, yes
    openSuse-13.1-1-Update-Debug-Non_Oss, no, yes
    openSuse-13.1-1-Non-Oss, yes, yes
    openSuse-13.1-1-Source, No, Yes
    openSuse-13.1-1-Update, Yes, Yes
    openSuse-13.1-1-Update-Non-Oss, Yes, Yes

    Thanks

Page 1 of 2 12 LastLast

Tags for this Thread

Posting Permissions

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