Start up with gray screen

I have a iMac G4 flat panel, I had a kernal panic and the computer told me to restart. I dod and now all I get is a gray screen with no apple...
is there anything I can do, soes it sound like a hardware or software issue???
thanks
Jarrod

You can do a reinstall as follows:
How to Perform an Archive and Install
An Archive and Install will NOT erase your hard drive, but you must have sufficient free space for a second OS X installation which could be from 3-9 GBs depending upon the version of OS X and selected installation options. The free space requirement is over and above normal free space requirements which should be at least 6-10 GBs. Read all the linked references carefully before proceeding.
1. Be sure to use Disk Utility first to repair the disk before performing the Archive and Install.
Repairing the Hard Drive and Permissions
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger, Leopard or Snow Leopard.) 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 installer. Now restart normally.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
2. Do not proceed with an Archive and Install if DU reports errors it cannot fix. In that case use Disk Warrior and/or TechTool Pro to repair the hard drive. If neither can repair the drive, then you will have to erase the drive and reinstall from scratch.
3. Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When you reach the screen to select a destination drive click once on the destination drive then click on the Option button. Select the Archive and Install option. You have an option to preserve users and network preferences. Only select this option if you are sure you have no corrupted files in your user accounts. Otherwise leave this option unchecked. Click on the OK button and continue with the OS X Installation.
4. Upon completion of the Archive and Install you will have a Previous System Folder in the root directory. You should retain the PSF until you are sure you do not need to manually transfer any items from the PSF to your newly installed system.
5. After moving any items you want to keep from the PSF you should delete it. You can back it up if you prefer, but you must delete it from the hard drive.
6. You can now download a Combo Updater directly from Apple's download site to update your new system to the desired version as well as install any security or other updates. You can also do this using Software Update.

Similar Messages

IBook g4 stuck on start up with gray screen and circle that looks like its downloading

iBook G4 stuck on gray startup screen with circle like it's downloading

If your iBook G4 portable running OS X 10.5.8 or 10.4+
shows a grey screen on startup or other similar variant
to the failure to fully start, there are a few good Support
articles from Apple Support site online that may help.
Each has information to read through, consider, & try.
•Mac OS X: Grey screen appears during startup...
http://support.apple.com/kb/ts2570
•Resolve startup issues & perform disk maintenance with Disk Utility and fsck
http://support.apple.com/kb/ts1417
This is akin to troubleshooting since you have a measure
of trial-and-error to resolve the problem; & at times there
may be more than one thing to do, &/or more than once.
Hopefully this helps.
Good luck & happy computing!

Macbook with gray screen on start up

ok so a few weeks ago I decided to open my macbook which I have had for 2 years or so. I followed instructions online on which parts to disassemble first, and so on.
After putting it back together it starts up as normal and everything works fine. Last night while online, the system froze, so I turned it off with the power button. I then turned it back on and it stayed on the gray screen. I have tried resetting in safemode (did not work) unplugging batter/power supply and holding the power button for 5 seconds. I have tried starting it up while holding optcommand+PR I heard the second chime the first time I tried it, and then let go... still started up on gray screen. I then took it back apart to see if the hardrive had been disconected while putting it back together (since my hard drive was not showing up when I inserted the disc1 tiger os x cd and held the option Button) I checked, and everything inside appears to be perfectly fine.
I then startup on the os x disc1 and go to disc utilities. I look to the left and I have (from top to bottom) 74.5 GB Hitatchi hts5****MEDIA>> and under that Disk0s2 >>>under that I have 5.1 GB MATSHITACD>>> under that I have the cd that is in my optical drive.
now I selected my 74.5 hardrive and checked if it was verifeid, and it was. I then ran "repair disc" and everything seems to be working fine until it ends up with the error message "First Aid Failed Disk Utility stopped repairing "diskos2" because the following error was encountered: The underlying task reported failure on exit." In the box that was checking the processes it says "Verifying volume "disk0s2"
Checking HFS Plus Volume
Checking Extents Overflow file
Invalid sibling link
The volume Macintosh HD needs to be repaired
Error: The underlying task reported failure on exit
1HFS Volume checked,
Volume Needs repair.
now I am here begging of help for someone to help me get my baby back and running. I do not have that much money, and have some very important data saved on my hardrive. I do not think I have any recent backups of my data. If anyone can help, I would sure appreciate it.

{quote}have some very important data saved on my hardrive. I do not think I have any recent backups of my data. If anyone can help, I would sure appreciate it. :D{quote}
Bad combination.
Disk First Aid is a decent first line of defense, but it won't help rebuild your directory in the event of a more serious fault. Disk Warrior and Tech Tools Pro are both popular tools for repairing and rebuilding directories and may offer a chance of getting your drive back online.

I have an iMac from 2008. When I start I get gray screen with apple and turning gear. Next blue screen. Then light blue screen with turning gear. Back to blue screen. Now just back and forth blue to light blur

I have an iMac from 2008. When I start I get gray screen with apple and turning gear. Next blue screen. Then light blue screen with turning gear. Back to blue screen. Now just back and forth blue to light blur

Reinstall OS X:
Reinstall OS X without erasing the drive
Do the following:
1. Repair the Hard Drive and Permissions
Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. 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 installer.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
2. Reinstall Snow Leopard
If the drive is OK then quit DU and return to the installer. Proceed with reinstalling OS X. Note that the Snow Leopard installer will not erase your drive or disturb your files. After installing a fresh copy of OS X the installer will move your Home folder, third-party applications, support items, and network preferences into the newly installed system.
Download and install the Combo Updater for the version you prefer from support.apple.com/downloads/.
Reinstalling 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: Select Reinstall Lion and click on the Continue button.
Note: You can also re-download the Lion installer by opening the App Store application. Hold down the OPTION key and click on the Purchases icon in the toolbar. You should now see an active Install button to the right of your Lion purchase entry. There are situations in which this will not work. For example, if you are already booted into the Lion you originally purchased with your Apple ID or if an instance of the Lion installer is located anywhere on your computer.

I have a 2007 Macbookpro and it started up with gray checkered boxes ann across the screen I tried to re load OSX and it work 1 day and started again is this a hard drive problem or Video? Now as it starts to load a screen comes up saying to restart

I have a 2007 Macbookpro and it started up with gray checkered boxes and across the screen I tried to re load OSX and it work 1 day and started again is this a hard drive problem or Video? Now as it starts to load a screen comes up saying to restart over and over again

I'd suspect this known issue:
http://support.apple.com/kb/TS2377
if you have a late 2007 MBP.
The only testing you can do at home is to attach an external monitor and see if the defects repeat on the external. If so, get to an Apple store. If the computer's video chipset fails a test the Apple Store will perform, you get a free logic board replacement. Turnaround is usually one day to one week--not bad at all.
If the defects do NOT repeat on an external monitor, then the problem is not covered by the above Repair Extension Program
The issue is heat-triggered. Be certain that you control heat once you get it fixed. Don't use the computer in your lap without a lapboard; don't block the vents under the display hinge; don't us in clamshell mode, etc.

IBook will not start up past gray screen w/ apple logo

iBook will not start up past gray screen w/ apple logo. So I have zeroed out the hard drive and reinstalled tiger. No change except if I start up holding shift it will boot and welcome comes up then black screen that says you must restart by holding down power key.
Zeroed out the HD again with same results. Also I have a iBook G3 with the same symptoms.

What you are experiencing is a kernel panic.
Try starting up from the Mac OS X Install Disc by inserting the disc and restarting your computer, holding down the C key as the startup chime is ending. Then choose Installer > Open Disk Utility (in Panther) or (in Tiger) click 'Next' at the language screen and choose Utilities > Disk Utility and select the hard drive in the left column. Choose the First Aid tab. Click Repair Disk to test and repair the hard drive.
Once you have repaired the hard drive with the Install disc's Disk Utility, then try to restart normally, and go to Applications > Utilities > Disk Utility. Click on the top hard drive icon in the left sidebar and note the S.M.A.R.T. status at the bottom right of the pane. What does it say?
Select the named boot volume in the left sidebar, ("Macintosh HD" unless you've renamed it). What is the hard drive capacity and how much space remains available on it? Repair permissions on it.
See if a little hard drive maintenance helps things out.

Hi i am having a big trouble. MY mac wont start past the gray screen. I tried starting on safe boot, single user user mode , recovery mode. Everything it gets stuck on the gray screen i even tried reinstalling it , same thing what should i do?

MY mac wont start past the gray screen. I tried starting on safe boot, single user user mode , recovery mode. Everything it gets stuck on the gray screen i even tried reinstalling it , same thing what should i do? it lets me reinstall sometimes Sometimes.... it is weird.

orshikhfromsc,
boot from the Mac OS X Install DVD that originally came in the box with your MacBook Pro (by holding down the C key as it starts up). When the desktop appears, select Disk Utility from the Utilities menu and erase your internal disk. After it’s been erased, reformat it. After it’s been reformatted, exit Disk Utility and reïnstall the version of Mac OS X from that DVD onto your internal disk. After that version of Mac OS X has been reïnstalled, boot from your internal disk and run Software Update to get it up-to-date within that version; that should allow you to redownload and reïnstall Mavericks, if desired. If Mavericks is reïnstalled, run Software Update again to get it up to date.
If you no longer have the two grey installation DVDs, you can purchase a replacement set from either Apple or iFixit.

My Mac Book Pro starts up with gray bars and instructs me to restart the sy

I started having problems with my Mac Book Pro last night. It crashed, and instructed me to restart the computer. I've tried the following with the install CD inside the CD ROM Drive:
1) Restarted it with the OPTION key pressed down
2) Restarted it with the C key pressed down
3) Restarted it with the D key pressed down
The extensive Hard Drive test did not detect any problems. I cannot boot from the main HD or the Install CD. I cannot enter safe mode.
On a regular boot up the computer starts up with gray bars and the gray bars fill the screen, the spinning gear appears and more gray bars on the screen. The screen then turns black and then I get the restart message.
Any suggestions would be appreciated.

Like BSteely, I am curious as to how you ran hard drive tests if you can't boot from the Installer disc? Do you have another bootable hard drive attached?
You might want to try pulling and reseating the RAM and hard drive along with performing an SMC reset. Disconnect any external USB and FireWire devices. You're getting kernel panics during startup which usually indicate a hardware issue.
-Douggo

HT3964 After updated to Maverick system is not starting , keeping light gray screen without progress

I updated first to Mountain Lion my Mac becomes slow, after trying to solve I updated again to Maverick. But my Mac after becomes slow not starting, so I restore a backup, but now some times doesn't start, stops on gray screen ...
I tried comm opt p r and other commands but still not solve. Should I format and install new system from zero?

HCQuintao,
try this first: boot your MacBook Pro into Recovery mode by holding down a Command key and the R key as it starts up. Once the Mac OS X Utilities menu appears, select Disk Utility. On the left-hand side of the Disk Utility window, select your internal disk’s boot partition (typically called “Macintosh HD”). On the right-hand side, press the Verify Disk button if it’s not greyed out; if it is greyed out, or if it reports that errors were found, press the Repair Disk button. Once the verification/repair is completed, exit Disk Utility and select Restart from the Apple menu to restart in normal mode. Does it still stop on the grey screen?

Two crashes: one OS crash with gray screen and loading bar- help? (Stuck overseas, so you guys are it!)

Hey everyone.
When firefox crashed last night, I figured it was just firefox being difficult, but when while using firefox my entire computer crashed this afternoon and rebooted with a gray screen, the spinny wait symbol, and a loading bar, I started to get concerned. After looking through console, I'm not sure what's caused it to crash like this so I'm hoping one of you bright people here can tell me what exactly happened. I'm running a mac book pro with 10.6.8, have no real addons on firefox aside from adblock plus, divx, memory restart, a french dictionary, and a skin I've been using forever and have also spoken to the developer in the past about. I'm also using Firefox 17.0.1. After trying to google some of the more unfamiliar/suspicious lines (mostly relating to launch agents), I typed into terminal the command to list all launch agents and received 3 replies naming adobe, divx, and google. I used terminal to delete them all just for safe measure (plus the adobe update window has been irritating me to no end so maybe it'll go away now, haha). I did three things when I tried to boot up again after the crash and the weird launch screen with loading bar came up: 1) I held down the power button again because a) the screen was weirding me out and b) I thought it got hung up again (bar seemed to stall for an unusually long time), 2) I tried to boot again and when the same gray screen came back I just figured I had no choice and had to sit through it. 3) when the bar was at about half way I pulled out my ethernet cord for safe measure in case something shady was going on. These three things are also reflected in the log below.
I currently live overseas and the nearest Apple store is over two hours away with no guarantee of a native english speaker working, so if anyone can let me know what caused the crash and if there's anything I can do about it, I would be extremely grateful. The following is my current console log in its entirety from today, including my attempted system update to see if that would improve things (which also resulted in a gray screen with loading bar later), and a really weird bit at the end that is also confusing (but possibly caused by me tinkering in terminal- not sure).
NAME is replacing my HD name, and my screen name here (caithris) has replaced my computer user name. NUMBER has replaced anything that looks like a serial number of some kind.
Thanks so much ahead of time-- please let me know if there's anything else I can share.
Mar 31 00:30:01 NAME newsyslog[9228]: logfile turned over
Mar 31 01:03:25 NAME firefox[8993]: Mozilla has caught an Obj-C exception [NSRangeException: *** -[NSCFArray objectAtIndex:]: index (1) beyond bounds (1)]
Mar 31 01:03:25 NAME [0x0-0x10010].org.mozilla.firefox[0]: 2013-03-31 01:03:25.193 firefox[8993:903] Mozilla has caught an Obj-C exception [NSRangeException: *** -[NSCFArray objectAtIndex:]: index (1) beyond bounds (1)]
Mar 31 01:04:06 NAME [0x0-0x10010].org.mozilla.firefox[0]: pure virtual method called
Mar 31 01:04:06 NAME [0x0-0x10010].org.mozilla.firefox[0]: terminate called without an active exception
Mar 31 01:04:20 NAME ReportCrash[9260]: Saved crash report for firefox[8993] version 17.0.1 (1712.11.28) to /Users/Caithris/Library/Logs/DiagnosticReports/firefox_2013-03-31-010420_NAME.c rash
Mar 31 01:05:35 NAME SubmitDiagInfo[9280]: Submitted crash report: /Users/Caithris/Library/Logs/DiagnosticReports/firefox_2013-03-31-010420_NAME.c rash
Mar 31 03:00:27 NAME loginwindow[31]: loginwindow SleepWakeCallback WILL sleep
Mar 31 03:00:28 NAME configd[13]: PMConnection IPConfiguration com.apple.powermanagement.applicationresponse.slowresponse 1120 ms
Mar 31 11:22:53 NAME configd[13]: Sleep: Success - AC 97 - Idle Sleep
Mar 31 11:22:53 NAME configd[13]: Wake: Success - AC 97 - OHC2
Mar 31 11:22:53 NAME configd[13]: Hibernate Statistics
Mar 31 11:22:53 NAME loginwindow[31]: loginwindow SleepWakeCallback will power on, Currenttime:3/31/2013 11:22:53.195 AM - Waketime:3/31/2013 11:22:43.930 AM = Deltatime:9.265338957
Mar 31 11:22:53 NAME loginwindow[31]: askForPasswordBuiltIn after makekey, Currenttime:3/31/2013 11:22:53.212 AM - Waketime:3/31/2013 11:22:43.930 AM = Deltatime:9.281565964
Mar 31 11:22:53 NAME loginwindow[31]: builtInAuthWindowBecameKey, Currenttime:3/31/2013 11:22:53.243 AM - Waketime:3/31/2013 11:22:43.930 AM = Deltatime:9.312892973
Mar 31 11:22:53 NAME configd[13]: network configuration changed.
Mar 31 11:22:54 NAME configd[13]: PMConnection AirPort configd plug-in com.apple.powermanagement.applicationresponse.slowresponse 9839 ms
Mar 31 11:22:54 NAME configd[13]: PMConnection IPConfiguration com.apple.powermanagement.applicationresponse.slowresponse 9849 ms
Mar 31 11:22:57 NAME configd[13]: network configuration changed.
Mar 31 11:22:57 NAME ntpd[20]: sendto(17.171.4.13) (fd=24): Network is unreachable
Mar 31 11:23:02 NAME loginwindow[31]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Mar 31 11:23:02 NAME loginwindow[31]: builtInAuthWindowDidResignKey
Mar 31 11:23:02 NAME loginwindow[31]: handleUnlockResult, Currenttime:3/31/2013 11:23:02.536 AM - Waketime:3/31/2013 11:22:43.930 AM = Deltatime:18.606058955
Mar 31 11:23:32 NAME loginwindow[31]: no spins reported for this wake
Mar 31 11:27:31 NAME SubmitDiagInfo[9444]: Cleaning up expired diagnostic messages database at path: /var/log/DiagnosticMessages/2013.03.01.asl
Mar 31 11:33:29 NAME [0x0-0x3b63b6].org.mozilla.firefox[9264]: NOTE: child process received `Goodbye', closing down
Mar 31 11:36:14 NAME ntpd[20]: time reset -4.060579 s
Mar 31 12:11:05 NAME firefox[9264]: -deltaZ is deprecated for NSEventTypeMagnify. Please use -magnification.
Mar 31 15:19:22 NAME kernel[0]:
Mar 31 15:28:23 NAME kernel[0]:
Mar 31 15:28:53: --- last message repeated 7 times ---
Mar 31 15:28:23 NAME kernel[0]:
Mar 31 15:30:22 NAME kernel[0]:
Mar 31 15:56:08 NAME kernel[0]:
Mar 31 15:56:13: --- last message repeated 1 time ---
Mar 31 15:56:13 NAME loginwindow[31]: in pam_sm_authenticate(): Failed to determine Kerberos principal name.
Mar 31 15:56:16 NAME kernel[0]:
Mar 31 15:56:46: --- last message repeated 8 times ---
Mar 31 16:00:10 NAME kernel[0]:
Mar 31 16:00:40: --- last message repeated 3 times ---
Mar 31 16:00:44 NAME kernel[0]:
Mar 31 16:01:14: --- last message repeated 5 times ---
Mar 31 16:02:36 NAME kernel[0]:
Mar 31 16:03:06: --- last message repeated 9 times ---
Mar 31 16:03:22 NAME kernel[0]:
Mar 31 16:10:31 localhost com.apple.launchd[1]: *** launchd[1] has started up. ***
Mar 31 16:17:50 localhost DirectoryService[15]: Improper shutdown detected
Mar 31 16:17:54 localhost fseventsd[33]: event logs in /.fseventsd out of sync with volume. destroying old logs. (707133 444 707763)
Mar 31 16:17:54 localhost bootlog[41]: BOOT_TIME: 1364713830 0
Mar 31 16:17:58 localhost fseventsd[33]: log dir: /.fseventsd getting new uuid: NUMBER
Mar 31 16:17:58 localhost blued[42]: Apple Bluetooth daemon started
Mar 31 16:18:02 localhost mDNSResponder[28]: mDNSResponder mDNSResponder-258.21 (May 26 2011 14:40:13) starting
Mar 31 16:18:03 localhost com.apple.usbmuxd[21]: usbmuxd-296.4 on Dec 21 2012 at 16:11:14, running 64 bit
Mar 31 16:18:04 localhost configd[13]: bootp_session_transmit: bpf_write(en1) failed: Network is down (50)
Mar 31 16:18:04 localhost configd[13]: DHCP en1: INIT transmit failed
Mar 31 16:18:04 localhost configd[13]: network configuration changed.
Mar 31 16:18:04 NAME configd[13]: setting hostname to "NAME.local"
Mar 31 16:18:04 NAME /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[29]: Login Window Application Started
Mar 31 16:18:04 NAME configd[13]: network configuration changed.
Mar 31 16:18:04 NAME mDNSResponder[28]: mDNSPlatformSetDNSConfig: Error: dns_configuration_copy returned NULL
Mar 31 16:18:04 NAME configd[13]: network configuration changed.
Mar 31 16:18:11 NAME mds[27]: (Normal) DiskStore: Creating index for /
Mar 31 16:18:17 NAME loginwindow[29]: Login Window Started Security Agent
Mar 31 16:18:18 NAME WindowServer[71]: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
Mar 31 16:18:18 NAME com.apple.WindowServer[71]: Sun Mar 31 16:18:18 NAME.local WindowServer[71] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
Mar 31 16:18:29 NAME SecurityAgent[92]: NSSecureTextFieldCell detected a field editor ((null)) that is not a NSTextView subclass designed to work with the cell. Ignoring...
Mar 31 16:18:30 NAME loginwindow[29]: Login Window - Returned from Security Agent
Mar 31 16:18:30 NAME loginwindow[29]: USER_PROCESS: 29 console
Mar 31 16:18:30 NAME com.apple.launchd.peruser.501[96] (com.divx.agent.postinstall): Unknown key: LimitToSessionType
Mar 31 16:18:30 NAME com.apple.launchd.peruser.501[96] (com.apple.ReportCrash): Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
Mar 31 16:18:36 NAME root[113]: /usr/libexec/ntpd-wrapper: scutil key State:/Network/Global/DNS not present after 30 seconds
Mar 31 16:18:37 NAME root[130]: sntp options: a=2 v=1 e=0.100 E=5.000 P=2147483647.000
Mar 31 16:18:37 NAME root[130]: d=15 c=5 x=0 op=1 l=/var/run/sntp.pid f= time.apple.com
Mar 31 16:18:37 NAME root[130]: sntp: getaddrinfo(hostname, ntp) failed with nodename nor servname provided, or not known
Mar 31 16:18:38 NAME-2 com.apple.launchd.peruser.501[96] (com.apple.mrt.uiagent[123]): Exited with exit code: 255
Mar 31 16:18:38 NAME-2 com.apple.launchd.peruser.501[96] (com.apple.Kerberos.renew.plist[124]): Exited with exit code: 1
Mar 31 16:19:55 NAME-2 XProtectUpdater[19]: NSURLConnection error: Error Domain=NSURLErrorDomain Code=-1009 UserInfo=0x100174890 "This computer’s Internet connection appears to be offline." Underlying Error=(Error Domain=kCFErrorDomainCFNetwork Code=-1009 UserInfo=0x1001744e0 "This computer’s Internet connection appears to be offline.")
Mar 31 16:19:55 NAME com.apple.launchd[1] (com.apple.xprotectupdater[19]): Exited with exit code: 255
Mar 31 16:22:04 NAME kextd[10]: updated kernel boot caches
Mar 31 16:25:04 NAME Software Update[178]: SWU: scan found 0 products:
Mar 31 16:25:05 NAME Software Update[178]: Error Domain=NSURLErrorDomain Code=-1009 UserInfo=0x10052e600 "This computer’s Internet connection appears to be offline." Underlying Error=(Error Domain=kCFErrorDomainCFNetwork Code=-1009 UserInfo=0x10052f760 "This computer’s Internet connection appears to be offline.")
Mar 31 16:25:14 NAME com.apple.launchd[1] (com.apple.suhelperd[181]): Exited with exit code: 2
Mar 31 16:25:18 NAME configd[13]: network configuration changed.
Mar 31 16:26:17 NAME Software Update[188]: SWU: scan found 1 products:\n041-9605
Mar 31 16:26:30 NAME ntpd[18]: time reset +1.140167 s
Mar 31 16:26:57 NAME com.apple.launchd[1] (com.apple.suhelperd[190]): Exited with exit code: 2
Mar 31 16:26:57 NAME com.apple.launchd.peruser.501[96] ([0x0-0xf00f].com.apple.Console[142]): Exited: Killed
Mar 31 16:26:57 NAME com.apple.launchd.peruser.501[96] ([0x0-0x15015].com.apple.SoftwareUpdate[188]): Exited: Killed
Mar 31 16:26:57 NAME com.apple.launchd.peruser.501[96] (com.apple.AirPortBaseStationAgent[126]): Exited: Killed
Mar 31 16:26:57 NAME loginwindow[29]: DEAD_PROCESS: 29 console
Mar 31 16:26:57 NAME /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[200]: Login Window Application Started
Mar 31 16:26:58 NAME loginwindow[200]: USER_PROCESS: 200 console
Mar 31 16:26:58 NAME WindowServer[203]: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
Mar 31 16:26:58 NAME com.apple.WindowServer[203]: Sun Mar 31 16:26:58 NAME.local WindowServer[203] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
Mar 31 16:26:59 NAME Software Update[209]: Looking for products to install
Mar 31 16:27:02 NAME Software Update[209]: Performing preflight
Mar 31 16:27:02 NAME Software Update[209]: Preparing session
Mar 31 16:27:02 NAME Software Update[209]: Starting session
Mar 31 16:27:03 NAME Software Update[209]: PKG: extracting "com.apple.pkg.MacBookProSMCUpdate"
Mar 31 16:27:03 NAME Software Update[209]: PKG: pre-flight scripts for "com.apple.pkg.MacBookProSMCUpdate"
Mar 31 16:27:03 NAME Software Update[209]: PKG: pre-install scripts for "com.apple.pkg.MacBookProSMCUpdate"
Mar 31 16:27:16 NAME Software Update[209]: REQ: moving files into place with shove
Mar 31 16:27:17 NAME Software Update[209]: PKG: post-install scripts for "com.apple.pkg.MacBookProSMCUpdate"
Mar 31 16:27:17 NAME Software Update[209]: PKG: post-flight scripts for "com.apple.pkg.MacBookProSMCUpdate"
Mar 31 16:27:17 NAME Software Update[209]: PKG: writing receipt for "com.apple.pkg.MacBookProSMCUpdate"
Mar 31 16:27:17 NAME Software Update[209]: REQ: install succeeded
Mar 31 16:27:18 NAME Software Update[209]: SWU: installing "MacBook Pro SMC Firmware Update, 1.6"
Mar 31 16:27:20 NAME [0x0-0x1a01a].com.apple.SoftwareUpdate[209]: /: no supported helper partitions to update.
Mar 31 16:27:20 NAME kextd[10]: updated kernel boot caches
Mar 31 16:27:20 NAME Software Update[209]: kextcache returned 0
Mar 31 16:27:20 NAME Software Update[209]: Running /sbin/reboot
Mar 31 16:27:20 NAME reboot[242]: rebooted by Caithris
Mar 31 16:27:20 NAME reboot[242]: BOOT_TIME: 1364714840 524942
Mar 31 16:27:20 NAME mDNSResponder[28]: mDNSResponder mDNSResponder-258.21 (May 26 2011 14:40:13) stopping
Mar 31 16:27:20 NAME DirectoryService[15]: BUG in libdispatch: 10K549 - 1960 - 0x10004004
Mar 31 16:27:20 NAME WindowServer[203]: hidd died. Reestablishing connection.
Mar 31 16:27:20 NAME WindowServer[203]: Unable to create event queue via hidd: (0x10000003)
Mar 31 16:28:03 localhost com.apple.launchd[1]: *** launchd[1] has started up. ***
Mar 31 16:29:52 localhost bootlog[47]: BOOT_TIME: 1364714882 0
Mar 31 16:29:53 localhost mDNSResponder[34]: mDNSResponder mDNSResponder-258.21 (May 26 2011 14:40:13) starting
Mar 31 16:29:54 localhost configd[13]: network configuration changed.
Mar 31 16:29:54 NAME configd[13]: setting hostname to "NAME.local"
Mar 31 16:29:54 NAME com.apple.usbmuxd[27]: usbmuxd-296.4 on Dec 21 2012 at 16:11:14, running 64 bit
Mar 31 16:29:56 NAME blued[17]: Apple Bluetooth daemon started
Mar 31 16:29:57 NAME /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow[35]: Login Window Application Started
Mar 31 16:29:59 NAME configd[13]: network configuration changed.
Mar 31 16:30:12: --- last message repeated 2 times ---
Mar 31 16:30:12 NAME ntpd[24]: time reset +0.227711 s
Mar 31 16:30:13 NAME loginwindow[35]: Login Window Started Security Agent
Mar 31 16:30:14 NAME WindowServer[61]: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
Mar 31 16:30:14 NAME com.apple.WindowServer[61]: Sun Mar 31 16:30:14 NAME.local WindowServer[61] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
Mar 31 16:30:21 NAME SecurityAgent[96]: NSSecureTextFieldCell detected a field editor ((null)) that is not a NSTextView subclass designed to work with the cell. Ignoring...
Mar 31 16:30:22 NAME loginwindow[35]: Login Window - Returned from Security Agent
Mar 31 16:30:22 NAME loginwindow[35]: USER_PROCESS: 35 console
Mar 31 16:30:22 NAME com.apple.launchd.peruser.501[99] (com.divx.agent.postinstall): Unknown key: LimitToSessionType
Mar 31 16:30:22 NAME com.apple.launchd.peruser.501[99] (com.apple.ReportCrash): Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
Mar 31 16:30:32 NAME com.apple.launchd.peruser.501[99] (com.apple.mrt.uiagent[124]): Exited with exit code: 255
Mar 31 16:30:35 NAME com.apple.launchd.peruser.501[99] (com.apple.Kerberos.renew.plist[125]): Exited with exit code: 1
Mar 31 16:30:47 NAME mdworker[81]: (Error) SyncInfo: Catalog changed during searchfs too many times -- falling back to fsw search /
Mar 31 16:36:05 NAME mdworker32[158]: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
Mar 31 16:36:22 NAME mdworker32[161]: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
Mar 31 16:36:29 NAME [0x0-0x10010].org.mozilla.firefox[149]: NOTE: child process received `Goodbye', closing down
Mar 31 16:39:07 NAME mdworker[157]: Warning: unknown JFIF revision number 0.01
Mar 31 16:39:22 NAME login[182]: USER_PROCESS: 182 ttys000
Mar 31 16:40:34 NAME /System/Library/CoreServices/CCacheServer.app/Contents/MacOS/CCacheServer[132]: No valid tickets, timing out
Mar 31 16:40:35 NAME mdworker[157]: Error, could not create MachMessagePort for com.apple.AddressBook.abd
Mar 31 16:40:37 NAME mdworker[157]: Unable to parse date (<XHTML-STRIPONREPLY>
</XHTML-STRIPONREPLY>)
Mar 31 16:40:38 NAME mdworker[157]: Unable to parse date ( S<XHTML-STRIPONREPLY>
</XHTML-STRIPONREPLY>him to any)
Mar 31 16:40:41: --- last message repeated 1 time ---
Mar 31 16:40:41 NAME mdworker[157]: Invalid char \n for PropertyName in line 1
Mar 31 16:40:41 NAME mdworker[157]: Invalid char \n for PropertyName in line 2
Mar 31 16:40:41 NAME mdworker[157]: Invalid char \n for PropertyName in line 3
Mar 31 16:40:41 NAME mdworker[157]: Invalid char \n for PropertyName in line 4
Mar 31 16:40:41 NAME mdworker[157]: Invalid char \n for PropertyName in line 5
Mar 31 16:40:41 NAME mdworker[157]: Invalid char \n for PropertyName in line 6
Mar 31 16:40:41 NAME mdworker[157]: Invalid char \n for PropertyName in line 7
Mar 31 16:40:41 NAME mdworker[157]: Invalid char \n for PropertyName in line 8
Mar 31 16:40:41 NAME mdworker[157]: Invalid char \n for PropertyName in line 9
Mar 31 16:40:41 NAME mdworker[157]: Invalid char \n for PropertyName in line 10
Mar 31 16:40:41 NAME mdworker[157]: Invalid char \n for PropertyName in line 11
Mar 31 16:40:41 NAME mdworker[157]: Invalid char \n for PropertyName in line 12
Mar 31 16:40:41 NAME mdworker[157]: Invalid char \n for PropertyName in line 13
Mar 31 16:40:41 NAME mdworker[157]: Invalid char \n for PropertyName in line 14
Mar 31 16:40:41 NAME mdworker[157]: Invalid char \n for PropertyName in line 15
Mar 31 16:40:41 NAME mdworker[157]: Invalid char \n for PropertyName in line 16
Mar 31 16:40:41 NAME mdworker[157]: Invalid char \n for PropertyName in line 17
Mar 31 16:40:41 NAME mdworker[157]: Invalid char \n for PropertyName in line 18
Mar 31 16:40:41 NAME mdworker[157]: Invalid char \n for PropertyName in line 19
Mar 31 16:40:41 NAME mdworker[157]: Invalid char \n for PropertyName in line 20
Mar 31 16:40:41 NAME mdworker[157]: Invalid char \n for PropertyName in line 21
Mar 31 16:40:41 NAME mdworker[157]: Invalid char \n for PropertyName in line 22
Mar 31 16:40:41 NAME mdworker[157]: Invalid char \n for PropertyName in line 23
Mar 31 16:40:41 NAME mdworker[157]: Invalid char \n for PropertyName in line 24
Mar 31 16:40:41 NAME mdworker[157]: Invalid char \n for PropertyName in line 25
Mar 31 16:40:41 NAME mdworker[157]: Invalid char \n for PropertyName in line 26
Mar 31 16:40:41 NAME mdworker[157]: Invalid char ^M for PropertyName in line 26
Mar 31 16:40:41 NAME mdworker[157]: Invalid char \n for PropertyName in line 26
Mar 31 16:40:41 NAME mdworker[157]: Invalid char ^M for PropertyName in line 26
Mar 31 16:40:41 NAME mdworker[157]: Invalid char \n for PropertyName in line 26
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 1
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 2
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 3
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 4
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 5
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 6
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 7
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 8
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 9
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 10
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 11
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 12
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 13
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 14
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 15
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 16
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 17
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 18
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 19
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 20
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 21
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 22
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 23
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 24
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 25
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 26
Mar 31 16:40:43 NAME mdworker[157]: Invalid char ^M for PropertyName in line 26
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 26
Mar 31 16:40:43 NAME mdworker[157]: Invalid char ^M for PropertyName in line 26
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 26
Mar 31 16:40:43 NAME mdworker[157]: Invalid char ^M for PropertyName in line 26
Mar 31 16:40:43 NAME mdworker[157]: Invalid char \n for PropertyName in line 26
Mar 31 16:41:27 NAME mdworker[157]: Corrupt JPEG data: 1 extraneous bytes before marker 0xd9
Mar 31 16:41:27 NAME mdworker[157]: JPEG datastream contains no image
Mar 31 16:41:33: --- last message repeated 1 time ---
Mar 31 16:41:33 NAME login[182]: DEAD_PROCESS: 182 ttys000
Mar 31 16:41:50 NAME mdworker[156]: iCal.mdimporter: could not parse ICS file: /Applications/Microsoft Office 2011/Office/OutlookCore.framework/Versions/14/Resources/en.lproj/Timezones.ics
Mar 31 16:41:51 NAME mdworker32[204]: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
Mar 31 16:43:41 NAME [0x0-0x10010].org.mozilla.firefox[149]: NOTE: child process received `Goodbye', closing down
Mar 31 17:07:10 NAME firefox[149]: -deltaZ is deprecated for NSEventTypeMagnify. Please use -magnification.
Thanks again- I mean it. It's lousy being stuck away from home when crazy thing happen to your main line of communication!
-Caithris

The gray screen with loading bar issue is a at boot fsck (file system check) that has discovered something wrong with your boot drive/partition and was attempting to fix it.
OS X is booting but can't complete, so that means your hard drive is good, just likely has been either subjected to shock which damaged data on the platters, or bad sectors (the drive is dying if after fixing it, problems occurs again), or something messed something up in the file structure.
Firefox is currently at 19.02, so it appears your background auto-update has not been occurring, which makes me suspect the machine's data is broken in some manner or you have malware on the machine blocking the updates.
Your problems are multiple, in your case I advise a complete erase and install.
1: If you have a backup of your user data on a external storage drive (not TimeMachine as it might be corrupted and compromised with malware it's just going to restore back) then your good, else you have to do this.
Create a data recovery/undelete external boot drive
Copy your data to a blank plain jane external storage drive as you want no executable files on it when you connect to the cleaned machine later.
2: Once your data is safely copied (copy visible files manually and what you know is good, not folders that can contain invisible malware programs!) then disconnect the drive(s)
3: Next assume all writeable media is contaminated with malware and treat as so. Even if you erased it.
4: Stick in your 10.6 install disk and reboot holding the c or option key down. You want Disk Utility and you want to select the ENTIRE internal drive and MUST USE the Security Option > Zero All Data (unless your in the military then use 7x erase, do not use 35x as it will take weeks and is unnecessary)
The Zero/7x erase will do two things, do a low level format and erradicate everything (including hidden stuff and deleted files) also will map off any failing sectors on the hard drive.
5: Follow the procedure here to install 10.6
How to erase and install Snow Leopard 10.6
6: Reboot the machine twice, then once you set up the machine (using a alias of course and not allowing registration), use a secured network and IMMEDIATLY Software update to 10.6.8, if you can download the 10.6.8 Combo update on another secure machine to a (new) USB thumb drive and install it on the clean Mac, do that instead.
WiFi security issues, at home and WiFi hotspots
https://support.apple.com/kb/DL1399
Still run Software update afterwards as Apple might not have fully updated the combo update yet.
7: Once you machine is secure, download the free ClamXav and run a scan on the external storage drive with just your files, perhaps one or more PDF's or other files are not what they seem to be.
8: Make sure to install fresh copies of software from original sources and not from rewriteable media, update them to be current. Malware can be hidden in copies of programs.
9: Trash all your rewritable media, or use a Linux PC or Linux Mint in a virtual machine (VirtualBox) on another computer like Windows to scrub and reformat all the rewritable media before attaching them to the clean Mac. You have to make sure it's getting the entire media.
10: Once your machine is set back up, then make clones and time and date them.
Most commonly used backup methods
If your still having problems with the machine, it's likley a failing hard drive and you will have to replace it and repeat the steps above pretty much.
Really it's best to replace the drive in the interest of security.
Install/upgrade RAM or storage drive in Mac's
For performance of Snow Leopard, check out this tip
For Snow Leopard Speed Freaks
Your overseas, if your in a foriegn country you have to assume FinSpy is being installed on your machine (uses a older iTunes verison "update" to get on) or there is other tricks via the ISP to install something on your machine. So mix things up and don't stick any old USB you see laying around into your Mac.
https://discussions.apple.com/community/notebooks/macbook_pro?view=documents#/

Power Mac G4 starts, gets to gray screen and shuts down

My Power Mac G4 will start up, but after it gets to the gray screen with the Apple and the spinning gear for a minute or so the computer shuts down. I have started the computer while holding down the "C" with the 10.4 OS disc in and used the Disk Utility to run First Aid. First Aid fails stating:
__*Keys out of order*__
__*Rebuilding Catalog B-tree.*__
__*The volume Macintosh HD could not be repaired.*__
__*Error: The underlying task reported failure to exit*__
__*1 HFS volume checked*__
__*1 volume could not be repaired because of an error*__
__*Repair attempted on 1 volume*__
__*1 volume could not be repaired*__
I have attempted to start computer in safe mode but it just shuts down... no difference.

Faurot, welcome to Apple Discussions
You have directory corruption on your hard drive that Dusk Utility can't repair. DiskWarrior can probably fix your problem. DiskWarrior by Alsoft
http://www.alsoft.com/DiskWarrior/index.html
 Cheers, Tom

Power mac G4 hangs at startup with gray screen

Hello all,
I have a Power mac G4 - mirrored drive door model. 512mb of RAM; 833mghz - about 50+ gigabytes of storage remaining.
I recently starting using this mac again, here is what happened:
Power mac G4 was running 10.2.1 - had never been updated; it also was capable of running classic os9 (even though I never used it)
Started using machine again a few weeks ago; let "software update" install 10.2.8 update - everything worked fine
Put computer into target disk mode to transfer files to my new macbook pro (13") - using firewire connection
While trying to connect (migration assistant) - window froze will calculating the amount of space that the "user" on the power mac totalled - power mac appeared to be frozen
Did a hard reset / power down of the power mac G4
Upon restart, power mac G4 goes through all start up functions up to gray screen with apple logo (with spinning wheel) and then goes to a darker gray screen (without the logo) and spinning wheel
Dark gray screen with spinning wheel hangs indefinitely - I've let it stay there for hours on end hoping it will resolve but it doesn't
Here's what I have done so far:
Placed power mac G4 into target disk mode again in conjunction with macbook pro
I can see all the files on the power mac G4 (and have already copied them to the macbook pro) - so I don't think the hard drive is damaged
Disconnected all non-apple peripheral devices - only had a card installed in the back - but took that out - issue persisted (did not replace card in back)
Removed one non-apple RAM stick - issue persisted
Replaced non-apple RAM stick and removed apple RAM stick - issue persisted
Reset PRAM
Started computer in single-user mode
used fsck and tried to have system check/fix issue; no matter how many times I re-run the command to repair it never comes back with a message saying no issues found - instead it keeps returning with a message saying that the issue was repaired "system modified"
Started computer in verbose mode
startup seems to hang when this appears:
"/System/Library/CoreServices/loginwindow.app/Contents/MacOs/loginwindow: (ipc/send) invalid destination"
"LayState: cannot map display interlocks."
"/System/Library/CoreServices/loginwindow.app/Contents/MacOs/loginwindow: kCGErrorFailure: CGSNewConnection"
"Cannot connect to server"
"/System/Library/CoreServices/loginwindow.app/Contents/MacOs/loginwindow: kCGErrorInvalidConnection"
"Connection called with invalid connection"
Tried re-installing with system discs
The only discs I received with the power mac G4 when I purchased are orange and say "SSW version 8.6" on it" ("iMac Software Restore" and "iMac Software Install")
Computer does not respond when holding down "C" key at startup with either disc in the drive
When holding down "option" key at startup, the computer shows the bootable choices as ONLY the internal HD - not either of the CDs I mentioned above; I wonder if it no longer recognizes the original CDs because I updated to 10.2.8 from 10.2.1 before the issue?
I also have an install disc for OS X 10.4.7 - for a friend's iMac (G5)
When holding down "C" key at startup with the OS X 10.4.7 in the drive I get a kernel panic
When holding down "option" key at startup, the computer shows the bootable choices as the OS X 10.4.7 in the drive AND the internal HD
When I choose the OS X 10.4.7 in the drive I get a kernel panic
When I choose the internal HD the startup hangs at the gray screen I mentioned above
At this point, I don't know what else to do. I believe the computer is still good because I can see everything on it when I put it into target disk mode; it just refuses to make it through the startup/login process. I have read discussion threads that suggest re-installing the OS using another computer - but I don't know how to do that. I also wondered if there was a way to tell the computer to re-install the software using the original CDs - but from the command line (in single-user mode)?
Someone - PLEASE HELP!

Sorry, SU Single User Mode, OF Open Firmware as these 2 where mentioned before.
As a test, let's try disconnecting the HD & see if it booys to any mode without it attached.
It could be the User's files or login messed up, if you want to try something a little more desperate...
Reset OS X Password Without an OS X CD...
http://theappleblog.com/2008/06/22/reset-os-x-password-without-an-os-x-cd/
It'll boot like a newly setup Mac, but all your stuff should still be there once filling out the stuff.
Except you could just use Target mode and move or rename that file.

Can't start up past gray screen on iMac G4 flat panel

My iMac G4 flat panel is messed up right now and I'd appreciate any help I can get here.
This morning after I realized my internet wasn't working I tried a restart but the restart stalled around the part where it just shows your desktop picture and wouldn't fully shut down. I watched this for about ten minutes and then held down the power button on the back to shut down. When I tried starting back up, it would just get to the gray screen with the apple and spinning gear and stall out there. The gear keeps spinning but I can tell from listening that the computer is not doing anything, and it just stays like that for a long time. My OSX disks are in Toronto and I'm here in Kingston, but I was able to start up off my housemate's ibook start up disk and run disk utility. Disk Utility said there was no problems with the disk, I told it to repair anyways and it told me no repairs were needed. However, when I tried to restart off the hard drive, gray screen again.
I know there's been some similar threads here, but I haven't found much help from them. If anyone can give me some advice as to what is making my iMac stall out like this, I'd really appreciate it.

check out the screen I get when I hold command at startup, what does this mean? none of the keyboard buttons respond to this or the mouse, except the return key which brings me back to the grey screen hanging forever.
iMac g4 flat panel Mac OS X (10.4.6)

Start Up Issue-Gray Screen, Apple Logo And Cognition Wheel-Blue screen before start up at times but no longer starting up beyond gray screen and cognition wheel

Power button pressed.
Start up light okay
Chimes okay
Gray screen, apple logo and cognition wheel spinning and the loading bar underneath loading 1/10th of the way.
Loading bar doesnt load fully and then disappears.
Gray screen remains with apple logo and cognition wheel only.
No start up to desktop. Before start up to desk top which is not happening any more a blue screen appeared before the desktop appeared. When start up complete the ' Finder' had no responded and did not work' Multi coloured loading pointer continually turned. ' Network' could not be loaded in 'System Prefrences'.
Ive tried reading and following propts...Results NVRAM/PRAM - Logic board battery replacement. How much will this cost?
Hardware test - No problem found
Safe Boot - ' volume Machintosh HD could not be repaired.'
' Run time corruption detected on Machintosh HD device'
What do you suggest aside from taking it to a apple store?
Thanks Stephen

Lion or Snow Leopard? If Lion, boot into your Recovery partition (hold down the Command and R keys whilst booting) and use Disk Utility to verify and, if needed, repair the boot volume.
If Snow Leopard, use the installation disc and use Disk Utility in the same manner.
Clinton

HT201475 Problem with gray screen after connecting external drive

I attached a LaCie external drive to back up photos and iTunes on iMac running Mountain Lion OS. I'm trying to resize partitions to back up but after attaching I'm having problems restarting and/or shutting down. I keep getting gray screen And have to shut down to start up. Now my external drive only shows one partition on desk top and I can't access in disk utility at all.

Hi!
We are having the same problem for years now (Forms10g with webutil) and had no solution but disabling the client cache. But this has to be done on the client.
In this Thread webutil&forms11g R2 64bit
a solution from oraclemysupport is mentioned, which can be done on the server:
JRE CRASHES/HANGS THE BROWSER HAVING HYPERTHREADING ENABLED [ID 601534.1]
(Solution 2)
We'l give it a try....

Start up with gray screen

Similar Messages

Maybe you are looking for