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.

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.

HELP Mac Mini will not boot after 10.5.1 update

After I tried installing 10.5.1 I received a warning message that the update will not be installed because of an error and I should contact the vendor. After that the Mini tries to reboot. It keeps repeating the process over and over. I have tried to do safe boot mode by manually turning off the computer and then restarting while holding shift, but nothing happens. Can anybody help?

BBlades wrote:
I think the problem might be with the external HDD I am running with this machine. I am reinstalling everything now from my time machine backup. I just added this hard drive the other night and it is loud as all **** and I believe it is why my machine has crashed. Before I added the drive, my system was running pretty good. It is a Calvary 160gb drive. I think I am going to have to send this POS back to newegg and get myself another Lacie drive, because my other Lacie is running smoothly.
I'd go with the LaCie. I got two from Amazon, 320 and 500 and both are quiet, have 800MHz FW and I have had no problems with either of them. The new one also has a 3-position switch - Off/Auto/On which allows it to sleep when not being accessed when in Auto.
I suspect that your external HD was the problem all along.

MAC Mini does not restart after Yosemite update

I bought my MAC mini in 2011 and I successfully updated to Mavericks with no problems. I am not sure why my MAC Mini will not restart after I updated to Yosemite. The completion bar gets stuck around 30%.
Any help or ideas appreciated
Larry

Okay, this is strange. I tried restarting three times yesterday with the same results. In fact I left it go overnight only to find the next morning that the bar was still stuck at 30%. I did a hard boot a little bit ago and waited a few seconds. I restarted an it booted up fine.
Larry

Mac Mini will not boot after Security Update 2008-007

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

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

Mac mini does not boot, no video signal, no chime

My mini "starts" without chime when I press the power button on the back. The fan starts, the light in front goes on and I hear some clicks which could be the hard drive. The screen remains black (no signal) and the mini does not respond to the USB keyboard power button. It does not start when pressing it and will not power down if I press it for any length of time when it is on. Pressing the power button on the back for some time shuts it down.
Time to get a new one?
Ingmar

You can try:
Resetting your Mac's PRAM and NVRAM
Intel-based Macs: Resetting the System Management Controller (SMC)
Then try booting from your installer DVD. If still no success then you most likely have a hardware failure.

2012 mac mini does not boot when usb 3 drive is connected

I have a late 2012 Mac Mini, Ivy Bridge, that has a USB 3.0 external hard drive connected to it. If the hard drive is powered on when I power up the Mac Mini, I get a light grey screen, but never see the Apple logo and the system just sists there. If I boot the Mac Mini with the USB 3.0 drive connected, but powered off, the Mac Mini boots just fine. Interestingly enough, if I reboot the Mac Mini with the USB 3.0 hard drive attached, the Mac Mini boots normally. I have installed all of the OS patches I can find and have not had any luck in resolving this. Does anyone have an idea what might be going on?

Something to check. Power everything down. Turn on
your external drives then do a PRAM zap booting the MIni.
http://support.apple.com/kb/PH11243
It may or may not help.
If it doesn't, then check the system log starting from the time
you start up the Mini and see what the last entry was. Wait a fair
amount of time so a gap in time in the log can be seen when you turn
the drive off. Could determine if it is some hardware issue, as BDAqua
was suggesting, or a driver issue.

Mac Mini will not boot after getting SBOD

Hi,
I was having problems with my Mac Mini being really slow to respond last night. I kept getting the SBOD every time I tried to move between applications or even between sites in Safari. It took an age to log on, sitting on the 'checking password' screen for minutes at a time every time I woke if from sleep/screensaver.
In the end I shut everything down this morning and tried a restart - however I ended up having to leave it before it had started up and go to work. Returning tonight it was still stuck on the grey screen with the wheel.
I tried both a couple of suggestions I found on a 'freezing after upgrading to 10.6..' thread - one was to reset the SMC, the other was to rest the PVRAM (or something like that - it involved holding down command-option-P-R) at start up. Both were unsuccessful - it's still sat here with the grey screen & the spinning wheel.
Any suggestions on what to do next? I've assumed that I'm on the latest version of Snow Leopard as I always tend to install the latest updates - but I can't be sure ... and obviously I have no way of checking!
HELP!

I tried the Disk Utility, which was unable to repair the problems. It then got worse, after not finding anyway to shut down (the only options I had were restart or start up disk) I just switched it off. Completely forgetting that this wouldn't eject the DVD! I then tried starting up again with the install DVD in an effort to try and find a way to eject the DVD, but now it just gives me a grey screen, no Apple logo, no gear wheel.
I now have an appointment with the Genius Bar today.

Brand new Mac Mini will not boot after 10.6.6 Update

Problem is exactly as described here: http://forums.macresource.com/read.php?1,1069909,1070656
The 1st restart was fine then it restarted for the 2nd time & it got to the gray screen with Apple logo & spinner. It sat there much longer than it ever had before then the Apple changed to a circle with a slash.
I tried booting into single user mode and it is hanging "waiting for root device"

Sounds like maybe your disk died.
I suggest that you boot from the install DVD that came with your Mac and run AHT to check it out.
Allan

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?

My new mac mini does not see usb drives, but in hardware info the usb is visible

my new mac mini does not see usb drives, but in hardware info the usb is visible
i'tried several usb flash drives even brand new ones, they are visible onder hardware info but they are not on the desktop nor in the finder.
what is wrong and doe anyone has a solution ?

It does not show up in disk utility, its only visible through systeminformation.
When you plug in the USB flash drive and then refresh systeminformation it becomes visible.
To remove it I shut down the computer because I cannot eject the USB device anywhere.
After starting up again when I have removed the flash drive it has gone from the systeminfo USB list.
By the way my USB mouse and keyboard are working fine, I also changed ports of these and they still keep on working so I don't think the USB ports are defect.
I guess it some kind software problem, and because I'm new to Apple I do not know much about it how to solve this.

Hello, mac mini will not boot. I get a file symbol with a question mark, then a white screen, Hello, mac mini will not boot. I get a file symbol with a question mark, then a white screen

Hello, My mac mini will not boot. When I turn it on, I get the chime, then the white screen, then the apple symbol, then a file symbol with a question mark, then the white screen and then it stays like that.
Is this a bad hard drive?

Sounds like it. Try booting from your OSX restore DVDs - startup and hold down "C". This will take AGES! Then run Disk Utility from the menu.
The flashing ? means your system is corrupt, dead, not there, on a dying HD, etc...

ITunes on new Mac Mini does not show shared libraries on network or songs on NAS drive

iTunes on new Mac Mini does not show shared libraries on network or songs on NAS drive
The latest version of iTunes on a 3-month old Mac Mini (8 gig RAM, OS 10.10.2) does not see any of the shared iTunes libraries on a MacBookPro (MBP) (OS 10.9.5) and a 14-month old Mac Mini (OS 10.9.5). And a network shared drive/media server does not appear as well. I have a Gigabite Ethernet G4 and on it, the MPB and the "old" mini I can see the various shared music libraries and NAS, but not on the new Mini.
The little house with a music note inside it that I see on the upper left corner of the iTunes 12.1 window on my MBP does not appear on iTunes 12.1 on the new Mac Mini. I have gone through all the iTunes preferences and can not find where I can turn on this feature. The new Mac Mini is on the local network and I can reach the internet successfully.
I have been using iTunes since its beginning (still have a PowerTower Pro with a working copy of SoundJam), so I am not a newbie, but this has me baffled.

May I add, that I gave full rights to the user at the Mac Mini to access and change data on the server drive for ITunes Media.

Why my 2006 mac mini does not receive updates

Why my Apple 2006 mac mini does not receive updates

To see if you are ready for 10.5, read:
https://discussions.apple.com/docs/DOC-2275
To see if you are ready for 10.6, read:
https://discussions.apple.com/docs/DOC-2455
To see if you are ready for 10.7, read:
https://discussions.apple.com/docs/DOC-2465

Mac Mini will not boot OS, can I get to files with another Mac?

My mac mini will not boot the OS proserly, it goes to a screen that tells me that some root folder can not be found.
The install CD works and I can boot to it. The disk utility reports no problems, all disk repairs done and OK.
The computer still will not boot to the OS.
How can I get the files I need off the drive before I reinstall the OS?
I have other Macs and fire wire cables, cross over cables, regular eithernet cables. What can I do?
Thanks!

How can I get the files I need off the drive before I reinstall the OS?
Connect it to another Mac with a FireWire cable and start it up with the T key held down.
(40535)

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

Similar Messages

Maybe you are looking for