Ubuntu :: Will Not Finish Booting - Press Esc To Enter Recovery Shell
Jan 22, 2010
I have never in a year had a problem with this d-boot system. Two days ago I tried to boot into ubuntu like every day. It started to load normal, went to the ubuntu logo and paused for about 15 seconds and posted this under the logo:
One or more of the mounts listed in /etc/fstab cannot yet be mounted
/: waiting for /dev/loop0
/tmp: waiting for (null)
/boot: waiting for /host/ubuntu/disks/boot
Press ESC to enter a recovery shell
I have looked everywhere and tried so many things, I can't look any further. All I have been doing for two days is trying to boot this system.
I'm randomly getting 'Continue to wait; or press S to skip mounting or M for manual recovery...' or something like that at boot ((it flashes very quickly)- If I don't press anything, I'm prompted for my password (I configured it to login with password) and the desktop loads...
I'm using Ultimate Edition 2.6.1 -> Ultimate Edition Home
I was using my 1TB hdd to dual-boot linux, windows, and for storage...Yesterday, I imaged the linux partition, and restored it to an approximately 66GB partition I created on a 150GB hdd...Besides the 66GB partition, the rest of the 150GB hdd is 'unallocated space'... That's when the above message started...Below are screenshots of the fstab and partitions as they are now...
I have just installed Fedora 12. After my pc boots up, the message:"Press any key to ent This continues to appeuntil I press any key and then the GRUB boot menu appears:Fedora (2.6.31.6-145.fc12.i686.PAE)BootIf I choose "Fedora", it boots properly into the login screen.What do I need to do to have the system boot directly into the log in screen, without going into this loop, boot menu and having to choose what to boot?
My Ubuntu was working perfectly fine until this morning. It is the latest release (10.04 I think) and it is the 64 bit version. This morning I go to my computer and see there are some updates waiting. I install the updates without paying much attention to them. I really do not remember what the updates were. Then Ubuntu asks me to restart so I restart. After restart I get the usual log in screen and I hear the drums. I put in my password, press enter and then the log in screen disappears and I expect to see my desktop. But that does not happen. Instead in a split second after disappearing, the log in screen reappears and I hear the drums again.
At the beginning I thought that I simply forgot my password. But that is unlikely because I have been using the same password for 6 years now. But just in case I tried an incorrect password and I got a different behavior. If I put in an incorrect password, Ubuntu will simply say "authentication failed" and the log in screen will not disappear. When I put in the correct password, the log in screen disappears for a split second (as if my password is correct) but then instead of taking me to the desktop it takes me back to the log in screen and sounds the drums again.
I have downloaded the Damm small linux iso ,and burned the image to the CD with infrarecorder .But when i try to boot it from the CD ,I get the DSL logo and press enter to boot ,then the computer freezes with two small penguins in the top left corner of the screen.
I'm trying to do exactly this: [URL] the first time i did it, I made it and everything was fine, except I didn't know what "installation size" meant in wubi, so as I selected 3GB, the rest of the partition was left empty and I didn't have enough space for ubuntu. Then I formatted the partition again and reinstalled ubuntu. Since then while it's booting, I get the message Disk boot failure insert system disk and press enter. I tried reinstalling many times, but I still get this message..
I have installed Ubuntu 10.10 x64 bit edition. On booting Ubuntu wouldn't mount my partitions, so I installed pysdm to auto mount them during booting. But since then I often get during boot: Press S to skip mount or M for manual recovery. What should I do?
I downloaded the appropriate iso for the ps3 from here:[url]
(specifically: ubuntu-10.04-desktop-powerpc+ps3.iso via torrent)
Installation runs smoothly up until 100% and then i am prompted to reboot.
When i click reboot, i get info on some daemons(?) shutting down(i think) and then the cd is automatically ejected and i am prompted to press enter.
So far, so good. After i hit enter though, i get a large amount of various read errors and finally a segmentation fault. The system just hangs there :/.
I forcibly reboot the PS3, and then i am greeted with the pack of errors that are shown in the screenshot.
I've been fiddling about with vortexbox (the one before 1.4 I think), for a while. This is a music ripping and server rpm setup using Fedora 11 as the base.
As it was on a test machine, decided to try changing the logical volume sizes of LogVol00 and LogVol02 to fit a few more cd's on 02 before getting a new pc (just to see how it works).
Logged on and opened up the graphic version of lvm (using gnome). Then selected the LogVol02 logical volume, select edit, changed name to LogVol02-Storage, saved and logged out. Rebooted vortexbox since then its been unable to start properly (is this a kernel panic?).
Read up a lot on lvm on the net, have access to Fedora 11 disk 1, so logged on. Eventually managed (I thought to) to change LogVol02-Storage to LogVol02 using lvrename.
However, still refuses to boot completely.
The message it gives is as follows (sort of): Welcome to Fedora Press '1' to enter interactive startup
Setting up Logical Volume Management: 3 logical volume(s) in volume group 'VolGroup00' now active
*** An error occurred during file system check. *** Droping you to a shell; the system will reboot when you leave the shell.
Give root password for maintenance (or type Control-D to continue):
Loving vortexbox appart from this. Will it be easier just to reinstall everything? If so, is there a way of listing all the changes I've done so I can reproduce (I'm thinking of just looking at all the commands I ran on the CLI).
Otherwise, is there a way of listing all of the commands I ran in terminal and piping them into a file so I can see what I need to do to rebuild after reinstalling?
Today, I was downloading some stuff from online. I left for a few minutes and came back to find that someone had hit my loose power cord, causing the computer to restart. When I completed the reboot (It always says "Insert system disk and press enter" after checking CD drives), and had it load OpenSuSE 11.3 Failsafe (Regular won't work for me), it loaded into Teal (BASH, Command Prompt, Kommand, whatever you want to call it). At first, I thought maybe I screwed up and told it to load into that. But, I tried again, and it did the same. I tried using Non-Failsafe, and got the same results. I am able to edit, add, or remove programs from the Linux partition, though.
I bought a t770.uk HP desktop PC, which came without a Hard drive as the pervious owner had removed it for security reasons. A week later I got a hold of a brand new - out of an anti-static sealed bag - compatible Western Digital Caviar SE 80GB SATA150 7200 HDD, and installed it as directed by my t770.uk manual. Up until now, things looked to be on a roll. As I don't have any windows OS, I figured Ubunutu would be the way to go (and it certainly is from what I've heard and read about it. I can't wait!).
So I sent off for a CD and it popped through my mail a few weeks back. The problem that I am having is after booting past a very brief view of the HP POST screen, the screen goes black with the error "Disc boot failure-insert system disk and press enter". I've tried placing the Ubuntu disc in (assuming it is asking for that? An OS disc) and restarting, and changing the boot order around, but no matter what I do the error persists and I can't install Ubuntu. I really want to get this PC running with Ubuntu.
i just installed fedora 13(fresh install) everything worked fine so i wanted to install the nvidia drivers (using akmod) everything went fine so i rebooted it. It started fine showing everything as[ OK ]But after showingEnabling monthly Smolt checkin: [ OK ]Starting atd: [ OK ]It stops rigth there...I dont know why, i just can reboot and cant go any furtherThe next one must be service local, but cant get it started
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.
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.
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?
Earlier today I was setting up ssh on a new computer. I modified permissions on the Passwd folder to complete the setup. I few hours later when I went to sudo something in the terminal I received the notice of an incorrect password (after using sudo prior to this), even though it was typed correctly.
I tried to restart the computer to solve the issue, but was met with an Authentication Failed message, regardless of the user I tried to log in with. I was hoping I could log in with recovery mode but was unable to do that as well. I have searched a substantial amount and have not found a solution. Could this be an issue with permissions on either the Passwd or Shadow folder? If so, could these be changed if I ran a Live CD?
I broke sudo when I wrongly edited a file in /etc/sudoers.d in vi(did not use visudo :-().I read that I could fix the same by rebooting into the 'Recovery Mode' by selecting the same from the grub menu.
However I'd earlier disabled the showing of the grub menu by editing /etc/default/grub. As a result I can't seem to go into recovery mode to fix my broken sudo.
I recently removed Winblows Vista from my laptop and replaced it with Kubuntu 10.10 (I left the recovery partition on there, just in case). When I turn on the computer, the GRUB menu appears, I press enter, then a little flashing underscore appears on the screen in the top left hand corner. After a few seconds, the Kubuntu logo appears and I can log in.But yesterday I replace Kubuntu with Ubuntu 10.10. The Boot process is the same, but the little flashing underscore in the top left hand corner flashes for about 10 seconds longer then Kubuntu 10.10 did, and then a few paragraphs of text appears for a few seconds, then I am logged in automatically.Is this "unusual" boot process anything to worry about, or am I just being a noob.
I have a new Dell R710 dual processor machine I'm trying to install Fedora 11 x86_64 on (all versions I mention in this post are x86_64 bit). I downloaded the cd iso files, burned them to cd (I don't have a DVD burner), then told my machine to boot to the optical drive.
I get a very brief introduction message about ISOLINUX then the monitor refreshes and gives me the following message: "Press the <Enter> key to begin the installation process."
Naturally, I press the Enter key(s) on my keyboard. Nothing happens. I try Alt ASCII combinations that might mimic an Enter key. No dice. ctrl-alt-delete works, however, and the machine reboots.
My checksums for the iso's are perfect, and the install process triggers perfectly on other machines. Just not this one.
After much vain research, I download the Fedora 11 Live-KDE, burn it to CD and try it. It doesn't work - the same thing happens. I tried the net install, and it doesn't work either.
On a lark, I download the Fedora 10 Live KDE iso and burn it to cd. It works perfectly and skips the "Enter" phrase entirely. I take my Fedora 11 Live KDE disc and put it in another machine and it, too, works perfectly, which leads me to believe my cd burns are fine.
I've also used usb creator to create a bootable USB drive. It doesn't ask me to press enter - it just fails with a really arcane IF=0 error (arcane to me, anyway).
So I'm at a loss. I'd like to install Fedora 11 on this machine, but may end up with Fedora 10 or CentOS if I can't figure this out.
Is there some weird BIOS setting somewhere I'm missing? I find it really weird that my fedora 10 cd works, but my fedora 11 cd does not (but my fedora 11 cd works in other machines).
I'm trying to install Fedora 11 (64-bit) but after a small message about ISOLINUX the monitor refreshes and displays the following message: "Press the <Enter> key to begin the installation process." At that point the keyboard dies and I can't go any further. I tried 4 different FC11 dvds, also tried different PS2 and USB keyboards but the problem persists.
How to install FC 10 first and then upgrade to FC11. I tried that as well with no luck. I can install FC10 with no problems but why not FC11?
Is there a button I can press when booting to log into a 'safe mode' ? Like f5-f6 does on windows? Or a command prompt? My ubuntu fails when it loads X and cant get out of it, is there something I can do to allow me to log into the system to see whats the problem or revert it back to the old settings?
I'm setting up an Ubuntu server and I keep getting strange problems with my editor.I'm not sure if this is because my keyboard configuration is wrong or I screwed up the installation but regardless it's quite frustrating.
When using the movement keys (arrows and numpad) I get "[" brackets and "C"s, if I hold down or push down on the key hard a list of errors and text comes up, usually involving something that says something like:"Mount disabled" or "____ disabled press CONTROL-X to restart the shell"Similair problems are also found in vi (when in insert mode).I have been plagued with text editor problems and have need several reboots just to get out of a file, often because it just flat out stopped responding to keyboard commands.
