OS does not boot after 10.5.6

I have a mid 2007 24" iMac with 4 GB of RAM. From 10.5.5 I ran the 10.5.6 from Software Update last night. The update never finished. In the reboot process, the iMac never shutdown--I saw the default desktop background and the wheel turning. I left it for about 45 minutes before turning it off by holding the power button.
Now, when I power it on, all I see is a flashing folder icon. I tried to boot from my AppleCare DVD by holding C, but that doesn't work.
Does anyone else have/had this problem? Is there a way to fix?

Do you have a wireless keyboard? If so, find a wired keyboard and try booting from the disk again.
You can also try starting up in the bootable drive menu by holding down the ‘option/alt’ key during startup.
Are you using the install disk shipped with that computer? It appears you have 2 iMacs. You cannot interchange the disks with the computers. It needs to be the install disk that came with that specific computer.
If you can repair the hard disk, download the update from the Apple Downloads website, check the .dmg file with Disk Utilities and try installing again.

Similar Messages

My mac mini does not boot, after backing the enire system onto an external drive with Carbon Copy Clone

My Mac Mini does not boot, after backing the enire system onto an external drive with Carbon Copy Clone. I had switched the start-up disk back to the original of course. Now all I see is the Apple logo. What should I do? Thanks in advance.

Try disconnecting any external devices, especially hard drives
and try rebooting.
If that doesn't help, then :
If you are running Lion, boot to the Recovery HD and run a
Repair Disk on the OSX partition.
If Snow Leopard, boot to the installl DVD and run Repair Disk.
Also, you may want to bookmark this:
http://reviews.cnet.com/8301-13727_7-57345273-263/troubleshooting-the-boot-proce ss-for-intel-macs/?tag=txt;title
for future reference. It is a pretty good explanation of the
Mac boot process and how to identify where problems may be.

New MBP i5 does not boot after hard disk swap

Hi there,
I received my new i5 MBP today. After booting it once with the installed HDD to check if it's ok, I exchanged the hard disk for the one in my Late 2008 Macbook Pro. After doing this, my Late 2008 Macbook Pro boots fine with the (new) hard disk from the new i5 MBP, but the i5 MBP does not boot with my old hard disk.
To give you some details:
- I have installed 10.6.3 on the (old) hard disk that's not booting.
- The i5 MBP boots fine from the installation DVD
- Disk utility finds and can read my hard disk, no errors
- PRAM NVRAM reset did not help
- when booting in safe mode, I can see the system stop booting after or while loading Extensions.mkext
My guess is, it tries to boot and load the wrong Extensions for the new system (CPU? GPU?). I have no idea how to fix this.
Any help would be greatly appreciated!

Focx,
Welcome to Apple Discussions.
Inserting the drive from an earlier model MBP will probably not work. The version of the system you have on that HD is designed for earlier hardware so when you put in in your new machine it's going to be recognized. What I'd recommend is re-installing the disk that came with the new machine and of course putting the 2008's disk back in the old machine. Then use Migration Assistant on the new machine and migrate your data from the old machine into the new machine.
This will provide a much more stable system and should work just fine.
Regards,
Roger

My iMac does not boot after update!!!

I have just update my iMac (Intel) with Apple Software update. I have not updated for quite a while and obvious there were a bunch of stuff to update on my mac. However, when the computer requests a restart, my computer simply does not restart at all. I have tried to make it restart from the apple icon, and it still stay on. So I turn it off manually and the problem kicks in. My computer start with the grey apple icon screen and the little progress indicator, but it does not boot into OS X!!! It remains in a blue screen with the mouse pointer.
I restarted it again unplugging everying and nothing changed. Then I tried Disk Repair and it does not help neither. Then I tried to hold the power button while turning it on till I get the loud beep noise and flashy light. The problem stay the same. I do not want to erase my disk...
Someone Helps!
Intel iMac 20" Dual Core / MacBook Pro 15" Mac OS X (10.4.6)

Interesting. Have you installed any third-party RAM? Is there any possibility that your RAM became loose? Make sure your existing RAM is seated properly.
Have you performed a SMC reset?
Resetting the SMC can resolve some computer issues such as not starting up:
From the Apple menu, choose Shut Down (or if the computer is not responding, hold the power button until it turns off).
Unplug all cables from the computer, including the power cord and any display cables.
Wait at least 15 seconds.
Plug the power cord back in, making sure the power button is not being pressed at the time. Then reconnect your keyboard and mouse to the computer.
Press the power button on the back to start up your computer.
Are you able to boot in SAFE mode? If so, you can trouble shoot from there.
Be sure the computer is shut down.
Press the power button.
Immediately after you hear the startup tone, press and hold the Shift key.
Tip: The Shift key should be held as soon as possible after the startup tone but not before.
Release the Shift key when you see the gray Apple and progress indicator (looks like a spinning gear).

Macbook pro does not boot after upgrading ram

I have a macbook pro late 2011 which runs with mavericks operating system . I have tried to upgrade my macbook to 8Gb. Macbook does not boot when the two ram slots are filled with 4GB ram but runs well when the slots are filled with 2GB ram. When i try them individually with one slot of 2GB ram and another slot with 4GB they run perfectly which shows status ok in the RAM info. What could be the problem .

Around here, most of us recommend only Crucial and OWC for RAM because it's guaranteed to work with Macs and it's what most of us have. If I were you, I would return the RAM and look at purchasing RAM from either Crucial or OWC. If you can't get their RAM to work then you'll know that there's some trouble with your actual slots.
Good luck,
Clinton
MacBook Pro (15-inch Late 2011), OS Mavericks 10.9.4, 16GB Crucial RAM, Crucial M500 960GB SSD, 27” Apple Thunderbolt Display

Help - Mac Mini does not boot after re-install of OS X

Hi,
I have a Mac Book Pro and Mac Mini. I needed to reinstall my Mac Mini but lost the install disks. The install disks of the Macbook do not work (machine specific). So what I did was boot the Mac Mini in firewire target mode and installed OS X to it from the Macbook. Worked ok. Except for one thing: The Mac mini does not boot the fresh OS X installation. I get a blinking folder icon with a question mark on top of it.
I booted from the Mac OS X install disk, repaired disk permissions etc. and tried to use the "Startup Disk" utility to select the hard drive as a boot device. But that utility does not offer me to select the hard disk, it doesn't even show up (while DiskUtility can perfectly see it).
Any hints for me? I am pretty much stuck right now.
Thanks

Well, see, the fact that it wouldn't let you boot from the MacBook install disks should have been your first clue to not try to do it. There's a reason it wouldn't let you. The MacBook install disks contain a version of the OS specific to the MacBook, in order to prevent people doing what you just tried to do (ie, installing the same copy of the OS on multiple machines).
If you don't have the Mac Mini system disks any more, you'll have to go buy a copy of OS X. You could also ask for help from an Apple Store, if there's one in your area, but I honestly don't know if they would give you new disks. I would think they should (for a small fee), since Mac Mini system disks would be useless to anyone who didn't already own a Mac Mini, but you never know.

Windows NT does not boot after installing NI-CAN 1.6.0 or security update

We are running Windows NT 4.0 SP 6 english with MS IE 5.5.
On one machine we had NI-CAN 1.6.0 installed. After installing the security update from Microsoft over the web the machine did not boot.
On another machine the security update was installed. After installing NI-CAN 1.6.0 the machine booted but hangs during logon. On this machine we installed Windows NT, MS IE 5.5 the security update and NI-CAN from new and the effect was the same.
Does anyone else have similar experience with this problem?
Machines with Windows 2000 and XP work well with NI-CAN 1.6.0.
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

Hi,
I haven't found any known issues. I going to try it out here. What's the security update you're installing?. I noticed there's a bunch of them in the Microsoft web site.
What CAN hardware do you have (PCI, PCMCIA, etc)?.
Let me know this details and I'll try to reproduce the problem.
DiegoF.
National Instruments.

Windows 7 does not boot after bootcamp installation

Hey!
I installed windows 7 x64 on my MBP 15" retina with bootcamp, and the installation went fine but after the installation when it said " prepairing your desktop" it just restarted and went into boot loop, so I had to boot into mac OSX and make it primary boot. This have happend 3 times, and I've recreated the ISO image on the USB and I've deleted windows 7 and the partition and I have done the whole process over again (3 times) and it still does not work. Sometimes I get into windows 7 the first time and can move around the desktop with the mouse for about 5 seconds, then it says "logging out" and I'm back at the same problem.
What can I do?
Best regards,
Jack Hellberg.

Hi Jack.........ok ive managed to create a link to that video on how to install bootcamp.....this is the tutorial i used and i managed to gain 100% completion on bootcamp 1st time no messing......like i said in my previous reply did you save the windows support files from apple....(Critical).....ok no point in messing about i suggest you start again from scratch........these are the things i used and YOU will need to complete bootcamp
mem stick or cd-r / dvd-r......original copy disc of win 7 ...i never used an iso i used original disc....allow a minimum of 30gb of space for your win 7 partition.....if you want bootcamp so you can use big programs like windows based games i.e.....Crysis/Call of duty etc etc ..then you will need to consider that you will need to allow a bigger partition to allow your HD to store the files.....this is the reason i installed bootcamp and so i made my partition i have a 750GB HD so i made a partition of 300gb for windows 7 and left the other 450gb for Mac....so you need to partition enough for what you want bootcamp for remember once you get bootcamp working you will need to install ALL Important Windows updates Including Win 7 SP1......once everything is installed you will have bootcamp up and running lovely.....u can then boot up with either win7 or mac......click this link and watch carefully and do exactly as shown ok and you should be fine...if you have any probs contact me again ok.....let me know how you get on ok..:)...http://www.youtube.com/watch?feature=fvwp&v=QFIWtXTl4d0&NR=1

Tecra A11-11N does not boot after CPU upgrade

Hi,
I would like to do a processor upgrade for my Tecra A11 11N from the i5-430M to a probably much faster i5.I thought the i5-580M would do, but the laptop did not boot when i installed this processor.
I reverted back to the 430M, did some research on the internet and found out that the 580M has a very high FSB speed and that is what probably made it not to work/incompatible with my machine.
http://ark.intel.com/products/43537/
http://ark.intel.com/products/49653
http://ark.intel.com/products/49652
and also at http://ark.intel.com/
Now i went back to the computer shop,returned the 580M and got an i5-560M as i compared it's specs and saw it would be compatible as it has the same FSB speed with the 430M.
I then later on in the day tried to install this cpu as an upgrade BUT alas!
It STILL WON'T BOOT ALSO.
I was left dumfounded.Processors in the same familly line are supposed to be compatible with one another provided:Lithography, FSB and socket type are similar.
Or what am i missing here?
I have done processor upgrades in many instances for both desktops and laptops and this is the first one that has left me with no words to say!
please offer some help/advice.
Simon
+Message was edited+

I solved this processor upgrade problem on my own.
I did some little research on what limits processor upgradability on computers and i
found out that BIOS was one of the factors that play a key part.
So,i went on a mission
to see if i could upgrade my BIOS and whether it would solve my problem.
I found this link to be very informative:
http://forums.computers.toshiba-europe.com/forums/thread.jspa?threadID=66624
I then downloaded the latest BIOS version for my laptop from this link:
http://uk.computers.toshiba-europe.com/innovation/download_bios.jsp
The following link gave me proof that the BIOS update would not bring any problems to my
machine and that there is already someone who had done it and not encountered any problems.
http://forums.computers.toshiba-europe.com/forums/thread.jspa?threadID=62459
Just to make sure that you are on the safe side,before carrying out the procedure to update
your BIOS,make sure you have a fully charged battery in addition to the AC plugged in.A power
outtage during this procedure would instantly kill your machine.
The BIOS installation took less than 3 mins.I copied the executable on the desktop and run it
from there.
On rebooting,the new BIOS was installed.The new BIOS version was 3.40 dated on 05/18/2012 while
the older one was version 2.0 dated on 04/03/2010.
From Intel's website,the i5-430M was released on Q1 2010 while the i5-560M and i5-580M were
released on Q3 2010.
It is pretty obvious that by the time BIOS version 2.0 was release,these two newer processors
had not been released and that explains why they were not being recognized when i installed them.
I finally swapped the 430M with the 560M,assembled back the machine and powered it.
Voil!,the machine booted to it's new life.Everything is as was before!
So far i have not seen any problems even to do with overheating or the cooling fan spinning any
faster that before.It is all the same as before.There is considerable performance gain with the
uprade.I am a software developer and my various development enviroments including compilers,
debuggers,database and deployment servers have all been running way way faster than they were!
I believe the 580M can also work but unfortunately i had returned it back to the shop.
There is no reason for buying new machines when we can upgrade the ones we have.What will
happen to the older ones?This means more electronic waste and so does new machines.Let us try
to make better use of the ones we have a in turn,SAVE OUR ONLY PLANET EARTH FROM GLOBAL WARMING!

Windows 7 x64 Professional does not boot after install

Hello.
I created a Windows 7 VM in Windows Server 2012 R2 Standard Hyper-V, all the installation process done successfully, but after installation, it failed to boot and shows a black screen, and didn't boot after it.
Following is the event log occurs.
'Win-7_QA-Testing' was faulted because the guest executed an intercepting instruction not supported by Hyper-V instruction emulation. If the problem persists, contact Product Support. (Virtual machine ID 5B827557-7009-4D83-AA7C-26A45651EC3A)
VmName
Win-7_QA-Testing
VmId
5B827557-7009-4D83-AA7C-26A45651EC3A
FailureCategory
<not a known problem>
InstructionByteCount
0
InstructionBytes
Rax
0x10
Rbx
0x80
Rcx
0x0
Rdx
0x80
Rsp
0x200
Rbp
0x6e08
Rsi
0x25da4a
Rdi
0x7da4a
R8
0x0
R9
0x0
R10
0x0
R11
0x0
R12
0x0
R13
0x0
R14
0x0
R15
0x0
Rip
0x9d
Rflags
0x10002
FpControlStatus
7F030000000000000000000000000000
XmmControlStatus
0000000000000000801F0000FFFF0000
Cr0
0x10
Cr2
0x0
Cr3
0x0
Cr4
0x0
Cr8
0x0
Xfem
0x0
Dr0
0x0
Dr1
0x0
Dr2
0x0
Dr3
0x0
Dr6
0xffff0ff0
Dr7
0x400
Es
0002000000000000FFFF000020009300
Cs
00000B0000000000FFFF000000B09F00
Ss
0002000000000000FFFF000020009300
Ds
0002000000000000FFFF000020009300
Fs
0002000000000000FFFF000020009300
Gs
0002000000000000FFFF000020009300
Ldtr
0000000000000000FFFFFFFF00000000
Tr
0000000000000000FFFF000000008B00
Idtr
000000000000FFFF0000000000000000
Gdtr
000000000000270000002B0000000000
Tsc
0x3b48531f8c6
ApicBase
0xfee00900
SysenterCs
0x0
SysenterEip
0x0
SysenterEsp
0x0
PendingInterruption
0x0
Any help will be appreciated.
Thanks

How many vCPU and how much RAM have you given the VM?
Are you using alt +F10 and going into the shell to format the VHD and prior to the installation?
Are you using media that has SP1 slip streamed into it?
Have you tried forcing the vm off and then back on again?
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.
vCPU = 1
RAM = 2048MB
No, I haven't try formatting the VHD between the window installation. This is the first time I'm facing the issue. It is a simple windows 7 pre activated iso file, not powered by SP1. I have tried forcing the VM off and ON again, but simply i can't get the
window screen back. Whenever the VM malfunctioning like this, then it cannot be shut down from the Hyper-V directly, but to make the VM Turn Off manually.

Mac does not boot after installing bootcamp

hello
installed bootcamp on my mbp with snow leopard today,for the first time mac and windows both started with no problem ,but when i was trying to boot back into the mac again ,it did not boot and just got stuck at the process with turning wheel forever ,showing the apple logo and the turning wheel.
i did try to hold the option button and chose the mac partition ,but again i can not pass thru the turning wheel and apple logo.Does anybody know what the problem is and how can i go beyond this .
thanks.mike

Csound1 wrote:
Have you tried a safe mode boot yet?
Reboot to the OSX partition and hold the shift key down as soon as you hear the chime. You can release the shift when you see the spinning gear wheel.
yes,i did try that too.unfortunately ,hard drive seemed to be the source of the problem.just replaced the hard drive with a brand new one and put this one inside a usb enclosure that i have ,so tomorrow i will get a backup first and then format it again and keep it for the future.
thanks.mike

Satellite M50D-A-10W does not boot after battery is fully empty

I have a Toshiba Satellite Notebook latop Satellite M50d-A-10W AMD A, 15.6.
I have problem when the battery is fully discharged I need use the needle to peform hard reset using switch behind the laptop.... then I can get into boot mode with f2
How can I solve the problem?
thank you

I guess you are talking about the force shutdown procedure as described in this document:
http://aps2.toshiba-tro.de/kb0/TSB3C03JR0000R01.htm
Such issue may appear in case the PC is freezing, not booting or has a power failure.
I think the notebook goes off in case the battery would be fully empty. In such case the system does not shut down properly.
As default state, the system does not shut down the notebook but usually the unit performs an hybrid shutdown. This procedure allows the notebook to boot much faster but this might affect system boot in case something would go wrong while shut down procedure.
You can disable this hybrid mode and in my opinion this is also recommended.
Details:
http://aps2.toshiba-tro.de/kb0/TSB2B03EY0002R01.htm
However, to avoid such issues its very important to perform the shut down procedure properly.

Macbook Pro does not boot after replacing HD

I have a Macbook Pro that I bought in early 2007. It came with 10.4, and I have since upgraded to 10.5, and then 10.6.
I decided to upgrade the original internal HD to a 500GB HD. I used Time Machine to back up the orignal HD.
After performing the surgery, I turned on the MBP with my Snow Leopard install DVD. After a while reading the DVD, the MBP spits out the DVD and displays the folder with the question mark.
I then create a recovery disk on an 8GB Flash Drive, using the Snow Leopard install disk as a source. I plug in the drive, start the MBP and hold down the 'option' key. I get a grey screen with a mouse cursor, but no drive icons.
I'm puzzled. The install DVD seems to look fine on other computers, as does the flash drive. I'm planning on getting a HD enclosure and cloning my old drive to the new drive, but does anyone have any suggestions as to what's gone wrong?
Thanks!

Dale Weisshaar wrote:
After performing the surgery, I turned on the MBP with my Snow Leopard install DVD. After a while reading the DVD, the MBP spits out the DVD and displays the folder with the question mark.
Are you holding down the small case letter c the whole time. Keep holding it till the install screen comes up.
Did that, still tried to boot (sounded like the drive was reading), and still got the folder with the question mark, and the DVD was ejected.
Also, it has to be a retail disk of Snow Leopard. A machine specific disk that came with another Mac will not work. You need the universal copy.
Right, my MBP came with 10.4 originally, so this was a retail disk.

Help! Arch does not boot after crash.

I'm so frustrated, I was just using my laptop like normal and I walked away from it for 2 minutes and when I got back it had turned itself off. I pushed the power and now when arch boots it gets as far as "INIT: Entering runlevel: 3" and after that it just hangs. This is extremely annoying because I can't do anything at all, it doesn't respond to any keys I press or anything, it just hangs there. I booted up to my ubuntu partition and got online to research my problem and I found that my inittab file had gone completely missing! I can't really think of any reason why this would happen, but it just vanished. Maybe it had to do with the fact that I upgraded earlier in the day (much earlier than the crash though)?
So what I ended up doing is taking the inittab skottish posted here http://bbs.archlinux.org/viewtopic.php?id=90539 and trying it, but no luck I get the same results. So then I tried reinstalling initscripts using the method described here http://bbs.archlinux.org/viewtopic.php? … 06#p694906 but that didn't do me any good either. I have no idea where to go from here, if there are any logs or other files I can post that will help you help me get this sorted out I will be happy to oblige. I would really like to be able to use my arch partition again, it had quickly become my favorite .
Thanks so much, I really appreciate any help I can get,
Nate

Here's what it says
Apr 28 23:03:55 nate-laptop kernel: BUG: scheduling while atomic: plymouthd/707/0x00000002
Apr 28 23:03:55 nate-laptop kernel: Modules linked in: fuse ext3 jbd snd_hda_codec_idt snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device arc4 ecb snd_hda_intel snd_pcm_oss snd_mixer_oss snd_hda_codec snd_hwdep radeon snd_pcm b44 b43 ttm drm_kms_helper snd_timer snd soundcore drm video sdhci_pci joydev dell_wmi i2c_algo_bit output ssb snd_page_alloc wmi sdhci mii ac battery pcmcia psmouse mmc_core pcmcia_core i2c_piix4 thermal button ohci_hcd processor ricoh_mmc mac80211 shpchp pci_hotplug ehci_hcd serio_raw i2c_core edac_core edac_mce_amd dell_laptop usbcore sg k8temp cfg80211 evdev rfkill dcdbas led_class rtc_cmos rtc_core rtc_lib ext4 mbcache jbd2 crc16 sr_mod cdrom sd_mod ata_generic ahci pata_atiixp pata_acpi libata scsi_mod
Apr 28 23:03:55 nate-laptop kernel: Pid: 707, comm: plymouthd Tainted: G D W 2.6.33-ARCH #1
Apr 28 23:03:55 nate-laptop kernel: Call Trace:
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff81044071>] __schedule_bug+0x61/0x70
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff8135a797>] schedule+0x577/0xad0
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff810785b2>] ? down_trylock+0x32/0x50
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff81057241>] do_exit+0x7e1/0x820
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff81359dfd>] ? printk+0x3c/0x3f
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff81053c35>] ? kmsg_dump+0x145/0x160
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff8100e9c5>] oops_end+0xa5/0xf0
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff810310e3>] no_context+0xf3/0x260
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff81031365>] __bad_area_nosemaphore+0x115/0x1d0
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff8103142e>] bad_area_nosemaphore+0xe/0x10
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff8103183a>] do_page_fault+0x25a/0x320
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff8135dfa5>] page_fault+0x25/0x30
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff8135b90b>] ? __mutex_lock_slowpath+0xcb/0x370
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff8135b8f0>] ? __mutex_lock_slowpath+0xb0/0x370
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff8113539a>] ? __d_free+0x3a/0x60
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff8135bbc1>] mutex_lock+0x11/0x30
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff811fbab4>] fb_release+0x24/0x70
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff811237fa>] __fput+0xda/0x1f0
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff8112392d>] fput+0x1d/0x30
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff8111ff88>] filp_close+0x58/0x90
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff81055187>] put_files_struct+0x77/0xe0
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff8105523d>] exit_files+0x4d/0x60
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff81056bbe>] do_exit+0x15e/0x820
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff81066048>] ? __sigqueue_free+0x38/0x40
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff81067047>] ? __dequeue_signal+0xd7/0x1f0
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff810572cc>] do_group_exit+0x4c/0xc0
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff81069679>] get_signal_to_deliver+0x2c9/0x500
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff81009370>] do_signal+0x70/0x7a0
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff81066385>] ? sys_rt_sigaction+0x85/0xc0
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff81009b05>] do_notify_resume+0x65/0x90
Apr 28 23:03:55 nate-laptop kernel: [<ffffffff8100a28e>] int_signal+0x12/0x17
Apr 28 23:03:55 nate-laptop kernel: b44: eth0: Link is up at 100 Mbps, full duplex.
Apr 28 23:03:55 nate-laptop kernel: b44: eth0: Flow control is off for TX and off for RX.
Apr 28 23:03:55 nate-laptop acpid: starting up
Apr 28 23:03:55 nate-laptop acpid: 4 rules loaded
Apr 28 23:03:55 nate-laptop acpid: waiting for events: event logging is off
Apr 28 23:03:56 nate-laptop acpid: client connected from 3563[82:82]
Apr 28 23:03:56 nate-laptop acpid: 1 client rule loaded
Apr 28 23:03:56 nate-laptop crond[3580]: /usr/sbin/crond 4.4 dillon's cron daemon, started with loglevel info
Apr 28 23:03:35 nate-laptop load-modules.sh: Not loading module alias 'pcspkr' because it is blacklisted
Apr 28 23:03:35 nate-laptop load-modules.sh: 'pci:v00001002d00004384sv00000000sd00000000bc06sc04i01' is not a valid module or alias name
Apr 28 23:03:35 nate-laptop load-modules.sh: 'pci:v00001022d00001101sv00000000sd00000000bc06sc00i00' is not a valid module or alias name
Apr 28 23:03:35 nate-laptop load-modules.sh: 'pci:v00001022d00001100sv00000000sd00000000bc06sc00i00' is not a valid module or alias name
Apr 28 23:03:35 nate-laptop load-modules.sh: 'pci:v00001002d0000438Dsv00001028sd000001F5bc06sc01i00' is not a valid module or alias name
Apr 28 23:03:35 nate-laptop load-modules.sh: 'acpi:LNXSYSTM:' is not a valid module or alias name
Apr 28 23:03:35 nate-laptop load-modules.sh: 'pci:v00001002d00005950sv00001028sd000001F5bc06sc00i00' is not a valid module or alias name
Apr 28 23:03:35 nate-laptop load-modules.sh: 'acpi:LNXSYBUS:' is not a valid module or alias name
Apr 28 23:03:35 nate-laptop load-modules.sh: Not loading module 'pcspkr' for alias 'platform:pcspkr' because it is blacklisted
Apr 28 23:03:36 nate-laptop load-modules.sh: 'platform:regulatory' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'platform:dell-laptop' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:PNP0C01:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:PNP0100:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:PNP0C04:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:PNP0000:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:SYN1015:SYN0100:SYN0002:PNP0F13:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:PNP0303:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:PNP0800:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:PNP0200:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:PNP0C02:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'wmi:05901221-D566-11D1-B2F0-00A0C9062910' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'wmi:8D9DDCBC-A997-11DA-B012-B622A1EF5492' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'wmi:A80593CE-A997-11DA-B012-B622A1EF5492' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'wmi:A3776CE0-1E88-11DB-A98B-0800200C9A66' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:36 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:37 nate-laptop load-modules.sh: 'ssb:v4243id0817rev03' is not a valid module or alias name
Apr 28 23:03:37 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:37 nate-laptop load-modules.sh: 'acpi:device:' is not a valid module or alias name
Apr 28 23:03:37 nate-laptop load-modules.sh: 'platform:radeon_cp' is not a valid module or alias name
Apr 28 23:03:37 nate-laptop load-modules.sh: 'ssb:v4243id0807rev03' is not a valid module or alias name
Apr 28 23:03:40 nate-laptop ntfs-3g[3271]: Version 2010.3.6 external FUSE 28
Apr 28 23:03:40 nate-laptop ntfs-3g[3271]: Mounted /dev/sda4 (Read-Write, label "OS", NTFS 3.1)
Apr 28 23:03:40 nate-laptop ntfs-3g[3271]: Cmdline options: rw
Apr 28 23:03:40 nate-laptop ntfs-3g[3271]: Mount options: rw,silent,allow_other,nonempty,relatime,fsname=/dev/sda4,blkdev,blksize=4096
Apr 28 23:03:40 nate-laptop ntfs-3g[3271]: Ownership and permissions disabled, configuration type 1
Apr 28 23:03:43 nate-laptop init: Entering runlevel: 3
Apr 28 23:03:43 nate-laptop dhcpcd: version 5.2.2 starting
Apr 28 23:03:43 nate-laptop dhcpcd: eth0: broadcasting for a lease
Apr 28 23:03:48 nate-laptop dhcpcd: eth0: offered 192.168.1.80 from 192.168.1.254
Apr 28 23:03:48 nate-laptop dhcpcd: eth0: acknowledged 192.168.1.80 from 192.168.1.254
Apr 28 23:03:48 nate-laptop dhcpcd: eth0: checking for 192.168.1.80
Apr 28 23:03:54 nate-laptop dhcpcd: eth0: leased 192.168.1.80 for 86400 seconds
Apr 28 23:03:54 nate-laptop dhcpcd: forking to background
Apr 28 23:03:58 nate-laptop kernel: b43 ssb0:0: firmware: requesting b43/ucode5.fw
Apr 28 23:03:58 nate-laptop kernel: b43 ssb0:0: firmware: requesting b43/pcm5.fw
Apr 28 23:03:58 nate-laptop kernel: b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
Apr 28 23:03:58 nate-laptop kernel: b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
Apr 28 23:03:58 nate-laptop kernel: b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
Apr 28 23:04:01 nate-laptop crond[3580]: FILE /var/spool/cron/root USER root PID 3646 job sys-hourly
Apr 28 23:04:01 nate-laptop crond[3580]: FILE /var/spool/cron/root USER root PID 3647 job sys-daily
Apr 28 23:04:19 nate-laptop smbd[3778]: [2010/04/28 23:04:19.414344, 0] printing/print_cups.c:108(cups_connect)
Apr 28 23:04:19 nate-laptop smbd[3778]: Unable to connect to CUPS server /var/run/cups/cups.sock:631 - No such file or directory
Apr 28 23:04:19 nate-laptop smbd[3779]: [2010/04/28 23:04:19.426490, 0] printing/print_cups.c:108(cups_connect)
Apr 28 23:04:19 nate-laptop smbd[3779]: Unable to connect to CUPS server /var/run/cups/cups.sock:631 - No such file or directory
Apr 28 23:04:20 nate-laptop kernel: NET: Registered protocol family 10
Apr 28 23:04:20 nate-laptop kernel: lo: Disabled Privacy Extensions
Apr 28 23:04:23 nate-laptop kernel: b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
Apr 28 23:04:23 nate-laptop kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Apr 28 23:04:43 nate-laptop nmbd[3788]: [2010/04/28 23:04:43.298321, 0] nmbd/nmbd_become_lmb.c:395(become_local_master_stage2)
Apr 28 23:04:43 nate-laptop nmbd[3788]: *****
Apr 28 23:04:43 nate-laptop nmbd[3788]:
Apr 28 23:04:43 nate-laptop nmbd[3788]: Samba name server NATE-LAPTOP is now a local master browser for workgroup WORKGROUP on subnet 192.168.1.80
Apr 28 23:04:43 nate-laptop nmbd[3788]:
Apr 28 23:04:43 nate-laptop nmbd[3788]: *****
Apr 28 23:05:24 nate-laptop shutdown[3819]: shutting down for system reboot
Apr 28 23:05:24 nate-laptop init: Switching to runlevel: 6
Apr 28 23:05:25 nate-laptop shutdown[3823]: shutting down for system reboot
Apr 28 23:05:26 nate-laptop acpid: exiting
Apr 28 23:05:26 nate-laptop nmbd[3788]: [2010/04/28 23:05:26.169070, 0] nmbd/nmbd.c:71(terminate)
Apr 28 23:05:26 nate-laptop nmbd[3788]: Got SIGTERM: going down...
Apr 28 23:05:26 nate-laptop ntfs-3g[3271]: Unmounting /dev/sda4 (OS)
Apr 28 23:05:26 nate-laptop syslog-ng[3468]: Termination requested via signal, terminating;
Apr 28 23:05:26 nate-laptop syslog-ng[3468]: syslog-ng shutting down; version='3.1.0'
Could it have something to do with those errors regarding my CUPS setup? That couldn't cause something like this could it?

Pismo does not boot after replacing hard drive

We have had an old Pismo for several years now. Two or so years ago we decided to replace the stock 6GB hard drive, which was getting full, with a new 60GB drive. We cloned the old drive via target disk mode, popped in the new drive, copied the data back (again via target disk mode), and were surprised when we were met with the flashing question mark/system folder icon. Sort of left it at that and forgot about it.
I stumbled upon the Pismo again today and decided to see if I couldn't get it working. After going through a few "why won't this even turn on" sessions (the machine hadn't been powered on in a few years, so pulling the internal battery and resetting the PMU fixed that), I popped the old drive back in and the machine booted just fine. Cloned the original drive (again) using Carbon Copy Cloner via target disk mode to a disk image on my MacBook. Powered it down, put the new (60GB) drive back in the Pismo, cloned the disk image back to the new drive. The data's there, because I can browse it in target disk mode, but I can't boot off the new hard drive. I can't boot off my Tiger install DVD either - the DVD drive spins up and tries to access the disc, but won't boot. I'm going to try and get my hands on the CD version of Tiger to see if there's a difference using that.
Disk Utility on the MacBook says there's nothing wrong with the Pismo's hard drive, but I'm not convinced that's the case. I'd heard about Pismos being picky with certain types of hard drives, is this true? If not, what other issues might be leading to this behavior?

Is this perhaps an artifact of the drive being formatted via target disk mode on my MacBook
I suspect that the problem lies somewhere in that situation. I suggest that you boot from the install disk as I suggested previously and reformat the HDD and reinstall the OS.
Formatting, Partitioning Erasing a Hard Disk Drive
Warning! This procedure will destroy all data on your Hard Disk Drive. Be sure you have an up-to-date, tested backup of at least your Users folder and any third party applications you do not want to re-install before attempting this procedure.
• Boot the MacBook Firewire Target Disk Mode.
• Insert install disk into MacBook's optical drive.
• Connect computers via firewire cable
• Option Boot Pismo.
• Select Install Disk for startup and click on the straight arrow.
• Select language
• Go to the Utilities menu (Tiger and later) Installer menu (Panther & earlier) and launch Disk Utility.
• Select your HDD (manufacturer ID) in left side bar.
• Select Partition tab in main panel. (You are about to create a single partition volume.)
• Click on Options button
• Select Apple Partition Map (PPC Macs)
• Click OK
• Select number of partitions in pull-down menu above Volume diagram.
(Note 1: One partition is normally preferable for an internal HDD.)
• Type in name in Name field (usually Macintosh HD)
• Select Volume Format as Mac OS Extended (Journaled)
• Click Apply/Partition button at bottom of panel.
• Select Erase tab
• Select the sub-volume (indented) under Manufacturer ID (usually Macintosh HD).
• Check to be sure your Volume Name and Volume Format are correct.
• Click Erase button
• Quit Disk Utility.
Open installer and begin installation process.
cornelius

Macbook air does not boot after yosemite update

After latest Yosemite update my Mac book Air is not finishing to reboot, all I see is the white apple on the black screen and the progress bar whch loads slowly and kind of get stuck half the way to the end, and it stays there forever.
I forced to restart with the start hardware key and it does the same. any idea what went wrong and or what can I do next?
thanks

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.

OS does not boot after 10.5.6

Similar Messages

Maybe you are looking for