Ubuntu :: Recovery Menu (in Recovery Mode) Does Not Work?
Aug 18, 2010
I've got a, as it seems to me, strange problem.I've inadvertently deleted my user from the group admin so I'm in the same situation of a lot of other users (read a lot of messages about it).My problem is that when restarted in recovery mode there is no way I can choose the 'drop to the root shell' or similar in the menu.The menu appears for a second and then I've got an empty screen. If I press a key I've been requested for a username and password that of course is not what I need.
I recently reinstalled Ubuntu 10.04. Since I did that I have had a problem with GRUB: I cannot see the Recovery Mode menu - at least not anything intelligible.
I can see the normal first GRUB menu with all installed operating systems, recovery modes, and MEMTEST, etc, but cannot see the Recovery Mode menu. What I do notice (if I select it) are some fuzzy lines at the top of the screen. I also notice the Ubuntu splash screen does not appear any more either.
Clearly it seems there is a resolution issue. I have a 1440 x 900 monitor and the current version NVIDIA driver.
This happened some time ago on previous Ubuntu releases, but was not an issue when I originally installed 10.04.
Attempted Fix:I installed the StartUp-Manager and have tried all the resolution combinations with no success. Some yield bigger more centrally displayed fuzzy lines, but still nothing legible.
Although this isn't "life-threatening" I'm just a bit worried that I might need the Recovery Menu and not be able to use it.
I started a thread over in installations and upgrades in which I was trying to upgrade from Ubuntu 10.04 to 10.10 using the upgrade manager. My computer froze in the middle of the process, requiring me to restart my computer. When I try rebooting Ubuntu, I get an error message "The configuration defaults for Gnome power manager have not been installed correctly" and then a blank screen. No mouse pointer, no cursor. It will not take me to the Ubuntu desktop screen. I've already found the sudo commands I can run to try and fix Ubuntu. They are as follows:
sudo apt-get clean (If the problem is not having enough free hard drive space) sudo dpkg --configure -a (If the problem deals with the upgrade installation process)
However, what I can't get is the terminal to come up to run these commands. In the other thread I started, someone mentioned that in the Grub menu, you can choose "recovery mode", hit "enter" to boot it, and it will give you a menu of options to choose from. However, when I choose "recovery mode" and hit "enter", I do not get a menu but instead 3 pages of data about my computer that ends with this:
"Begin: Running/scripts/init-bottom... Done. "
It gives me a blinking cursor at the very end but I cannot type anything and I cannot page up to see the 3 pages of data. What I am looking for is a way to get to the recovery mode menu OR somehow open up a terminal so I can run the sudo commands. My computer automatically logs me in, so I do not get a login screen and Ctrl+Alt+F1 does not work for me. Anyone know how I can open a terminal with only access to the Grub menu? Perhaps a BASH command that I can use in the command line that will open up a terminal? To summarize: My computer does not boot Ubuntu. I get an error message followed by a blank screen. It does not go into the desktop screen so I cannot choose Applications->Accessories->Terminal.
My Grub menu consists of Ubuntu and it's version, Ubuntu and it's version with recovery mode, memtest, and Windows XP (I have a dual boot system). In the Grub menu, I can select "e" for edit, "c" for command line and "enter" to boot either regular Ubuntu OS or Ubuntu recovery mode. "Sudo" commands are not recognize if I choose the command line for either Ubuntu OS or recovery mode. I have a Live CD for 10.04 but you cannot run sudo commands because you do not have access to root on the Live CD.
Afraid I'm an utter newbie. I'm using 10.04 64 bit. I only noticed this after I tried to install the NVIDIA driver and all my ubuntu os'es blackscreened after restart. Because I couldn't even access recovery mode, I ended up reinstalling ubuntu, overwriting the old root.I thought the problem was due to the driver, but it's even now persisting. I can run the terminal (within X?) but if I try ctl alt <F1-6>, the screen just freezes until I do ctl alt F7. Furthermore, recovery mode still leaves a black screen after the initial loading text. I need it to work before I attempt reinstalling the NVIDIA drivers again, as I don't want to reinstall the OS and all the programs.
Sometimes it feels like I can do stuff in recovery mode, like Ctl Alt Delete or sudo shutdown, but sometimes not. Not sure if this is related, but grub also lists windows vista and windows recovery as the opposite they should be (I thought my windows was completely screwed until I tried windows recovery).
I attempted to install Catalyst 10.11 for my ATI HD 2600XT and the system now only displays lines and a large block of pixels where the mouse would go. CTRL-ALT-F1 kills the system and does not provide a command prompt. This is a single installation, not dual-boot, but there is no Press Esc to access the Grub menu during startup so I cannot choose safe mode. I attempted to get into Recovery mode using the flash drive that I used to install the system and it tells me there is no Recovery kernel (I used the 64-bit Desktop installer, not alternative). Does anyone know an alternative to get into the Grub menu other than ESC during bootup? Alternatively, do I need to download the 64-bit Alternative ISO and create a new boot disk with it so I can access Recovery mode? Is there something else I'm not thinking of?
I accidentally chose the "recovery mode" and now i dont know what to do. What commands i have to enter to go back to normal ubuntu mode with graphic etc?
ok so i have been haviung the same problem for a while now and it is starting to **** me off, with every distribution of ubuntu i am getting thuis stupid message when i log in it is ionoly every once i a while that i get it but saince i have upgraded to 220.04 cannot fix it. i could fix it befor pretty easily, the probklem is when i get t o the login screen i get this generic login menu whne i attept to login i get this message somethiung like power management is not installed correctly. like i said b4 it was easy to fix, all i would do is to go to the ubuntu recovery thing, which is apparently not available ion 10.04 it does not evn give me a choice which to boot how do i get to recover mode in ubuntu 10.04?
Upgrading over the weekend, but it failed, and suggested running dpkg-reconfigure -a
I couldn't launch any terminal/xterm windows, and couldn't login via ssh (kicked me out with xmalloc failure) or through a virtual console (showed garbled characters)
So I had to reboot.
Now the boot process -- I've tried recovery mode for all othe kernels I've got installed, but all fail in the same way:
I run 9.10 from a live usb with persistece, and got /etc/sudoers awfully messed up. now i'm told to fix in through 'recovery mode', but i don't think live usb has one. is that true? what about my sudoers? is there another way to fix it?
I have a HP mini 2133 with Ubuntu 10.04 NBR installed, but because the CMOS battery went flat and the date on the BIOS got reset to 1980, I now get a failure starting the machine (Superblock failure: Last mount time is in the future). I've already googled on this error, and the general advise seems to be "run fschk and let it complete", but my question is...I don't get a grub screen come up when Ubuntu boots, and Contrl/Alt/F* doesn't bring me to any login windows. So how do I interrupt the startup, and get to a login window before I get the mount error.
I messed up my video drivers and now can't get into recovery mode. Pressing the shift key isn't working. All that happens is the splash screen appears in faded looking colors and then fades to white.
I've got an ASUS N61 laptop with an ATI Radeon 5730 graphics card. I just upgraded to 10.10 from 10.4 and was trying to install the open source video drivers. I must have messed something up and can't get to the terminal now.
I'm having a huge problem right now and I could use some help deciphering what's wrong.I can't get my system to boot (see signature) and even the recovery mode is buggered. henever I try to boot, all I get is a flashing underscore. This is the same for both the normal and recovery modes Kernels. I've run the boot info script from a live cd and I've attached it to this post.
Ubuntu cannot boot. says Starting system V runlevel compatibility [fail]it is after replacing xorg.I want to enter in recovery mode. But when i try escape it just enters bios. if i try holding shift it just does nothing.So how to enter recovery mode in ubuntu 11.04 i just cannot get to grub menu.
This is an urgent problem. I removed my propreitary ati display drivers because I had to update them but I don't know what happened. Now I can't boot. The screen shows the Ubuntu splash screen but then the login screen does not come on. I get a blank screen. Worst of all, I had removed Recovery entries from the grub so I can't boot into recovery mode so easily. It's urgent. I don't want to reinstall with my exams a week away.
in Ubuntu 10.04 I would like to enter in recovery mode, so I restarted computer and pressed <Esc> key just like in any previous version, but nothing happens Ubuntu still starts to boot.
How to enter into recovery mode in the latest version of Ubuntu?
I'm running 9.04 on a Powerbook G4 and, long story short, I accidentially put it into hibernate mode. When I try to turn it on, I am greeted with a blank screen after the bootloader. Unfortunately I can find no way to get out of this, since I'm using yaboot instead of grub. I can access my yaboot.conf file if I mount the HD from a live CD, but is there something I can put in there to tell it not to try to resume from hibernation? Or would deleting the swap partition at hda4 that apparently contains my hibernation data solve the problem?
I installed lucid last week, and this morning installed some updates that appeared in update manager and then started having issues with permissions so I rebooted. Now when I try and log in I get the message Authentication Error Normally this wouldn't be a problem I would reboot again hit ESC just before loading Grub appeared and go into recovery mode and change the password for my master user. But I never get the chance to press ESC, and even I hold the key down from the time my BIOS flash screen is up, I never get the GRUB menu.
I decided to install ubuntu on my family desktop because it is quite old now and it needs constant maintenance for windows. I have used the old ubuntu on this computer some time ago i believe it was the 8.04 version. But anyway back to the point, i have decided to put ubuntu back onto the computer but i have encountered an issue. The issue is that when i installed ubuntu everything seemed to be working perfectly out of the box the printer, wireless etc... but when i installed the restricted drivers for the ati card inside.Upon loading ubuntu a big OUT OF RANGE came up on the monitor and i cannot access anything. I looked at the FAQ but am unable to get into recovery mode to type in the relevant command prompt and there seems to be no grub popping up to press esc/shift to get into the menu. Is there anyway around this? i am prepared to reinstall ubuntu but what could i do to prevent this upon re installation?.
I have made an entry in fstab that is keeping me from booting. I am able to get into recovery either from entering "M" as it is trying to mount my bad entry or from Grub.
However once in recovery I am unable to save my edits in vi. I have tried several attempts at saving my edits to no avail. What trick will I have to impose in order to clean up my fstab so I can boot successfully.
as Ubuntu is my only OS on this box.I had this PC running as a server for a few months with few reboots.I installed updates as usual yesterday, and hadn't changed anything configuration-wise since the last reboot. Well last night this server that I was running was moved to another Windows box and so I finally got to shut this PC down for the night. In the morning, I was greeted with an endless splash screen. It went on for 20 minutes without anything. I did update the kernel through update manager.
So what do I do? This machine has a 1TB HDD with a lot of very important data on it--reformatting is not a considerable option at this point. Which is bad because I don't know what else I could so when even recovery mode isn't working...
I installed Ubuntu 10.04 32 bit on an Acer Aspire 7520 laptop running Vista.Thereafter, Vista could only be run via the "Windows Recovery Environment" grub menu option, which is on /dev/sda2. However, within Vista than the wireless network is not functioning any more. It has given lot of headaches to find a way out. Unsuccessful, so far.
I had many problems with installing kubuntu 11.04 on my laptop HP Elitebook 8560p and after downloading different iso everything works well, but sistem freezeout and would not reboot also in recovery mode that would load untill Recovery menu when system won't responde.
I used Ubuntu Tweak on ubuntu 10.10 and i don't remember what stupid thing i did. Now, my ubuntu never logs on, neither in recovery mode. I have attached the Camera Screenshot of the error screen. And i am a beginner, and it feels bad when my ubuntu doesn't work.
I am trying to run boot up in recovery mode in Lucid Lynx 10.04 on a Dell XPS M170. When it gets to [1107.134155][drm] nouveau 0000:01:00.0: GPU lockup-switching to software fbcom, it stops and freezes up and will go no further.
After upgrading to 9.10 Karmic Koala, my Amilo Laptop (AMD64) refuses to boot. I installed GRUB2 which works fine for my WinXP ... and Karmic will boot in recovery mode.
When trying a normal boot, I get a black screen. CRTL-ALT-F1 yields just a blinking cursor. The system will immediately reboot when pressing CRTL-ALT-Entf.
When booting in recovery mode, I choose "Resume normal boot" from the menu, log in while in cosole mode and enter "startx" ... and the grafic environtment works fine!
Why does the system work in recovery mode, but does not start with a normal boot?
Fly.By.Wire
Here's some information on my system:
cat /proc/version
Linux version 2.6.31-17-generic (buildd@crested) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu ) #54-Ubuntu SMP Thu Dec 10 17:01:44 UTC 2009
Today I wanted to make a backup of my Ubuntu server. Since the program wasn't working for me, I rebooted my computer and right now it wont boot. Now I entered recovery mode and I'm trying to recover my /var/www and /etc/mrtg folders. I want to copy them to my USB-Stick but Ubuntu wont do this.
The command I tried: Code: cp -r /var/www /dev/sdg1/www I already created the folder via a other system. I also tried to mount the USB stick: Code: mount /dev/sdg1 /mnt/usbe But im getting the following error: error while loading shared libraries: /lib/libsepol.so.1: Invalid ELF header.
A few days ago I began to get messages about my hard drive running out of space, and while I tried to clear out some files to make room I somehow managed to mess something up such that my main login screen appeared with hugely distorted letters and dialog boxes, and it wouldn't let me log in. While this is still the case, I can now log in by booting to recovery mode, selecting the netroot option, doing an "su myusername", and then executing "startx".
While this is a little inconvenient, it does bring up my standard Ubuntu operating environment and I now have access to all my files, email, internet, etc. There are still a few miscellaneous things that are messed up, however, and I don't yet know how to fix themIn particular:a) I can't print. I tried running the printer configuration tool from the System->Administration menu, but there's no "New Printer" icon. Alsowhile trying to get it working, I managed to generate a "The cups scheduler is not running" error message.b) I can't mount a USB drive. Every time I plug one in, I get an error message that says "Unable to mount drive, not authorized."c) Finally, there's the basic problem of still not being able to login without going thru my recovery mode workaround.I suspect all these problems are related, though I'd be happy to fix them one at a time if that's what it takes.
