Gray screen after login - Cinnamon 2.2/Nvidia 334
I did a -Syu, saw the new Cinnamon. I then proceeded to snapshot my btrfs root vol, and went ahead with the upgrade. Rebooted, no desktop, just a gray screen with the pointer. I then booted off my install media, and mv'ed my snapshot back to replace my /
Unfortunately, that still somehow didn't fix it, which makes me think a conf is borked in my home dir (not in the snapshot). Nothing in the system journal.
Any ideas?
So, I added the following to pacman.conf -
IgnorePkg = cinnamon* muffin* nemo*
and this is the list of packages I allowed to upgrade -
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
infinality-bundle is up to date
infinality-bundle-multilib is up to date
Foreign packages: / 29 / 29
==> Package upgrade only (new release):
core/libsystemd 212-2 2 -> 3
core/systemd 212-2 2 -> 3
core/logrotate 3.8.7-1 1 -> 3
core/mlocate 0.26-1 1 -> 3
core/shadow 4.1.5.1-7 7 -> 9
core/systemd-sysvcompat 212-2 2 -> 3
extra/mesa 10.1.0-4 4 -> 5
extra/pango 1.36.3-1 1 -> 2
extra/clutter-gst 2.0.10-1 1 -> 2
extra/gthumb 3.2.7-1 1 -> 2
extra/libreoffice-en-US 4.2.3-1 1 -> 2
extra/libreoffice-common 4.2.3-1 1 -> 2
extra/libreoffice-base 4.2.3-1 1 -> 2
extra/libreoffice-calc 4.2.3-1 1 -> 2
extra/libreoffice-draw 4.2.3-1 1 -> 2
extra/libreoffice-gnome 4.2.3-1 1 -> 2
extra/libreoffice-impress 4.2.3-1 1 -> 2
extra/libreoffice-math 4.2.3-1 1 -> 2
extra/libreoffice-writer 4.2.3-1 1 -> 2
extra/pkgstats 2.3-3 3 -> 5
extra/polkit 0.112-1 1 -> 2
==> Software upgrade (new version) :
core/glib2 2.38.2-1 -> 2.40.0-1
core/device-mapper 2.02.105-2 -> 2.02.106-1
core/iproute2 3.12.0-1 -> 3.14.0-1
core/linux 3.14-4 -> 3.14.1-1
core/lvm2 2.02.105-2 -> 2.02.106-1
core/man-db 2.6.6-1 -> 2.6.7.1-1
extra/at-spi2-core 2.10.2-1 -> 2.12.0-1
extra/atk 2.10.0-1 -> 2.12.0-1
extra/at-spi2-atk 2.10.2-1 -> 2.12.0-1
extra/gobject-introspection 1.38.0-1 -> 1.40.0-1
extra/gdk-pixbuf2 2.30.6-1 -> 2.30.7-1
extra/cogl 1.16.2-1 -> 1.18.0-1
extra/json-glib 0.16.2-1 -> 1.0.0-1
extra/clutter 1.16.4-3 -> 1.18.0-1
extra/gtk-update-icon-cache 2.24.22-1 -> 2.24.23-1
extra/libcups 1.7.1-4 -> 1.7.2-1
extra/gtk3 3.10.7-1 -> 3.12.1-1
extra/clutter-gtk 1.4.4-4 -> 1.5.2-1
extra/cups 1.7.1-4 -> 1.7.2-1
extra/dconf 0.18.0-1 -> 0.20.0-1
extra/gnome-icon-theme-symbolic 3.10.1-1 -> 3.12.0-1
extra/gnome-icon-theme 3.10.0-1 -> 3.12.0-1
extra/libsecret 0.16-2 -> 0.18-1
extra/gsettings-desktop-schemas 3.10.1-1 -> 3.12.0-1
extra/evince 3.10.3-1 -> 3.12.1-1
extra/file-roller 3.10.2.1-1 -> 3.12.1-1
extra/fontsproto 2.1.2-1 -> 2.1.3-1
extra/gcr 3.10.1-3 -> 3.12.0-1
extra/gtksourceview3 3.10.2-1 -> 3.12.1-1
extra/libpeas 1.9.0-2 -> 1.10.0-1
extra/pygobject-devel 3.10.2-2 -> 3.12.0-1
extra/python-gobject 3.10.2-2 -> 3.12.0-1
extra/gedit 3.10.4-2 -> 3.12.1-1
extra/gnutls 3.2.13-1 -> 3.3.0-1
extra/glib-networking 2.38.2-1 -> 2.40.1-1
extra/gnome-common 3.10.0-1 -> 3.12.0-1
extra/gnome-keyring 3.10.1-2 -> 3.12.0-1
extra/gnome-screenshot 3.10.1-1 -> 3.12.0-1
extra/gnome-themes-standard 3.10.0-1 -> 3.12.0-1
extra/libsoup 2.44.2-1 -> 2.46.0-1
extra/xorg-server-common 1.15.0-5 -> 1.15.1-1
extra/xorg-server 1.15.0-5 -> 1.15.1-1
extra/nvidia-utils 334.21-7 -> 337.12-1
extra/nvidia-libgl 334.21-7 -> 337.12-1
extra/webkitgtk 2.2.5-2 -> 2.4.0-1
extra/gtk2 2.24.22-1 -> 2.24.23-1
extra/gucharmap 3.10.1-1 -> 3.12.0-1
extra/gvfs 1.18.3-3 -> 1.20.1-2
extra/libplist 1.10-1 -> 1.11-1
extra/libimobiledevice 1.1.5-2 -> 1.1.6-1
extra/gvfs-afc 1.18.3-3 -> 1.20.1-2
extra/gvfs-mtp 1.18.3-3 -> 1.20.1-2
extra/gvfs-smb 1.18.3-3 -> 1.20.1-2
extra/lcms2 2.5-2 -> 2.6-1
extra/imagemagick 6.8.8.9-1 -> 6.8.9.0-1
extra/js 17.0.0-1 -> 24.2.0-1
extra/libgee 0.12.0-1 -> 0.14.0-1
extra/libgnome-keyring 3.10.1-2 -> 3.12.0-1
extra/libtracker-sparql 0.16.4-1 -> 1.0.0-2
extra/nvidia 334.21-4 -> 337.12-1
extra/python2-gobject 3.10.2-2 -> 3.12.0-1
extra/python2-atspi 2.10.0-2 -> 2.12.0-1
extra/upower 0.9.23-2 -> 0.99.0-2
extra/usbmuxd 1.0.8-2 -> 1.0.9-1
extra/vte-common 0.34.9-1 -> 0.36.0-1
extra/vte3 0.34.9-1 -> 0.36.0-1
extra/webkitgtk2 2.2.5-2 -> 2.4.0-1
extra/xproto 7.0.25-1 -> 7.0.26-1
community/cjs 2.0.0-1 -> 2.2.0-1
community/python2-pillow 2.3.1-2 -> 2.4.0-1
multilib/lib32-pcre 8.34-1 -> 8.35-1
multilib/lib32-glib2 2.38.2-1 -> 2.40.0-1
multilib/lib32-nvidia-utils 334.21-5 -> 337.12-1
multilib/lib32-nvidia-libgl 334.21-5 -> 337.12-1
aur/jdk7 7.51-2 -> 7.55-1
==> New package :
extra/libinput 0.1.0-1 (required by clutter)
extra/libusbmuxd 1.0.9-1 (required by libimobiledevice)
extra/js17 17.0.0-1 (required by polkit)
and I still had the same issue with the gray screen after login.
Last edited by madscience (2014-04-16 15:02:33)
Similar Messages
-
Gray screen after loading Yosemite
Hi. Have problem with Yosemite after 10.10.2 update from appstore. My MacBook restart and on 30-50% l see gray screen and no more, it's freeze after login or before. I can't go to recovery mode, can't install/ reinstall Yosemite.
On cmd+r - didn't see anything, just load
on shift - the same
on alt+cmd+r+p - restart and again great freeze screen
on alt - I see my hdd and ssd, if I input usb with Yosemite , I see this usb, no more.
On click on usb with Yosemite I see loading and gray screen after all of this..
If I inset second monitor, on MacBook freeze I see vertical lines. Red-green-blue-white vertical lines on all monitor
Please help me. I need work...Install Mavericks, Lion/Mountain Lion Using Internet Recovery
Be sure you backup your files to an external drive or second internal drive because the following procedure will remove everything from the hard drive.
Boot to the Internet Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND-OPTION- R keys until a globe appears on the screen. Wait patiently - 15-20 minutes - until the Recovery main menu appears.
Partition and Format the hard drive:
Select Disk Utility from the main menu and click on the Continue button.
After DU loads select your newly installed hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the process has completed. Quit DU and return to the main menu.
Reinstall Lion/Mountain Lion. Mavericks: Select Reinstall Lion/Mountain Lion, Mavericks and click on the Install button. Be sure to select the correct drive to use if you have more than one.
Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.
This should restore the version of OS X originally pre-installed on the computer. -
SAP BPC 10.0 Web Client Blank Screen after login
Hi ALL,
We are using SAP BPC 10.0 Web Client with Adobe Flash Player 13.0.0.214 with IE 9.0 on Windows 7.0.
We face strange error where on only on certain PC, the BPC web client working.. On other getting Blank/Blank Screen after login (with "movie not loaded" on the adobe flash player).. Both PCs are having the same setting.
Even one of PC which previously working, starting this week suddenly getting the same error.. I have created OSS message and got feedback with also share this problem on this forum.
I have done several actions as mentioned on several SAP notes )1624267, 1664889, 1681147, 1694871, 1752971, 1798336, 1804221, 1806371, 1811218, 1820505, 1918631, 1968584), but still no luck..
If you have the same issue, kindly share..
Thanks and regards,
HeryYes .. Compatibility View also checked.. in several PCs, it is working well. both failed and working PCs have the same setting.
Just found another weird: in one working PC, 2 different windows local-admin users login to the same PC for BPC-web and getting different result (1 Ok ; 1 failed) ..seems it is related with the user profile and login-domain servers (we have multiple login-domain servers with load balancing mechanism).
Thanks and regards,
Hery -
Mavericks white screen after login
After upgrading to Mavericks my MacBook now goes to a white screen after login screen. Anybody having same issue? Any solutions?
Reinstalling Mavericks, Lion/Mountain Lion Without Erasing the Drive
Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu.
Reinstall Lion/Mountain Lion, Mavericks: Select Reinstall Lion/Mountain Lion, Mavericks and click on the Continue button.
Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless. -
Hi all,
I understand APO is diff. from R/3 .If so,does SAP APO menu has only functionality in APO, or if the main screen after login has all modules (HR accounting etc)?
Thanks.Somnath
Doesn't SAP Marketing manage to confuse everyone, even those who have been using it for 10 years or more!
Just to help clarify for Sona:
Supply Chain Management (or SAP SCM) is split into three parts:
Planning: which is mainly what us older consultants refer to as SAP APO
Execution: Mostly the ECC part and includes what used to be referred to in modular terms as SD, MM, PP,etc
Collaboration: The old ITS server web-portal stuff with suppliers and customers
The term SCM covers all of the above but requires several different servers and systems to give a complete solution.
Have a look at the SAP website to give you an overview of how this all fits together.
[SAP SCM Website|http://www.sap.com/solutions/business-suite/scm/index.epx]
Regards
Ian -
TS2570 white screen after login
i have a white screen after login on my macbook pro 17' what does that mean?
i cant do anything but all the users are accesable
no finder no desktop... nothingReinstall Lion, Mountain Lion, or Mavericks without erasing drive
Boot to the Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Repair
When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported then click on the Repair Permissions button. When the process is completed, then quit DU and return to the main menu.
Reinstall Lion, Mountain Lion, or Mavericks
OS X Mavericks- Reinstall OS X
OS X Mountain Lion- Reinstall OS X
OS X Lion- Reinstall Mac OS X
Note: You will need an active Internet connection. I suggest using Ethernet
if possible because it is three times faster than wireless. -
Blue screen after login and HD and startup disk is full -how to erase data?
Blue screen after login and Hard drive and startup disk is full -How do I get in to erase data?
this user tip might help:
Your Mac needs adequate hard drive space to operate normally. How full can a drive be before it's too full? There is no hard and fast rule that says “X” amount or “%” of free drive space is needed. A low amount of RAM requires more drive space for Virtual Memory’s swap files.
Problems from insufficient RAM and free hard disk space are discussed in this link
http://www.thexlab.com/faqs/lackofram.html
Here’s some general guidelines for minimum hard drive free space:
1. As a general rule, your available space should be 5GB as an absolute minimum as it generally requires that much free space to perform an Archive and Install of Mac OS X and still preserve some free space for VM swap files.
2. Some say that your hard drive should have at least 5% of it's capacity available for use. Still others say 10% to 15%. If you routinely process complex graphics and videos, even more space is required.
Look at these links about freeing up more space.
Where did my disk space go?
_*http://www.macfixitforums.com/showflat.php?Cat=&Board=Forum38&Number=770243*_
Download & use WhatSize described in this link or Disk Inventory X @ _*http://www.derlien.com/*_
Freeing space on your Mac OS X startup disk
_*http://www.thexlab.com/faqs/freeingspace.html*_
Amazing Disappearing Drive Space
_*http://www.pinkmutant.com/articles/TigerMisc.html*_
Increase HD Free Space
_*http://macosx.com/forums/howto-faqs/275191-how-easily-increase-hd-free-space-lap top.html*_
How to free up my disk space
http://www.macmaps.com/diskfull.html
JGG -
Gray screen after deleting old user accounts - with a twist...
I have two MacBook Pros w/retina displays. Purchased about 6 months apart, they are both running 10.8.4. The newer unit was recently bought from my employer (work unit) and connected to my wi-fi. I set up file sharing and deleted the work-related users accounts on both. When I rebooted, both went to gray screen, apple icon, and wheel spinning. Then icon only with no wheel.
Command-P-R to repair permissions and repair tasked 3-4 times - Same result after reboot.
Reinstalled OSX on work unit - SUCCESS and all my changes made before the gray screen were intact.
Reinstalled OSX on home unit - The install ran its course but after reboot, gray screen. Command P-R revealed that repair was available but repair permissions button is not grayed out. Repaired 2-3 times. Same result. Restalled OSX 3-4 times. Same result.
The files are intact...at least the space is showing utilized. My last option is to slave home unit to work unit and transfer all files then reinitiallize.
Help me Obi-Wan. You're my only hope.
Thx in advance! DCTake each of these steps that you haven't already tried. Stop when the problem is resolved.
Step 1
The first step in dealing with a boot failure is to secure your 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 your last backup, you can skip this step.
There are several ways to back up a Mac that is unable to boot. You need an external hard drive to hold the backup data.
a. Boot into 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.”
b. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, boot 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.
c. 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
Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to boot, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can boot 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.
If you've booted from an external storage device, make sure that your internal boot volume is selected in the Startup Disk pane of System Preferences.
Step 3
Boot in safe mode. Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Post for further instructions.
Safe mode is much slower to boot 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 your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
When you boot 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, your boot volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 5.
If you can boot and log in now, empty the Trash, and then open the Finder Info window on your boot 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 reboot as usual (i.e., not in safe mode.)
If the boot process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
Step 4
Sometimes a boot failure can be resolved by resetting the NVRAM.
Step 5
Launch Disk Utility in Recovery mode (see Step 1.) Select your 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 reboot as usual.
Step 6
Reinstall the OS. If your Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
Step 7
Repeat step 6, but this time erase the boot volume in Disk Utility before installing. The system should automatically reboot into the Setup Assistant. Follow the prompts to transfer your data from a Time Machine or other backup.
Step 8
This step applies only to older Macs (not current models) that have a logic-board ("PRAM") battery. The battery is distinct from the main battery of a portable. A dead logic-board battery can cause a gray screen at boot. Typically the boot failure will be preceded by loss of the startup disk and system clock settings. See the user manual for replacement instructions.
Step 9
If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store to have the machine tested. -
IMac - gray screen after OSX 10.9.4 upgrade
iMAC
21.5-inch, Late 2009
Processor 3.33 GHz Intel Core 2 Duo
Memory 16 GB 1067 MHz DDR3
Graphics ATI Radeon HD 4670 256 MB
Software OS X 10.9.4 (13E28)
After being gone for 2 weeks we returned home and initially the iMAC booted fine and my wife was able to use it with no issues. Then she called later in the day reporting that she could no longer log into the machine despite trying to restart and then powering off/on. I had auto updates turned on so my guess is that the update to 10.9.4 happened but failed to complete.
I rebooted using the recovery disc, ran the check disk utility and there were some issues with permissions on some of the printer related files. After the utility corrected those I attempted to reboot again. Still ended up with the gray screen.
I installed OSX again, received no error messages, but still gray screen again. Rebooted in safe mode, checked the disks again and no issues. I followed all the steps to in the knowledge base article to check peripherals (none connected), clear memory, reinstall, etc. Getting the machine back in working mode required erasing the main drive and reinstalling OS X again. Since I have a cloud backup of my data, I was able to do that without serious data loss. It seems there was some issue with the update conflicting with some data that existed on the drive. Don't know where that would have been logged and not enough time available for me to scour the support site to track it down. This is mainly an FYI that the 10.9.4 updater may have issues and it took some drastic measures on my part to get my machine working again.Take each of these steps that you haven't already tried. Stop when the problem is resolved.
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 you use a wireless keyboard, trackpad, or mouse, replace or recharge the batteries. The battery level shown in the Bluetooth menu item may not be accurate.
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, or if a firmware password is set, or if the startup volume is a Fusion Drive or 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. -
I can't get past the gray screen after update of 10.10.3
downloade the new software on my 2011 Mac this morning, and after the download when the computer restarts a gray screen appear. I don't know how to get rid of it. It was working fine before the updat. Anyone have this problem?
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. -
How do i get out of white screen after login
How do i get out of the white screen after signing on to my computer.
Hi GregConk,
Thank you for visiting Apple Support Communities.
If I understand right, your iMac is only starting up to a blank white screen after you log in. If so, there are some good troubleshooting steps that may resolve this behavior.
First, try booting your computer into Safe Mode, to see if your desktop appears in this mode:
Shut down your Mac. If necessary, hold your Mac's power button for several seconds to force it to power down.
Start your Mac, then immediately hold the Shift key. This performs a Safe Boot. Advanced tip: If you want to see the status of a Safe Boot as it progresses, you can hold Shift-Command-V during start up (instead of just Shift).
Note: A Safe Boot takes longer than a typical start up because it includes a disk check and other operations.
If your Mac starts up as expected, immediately try restarting.
From:
Mac OS X: Gray screen appears during startup - Apple Support
If you see your desktop in Safe Mode, but not when starting up normally, try the troubleshooting tips in this article next:
OS X Yosemite: If you think you have incompatible login items
Best Regards,
Jeremy -
MacBook Pro mid 2013 13' gets stuck on White screen after login.
I'm in safe mode right now. I Booted it up in Safe Mode by holding down the shift key during startup. What do I do now to not get the white/grey screen during startup after login?
Mac OS X: Gray screen appears during startup
If the grey screen occurs when you boot normally (not safe mode) try bypassing your Login Items by holding a Shift key in the same manner during login (i.e. not during boot). If you can log in, you effectively isolated the problem to one of more of your Login Items. -
Beach Ball of Death, Dark Gray Screen after Clean OS ReInstall- Please Help
My 13" MBP is less than two months old.
I read online somewhere that a company that buys large quantities of Macs has a strategy for combating the industry standard 5% hard drive failure in new notebooks. It said something along the lines of performing a clean install / reformat of OS X was a good idea to see if any problems arise- then the HD would likely have problems in the near future, etc...
Being the nerd that I am I performed a clean install on my MBP. I had just performed one the day before on my other Mac (which worked perfectly).
First of all, my MBP took roughly 15 minutes to boot from the disk (to begin the reinstall). Actually one time I gave it over 20 minutes and it never did load. Once I finally got to the Language select screen it froze, clicking the continue arrow did nothing and I couldn't even choose another language. So I shut down and tried again. The DVD doesn't look scratched. Is my drive less than stellar?
This time, it worked, albeit, it took much longer to install than my lesser powered Mac Mini. OS X notified me that the installation was successful and that it now simply needed to restart. Upon restart I was greeted with a dark gray screen and mouse cursor spinning beach ball (that responded to trackpad).
Shut down, turned it back on- same thing. Tried a bunch more times, no luck.
Called Apple Care and after a few questions / tips we concluded that it needed to be sent in, the associate imagined it was a HD problem.
I took my MBP to a local authorized service provider and they took it, and called me back in a few hours. I asked what they did to fix it, and they skillfully dodged the question. They said it should be good now, that it passed all hardware tests, but to let them know if it happened again.
Since then it's been running okay. As a nerd it's a bit bothersome to know that I can't perform a clean install when I see fit- and that if I did, I'd have to take it into Apple Care again in the future, and once Apple Care runs out than a clean install just isn't an option.
It boots up just as fast, but when it gets passed the white screen with the Apple logo... when the desktop is loading I noticed that it stays at the flash of the solid blue desktop a bit longer than usual (the second before it loads your desktop bg image). It also seems that fully loading all of the top right menu bar items takes a bit longer than before.
Also, not sure if the hard drive's sudden motion sensor is going haywire. But randomly, the hard drive will make a singular faint "thud / click" noise. Very faint. But it's not your usual "reading data from the HD" hard drive thrashing noise you hear when you open an app / file. It's a single, more sudden noise, but like I said it is fairly quiet- I hear it when I have literally nothing running except this Safari window. This is something I didn't notice the first few weeks with the MBP.
Also in system profiler, the battery's condition was never good, but only "Normal." I did calibrate my battery one of the first days I had it.
Here's some coconutBattery info:
Current Battery Capacity: 5588 mAh
Original Battery Capacity: 5770 mAh
Which is 96%.
Load cycles: 10
Anyways, curious if anyone has any ideas about my inability to perform a clean install and successfully boot up? I don't see any reason why it should have taken THAT long to boot from the disk, frozen in several random spots throughout, and then not be able to boot up.
The HD noises aren't a huge deal just a bit concerning, and admittedly the battery info is just nerdy paranoia. Just curious what's going on with my MBP. Is there anything I can do, or should read?Hi simplecoder13,
I perform a similar process on all the HDs that I buy, only I take it a step further. I'll run a single pass erase on drives under 500GB and a seven pass erase on drives larger than 500GB and ones that are deemed "mission critical." Here's an interest metric, though.
Since 01/01/10 on laptop drives (Seagate, Western Digital, Hitachi)
+HDs purchases - 461+
+Drives > 500GB - 119+
+Drives < 500GB - 342+
+Drives that fail zero test - 13+
+Drives that pass zero test, fail within 30 days - 2+
+Drives that pass zero test, fail within 60 days - 0+
+Drives that pass zero test, fail within 90 days - 3+
+Drives that pass zero test, fail within 180 days - 4+
+Total drive failures within 6 months - 22 (4.77%) ~ 5%+
I don't have a manufacturer break down, I suppose I should start logging that more closely. Anyway...
I have a new MacBook Pro (13" @ 2.4GHz) and booting off the installation disc, from selecting the installer disc via the boot manager to the language selection screen is ~ 6 mins and 44 seconds. I use that as an average, I did it over 10 restarts but it was a pretty fair assessment. The fact that the installer is freezing is definitely cause for alarm, that's not normal or to be expected. Process of elimination would tell me the following:
1.) The disc is bad
2.) The optical drive is bad
My understanding of the installer is the HD isn't initially accessed during the installer until you choose an install location (at which point it's mount point is verified).
Regarding the battery, your full charge capacity is going to bounce around the first couple of months, usually anywhere from 250-400 mAh. I noticed sporadic reporting until I reached the 50 cycle mark (or around 6 months based on usage). That being said, I don't see any problems or cause for alarm with the information you've reported. -
I am having an issue with an iMac that has OS X 10.5.8 installed.
Immediately after login I get a blank wallpapered screen (wallpaper is the same as wallpaper at login) w\ cursor. ...It never goes into the desktop where there is a taskbar and desktop icons. This started happening to a couple of my desktops after I installed ESET NOD32 4.0.12 for Mac (AntiVirus).
Has anyone else seen this issue or know of a fix.You will have to see if you can start the computer via other means,
in that if you can start in SafeBoot mode, you may be able to be rid
of that anti-virus software. That likely is the problem's main cause.
SafeBoot mode: restart, hold Shift key, until you get log-in screen;
login to get to desktop. From here, you can do a few things, but the
computer is not running at full system usefulness. You may be able
to remove this AV software, or see if it has an Uninstaller; and also
you can repair disk permissions in Disk Utility. Among other tasks.
When done, restart normally. (You could also boot from install disc
and use the menu options to run Disk Utility, and other jobs.)
If the product did not come with an Uninstaller in its software, you
may have to try & remove it by other means. These things will put
more into the computer's OS than just an item in the Utilities or
Applications folder; so an Uninstaller is likely a necessity. There
are a few shareware and free ware uninstallers, such as AppDelete
available online as downloads. If you can't find an Uninstaller in the
software you installed (may be in the app's folder in Mac) you may
have to contact the products customer support and ask how you
are to remove the entire product and its parts from your Mac.
If you are lucky, they may actually know where you could go in and
carefully remove those bits; and luckier still, if there is an uninstaller.
Good luck & happy computing! -
Mac Pro stuck on gray screen after installing software for a new keyboard
I am having a huge issue with my very important work computer! For a few weeks, my Mac has been freezing on the gray screen during start up. Since I had two external hard drives plugged in, I would unplug one of them and the Mac would always restart correctly once one was unplugged. Well today I was installing software for a new keyboard and the mac prompted me to restart. Once I restarted, the gray screen came up again and no matter what I did it would not start up correctly again. I tried unplugging everything except the keyboard and monitor and nothing works. I tried ejecting the crash-causing CD with the keyboard using all of the commands I found on this forum board and nothing worked. I saw forums about manually ejecting the CD by pushing a pin-hole but I cannot find that pinhole anywhere! Then again, the CD might not even be the problem but since the computer gave me the gray screen of death right after using the CD I am thinking that it is the problem. I use this computer for editing a TV show and creating websites so there is a ton of files on it and I need to get it up and running again ASAP. Any suggestions would be appreciated and I am sure by now you can tell that I am not a Mac expert so please dumb it down for me. Thank you!!
I would start by breaking your thoughts and sentences out from one long paragraph.
Start at the basics.
Always have backups.
One at least that is a spare boot system you can use.
Clone your system. SuperDuper does a great job for only $29
Boot from another hard drive or last OS X DVD
Repair your drive with Apple Disk Utility along with 3rd party disk maintenance and repair
Hold Option key until the boot manager, then hold mouse to open optical drive.
You can hold mouse on startup and it will eject also.
Hold and continue to hold Shift key during startup to repair the boot drive in minimal fashion.
What device and driver? hint: never use CD, just go online as the CD is usually out of date anyway.
Fill in Mac OS X version and more about hardware would help in posts and in your profile signature.
http://www.shirt-pocket.com/SuperDuper/SuperDuperDescription.html
http://www.macintouch.com/readerreports/harddrives/index.html#d12aug2010
http://www.alsoft.com/DiskWarrior
Maybe you are looking for
-
Payload involving BPM does not display in RWB
HI I have two scenarios one with BPM and another without BPM. Both work fine end to end. For the non BPM scenario I am able to display the message content>payload on the details page of RWB. But I am not able to see the payload in any of the steps fo
-
[SOLVED] "Loading console font" fails at boot
Hello everyone, At each boot, the line where it loads the console font fails. The font configured in rc.conf is "161", it's the one by default on installation. /var/log/boot Loading Console Font: 161 ^[[231G [BUSY] ^[[231G [FAIL] It's a fresh install
-
I bought a HD movie from itunes, SD version was already downloade but HD version does not start at all, please help...What should i do?
-
Help!!
-
I just did a complete backup of my catalogue. Since I was asked for a new file name to save it to I assume that once the backup has been created you should be save to delete the original backup? Is this correct?