[SOLVED] Kernel will not boot after update to 3.1.5

Not sure what went wrong here. Pacman seemed to hang when updating, so I CTRL-C'd it and restarted the upgrade. It seemed to complete properly. That was a few hours ago and I did not immediately reboot the computer but went on with my work instead. After rebooting the laptop I get this
***normal boot up to this :
Running Hook [uresume]
resume libgcrypt version: 1.5.0
resume: Could not stat the resume device file '/dev/sda4'
Please type in the full path name to try again or press ENTER to boot the system: _
Pressing ENTER at this point results in mean looking error message :
ERROR : Unable to determine major/minor number of root device '/dev/sda4'
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty: job control turned off
[ramfs /]# _
**typing exit**
Trying to continue (this will most likely fail)...
mount: you must specify the filesystem type
You are being dropped into an emergency shell
sh: can't access tty: job control turned off
[ramfs /]# _
Did I somehow ruin my install or is there something I can do?
EDIT : Oh and it can still boot the windows partition, so it's not likely due to defective hardware.
Last edited by bolshevik (2011-12-16 14:31:19)

bolshevik wrote:
Not sure what went wrong here. Pacman seemed to hang when updating, so I CTRL-C'd it and restarted the upgrade. It seemed to complete properly. That was a few hours ago and I did not immediately reboot the computer but went on with my work instead. After rebooting the laptop I get this
***normal boot up to this :
Running Hook [uresume]
resume libgcrypt version: 1.5.0
resume: Could not stat the resume device file '/dev/sda4'
Please type in the full path name to try again or press ENTER to boot the system: _
Pressing ENTER at this point results in mean looking error message :
ERROR : Unable to determine major/minor number of root device '/dev/sda4'
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty: job control turned off
[ramfs /]# _
**typing exit**
Trying to continue (this will most likely fail)...
mount: you must specify the filesystem type
You are being dropped into an emergency shell
sh: can't access tty: job control turned off
[ramfs /]# _
Did I somehow ruin my install or is there something I can do?
EDIT : Oh and it can still boot the windows partition, so it's not likely due to defective hardware.
If you foolishly interrupted the initramfs creation after a kernel upgrade and didn't regenerate it manually, you earned this.
You'll need to find a live CD so you can chroot to your install and rerun mkinitcpio.

Similar Messages

Will not boot after updates

I have a macbook air. It is running Lion. After updates it will not boot. It starts installing updates and just stops all together. Any help would be very welcome.

Hey bfa67,
Thanks for the question. To isolate the issue, what happens when you start up in Safe Mode?:
OS X: What is Safe Boot, Safe Mode?
http://support.apple.com/kb/HT1564
Thanks,
Matt M.

[SOLVED] Kernel will not boot. No early hooks, nothing...

I am having some serious trouble getting my machine to boot. It never even gets to ":: running early hooks (udev)."
I normally shut it down every night, but I recently kept in on for a few days straight. I was having some trouble with a USB flash drive being read-only in Windows 8 in VirtualBox. I shut down Windows 8 and then arch wouldn't even read the flash drive. I'm pretty sure that pacman updated the kernel since I last shut down the machine, so I decided to restart just for good measure. I never got back in...
I am UEFI booting, running LVM on top of LUKS on top of two Samsung 830 256GB SSDs in mdadm raid 0. I have encrypted root and no swap. I have /boot mounted on a 512MB FAT32 partition and use a straight efibootmgr entry to start the system. It has worked fine until today.
My mkinitcpio.conf has
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are run. Advanced users may wish to specify all system modules in this array.
MODULES="ahci dm_mod dm_crypt aes_x86_64 raid0"
# BINARIES
# This setting includes any additional binaries a given user may wish into the CPIO image. This is run last, so it may be used to override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added as-is and are not parsed in any way. This is useful for config files.
# Some users may wish to include modprobe.conf for custom module options like so:
# FILES="/etc/modprobe.d/modprobe.conf"
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS="base udev autodetect pata scsi sata filesystems"
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
## ORIGINAL ##HOOKS="base udev autodetect pata scsi sata filesystems usbinput fsck"
HOOKS="base udev autodetect sata mdadm usbinput keymap encrypt lvm2 filesystems fsck shutdown"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""
My kernel parameters are
cryptdevice=/dev/md1:RootVault root=/dev/RootArray/VolRoot ro rootfstype=ext4 init=/bin/systemd add_efi_memmap initrd=initramfs-linux.img
I can boot fine from the Arch install media via UEFI at which point I can luksOpen, activate the lvm volumes, mount everything, and chroot in like normal. I have:
rebuilt the initramfs
reinstalled linux, mkinitcpio, and udev
erased and recreated the efibootmgr entry
tried to boot straight from the UEFI shell
slimmed down to minimal hooks in mkinitcpio
tried nomodeset and mem=4G kernel parameters
tried booting the kernel with debugging enabled at various levels
I get nothing at all every time. I boot up to a black screen with a static white cursor in the top left.
I am happy to offer any more necessary information and I would be extremely grateful for any suggestions. Thanks.
Last edited by matthew02 (2012-11-02 15:14:46)

lesto wrote:
same problem here with a stock kernel. solver rolling back to 3.6.3-1 by livecd.
seems a problem with AMD cpu. solution here https://bbs.archlinux.org/viewtopic.php?id=151686
I had just rolled back my kernel and was about to comment here that it worked when I saw your post. I had actually skimmed that other post, but since mem=4G didn't work for me, I didn't figure it applied. I suppose I should have read it more thoroughly. Thanks for the help everyone!

Macbook Will Not Boot After Updating Leopard

I just reinstalled Leopard after having some trouble with my partition tables, and everything ran smoothly and worked fine. After the install I let software update update everything including the 10.5.5 update. It prompted me to reboot, and when I did it got to the grey Apple screen and the thing spun for about 30 seconds before it restarted and did it again. This happened a few times and then I booted from a Leopard disk to look at disk permissions and they seem to be fine. Anyone have any idea why this is happening or how I would fix it?
Thanks in advance, hope to get this sorted out quickly, I thought I had finally gotten my computer working fine again when I reinstalled Leopard. :P

At start up, press 'C' to boot directly from a CD/DVD. Or, you can press 'Option' and you should get a list of bootable selections (CD/DVD, external hardrives) that you can boot from - assuming you have something that IS bootable.
I recently had a problem and ended up reinstalling my OS (via TimeMachine). I also confirmed that you can boot from your original OSX install disk. As part of this process I also discovered I could NOT boot directly FROM the AppleCare provided TechTools Deluxe disk. Supposedly you can boot INTO that disk via a restart but that seems kind of silly to me.
However, if you have signed up for AppleCare and go to the Apple Support web site, you can download TechTools Deluxe and it can be made bootable by burning the .dmg file via Apple Disk Utilities. I don't understand Apple logic of not making the provided AppleCare TechTools Deluxe disk bootable.

IMac, 2010, will not boot after update

After downloading Yosemite, my 2010, 27" iMac will not reboot. It appeared to install ok but it stayed white screen, no text for more than an hour after it automatically rebooted. Idaes?

Take each of these steps that you haven't already tried. Stop when the problem is resolved.
To restart an unresponsive computer, press and hold the power button for a few seconds until the power shuts off, then release, wait a few more seconds, and press it again briefly.
Step 1
The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
Step 2
If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
Step 3
Sometimes a startup failure can be resolved by resetting the NVRAM.
Step 4
If a desktop Mac hangs at a plain gray screen with a movable cursor, the keyboard may not be recognized. Press and hold the button on the side of an Apple wireless keyboard to make it discoverable. If need be, replace or recharge the batteries. If you're using a USB keyboard connected to a hub, connect it to a built-in port.
Step 5
If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
Step 6
Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
Step 7
If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
Start up in safe mode. Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Post for further instructions.
Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.
If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
Step 8
Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
Step 9
If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.
Step 10
Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
Step 11
Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
Step 12
This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
Step 13
If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

[Solved] xorg will not start after update

Hi there,
I updated Arch and when I restarted my computer lightdm did not start. I ran systemctl disable lightdm.service and I was able to boot up to a command prompt and login. I tried to start xorg-server by running startx (my .xinitrc file has exec mate-session in it) and I got an error. Here is my xorg log...
[ 137.060]
X.Org X Server 1.17.1
Release Date: 2015-02-10
[ 137.104] X Protocol Version 11, Revision 0
[ 137.118] Build Operating System: Linux 3.18.6-1-ARCH x86_64
[ 137.133] Current Operating System: Linux watchtower 3.19.2-1-ARCH #1 SMP PREEMPT Wed Mar 18 16:21:02 CET 2015 x86_64
[ 137.133] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=04918701-88f8-4f79-ab8d-0c0177e45fef rw quiet
[ 137.161] Build Date: 14 March 2015 06:45:50PM
[ 137.174]
[ 137.187] Current version of pixman: 0.32.6
[ 137.213] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 137.213] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 137.265] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar 25 20:01:44 2015
[ 137.278] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[ 137.278] (==) No Layout section. Using the first Screen section.
[ 137.278] (==) No screen section available. Using defaults.
[ 137.278] (**) |-->Screen "Default Screen Section" (0)
[ 137.278] (**) | |-->Monitor "<default monitor>"
[ 137.278] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 137.278] (==) Automatically adding devices
[ 137.278] (==) Automatically enabling devices
[ 137.278] (==) Automatically adding GPU devices
[ 137.278] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/OTF/".
[ 137.278] Entry deleted from font path.
[ 137.278] (Run 'mkfontdir' on "/usr/share/fonts/OTF/").
[ 137.278] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 137.278] Entry deleted from font path.
[ 137.278] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 137.278] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 137.278] Entry deleted from font path.
[ 137.278] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 137.278] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 137.278] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 137.278] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 137.278] (II) Loader magic: 0x815d80
[ 137.278] (II) Module ABI versions:
[ 137.278] X.Org ANSI C Emulation: 0.4
[ 137.278] X.Org Video Driver: 19.0
[ 137.278] X.Org XInput driver : 21.0
[ 137.278] X.Org Server Extension : 9.0
[ 137.280] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c1
[ 137.280] (--) PCI:*(0:1:0:0) 10de:1380:1462:8a9b rev 162, Mem @ 0xf6000000/16777216, 0xe0000000/268435456, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 137.280] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 137.280] (II) LoadModule: "glx"
[ 137.280] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 137.286] (II) Module glx: vendor="NVIDIA Corporation"
[ 137.286] compiled for 4.0.2, module version = 1.0.0
[ 137.286] Module class: X.Org Server Extension
[ 137.286] (II) NVIDIA GLX Module 346.47 Thu Feb 19 18:09:07 PST 2015
[ 137.286] (==) Matched nouveau as autoconfigured driver 0
[ 137.286] (==) Matched nv as autoconfigured driver 1
[ 137.286] (==) Matched modesetting as autoconfigured driver 2
[ 137.286] (==) Matched fbdev as autoconfigured driver 3
[ 137.286] (==) Matched vesa as autoconfigured driver 4
[ 137.286] (==) Assigned the driver to the xf86ConfigLayout
[ 137.286] (II) LoadModule: "nouveau"
[ 137.286] (WW) Warning, couldn't open module nouveau
[ 137.286] (II) UnloadModule: "nouveau"
[ 137.286] (II) Unloading nouveau
[ 137.286] (EE) Failed to load module "nouveau" (module does not exist, 0)
[ 137.286] (II) LoadModule: "nv"
[ 137.287] (WW) Warning, couldn't open module nv
[ 137.287] (II) UnloadModule: "nv"
[ 137.287] (II) Unloading nv
[ 137.287] (EE) Failed to load module "nv" (module does not exist, 0)
[ 137.287] (II) LoadModule: "modesetting"
[ 137.287] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[ 137.287] (II) Module modesetting: vendor="X.Org Foundation"
[ 137.287] compiled for 1.17.1, module version = 1.17.1
[ 137.287] Module class: X.Org Video Driver
[ 137.287] ABI class: X.Org Video Driver, version 19.0
[ 137.287] (II) LoadModule: "fbdev"
[ 137.287] (WW) Warning, couldn't open module fbdev
[ 137.287] (II) UnloadModule: "fbdev"
[ 137.287] (II) Unloading fbdev
[ 137.287] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 137.287] (II) LoadModule: "vesa"
[ 137.287] (WW) Warning, couldn't open module vesa
[ 137.287] (II) UnloadModule: "vesa"
[ 137.287] (II) Unloading vesa
[ 137.287] (EE) Failed to load module "vesa" (module does not exist, 0)
[ 137.287] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 137.287] (++) using VT number 1
[ 137.287] (--) controlling tty is VT number 1, auto-enabling KeepTty
[ 137.287] (EE) open /dev/dri/card0: No such file or directory
[ 137.287] (WW) Falling back to old probe method for modesetting
[ 137.287] (EE) open /dev/dri/card0: No such file or directory
[ 137.287] (EE) Screen 0 deleted because of no matching config section.
[ 137.287] (II) UnloadModule: "modesetting"
[ 137.287] (EE) Device(s) detected, but none match those in the config file.
[ 137.287] (EE)
Fatal server error:
[ 137.287] (EE) no screens found(EE)
[ 137.287] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 137.287] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 137.287] (EE)
[ 137.367] (EE) Server terminated with error (1). Closing log file.
It looks like it's trying to start the nouvea driver. The thing is I'm using the proprietary nvidia driver. Any help would be appreciated. Thanks.
EDIT:
Okay, making progress... I ran sudo modprobe nvidia and my driver loaded. I ran startx and xorg-server started, Hooray! Then my desktop opened and..... froze. Ctl-Alt-F1 did not open another tty, everything was completely frozen. I had to hit the restart switch. Any ideas?
Last edited by necbot (2015-03-27 23:54:13)

Okay, I'm not really sure what I did to fix the problem, but it seems to have gone away. I rebooted a few times and had to manually load my nvidia driver using modprobe in order to start xorg-server. My system would still freeze though, then I installed the nouveau driver and started using that and the freezes stopped. I reinstalled the nvidia driver and... everything seems to work fine. I reenabled lightdm service and my desktop loaded with no errors and there have been no system freezes. ????????????? I have no idea why that worked.
Last edited by necbot (2015-03-27 23:55:17)

Server will not boot after update !! Help needed fast !!

I have a new (Aug 2005) XServe G5, running 4.3.
Active Directory integrated, stores home folders (AFP), manages preferences and 5 print queues for 55 Mac OS X.4.3 clients and 200 users.
It downloaded the 4.4 update, unchecked the OS 4.4 update (I think was my first mistake), restarted. Now, at boot up, about the moment the apple would appear (maybe it appears for a split second) all I get is the ugly not sign.
-- Am able to boot to external firewire drive
-- Drive shows as boot option
-- Disk repair reported no problems to fix
-- Can not find any log entries after last shut down. No service ever starts for any entries to be made.
-- Applied the 4.4 update successfully while booted from external fw drive, no effect. Startup disk reports system to be OS X Server 4.4 and lists as a boot option.
-- Drive behaves same when transferred to my G5 tower: big not sign.
What other steps can I do to troubleshoot this boot problem? If I don't get this server up this weekend, I'll get roasted by an angry mob.
Any suggestions are welcomed and greatly appreciated.

Eeh...
Always clone the existing system prior to updating it. Do so when the server is not in use, shut off services where possible (you want it to be as quiescent as possible).
Mike Bombich (at Apple) describes how you can do this via the command-line, which I prefer for this purpose (you can stagger the process):
http://www.bombich.com/mactips/image.html
Now then:
Have you booted from the install CD and used Disk Utility to run Repair Permissions ? That should be your first step.
It may change nothing, but can you boot into Safe mode ? Hold down the Shift key at powerup and keep holding it until you see: "Safe boot"
If you CAN get it booted in that state, then run the 10.4.4 COMBO updater
you need to run the combo updater at this point. After doing so, use Disk Utility to run repair permissions on the boot drive itself, and then reboot.
Otherwise, start it in Target Disk Mode as you did before, connect it to a unit running 10.4.4, and run the /combo/ 10.4.4 Server updator (NOT client, of course) onto the server's mounted hard drive.
I'm not sure you can do this while running 10.4.x client. You may need to do a quick install of 10.4 server (say onto a Firewire drive), boot your spare Mac from it, and -then- mount the server via Firewire target mode, and apply the 10.4.4 server combo updater.
Good luck !

Macbook (Black) Will Not Boot After Update (grey screen of non-booting)

I bought my first MacBook less than one month ago.
Last night at 9pm the apple update software said there was an update and I should restart. It has not been able to boot since.
Now, when the computer turns on it shows a grey screen with a dark grey apple logo for a few minutes, then turns off again.
I am completely lost, any help would be greatly appreciated.
Thank you for your time.
Chris Albon

Sorry to hear about your troubles Chris.
Was this a System/Security update you installed or just for an application? Personally, I never install anything system related without first running a 3rd party Disk Utility like DiskWarrior. It's important to ensure that there are no latent issues before doing so. That being said, if you don't have access to DW, try booting up from your OSX installation DVD (insert the disk and hold down the 'C' key on startup) and choose Disk Utility's disk repair option from the file menu once it's loaded. Post back once you've tried this.

HP Pavilion 500 (desktop) will not boot after updating driver's.

Working on my mothers CPU but I cant seem to get past this screen now
This was after I had downloaded and installed drivers from this site. I cant seem to figure out why it is not going in to windows xp. Any ideas? It also was giving me a fan error which was easy to fix but cant seem to figure this out.

wow no one can help I guess everyone is duped as I am. DaRN HP

HP Pavilion 15-n268sa will not boot after windows update (windows 8.1)

After a series of windows update (windows 8.1) my HP Pavilion 15-n268sa will not boot up, no fan noises, no lights no nothing.
I have tried a "hard reset" a number of times with no success.
When the battery is present the white LED flashes 3 times when the power button is pressed.
Please please help.

Hello Cuffy,
Welcome to the HP Forums!
I understand you notebook will not boot after a series of Windows updates.
Can you tell me if you are able to access the HP Recovery Manager by repeatedly tapping the F11 key while the notebook turns on? If you can access this, try doing a system restore to before you installed the updates. If not I would suggest you go through this document: Computer Does Not Start and the LEDs Blink or the Computer Beeps.
If it's the Caps Lock light that is blinking this document will tell you exactly what the error is (spoiler: 3 beeps is a memory failure). This could also explain the failed updates. The updates are stored in the RAM before being applied to the operating system.
You can try reseating the RAM, or using only 1 of the RAM cards, as you have 2x4GB cards. If it still doesn't work with 1 card, try the other card to confirm it has failed.
You can replace defective cards via HP Phone Support if covered under warranty or at the HP Part Store if not covered. You can contact HP Technical Support at 1-800-474-6836 in North America. For all other regions click here.
Hopefully this information helps!
Please click the "Kudos, Thumbs Up" at the bottom of this post if you want to say "Thanks" for helping!
Please click "Accept as Solution" if you feel my post solved your issue, it will help others find the solution.
The Great Deku Tree
I work on behalf of HP.

Mac Mini will not boot after Security Update 2008-007

Hello,
A G4 Mac Mini machine I was asked to take a look at will not boot after the owner (succesfully) installed Security Update 2008-007 from Software Update. Booting always hangs at the blue screen after the Apple logo, and booting in verbose mode reveals that WindowServer is crashing repeatedly. Permissions and filesystems have been repaired, PRAM reset, etc. Safe boot also exhibits the same problem, but it is possible to boot to single user mode. Hardware checks out fine with diagnostic utilities.
Any suggestions on how to fix this? Unfortunately, backups are not available (it's not my machine =).

Hi Arkku , and a warm welcome to the forums!
I'd certainly give Sig's advice a try first.
If that should fail...
applesetupdone...
This was Posted by: JoseAranda at September 9, 2006 3:48 AM
"OK, restart your computer, hold down Command-s and type in the following:
/sbin/fsck -fy Enter
/sbin/mount -uaw Enter
rm /var/db/.applesetupdone Enter
# The rm command is the remove command which deletes the file.
# Robert: I'd rename the file via: mv /var/db/.applesetupdone /var/db/.applesetupdone.old
reboot Enter
Once you've done that the computer reboots and it's like the first time you used the machine. Your old accounts are all safe. From there you just change all other account passwords in the account preferences!!
end of posted by: JoseAranda"
Reset OS X Password Without an OS X CD...
http://theappleblog.com/2008/06/22/reset-os-x-password-without-an-os-x-cd/

MacBook Pro will not boot after software update

MacBook Pro will not boot after doing an Apple Software Update (of course they will not help you). MONEY, MONEY, MONEY is the name of the game. They can cause your computer to crash and still charge you!
Does anyone have an answer to why my computer is showing a little gear spinning for hours? I have tried several things with NO luck.
Thanks-

Run through the list of fixes here
Step by Step to fix your Mac

MBP 17" will not restart after updating Java... why?

MBP 17" will not restart after updating Java...why?
It would actually try to restart for about 10-15 seconds but would quit and then shut down. Tried using P_R_Command_Options but that too failed and again it just shut down. Tried using D at startup which ran a test of the hard drive. No issues there which tells me there's a software problem.
Can any one help?

Disk Utility suggest reformating
Reformatting is not a Recovery Aid. When Disk Utility suggests reformatting, it is because it considers your drive unsalvageable. Yes, you lose all the data on the drive when you reformat.
And yes, Mac OS X Extended, journaled is the method you will need for a Mac OS X Boot drive.
You should also consider buying a replacement drive to have on hand the next time this internal drive gives you the slightest bit of trouble. Possibly an external enclosure to put it in as well. and it would not hurt to go ahead and Install Mac OS X on it and try booting from it, to make sure it is ready.
And make sure your Backups are current, as the next time that internal drive screws up you may get no warning whatsoever.

HT4623 iPhone 4s will not boot after trying to install ios7 beta 4. Stops at apple logo with progress line under it. how can I reset it or get it back up to do a restore then try the iOS 7 beta 4 install again. Issue was probably caused by disconnection

iPhone 4s will not boot after trying to install ios7 beta 4. Stops at apple logo with progress line under it. how can I reset it or get it back up to do a restore then try the iOS 7 beta 4 install again. Issue was probably caused by disconnection

Obviously since you have iOS 7 you're a developer. As a developer, you signed a NDA with Apple not to discuss the iOS on a public forum. Please log in to the Developer Forum using your credentials and ask for help there, lest you risk having your credentials terminated.
Thanks, and best of luck to you.
GDG

X240 will not boot after latest bios update

I bought windows 8 .1 machine from factory. Then I had local shop install 8.1 on larger ssd. I just performed latest bios update and now machine will not boot. I am sure this is uefi related but I am not knowledgable in that area. The boot parameter returned to me by the shop was "legacy only" and secure boot was disabled.
Solved!
Go to Solution.

StanFan wrote:
I bought windows 8 .1 machine from factory. Then I had local shop install 8.1 on larger ssd. I just performed latest bios update and now machine will not boot. I am sure this is uefi related but I am not knowledgable in that area. The boot parameter returned to me by the shop was "legacy only" and secure boot was disabled.
Since doing the BIOS update are the settings still as you noted above? You also didn't mention which SSD is now installed in the system.
Just as an aside, installing Windows 8.1 in legacy mode isn't exactly optimal. Were there any particular reasons for this? Just being curious.
Andy ______________________________________
Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
Deutsche Community Comunidad en Español English Community Русскоязычное Сообщество
PepperonI blog

[SOLVED] Kernel will not boot after update to 3.1.5

Similar Messages

Maybe you are looking for