Boot stopped at "Rescue mode"

Hey guys,
I've been using archlinux for a while now (laptop & homeserver). Though I got a dedicated root server (@strato) for a few reasons, I thought I'd give it a try there, too.
Yet I have to deal with a little problem, though. Installation via the 'squashfs-method' using the RecoverySystem went smoothly. But when I try to boot the maschine, it doesn't start up properly.
Below's the output of the serial console after grub. I can't see the rescue shell itself, though. Dunno if that's due to the serial attachment.
Welcome to Arch Linux!
[ OK ] Set up automount Arbitrary Executable File Formats F...utomount Point.
[ OK ] Listening on Journal Socket.
Starting Apply Kernel Variables...
Starting Journal Service...
[ OK ] Started Journal Service.
Mounting Debug File System...
Starting Setup Virtual Console...
Mounting Huge Pages File System...
Starting Create static device nodes in /dev...
Mounting POSIX Message Queue File System...
[ OK ] Reached target Encrypted Volumes.
Mounting Configuration File System...
[ OK ] Listening on udev Kernel Socket.
[ OK ] Listening on udev Control Socket.
Starting udev Coldplug all Devices...
[ OK ] Reached target Swap.
Mounting Temporary Directory...
Starting Remount Root and Kernel File Systems...
Expecting device dev-sda1.device...
[ OK ] Started Apply Kernel Variables.
[ OK ] Mounted Debug File System.
[ OK ] Started Setup Virtual Console.
[ OK ] Mounted Huge Pages File System.
[ OK ] Started Create static device nodes in /dev.
[ OK ] Mounted POSIX Message Queue File System.
[ OK ] Mounted Configuration File System.
[ OK ] Mounted Temporary Directory.
[ OK ] Started Remount Root and Kernel File Systems.
[ OK ] Started udev Coldplug all Devices.
Starting Load Random Seed...
Starting udev Kernel Device Manager...
[FAILED] Failed to start Load Random Seed.
See 'systemctl status systemd-random-seed-load.service' for details.
[ 2.685427] systemd[1]: Failed to start Load Random Seed.
[ OK ] Started udev Kernel Device Manager.
[ OK ] Reached target Local File Systems (Pre).
[ OK ] Found device M4-CT128M4SSD2.
Mounting /boot...
[ OK ] Mounted /boot.
[ OK ] Reached target Local File Systems.
Starting Recreate Volatile Files and Directories...
Starting Trigger Flushing of Journal to Persistent Storage...
[ OK ] Started Recreate Volatile Files and Directories.
Starting Update UTMP about System Reboot/Shutdown...
[ OK ] Started Update UTMP about System Reboot/Shutdown.
[ OK ] Started Trigger Flushing of Journal to Persistent Storage.
[ OK ] Reached target System Initialization.
Starting Rescue Shell...
[ OK ] Started Rescue Shell.
[ OK ] Reached target Rescue Mode.
The output states to look at the journal, but when I chroot into arch or try to look at the journal by hand, all journals are empty.
Any ideas what could be wrong? What files shall I provide for better help?
I've looked up some threads in the forum, but none of the ones I found were helping with my issue.
Thanks for your help in advance!
Cheers,
willi hunger

I've added extended logging to the console, so there are a few more things to show the errors:
[ OK ] Mounted /boot.
[ OK ] Reached target Local File Systems.
Starting Recreate Volatile Files and Directories...
Starting Trigger Flushing of Journal to Persistent Storage...
[ OK ] Started Recreate Volatile Files and Directories.
Starting Update UTMP about System Reboot/Shutdown...
[ OK ] Started Update UTMP about System Reboot/Shutdown.
[ OK ] Started Trigger Flushing of Journal to Persistent Storage.
[ OK ] Reached target System Initialization.
Starting Rescue Shell...
[ OK ] Started Rescue Shell.
[ OK ] Reached target Rescue Mode.
[ 2.915824] systemd[255]: Failed at step CHDIR spawning /bin/plymouth: No such file or directory
[ 2.934292] systemd[257]: Failed at step CHDIR spawning /bin/echo: No such file or directory
[ 2.952007] systemd[260]: Failed at step CHDIR spawning /sbin/sulogin: No such file or directory
[ 2.970414] systemd[263]: Failed at step CHDIR spawning /usr/bin/systemctl: No such file or directory
Remember, this is a fresh installation. Only the base base-devel and vim packages are installed.
Any ideas?

Similar Messages

Booting in single user mode to trouble shoot grey screen the boot stops at "CODE SIGNING .... clearing CS_VALID" will not command c past - stuck

booting in single user mode to trouble shoot grey screen the boot stops at "CODE SIGNING .......... clearing CS_VALID" - cannot command C past - just stuck

Hi opjml0,
Welcome to the Apple Support Communities!
If your Macbook is starting up to the gray screen, I suggest the steps in the following article.
Mac OS X: Gray screen appears during startup
http://support.apple.com/kb/ts2570
I hope this helps,
-Joe

Network Boot (Rescue Mode)

I need to rescue a OL5 VM guest the other day and discovered you can Network boot into rescue mode by using the following arguments in the boot string.
--args rescue http://server/pathtodistribution
Just thought I would share. You could always just mount the virtual disk on another host but to me... this is simpler and faster.

I've added extended logging to the console, so there are a few more things to show the errors:
[ OK ] Mounted /boot.
[ OK ] Reached target Local File Systems.
Starting Recreate Volatile Files and Directories...
Starting Trigger Flushing of Journal to Persistent Storage...
[ OK ] Started Recreate Volatile Files and Directories.
Starting Update UTMP about System Reboot/Shutdown...
[ OK ] Started Update UTMP about System Reboot/Shutdown.
[ OK ] Started Trigger Flushing of Journal to Persistent Storage.
[ OK ] Reached target System Initialization.
Starting Rescue Shell...
[ OK ] Started Rescue Shell.
[ OK ] Reached target Rescue Mode.
[ 2.915824] systemd[255]: Failed at step CHDIR spawning /bin/plymouth: No such file or directory
[ 2.934292] systemd[257]: Failed at step CHDIR spawning /bin/echo: No such file or directory
[ 2.952007] systemd[260]: Failed at step CHDIR spawning /sbin/sulogin: No such file or directory
[ 2.970414] systemd[263]: Failed at step CHDIR spawning /usr/bin/systemctl: No such file or directory
Remember, this is a fresh installation. Only the base base-devel and vim packages are installed.
Any ideas?

Unable to boot normal, in safe mode or from install DVD

When I walked into my office this morning and hit my keyboard to wake my Mac all I saw on the screen was a white mouse arrow and a black screen. I held down the power button to restart, it starts to boot and then stops at a gray screen telling me to hold down the power button and restart. Doing this brings me to the same screen. I have attempted the following:
Booting while holding the Shift key - this takes a bit longer but takes me to the same gray screen
Booting with the install DVD in and holding the "c" key - DVD spins a bit then gray screen
Booting while holding "option" and selecting the install DVD - DVD spins a bit then gray screen
Booting in Single User mode and ran "/sbin/fsck -fy" it returned - *** FILE SYSTEM WAS MODIFIED ***, ran it again and returned - ** The volume Macintosh HD appears to be OK
I am not sure where to go from here, and advice would be much appreciated.
Thanks,
Bob

I posted in the wrong forum, I am using 10.5, I have reposted this in that forum.

Arch boot stops on systemd-fsck

Today I upgraded my packages then I replaced catalyst package with catalyst-total after reboot the booting process stops on this line
Systemd-fsck[362]: /dev/sda5: clean etc
The sda5 is my home drive the boot stops after this line
I pressed alt+f2 to switch in CLI mode then I removed catalyst-total and installed catalyst but the booting process still stops Even when I run startx in CLI mode it gives
Unable to connect x server
The xorg log file error is
DRM report mode setting isn't supported
Unload module radeon
Devices detected but none match those in config file

Not using catalyst myself, so I'm not sure about this. But to me it looks like a conflict w/ either the radeon module or KMS. The wiki has information about this: https://wiki.archlinux.org/index.php/AM … le_at_boot
See "disable KMS" and "blacklist radeon", have you done these? Edit: Maybe recheck...
Regards
Edit2: Also maybe check whether something else is failing, either remove "quiet" from kernel parameters or check via systemctl (see systemd wiki for more information).
Last edited by rebootl (2014-05-19 22:41:15)

Rescue mode HELP

The other day I had my creative zen touch in my pocket, and when got it out it had frozen. I restarted it, but when it was restarted it went into what appears to be rescue mode (reload firmware, reboot, etc). Now every time i turn it on or reboot it goes to this rescue screen. How do I stop this and get back into my music without deleting it's Any help would be really appreciated.

If the touch has disk clean up then do that. if that does not work try reloding the firmware and if that dont wrk you might have to formate

Snow Leopard booting in unwanted Verbose mode

Hi,
Just bought a 2nd hand Mac Mini on which I clean installed Snow Leopard. Whenever I boot the screen goes black and fills with white text with information about the boot process. Verbose Mode, I presume. After the GUI comes in the Mac Mini boots and functions as normal. My question is how do I turn this off. I have tried: "sudo nvram boot-args=" to no effect. Is there another way to stop Verbose mode?

Try resetting PRAM http://support.apple.com/kb/HT1379

Zen Micro hangs up both in rescue mode and normal m

I've had my Zen Micro for about 2 months now but all of a sudden it just didn't want to start up at all (It came to the CREATIVE screen and then just stopped). Not knowing about any rescue mode, I decided to send it back to where I bought it. I got it back a few weeks later, with the message that I had to manually update firmware again but I didn't really know how I could since it wouldn't even be recognized in windows. I then came here and saw that there was this cool Rescue Mode thing. I started it up and just decided to format it all. I looked at it after 0 minutes but it was still saying "Formating all". Waited a few hours, same thing. Then I went to bed. When I woke up, the screen was blank and I thought it was done but it had just ran out of batteries. So I plugged it in and tried to start it up, but same thing with the creative screen. Then I decided to go into the rescue mode (again) and try to do the reload firmware. It have been standing at "Erasing firmware" for about 3 hours now and nothing has happened.
Should I just return it's

ey.. sad to hear that. i experienced exactly the same problem. i emailed the support team and i am attaching their reply:
Thank you for reaching us at Creative Technical Support; we appreciate
the opportunity to assist you.
As regards to your enquiry, you might wish to visit the following URL
address to download our latest driver/firmware/application for your
product.
http://asia.creative.com/support/downloads/
Select Product Type + Product Categories+ Product Name and click Next.
Once you have select your product option, select the File Type +
Language + ?Operating system and click Go
Please download the following driver/firmware/application:
. Creative Zen Micro *PlaysForSure/MTP Firmware 2.00.2 (.62 MB)
Once you have download the firmware, you might wish to try the steps
below to install the firmware.
? Ensure that the Zen Micro is turned off.
? Remove the battery.
? Move and hold the Power button to the Power On position and re-insert
the battery to the Zen Micro. Hold the Power button until the rescue
mode appears.
? The following options will be displayed:
. Clean Up (Performs a disk scan on the players harddisk)
2. Format All (Formats the players harddisk - Note: all contents will be
lost)
3. Reload OS (Reloads the Operating System on the Jukebox. Note:
Reloading your OS, will not effect the contents of the files stored on
your Zen Micro)
4. Reboot (Reboots the device).
Upon enter Media Recovery mode, please select the third option (3) to
enter Reload OS mode. The following message will appear on the Zen Micro
screen 'Easing firmware'. System will reboot into Recovery mode again
and prompt you to plug in the player to your PC to perform a firmware
upgrade.
Once you had plugged in the player, execute the firmware. Click on the
'upgrade' button to proceed with the process.
Once the process is done, the Zen Micro screen will prompt that it is
going to restart the player. Do not close the dialog or disconnect the
player form your system!
Upon player start-up, the dialog on the monitor screen will prompt you
that 'Firmware upgrade completed'. Select the close button.
Disconnect the player from your PC system and start up the player and
did you encounter with any error?
In case if you need any clarification, please do not hesitate to contact
us.
Do email back on the status concerning the issue so that I can assist
you further. Thank you.
Please retain all the previous correspondence when replying to this
email.
Best Regards
(Removed)
Technical Support
Creative Labs Asia
?
unfortunately, i was not able to try the solution they suggested cause i decided to return my unit to the shop, and it was replaced after diagnosing that it was a factory defect.
PS: Edited to remove support name. Please omit support name for future posting.Message Edited by Jason-CL on 05-27-2005 03:7 PM

Grub starts, but drops to rescue mode: 'grub_term_highlight_color'

Howdy, all;
An upgrade involving grub seemed to go well, and it included an update to grub. Ran grub-mkconfig, and rebooted.
Grub starts to load with "Welcome to Grub" before the menu loads, and then drops to rescue mode with the error:
"error: symbol 'grub_term_highlight_color' not found."
The only [solved] issue I can find is by user cfr, and the 'solution' isn't helpful: cfr writes "This is sorted though I still don't know what on Earth I did". Can't seem to find a solution in the Gentoo guides or even the Fedora forums.
If someone could point me to the right direction so I can solve this thing, I'd be grateful.
Thanks in advance!
[edited to add]: insmod linux.mod and normal.mod both kick back the same 'highlight color' error.
Last edited by fionn (2013-10-12 16:34:16)

fionn wrote:
Howdy, all;
An upgrade involving grub seemed to go well, and it included an update to grub. Ran grub-mkconfig, and rebooted.
Grub starts to load with "Welcome to Grub" before the menu loads, and then drops to rescue mode with the error:
"error: symbol 'grub_term_highlight_color' not found."
The only [solved] issue I can find is by user cfr, and the 'solution' isn't helpful: cfr writes "This is sorted though I still don't know what on Earth I did". Can't seem to find a solution in the Gentoo guides or even the Fedora forums.
If someone could point me to the right direction so I can solve this thing, I'd be grateful.
Thanks in advance!
[edited to add]: insmod linux.mod and normal.mod both kick back the same 'highlight color' error.
Did you update files in /boot/grub via grub-install? The changes i grub-mkconfig depend on updated files in /boot/grub.

BootCamp + XP not SP2 + Parallels= Refuses to boot, load CD, Firewire mode

Hi there,
Yesterday I was doing too many things at once.
Changing my HP laptop screen hinges (PC are so-so with mechanics...)
and installing Parallels on my macbook.
I was trying to get a parallel installs on a 32GB boot camp partition.
I did use Sun's Virtalbox once and it's perfectly happy with XP not being SP2
It seems that BC+// does not.
That's when the XP installer offered me a C:137GB that I new I was wrong.
I canceled the installation, hopping to boot back in osX.
I was wrong...
My Macbook is not booting at all.
I got the boot sound, the CD spins, and the drive seems to wake up too.
But I got nothing but a gray screen.
I tried to erase Pram, Reset the power manager.
I tried to "C" boot on the 10.4.10, on the 10.5 on XP and a XPsp2. Nothing works
I tried to "T" boot to get firewire mode, nada
I tried to "D" boot to get hardware mode, Question mark with no cd
nothing on screen with 10.4.1 cd inserted
I tried "Option", I got the pointer, but no partition to boot from
I tried "F1", I got a blinking world map that eventually stops blinking.
I guess there's something messed up with the EFI
If I could, I would go to an Apple Store.
The closest one from my remote Caribbean island is 2 hours flight...
Is there a secret keystroke at boot ?
Is there a way to falback on "default EFI" like there are ghost bios on PCs ?
Is there a linux distro that could help me fix this ?
Thanks.

goto: http://www.jacsoft.co.nz/TechNotes/MacKeys.shtml or Hold down the SHIFT key will boot into Safe Mode.

Zen Micro is frozen, Rescue mode not availa

Aurgh. I've had my Zen Micro since October, and it's worked well up until today. I went to power it on and it would boot up just to the Zen Micro splash screen, where it stayed. I couldn't power it off using the power button so I took the battery out several times. Each time I put it back the Micro would boot to the Zen Micro screen, but wouldn't go any further. Finally, I read how to put the player in Rescue Mode. When I boot up after taking the battery out and with the power button held, it does the exact same thing. No Rescue Mode is available, no other menu comes up.
Any ideas on how to resolve? I really don't want to send this back to Creative for repair.
Thanks-
Jennifer Portnick

Not sure if this is even possible (if it won't start up under any circumstance), but have you tried updating to the newest firmware?
http://us.creative.com/support/downloads/download.asp
Download ZenMicro_PCFW_LB__02_05_PDE.exe.
Connect your player to your computer.
Double-click (filename).
Choose your language.
Click the Upgrade button and follow the instructions that appear.</LI>

Can't boot properly in UEFI mode

Hi!
After enabling "windows 8 feature" and booting in uefi only mode, no boot device is detected anymore. The efi shell comes up after the bios has started and I can't boot into windows. I tried a clear cmos but it didn't work. I have a Z87-GD65 (latest 1.11 or 1.1B bios) and my sata devices are a crucial mx100 ssd (with windows 8.1 64-bit), western digital black hdd and asus dvd reader. I'd like to be able to boot in uefi normally. Thanks for your help!

I think I've found topic for you
https://forum-en.msi.com/index.php?topic=250729.0;topicseen
It's about notebook but installation process is actually the same

Z77A-GD65 (mostly) unable to boot usb in legacy mode

So I already made a post about this issue over in the BIOS forum back when I assumed it was something to do with the forum flash tool, but upon closer examination I was able to replicate this problem with other bootable usb sticks when I attempted to boot them in legacy mode instead of UEFI mode (and while this is viable for the Windows 8 image usb it isn't for the flash tool since when I try to boot that drive in UEFI mode it hands off to the Windows bootloader).
I am not sure where I'm going wrong here (or where to start) because this behavior doesn't seem entirely consistent and I haven't recognized any pattern in which it occurs. Basically whenever I try to boot a bootable usb device from the efi boot menu in legacy usb mode I'm presented with a black screen with a blinking white cursor in the top left corner. The inconsistency that I describe is that every so often the usb will actually boot, sometimes after only a few seconds of the blinking cursor, sometimes after leaving the screen up for an hour or so, and sometimes even if I leave the screen up overnight it still will not boot (this is what happens the majority of the time, regardless of the time interval).
I've used the "fix my stick" option in the forum tool. I've used the HP utility. Since it can be replicated across multiple usb drives I am fairly certain it isn't a geometry issue and has got something to do with my bios settings or my usb controller itself (although the only other problem I've had regarding usb is my wifi adapter only working properly on a specific port and I believe that to be unrelated).
Obviously something is amiss here. Any settings I should check out? I'm currently running no OC and I'm trying to recover my BIOS A after something went awry with the flash tool (long story as to why I was flashing in the first place, not really worth going through unless prompted...but this issue has been going on since at least early january).

I did have some issues with the ME fw at the beginning of January after a bad M-flash, but I thought I had recovered. After seeing someone with a similar problem (but with more symptoms of bad usb) had success with booting from usb after disabling the sata controller temporarily. So I've been doing that and it seems to work for now, even if it is kind of a roundabout way.

Do not upgrade to an IvyBridge processor if you need to boot into 32-bit mode with Lion

I recently upgraded to a MBP running the Ivybridge processor and tried to boot into 32-bit mode. Although it did boot after a short period (3-5 mins) it totally crashed a locked up. This was precursored by a graphics error and then the mouse cursor could be moved but nothing else could be done and it was only solved by a hard shut down (holding down the power button). Previously I had been running a MBP with the Sandybridge architecture and this booted fine into 32-bit mode and worked without a problem.
I spent a lot of time on the phone with Apple care who said they'd not had any reports of this issue and we went right though my system until they said there was nothing else they could do and I should try a re-install of Lion. I did this onto another hard-drive, booted into it and managed to get the machine to crash again... leading me to understand that it's nothing to do with my setup.
Thinking it might be an issue with my firmware on the mac today I visited an Apple store and tried booting 5 MacBook Pro's and a MacBook Air - all running IvyBridge - into 32-bit mode and managed to cause the same crash on all of them. If the machine is just booted an left with finder it didn't seem to want to crash but when I opened programs, mainly mac mail, it didn't take too much longer for the crash to occur.
If there are any Apple engineer reading this could you try and reproduce the issue and look at fixing this please as a lot of people still use 32-bit and if I'd known that the IvyBridge processors weren't going to work in 32-bit mode I would have stayed with the Sandybridge MBPs.
Many Thanks,
Adam Peters,

That is a pain then. Pretty much all of the OS included applications (finder, Mail, iTunes, Safari,...) are all fully 64-bit programs now (since Lion) so I can see where launching them when booted into 32-bit mode could cause stability issues.
If you boot into 32-bit mode and just run the Tascam software without launching anything else, will it work?
Was it alright in 10.6? And if so, how about keeping 10.6 in a virtual machine or on a separate disc or partition?

ALWAYS BOOTS UP IN SAFE MODE

MY MAC ALWAYS BOOTS UP IN SAFE MODE. I REPLACED THE KEYBOARD DUE TO A JAMMED SHIFT KEY WHICH WAS CAUSING IT TI DO THE SAME THING, BUT ITS DOIN IT AGAIN. CAN SOMEONE HELP PLEASE?

ACTUALLY IT BOOTS THE RIGHT WAY IF I LEAVE THE KEYBOARD OFF UNTIL THE SIGN IN SCREEN COMES UP. AND YES IT IS A WIRELESS. IF I TURN THE KEYBOARD ON BEFORE I TURN THE COMPUTER ON IT WILL BOOT IN SAFE MODE. IS THERE ANYTHING ELSE THAT I CAN TRY, OR SHOULD I JUST SAY FORGET IT, AND WAIT UNTIL THE SIGN IN SCREEN COMES UP BEFORE I CUT IT ON?

Boot stopped at "Rescue mode"

Similar Messages

Maybe you are looking for