MBP won't start or boot up

Hi all, new to the mac world but learning alot! I have owned my Pro for 8 months now and work 50% of time in Thailand. This recent trip, my MBP simply stopped booting up. It starts fine with the normal start chime, noise from CD drive, then white screen with apple logo and spinning wheel. That's as far as it gets. I started using command s for single user and did a repair of the HD. This worked, I then rebooted using start up disk and pressing C. Still not starting, stopping at logo and spinning wheel. I then went to command v and watched for hang up. It seems to stop and repeat trying to access (com.apple.mDNSResponder [311]: posix_spawnp("/usr/sbin/mNDSResponder", ... No such file or directory.
I am at a loss as to what this is and how to get past this. I do remember that the last time I was on the machine, 3 days ago, I changed the permission of the hard drive for guests to read only. I am wondering if this is the problem. When I started in single mode, the root is read only. How can I change this if I need to? I am far from any mac repair facility and am 4 weeks from going back to Vancouver, soooo, I am hoping someone out there can assist me. I don't mind typing commands in at the root, I just don't know the language. I am working from a borrowed Toshiba for the time being, but I am missing my mac. Long and short of it is if I have to reformat, I don't mind, I have my install disks with me. Thanks

Okay, so no whiz kids have read this post yet. I got a little further by getting the cd drive to boot in single user, however it too stopped at a unable to read and write to someplace, this may be RAM problems, will try booting from one and the other RAM set independently, more to follow.

Similar Messages

MBP won't start up. Steps to take?

Hi
MBP, 10.6.8
After a few days of more and more sluggish starts my MBP won't start up. Not the wheel but the strips keep circling. The last time it started it took about 10 minutes to happen.
I'd like to do the reinstall where apps aren't touched, but should I do the hardware test first or just go for the reinstall? Or are there other procedures I should entertain?
Also, if I do the easy reinstall that will drop me back to a lower osx. Can I immediately click software update and gete back up to 10.6.8 or will that be a problem?

Ok, first I got this message:
Checking Journaled HFS Plus volume.
Checking extens overflow file
Unused node is not erased (node = 882)
Checking catalog file
Invalid mode strictire
The volume My Name was found corrupt and needs to be repaired.
Error: Dist Utility can’t repair this disk. … dis, and restore your backed-up fiiles
Then a window dropped down saying
Version:1.0 StartHTML:0000000105 EndHTML:0000002844 StartFragment:0000001899 EndFragment:0000002808
Disk Utility stopped repairing My Name
Disk utility can’t repair this disk. Back up as many files as possible, reformat the disk, and restore your backed-up fil.
Ok, but how do I back-up my files when I can't see the drives? Would the hardware test provide any repair help? Can I attach it to my old MBP and start up while holding down 'T' to make it a fw drive?
In this install mode from my disc will I be able to choose the version that allows my apps to be saved or only clean install?
And when I reformat which format should I use?
Any suggestions?

2010 mbp won't start

Hello Everyone:
MY mid-2010 MBP won't start and instead of the usual start up chime, I get a relatively short beep every few seconds until I turn it of. once in a while< like now< it starts but according to my teen, video is very choppy. i watch video but different speed i think. I use a host site to stream videos like american horror story, scandal, walking dead but no japanese anime - which is what my kid watches as well. But he also watches tv shows from a similar site but finds all videos in general-choppy. I've seen some choppiness in the scandal video; i would have thought it would have been the Walking Dead. Can anyone tell me what they feel my system's issue is?
I have another issue but i believe they're completely unrelated so i'll post it separately (that's a hopeful invite for all your mac "doctors" who love to 'heal'.)
Thanks again, in advance, for your help.
Regards,
Ciaochiao

It's probably a failing graphics processor. The 2010 MBP are notorious for that: MacBook Pro (15-inch, Mid 2010): Intermittent black screen or loss of video - Apple Support

NVRM error, now mt MBP won't start

Over the last 2 weeks, my MBP would crash (mostly during playing games). At first, I could just restart it and after a few restart it would be fine. But yesterday it crashed again after I managed to restart it (after another crash). But now it won't start up.
At start up, I would get the grey screen with Apple logo and then after 30 seconds or so, the grey screen gets distorted and generally the graphics are all messed up (and crash). I have tried booting up from Leopard CD, but it gets to a certain part and I get the Mac crash screen where it says the Mac has crashed and I need to restart.
Before it got to this stage, I have managed to restart it and after a restart, I got a noticed saying my Mac has crash and would I like to send report to Apple. So I did (3 times) and below is the error I got.
Fri Feb 6 22:56:59 2009
panic(cpu 0 caller 0x00405DEB): "NVRM: Read Error: GPU 0, PCI 0x00000100, BAR0 0x92000000 0x3a0e2000"@/SourceCache/xnu/xnu-1228.9.59/iokit/Kernel/IOLib.cpp:724
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x39cb7548 : 0x12b4f3 (0x45b13c 0x39cb757c 0x1335e4 0x0)
0x39cb7598 : 0x405deb (0x49da40 0xda3280 0x39cb75dc 0x39cb75cc)
0x39cb75b8 : 0xb744f7 (0xda3280 0xda3280 0xd67c88 0x0)
0x39cb75f8 : 0xe2bd1a (0x4d73404 0x4d78804 0x100b80 0xbb356a)
0x39cb7638 : 0xe10feb (0x4d78804 0x100b80 0x0 0x0)
0x39cb7688 : 0xddb6ef (0x4d78804 0x4d8f804 0x39cb77b8 0x0)
0x39cb77f8 : 0xe44d16 (0x4d78804 0x4b7c004 0x0 0x1)
0x39cb7878 : 0xe1bd79 (0x4d78804 0x4bbc604 0x40 0x3e8)
0x39cb7998 : 0xcd6a00 (0x4d78804 0x4eeb804 0x39cb7a88 0x39cb7a88)
0x39cb7ab8 : 0xcd66c2 (0x4d78804 0x4ef4804 0x0 0x0)
0x39cb7b38 : 0xe14392 (0x4d78804 0x4ef4804 0x6 0x2)
0x39cb7bb8 : 0xe1517e (0x4d78804 0x4eeb804 0x1000 0x39cb7cdc)
0x39cb7d38 : 0xe46320 (0x4d78804 0x4eeb804 0x0 0x0)
0x39cb7e88 : 0xcca16f (0x4d78804 0x4bbc604 0x0 0x0)
0x39cb7ed8 : 0xb749b6 (0x4d78804 0x4bbc604 0x0 0x0)
0x39cb7f18 : 0x4224ff (0x0 0x4fb1c80 0x1 0x19eb5b)
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.nvidia.nv50hal(5.3.6)@0xdb8000->0x100cfff
dependency: com.apple.NVDAResman(5.3.6)@0xb5b000
com.apple.NVDAResman(5.3.6)@0xb5b000->0xdb7fff
dependency: com.apple.iokit.IONDRVSupport(1.7.1)@0xb4d000
dependency: com.apple.iokit.IOPCIFamily(2.5)@0x5d2000
dependency: com.apple.iokit.IOGraphicsFamily(1.7.1)@0xaee000
BSD process name corresponding to current thread: kernel_task
Mac OS version:
9G55
Kernel version:
Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST 2008; root:xnu-1228.9.59~1/RELEASE_I386
System model name: MacBookPro3,1 (Mac-F4238BC8)
This sounds very much like this error http://support.apple.com/kb/TS2377 but in this doc, nothing was said about not being able to start up the MBP.
The thing is I really need to boot up one last time to get some files off there, is there anyway I could boot up one last time? As I said before it won't boot up from HDD, not from CD, I tried booting up from external HDD but that system is 10.4 so it didn't show up.
Would appreciate any help so I can get these files off before I take it into repair!
Thanks

I just had a whole day of kernel panics and screen flicker (video flicker - not backlight) yesterday. I had stuck and incorrectly updated windows on the screen. Soon after that the machine crashed. A few reboots later the MacBook would freeze after a few minutes of use and then finally it would only boot into the dimmed screen of death or a stuck spinning wheel (even when booting form CD!!!). Inbetween, I managed to boot it from CD, but the machine crashed during disk check and finished the check (no errors) the third time!
I followed all instructions (5 secs power button while without battery and power) did NOT help.
I disconnected battery and power supply and let the MacBook sit for a few hours. That helped and magically the machine booted as if nothing happened.
I ran the loooong hardware test. Everything fine. I ran the disk check everything fine. I am clueless.
Today I had the same crash again, but at least everything was fine after a hard reboot. It even crashed the attached iPhone, which suddenly showed the Apple icon ?!? Hard to believe!
Remark: many of the crashes did not result in a kernel panic, but just froze the computer.
Kernel Panic Backtraces:
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.NVDAResman(5.4.4)@0xb6d000->0xdcbfff
dependency: com.apple.iokit.IONDRVSupport(1.7.3)@0xb5f000
dependency: com.apple.iokit.IOPCIFamily(2.6)@0x5cd000
dependency: com.apple.iokit.IOGraphicsFamily(1.7.3)@0xac6000
com.apple.iokit.IONDRVSupport(1.7.3)@0xb5f000->0xb6cfff
dependency: com.apple.iokit.IOPCIFamily(2.6)@0x5cd000
dependency: com.apple.iokit.IOGraphicsFamily(1.7.3)@0xac6000
com.apple.iokit.IOGraphicsFamily(1.7.3)@0xac6000->0xae2fff
dependency: com.apple.iokit.IOPCIFamily(2.6)@0x5cd000
BSD process name corresponding to current thread: WindowServer
Mac OS version:
9J61
Kernel version:
Darwin Kernel Version 9.7.0: Tue Mar 31 22:52:17 PDT 2009; root:xnu-1228.12.14~1/RELEASE_I386
========== (Booted from CD) ===============
Backtrace continues...
Kernel loadable modules in backtrace (with dependencies):
com.apple.NVDAResman(5.1.6)@0x64308000->0x64534fff
dependency: com.apple.iokit.IONDRVSupport(1.5)@0x54eb1000
dependency: com.apple.iokit.IOPCIFamily(2.4)@0x54efc000
dependency: com.apple.iokit.IOGraphicsFamily(1.5)@0x55146000
com.apple.iokit.IONDRVSupport(1.5)@0x54eb1000->0x54ebefff
dependency: com.apple.iokit.IOPCIFamily(2.4)@0x54efc000
dependency: com.apple.iokit.IOGraphicsFamily(1.5)@0x55146000
com.apple.iokit.IOGraphicsFamily(1.5)@0x55146000->0x55161fff
dependency: com.apple.iokit.IOPCIFamily(2.4)@0x54efc000
BSD process name corresponding to current thread: WindowServer
Mac OS version:
9A581
Kernel version:
Darwin Kernel Version 9.0.0: Tue Oct 9 21:35:55 PDT 2007; root:xnu-1228~1/RELEASE_I386
System model name: MacBookPro3,1 (Mac-F42388C8)
Message was edited by: katzlbt

2010 13" mbp won't start.

Hey all,
My mbp isn't working properly, it's a 13" from 2010. When I turn it on it sounds like it's starting to boot but will then shut down after about 5-10 seconds. After that it will start up again but the screen stays black. The fan will continue to blow until the computer shuts down (after holding the power button). During this whole time the caps button light doesn't turn on when pressed (if that makes a difference). I'd love to get this thing working as its only a couple years old. Any help would be greatly appreciated.
TIA

Thanks for the quick response pennbank unfortunately the screen is still blank on startup. When I reset the smc the led on the power adapter turns from orange to green then back to orange again. After doing all of this the computer does the same thing it did in my previous post. I can't reset the pram. Ive tried a couple different combinations of holding the 4 keys in that reset (on first start-up, on second and at different times on the second strat-up) but it won't restart.
Any other help would be greatly appreciated.
TIA

New MBP won't start up

I have a brand new 13" Macbook Pro, just a few days old, which I have barely used or had time to set up yet. Last night I shut the lid and it went into sleep mode. The battery was almost full. This morning I opened the lid and it came on instantly as expected, but before I could do anything the screen dimmed and a message box appeared in the middle of the screen with the message that I needed to power down the laptop and then reboot it! This was in about five languages (I think - I never really took much notice before I switched off) When I tried to turn it back on, it simply won't start. When you push the power button, the 'power/sleep' light on the front lights up briefly then goes off again. The battery charge is still the same as last night i.e. almost full (all bar the last two LED's come on) I tried the SMC reset but it makes no difference. It simply won't power up. Obviously I will be taking it back to the Apple store, but I wondered if anyone else has had the message appear and why? And then fail to boot!
Message was edited by: Murena22

As I'm new to this forum, I'm not sure how it is supposed to work, but it is certainly not like others I have used! What is happening here? I edited my post and it shows at the bottom that it was edited, yet the edited post does not appear - it is still the same as the original! None of the added text appears.
I tried to add that there were no programs running and it was on battery when closed at night and when opened this morning. I've also tried it on mains power, but it makes no difference. It still appears to charge correctly judging by the power lead and laptop LEDs. It just won't turn on.

IMac Won't Start Up/Boot

My iMac won't start up. I've tried holding all kinds of key combinations while I turn it on, but it doesn't even get that far. It gets stuck on a folder with the Apple picture alternating with a question mark. It doesn't do anything else for a while, and then the fan turns on (???).

This is indicative of a corrupted system or drive. The first thing to try is:
Repairing the Hard Drive
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.) 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 quit DU and return to the installer. Now shutdown the computer for a couple of minutes and then restart normally.
If DU reports errors it cannot fix, then you will need Disk Warrior (4.0 for Tiger) and/or TechTool Pro (4.5.2 for Tiger) 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.
If this doesn't solve the problem then you will have to reinstall OS X. If the drive tests out OK per the above then you can reinstall without erasing the hard drive:
How to Perform an Archive and Install
1. Be sure to use Disk Utility first to repair the disk before performing the Archive and Install.
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.
Why reward points?(Quoted from Discussions Terms of Use.)
The reward system helps to increase community participation. When a community member gives you (or another member) a reward for providing helpful advice or a solution to their question, your accumulated points will increase your status level within the community.
Members may reward you with 5 points if they deem that your reply is helpful and 10 points if you post a solution to their issue. Likewise, when you mark a reply as Helpful or Solved in your own created topic, you will be awarding the respondent with the same point values.

MBP won't start up past initial grey screen!!!

My MBP just stopped starting up today. When I turn it on, it goes to the normal grey screen with the apple. Then, when it switches to the blue screen, it just gets frozen, and won't do anything. I don't know what to do. Any suggestions????

DiskWarrior would probably fix it. Did you try to fsck it?
1. Reboot/Startup holding your Command-S key down.
2. At the command line type the following and hit 'Return.'
/sbin/fsck -fy
3. After it has check/repaired your disk, type 'reboot' and hit 'Return' again. Unit should bootup normally.
-Bmer
Mac Owners Support Group
Join Us @ MacOSG.com
ITMS: MacOSG Podcast
 An Apple User Group 

MBP Won't start, blinking ? Mark... Nothing works

I'm currently at work writing this on my 4 year old ibook g4, because after a complete system lock up yesterday, my MBP would not start up. It chimes, and then gives me the screen with a blinking question mark inside a folder.
I've read about this problem alot, and I've done almost every possible fix i could think of. I'm just finally getting my system back the way I had it after a crash a couple months ago in which i archived and installed, only to find the previous system folder intact, nothing switched over (users, settings etc), and my permissions all sorts of messed up.
So i'm really trying to avoid having to do another archive and install. Here's what I got so far:
The MBP's hard drive works, and mounts fine on the iBook using target disk mode. I ran disk utility (both from the iBook using TDM, and from the 10.5 install disk), both said the volume is fine and no repairs were necessary. I also reset pram, and tried starting up without extensions. no luck
i most recently downloaded DiskWarrior, and ran the rebuild on the system.
This also had no effect.
Is there anything else I can do to make this work?
I have full access to the MBP hard drive via the ibook.
Starting from CD, the hard drive is not an option for startup in "startup disk", and is also not an option from startup disk on the ibook.

It's quite possible for a drive to pass all the diagnostic tests and yet not be bootable simply because one or more files are damaged but not in any way that the diagnostic software can find. You have no choice but reinstall the operating system. Whether you choose Archive & Install or erase and install is up to you.
Your description of the earlier A&I is not typical and it sounds like something went awry. Usually A&I is the best and safest method of reinstalling the OS.

[SOLVED - partly] Minidlna won't start on boot, but OK otherwise

I am using an up-to-date system as of 2012-11-13. The problem is that minidlna fails to start on boot:
minidlna.service - minidlna server
Loaded: loaded (/usr/lib/systemd/system/minidlna.service; enabled)
Active: failed (Result: exit-code) since Tue, 2012-11-13 07:53:55 CET; 1h 33min ago
Process: 401 ExecStart=/usr/sbin/minidlna -P /var/run/minidlna/minidlna.pid (code=exited, status=255)
CGroup: name=systemd:/system/minidlna.service
Nov 13 07:53:59 earth minidlna[401]: [2012/11/13 07:53:54] minidlna.c:754: fatal: No IP address automatically detected!
So I guess it has to do something with the network, I am using DHCP, with systemd + net-auto-wired.service.
I have found this: https://ask.fedoraproject.org/question/ … r-dhcp-has
They have solved the problem by changing the after part in the unit by adding: dbus-org.freedesktop.NetworkManager.target
Since I do not use networkmanager, this is not an option for me. The current, unmanipulated state of the minidlna unit is:
[Unit]
Description=minidlna server
After=network.target
[Service]
Type=forking
User=nobody
ExecStart=/usr/sbin/minidlna -P /var/run/minidlna/minidlna.pid
PIDFile=/var/run/minidlna/minidlna.pid
[Install]
WantedBy=multi-user.target
What I have noticed is that it refers to a network.target in the after section, but it seems to me that I don't have one.
I only have:
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
basic.target loaded active active Basic System
cryptsetup.target loaded active active Encrypted Volumes
getty.target loaded active active Login Prompts
graphical.target loaded active active Graphical Interface
local-fs-pre.target loaded active active Local File Systems (Pre)
local-fs.target loaded active active Local File Systems
multi-user.target loaded active active Multi-User
remote-fs.target loaded active active Remote File Systems
sockets.target loaded active active Sockets
sound.target loaded active active Sound Card
swap.target loaded active active Swap
sysinit.target loaded active active System Initialization
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
JOB = Pending job for the unit.
12 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
Edit: having run the command again with the --all prefix:
Notice: network.target loaded inactive dead Network
UNIT LOAD ACTIVE SUB JOB DESCRIPTION
basic.target loaded active active Basic System
cryptsetup.target loaded active active Encrypted Volumes
emergency.target loaded inactive dead Emergency Mode
final.target loaded inactive dead Final Step
getty.target loaded active active Login Prompts
graphical.target loaded active active Graphical Interface
local-fs-pre.target loaded active active Local File Systems (Pre)
local-fs.target loaded active active Local File Systems
multi-user.target loaded active active Multi-User
network.target loaded inactive dead Network
nss-lookup.target loaded inactive dead Host and Network Name Lookups
nss-user-lookup.target loaded inactive dead User and Group Name Lookups
remote-fs.target loaded active active Remote File Systems
rescue.target loaded inactive dead Rescue Mode
shutdown.target loaded inactive dead Shutdown
sockets.target loaded active active Sockets
sound.target loaded active active Sound Card
swap.target loaded active active Swap
sysinit.target loaded active active System Initialization
syslog.target loaded inactive dead Syslog
umount.target loaded inactive dead Unmount All Filesystems
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
JOB = Pending job for the unit.
21 loaded units listed.
To show all installed unit files use 'systemctl list-unit-files'.
My question is what should I add to the after part to make minidlna work upon booting? Wouldn't a graphical.target be an overkill?
Thanks in advance.
Last edited by szebenyib (2012-12-02 16:45:26)

szebenyib wrote:(However I cannot access the internet that way, maybe because of a bad network file. Honestly I have some space to improve my network knowledge.)
In the case of the possible bad network file. here is what it expects. First, you need to know the router's IP address. In the following I will assume 192.168.0.1 for the router's IP address.
192.168.0.1 is common for D-Link routers, but it does vary by router manufacturer and model. I believe 192.168.1.1 is common for Linksys.
/etc/conf.d/network
interface=eth0 # ethernet port to activate, usually eth0
address=192.168.0.110 # IP address you want the minidlna computer to have. the first 3 triads must be the same as the router's IP addr in this case 192.168.0 the fourth triad can be from 5 to 250
netmask=24
broadcast=192.168.0.255 # the first 3 triads must be the same as the router's IP address and the fourth triad should be 255
gateway=192.168.0.1 # the IP address of your router
In a terminal window, enter:
systemctl restart network.service
ping -c5 127.0.0.1
which is localhost. The -c5 means ping 5 times then quit. If you get: 5 packets transmitted, 5 received, 0% packet loss then the ping was successful, which means
that the ethernet port (usually eth0) is active. If this ping is not successful, go back and check the syntax and spelling in both /etc/conf.d/network and /etc/systemd/system/network.service
If the ping is successful:
ping -c5 192.168.0.1
and ping the router.
If you cannot ping the router's IP address, then there is still something wrong in one of the two involved files. or the router's settings need to be changed.
If you can ping the router's IP address successfully and still cannot get to the internet, you probably have DNS server issues.
ping -c5 google.com
ping -c5 8.8.8.8
If you cannot ping google.com but can ping 8.8.8.8 then you have DNS problems, see Arch WIKI resolv.conf
My network is a mixture of DHCP and STATIC IP addresses. In my router, I have the DHCP server enabled to give IP addresses between 192.168.0.10 and 192.168.0.60
this gives the router 50 DHCP addresses to work with which is more that enough for my home network. The rest of the addresses between 192.168.0.61 and 192.168.0.250
can be used as static addresses. Just an example, this can be changed as necessary.
HTH
Pudge

Openntpd won't start at boot [SOLVED]

Hi all!
My system clock is perpetually off by 4 hours, and I've narrowed it down to an issue with Openntpd; it seems to be refusing to start at boot time. Here are the relevant lines from daemon.log:
Sep 1 21:30:26 raskolnikov ntpd[1440]: Terminating
and the output of ps aux | grep ntpd:
[raskolnikov@raskolnikov ~]$ ps aux | grep ntpd
ntp 1323 0.0 0.0 3184 700 ? S 17:32 0:00 /usr/sbin/ntpd -s
root 1332 0.0 0.0 3292 256 ? Ss 17:32 0:00 /usr/sbin/ntpd -s
1000 1412 0.0 0.0 3616 800 pts/0 S+ 17:33 0:00 grep ntp
I can manually restart the daemon via /etc/rc.d/openntpd restart, which works fine, and the time is set correctly. However, when I reboot, the adjustments are wiped out, and the daemon does not start again (same message in daemon.log). I have the default ntpd.conf. I have found very little helpful information on Google, I would greatly appreciate it if someone could point me in the right direction, I've wasted quite a few hours this evening working on this problem! Thanks!
Edit: Just in case it's helpful, here is my daemons array from rc.conf:
DAEMONS=(syslog-ng !network acpid eee hal networkmanager netfs crond openntpd bitlbee)
Last edited by happycodemonkey (2009-09-02 03:55:46)

I've had this problem too, although I do not use networkmanager. I've found that openntpd fails to configure itself properly if the network is not up when it starts (in my case this happens when I background the network daemon and start openntpd in the daemons array).
My current working solution* is to add this line to rc.local:
(sleep 300 && /etc/rc.d/openntpd start) &
That will wait 5 minutes before starting the openntpd daemon which gives the network more than sufficient time to start. An alternative would be run "/etc/rc.d/openntpd restart" in an hourly cronjob if your network settings change often.
* Why not just unbackground the network daemon you ask? If the network isn't up then it takes a while to timeout and I don't want to wait to boot in that case.
Last edited by Xyne (2009-09-02 02:05:52)

MBP won't start on battery even tho its charged.

Hi,
I have a Mac Book Pro which I bought sometime in April. Just yesterday, when I unplugged the AC adaptor, the computer shut down, even though the battery says it is fully charged.
The green lights on the battery itself are all on.
When I try to start up my Macbook without the AC adaptor, it turns on for a second(i hear the superdrive turning), then it shut downs again. I just got this computer..whats the deal . Good thing I have apple care.
Oh, I tried to restart the PMU. I shutdown comp, take ac adaptor out, and battery out, and click on the power button for five seconds. Still no progress. I saw another thread on this..let me see if it'll help.

I report another case of the identical problem: The MBP will not start on battery alone, though it is completely charged as indicated both by the menu bar and by battery LED's. Furthermore, disconnecting the power adapter while running, causes the computer to go down immediately and completely, despite fully charged battery.
The behavior began abruptly after about ten weeks of normal use, though it was preceded in the last week or two by a few instances of the battery running completely down without a "low power" warning. Whether these are related symptoms, I don't know, but have read a number of reports of the latter problem.
I will request a new battery from Apple Care, but it sounds as if this may not get to the heart of the problem. Any further info would be appreciated.
MacBook Pro Mac OS X (10.4.7)

MBP won't start after failed update

my mbp wont start after shutting down during the latest RAW photo update. the update completely failed and now the computer won't boot anything. i could hear the hard drive try to start over and over but never get anywhere, so i inserted the leopard cd. the computer wont even boot from the disk at this point; all i hear is the optical drive making the same, start-up, squeaking sound again and again until i finally hold power for 5 seconds and shut it off.
i have a mbp from summer 2007.

Press the Power Button and immediately press and hold down the Command and the S keys as the machine starts up. This boots you into Single-user mode and you should see white text appear on the screen.
When you see the # Command prompt, type /sbin/fsck-fy and hit the Return.
Now sit back & let your computer do its thing. This should take approximately 15 minutes or so. Depending on how messed up your computer is. Just be patient.
If and when you see the message File System was modified repeat the steps above again & again until you hopefully see the message no problems were found." When that happens type reboot and hit Return again.
If these steps do not work then boot from your install disc to repair disk. I believe you already tried this.
To use the Install Mac OS X disc, insert the disc, and restart your computer while holding down the C key as it starts up.
Select your language.
Once on the desktop, select Utility in the menu bar.
Select Disk Utility.
Select the disk or volume in the list of disks and volumes, and then click First Aid.
Click Repair Disk.
Your random question, only Apple can answer that for you. Ask them and back up before you bring in your computer to the Apple store just in case.

MBP won't start from Disk Warrior CD and now won't restart at all.

I tried starting my MBP from DW CD and I keep getting screen with Terminal type font and a message that says I need to restart my computer. When I restart I get the same screen over and over. (Now typing on iPhone so bare with me!)

What you will need to do is restore your OS.
http://support.apple.com/kb/PH11273
Follow the instructions on this page. If you need someone to help you walk through it just let me know. This process will bypass your computer trying to boot on the Operating System and will boot on a recovery partition. And from here you can try to see whats going on. You might try and go through disk utility and verify disk and see if it can locate the problem. If there is click repair and hopefully it will do the trick.
Hope this helps!
-Steven

MBP won't start up after Snow Leopard update

Hi, I just installed the update for Snow Leopard. I restarted my computer and now it won't get past the grey screen, the darker screen just comes down and says I need to restarte my computer.
Is there anything I can do myself or do I need to take it in to get checked?
Thanks!

HI Phillip,
Grab your install disk that came with your MBPro and use Disk Utility to check the drive.
Insert Installer disk and Restart, holding down the "C" key until grey Apple appears.
Go to Installer menu (Panther and earlier) or Utilities menu (Tiger and later) and launch Disk Utility.
Select your HDD (manufacturer ID) in the left panel.
Select First Aid in the Main panel.
*(Check S.M.A.R.T Status of HDD at the bottom of right panel. It should say: Verified)*
Click Repair Disk on the bottom right.
If DU reports disk does not need repairs quit DU and restart.
If DU reports errors Repair again and again until DU reports disk is repaired.
When you are finished with DU, from the Menu Bar, select Utilities/Startup Manager.
Select your start up disk and click Restart
While you have the DU window open, look at the bottom of the window. You will see Capacity and Available. Never allow the free disk space to fall below 10% of the capacity.
If you cannot boot from your install disk, try booting in Safe Mode
What is Safe Mode
Carolyn
Message was edited by: Carolyn Samit

MBP won't start or boot up

Similar Messages

Maybe you are looking for