Mini hangs at boot up screen

My mini hangs at the grey bootup screen and will not continue beyond it.
I recently had an old Macbook pro hardrive attached to the Mini via USB to transfer some data.
This old drive also had a recent version of OSX on it but I never booted to this drive.
The Mini read the drive, I transferred the data, shut it down, and the next day it would not boot and would only hang on the grey boot up screen.
It won't boot up whether or not I have the old Macbook drive attached or not.
I tried a PRAM reset.
Did I somehow make the Mini look for a wrong boot drive and is there anyhting I can do to fix or reset it without having to reformat?

It was purchased in August 2012 and I'm pretty sure it's dual i5's with 8GB ram running the latest OS.
I don't have the recover disk at the moment as the computer was recently loaned to me. Does this typically come on thumbdrive with the computer? (If so I cn have the owner search for it but he say's he does not recall it.)
It has no drive for CD/DVD reinstall.
If I had an external USB drive with the same OS on it would I be able to boot to that drive? And from there backup the main drive to the USB drive and then reformat the main drive if necessary?

Similar Messages

Mac Mini hangs on boot with grey Screen. No response to Keyboard

Hello,
yesterday my Mac Mini (C2Duo, fifth generation unibody) startet to behave strangely. First thing was that it was not responding to the mouse(connected throught the keyboard)
I replaced the mouse and everything seemed to be ok.
I then did the latest update available on Mountain Lion and went home.
When I came back this morning, the Mac Mini hang with grey screen. I restarted. Again grey screen.
Chime comes. Then nothing.
Tried everything from http://support.apple.com/kb/ts2570 but nothing worked. The Mac Mini does not seem to be responding
to any keyboard command to enter safe mode, select boot device etc. No firmware password has been set.
Any help/ suggestions would be appreciated.
Yours,
Andreas

Have you reset the SMC, then held down the mouse button while restarting to get the CD out?
Reset SMC:
Shut down the computer.
Unplug the computer's power cord.
Wait fifteen seconds.
Attach the computer's power cord.
Wait five seconds, then press the power button to turn on the computer.

Tecra S1 doesn't boot and hangs at (boot) splash screen

Tecra S1 Model PT831E-107EQ-GR
Problems started a month ago. It randomly didn't booted. After some power off/on tries it finally booted and worked properly. Because it happened more often I've bought a new hard drive (Toshiba 40 GB). I've had Acronis True Image and planned to make a disk clone to the new drive. The problem is that a notebook now doesn't boot anymore so I cannot boot it from A CD nor hard drive. It stops at "In Touch..." logo with "Press [F12] for the boot device selection menu" text and doesn't react any key. I tried to boot with no CD, no hard drive - the same. I also connected internal HD using ATA-To-USB adapter - the same. Does it mean that's not a disk problem but motherboard or other components? Is it possible to enter BIOS before boot selection screen?
Regards,
Jacek

Problem solved. There was a broken PCB under the CPU socket. I've found that pressing with my finger and holding CPU while booting allowed to startup the system while releasing the finger caused system hanging and its total crash. Our local service tried to repair it but with no success. Finally two days ago we've found a working motherboard (a used one) for about 200 USD and now I'm waiting for installing it in the laptop. Th regular price for a new one (about 400 Euro) is too much, but 200 USD is OK. I do like the laptop because of its ports (LPT, RS232). It's used for programming and controlling some older devices. Newer laptops have no LPTs nor RS232s and it's not easy to find a working USB adapter because the software we're using is even from DOS times and has hard-coded IRQs for those ports.
Anyway, I hope it'll back from the service fresh and new, and of course working ;)
Thank you for your tips.
Regards,
Jacek

T43 - Hangs on boot-up screen

Dear all,
I have a 2668-45G Thinkpad T43 which just doesn't boot anymore. This laptop wasn't booted or charged for a long time before I got it. Warranty has run out just 1,5 months ago.
Exact description:
- Pressing Power-On button results to start-up the notebook. Boot-up screen is shown and nothing else happens.
- No reaction if I press the "Access IBM" button or F1 at all. I cannot enter BIOS, nor is there any other reaction (no beeps, no error message, no num-lock-light switching).
Hard drive is turning, CD-ROM is preparing.
What did I try so far:
- Take out battery and AC-cable, pressed power-on button 10 times for a longer time. Then I plugged the AC cable in and pushed F1 during power-on. Sometimes I come to the startup menu. But only rarely. And if I get there, again no reaction on key pressing.
- I opened the laptop, if there is any visible problem. There isn't. After opening and closing, I could once switch to the BIOS, but there was no reaction to any further key pressing. So I could not reset the BIOS to some default state.
- The laptops beeps though if I remove the memory module.
What can I do now?
Please help me.
Best regards
Laurence
Message Edited by lm1976 on 11-21-2008 10:56 AM
Message Edited by lm1976 on 11-21-2008 11:04 AM
Message Edited by lm1976 on 11-21-2008 11:13 AM
Message Edited by lm1976 on 11-21-2008 11:27 AM
Solved!
Go to Solution.

Another shot in the dark...can you swap the CMOS battery with one from your R50?
If we don't have a BIOS that is messed-up (which is an unfortunate option) sheer persistance and attention to small details might get us somewhere...
My knowledge is really of little use right now, as is my experience. Personally, I'd keep the HD out, along with battery, wireless and BT cards and keep attempting to get it to boot in different intervals...not much science there, but that's the best I've got right now, I might be smarter a little later...or never...
Also, applying permanent pressure of a light nature on the spot where keyboard enters the planar as in couple of bent "post-it" sheets might be worth considering...
Good luck and keep us posted.
Cheers,
George
In daily use: R60F, R500F, T61, T410
Collecting dust: T60
Enjoying retirement: A31p, T42p,
Non-ThinkPads: Panasonic CF-31 & CF-52, HP 8760W
Starting Thursday, 08/14/2014 I'll be away from the forums until further notice. Please do NOT send private messages since I won't be able to read them. Thank you.

[~SOLVED] 1 min hang during boot while mounting xfs partitions (LVM)

Hi all,
After the upgrade I did yesterday (which included linux-3.12.8-1 and lvm2), the boot time has increased by 1 minute as the system hangs while mounting two partitions formatted as xfs and residing on logical volumes.
$ systemd-analyze blame
1min 13.676s home-VDP76-videos.mount
1min 13.111s home-VDP76-VBox_VMs.mount
2.980s [email protected]
I have the fsck hook as second-to-last entry in my mkinitcpio.conf, but the fstab entries for these partitions include
... xfs defaults 0 0
so, as far as I undertstand, the partitions should not be checked, am I missing something!?
I have googled for similar issues but I did not find anything useful, any suggestion would be greatly appreciated.
Thanks
edit: I blame the check disk because of what reported on the system journal (note the time stamps):
Jan 23 00:10:37 ArchTP kernel: psmouse serio5: alps: Unknown ALPS touchpad: E7=10 00 64, EC=10 00 64
Jan 23 00:10:39 ArchTP kernel: psmouse serio5: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3
Jan 23 00:10:40 ArchTP kernel: input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio4/serio5/input/input25
Jan 23 00:11:47 ArchTP systemd[1]: Mounted /home/VDP76/VBox_VMs.
Jan 23 00:11:47 ArchTP kernel: XFS (dm-4): Ending clean mount
Jan 23 00:11:47 ArchTP kernel: XFS (dm-3): Ending clean mount
Jan 23 00:11:47 ArchTP systemd[1]: Mounted /home/VDP76/videos.
Jan 23 00:11:47 ArchTP systemd[1]: Starting Local File Systems.
Jan 23 00:11:47 ArchTP systemd[1]: Reached target Local File Systems.
I should also add that the involved partitions are ~20 Gb each and quite full...
edit2: I have freed up almost all space on the video partition and the time for mounting those partitions has now decreased to 8 sec...I will mark the thread as solved, but I still would appreciate an input on the reasons why the partitions are checked regardless of the fstab setting, for example, is this pertinent!?
dumpe2fs -h /dev/mapper/waldorf-video | grep -i 'mount count'
dumpe2fs 1.42.8 (20-Jun-2013)
dumpe2fs: Bad magic number in super-block while trying to open /dev/mapper/waldorf-video
Last edited by VDP76 (2014-01-22 23:38:25)

WonderWoofy wrote:I don't think that the fsck.xfs is really a fsck at all. It is there for compatibility purposes, and a real check can be done with xfs_check and xfs_repair. So the fsck.xfs will just always give an exit status of zero.
exactly..in fact the man page says
fsck.xfs(8) wrote:fsck.xfs - do nothing, successfully
so fsck.xfs simply exits with a zero exit status.
running xfs_check gives
xfs_check is deprecated and scheduled for removal in June 2014.
Please use xfs_repair -n <dev> instead.
and xfs_repair does not find errors on both partitions.
Still, I do not understand how nothing being done can take up so much time.
By the way, a short S.M.A.R.T. self-test did not report errors...
In the meanwhile, there has been another kernel upgrade and the timing issue persists, so I am assuming it has something to do with the last lvm2 upgrade.

Mac Mini hangs on startup screen

Need help, my mini hangs on the startup screen the dial benieth the apple logo spins, but nothing else happens. I was having difficulty connecting to the internet before the issue started, tried to open internet connect, when it wouldn't open I tried a restart, now all I get is the startup screen.
I'm really concerned with un-backed up data, any ideas of how to get in and backup before making any drastic changes?
I can take to the apple store tomorrow, so I don't want to do anything that would potentially lose data or make things worse.
Please help if you know what is going on. Thanks.

Whatever else, do not, at this time, attempt an erase and install, since this would delete all your existing data in the attempt to get a bootable system back in operation.
Since your primary concern is your data, backing this up is the first priority. To do this, you could use firewire target disk mode if you have another Mac available (as previously suggested). However, if you do not have another Mac to hand for this, the safest way to deal with the situation with least risk to existing data is to use an external drive, preferably connected via Firewire, and install MacOS on that, then boot the system to it by holding the Option key down during startup. That would give you a booted system from which you can then examine the internal drive.
There is a possibility that your internal drive will then not be visible, which would indicate either serious directory damage or a hardware issue. Disk Utility can be used to check the drive if it is visible, and even attempt a repair if it is. However if it fails, you will then need to use commercial software such as ProSoft Data Rescue II (an excellent data recovery application) to retrieve data from the drive, or Allsoft's DiskWarrior to attempt a repair on the drive, being aware that even though often effective, there is a risk with tools such as DiskWarrior that in using them they can effect a repair on the drive that makes it viable again, but loose data in the process, thus backing up or retrieving data first is usually the wisest course.
As to the drive itself, it is possible the boot issue being experienced is due to a hardware problem with the drive which would mean a replacement is needed. This is not all that common however. It is more likely to be the result of directory structure errors, in which case Disk Utility or DiskWarrior may be able to resolve the problem, leaving the drive functional without any further action or with little more than an archive and install. However, not all such errors are repairable, and hence an erase and install may be needed.
One way or another, do not attempt to write anything to the drive or change any data on it until you have either retrieved/backed up your data, or decided not to do so. If the data structure is damaged, any and every attempt to modify the data on the drive can render it harder to recover data from it intact.

Mac mini unable to boot, stuck in grey screen.

Hi,
i have a Mac Mini which I have kept up to date with current version of OS X (Mountain Lion)
After a recent reboot the system won't come up, it just hangs displaying a grey screen.
I have tried:
http://support.apple.com/kb/TS2570
I can boot up the system in single user mode.( https://support.apple.com/kb/ht1492 )
I have done a /sbin/fsck -fy and this works fine. I can browse the file system, the only
strange thing I notice is "BootCacheControl: Unable to open /var/db/BootCache.playlist: 2 No such file or directory".
I have googled quite a lot but I have not managed to find a solution for this, though it is frequently mentioned.
I have tried the normal diagnostics and no hardware error is reported.
I have tried to boot into local recovery, this starts but after a while I end up with the grey screen.
I have tried a Internet recovery and this starts, the screen flashes for a second and I end up with the gray screen
I have tried the different reset methods, such as NVRAM ( http://support.apple.com/kb/HT1379 )
I have tried to reset the SMC ( http://support.apple.com/kb/ht3964 )
I have swapped the RAM modules for other ones.
testing my internet connectivity; speedtest.net reports 15 Mbit downstream and 2 Mbit upstream
Even if I leave my Mac mini on for 12+ hours the internet recovery never finishes, nor am I presented with any options, just the grey screen.
Because the Mac mini doesn't ship with any DVD-media and the Mountain Lion I have bought is through the app store I couldn’t try to boot
from a DVD.
The reason I bought a Mac was to get away from problems which is typically related to computers (Windows). I am running out of ideas here,
please help!
Kind Regards

Whew,
Great work so far, is it still covered unfer AppleCare? I think you'd done all you can do & it needs to be taken in.

My G4 hangs on a grey screen when I try to boot in OS 9 help?!

I'm desperate! My mac G4 that I've been running for years with both OS X and OX 9 has been unable to boot in OS 9 and I've tried almost everything form option hold on restarts to shift (exrtensions off) zapping the pram etc. I know others have had this problem. I've researched a lot already. I used the same G4 and the same monitor and hardware and everything for years and this problem suddenly sprang up out of nowhere. I desperately need to get this machine to boot in OS 9 because I'm using Protools with many plugins and cards that are not supported on OS X. When I boot in OS X it acts fine no problem like it always did. When ever I try to boot in OS 9 it hangs on a grey screen and then freezes up before and happy face and or extensions have loaded etc.
One thing, and I don't know how important this may be, is that the first time I encountered this problem was after I had attached a USB hub to my computer which had been sitting unused for some weeks and the Hub somehow made the computer start up when I plugged in the USB cable to the USB Hub?! After that OS 9 has refused to boot period no matter what I do. I can run some apps in the classic environment but cannot boot to OS 9 at all ever.
I read in one forum where a guy did an open firmware reset and got some error messages that had to do with USB. He was having the same problem the grey screen when trying to boot on OS 9.
Does any one have an answer Please I'm almost ready to give up!

Hey me back again month later. Well I have tried everything. I even pulled the hard drive out of my G4 and replaced it with a tested and working hard drive which had only OS9 installed on it. In other words that computer had two choices boot into OS 9 or hang on a grey screen. There was no other system present to boot into, so after chiming and starting the boot process it just hangs on the grey screen again. So I guess what Steve Jobs meant when he said OS 9 is dead is that they killed OS 9 because my machine will not look at any OS 9 system folder regardless of whether OS X exists on the machine or not. I tried to reboot holding down option command P R and after the second chime grey screen again. I've read that OS 9 requires some small folder or bytes to be recognized in order to boot which it is obvious newer versions of OS X purposely and maliciously delete in order to make it inoperable. My protools gear works fine I've rested it on other machines. The only way that I can use it is to be able to boot into OS9. Which has been corrupted by OS X. They say you can format a disc with OS 9 drivers but I see no such option using OS 10.4 tiger so I'm not sure what they are talking about.
So here is my question. Why would a G4 450mghz machine with a working OS 9 hard disc installed with no other system folders available not boot after it chimes and begins the start up process. If it is because running OS 10.4 disables the OS 9 drivers and corrupts the machine so that it can never look at a OS 9 again let's just admit that and say OK Steve was right OS 9 is dead but it did not die of natural causes.

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...

System Boot Hangs on Grey Apple screen / AppleIntelCPUPowerManagement

Hi All
I have had this issue on going on MacPro (early 2008) Quad 3.0 and Quad 2.8 machines since 10.5.6.
Boot will hang on the grey screen with Apple Logo or in verbose mode more specifically on AppleIntelCPUPowerManagement: Initialization Complete.
In an attempt to fix I have repaired permissions & disks, both with DU and DW which report no major problems, removed system cache files and eventually reinstalled OSX from scratch and updated to current 10.5.8 systems. I have also tried the singleuser boot and /sbin/fsck -fy command which reports no problems. Still it persists.
The issue presents it's self randomly on multiple machines at various times. If I leave the computer long enough sometimes the boot will complete.. or not. Simply booting up in verbose mode will sometimes get the machine booting. This usually requires a hard power cycle from the hanging boot. re-seating the ram has also helped but so far no conclusive fix.
The only thing that I can think to relate it to is that these machines all share the same system image created with Carbon Copy Cloner (Current Version), however this also occurs on the Master machine. So either I have cloned the issue from the source (twice) or it is inherent to the machines. I have used a different master machine on the 2nd reinstall of the OSX system to rule out the master machine as the introduction of the issue.
These are all standard config Macpro machines with no modifications since getting them out of the box. I only mention this as I have researched this issue and mostly find that the machine in question had been altered in some way.
Does anybody have any further ideas on how I could resolve this?
I would appreciate your perspectives.
cheers,
k.
Ps. I have also posted in http://discussions.apple.com/message.jspa?messageID=10177491#10177491 as it has been the most relevant thread.

bump

Mac Mini running Snow leopard gray screen won't boot up.

My mac mini server was running great! working on some file sharing issues system crashed. Ran utilities check repair disks and first aid said no problems with either HD. I would like to reboot and install system software. without deleting my tunes lib. and some other software. what can I do?

I think you want to first disable Lion Server: How to disable Lion Server. Then reinstall Lion:
Reinstalling Lion
Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alterhatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu.
Reinstall Lion: Select Reinstall Lion and click on the Continue button.
Note: You can also re-download the Lion installer by opening the App Store application. Hold down the OPTION key and click on the Purchases icon in the toolbar. You should now see an active Install button to the right of your Lion purchase entry. There are situations in which this will not work. For example, if you are already booted into the Lion you originally purchased with your Apple ID or if an instance of the Lion installer is located anywhere on your computer.
Then reinstall Lion Server.

Satellite L640 hangs at boot screen

Hi all,
I have an L640/01H which I bought at the beginning of this year. Besides the original Windows 7 OS, I installed a Linux system on a separate partition.
Earlier today I was using the Linux (which is what I normally use) and everything was really slow.
Eventually I force-shut-down using the power button.
Now, I've noticed an issue with the BIOS on this laptop - if I attempt to boot up when there is a USB flash drive plugged in, the boot screen just hangs. Today when I rebooted I realized that I had left a flash drive in, so I took it out and tried to boot again, a couple of times. Each time the computer would just hang indefinitely on the boot splash screen.
Eventually I gave it enough time and it got to the Linux boot selection menu, then I tried to boot my usual kernel but it gave me some message about a bad MBR.
I kept trying to boot but the boot process is stuck, what happens is as follows:
*The three lights on the left (power, battery and on light) come on, no problem
* The HDD light flashes white for a couple of seconds, then goes off. Occasionally it flashes again.
* Meanwhile the screen is just stuck on the boot splash screen. If I try to press f2, f12 or any key too many times it will start emitting beeps every time I press it. There's no way to get into the BIOS settings.
I also cannot boot from CD (Windows recovery CD or Linux liveCDs). Eventually some sort of time-out comes into effect and the computer restarts itself to begin the process all over again. Yay!
I tried the "unplug power cord, remove battery, hold down power button, plug back in, try to start" trick but nothing changed. I also tried switching memory slots (only one RAM chip, so I can't try an elimination process on the RAM).
Finally, I also opened up the HDD compartment and removed the HDD, then tried to boot. This time the BIOS responded, if only to tell me that there was no suitable boot media. At this point the BIOS was responsive and I could change settings in it, but I still couldn't boot from CD.
I was thinking of trying to reset the CMOS battery but I'm worried I'll damage something/make the problem worse. Does anyone have any ideas? I know the thing is still under warranty, but service centres are often slow and I don't want to lose hard drive data.
Any help would really be appreciated.

> Finally, I also opened up the HDD compartment and removed the HDD, then tried to boot. This time the BIOS responded, if only to tell me that there was no suitable boot media. At this point the BIOS was responsive and I could change settings in it, but I still couldn't boot from CD.
It could be a problem with CD/DVD drive what do you think about this idea?
Possibly the BIOS cannot recognize the CD/DVD drive properly and therefore there is a problem booting up from the bootable disk.
Additionally it could be possible that the HDD malfunctions and therefore you have received error message concerning MBR (master boot record) .
Remove the CD/DVD drive and try to install the Windows booting from USB flash drive.
_Regarding the CMOS battery:_
I would not recommend to disassemble the notebook because you could damage other parts and additionally you have to know that the CMOS battery is not removable its soldered on mobo

HP Mini 110-3500 Netbook: How to skip Boot Manager screen when booting into Windows 7 Starter

Hi,
As per the topic. I can't seem to deactivate the boot manager screen and it's getting really annoying having to press the enter key each and every time I turn on my netbook.

First you need to get into the BIOS. You can accomplish this by holding down the F10 (aka volume up) key located on the top of the keyboard near the right.
Next hit the right > arrow key (located on the right bottom of the keyboard) 3 times to get you to the System Configuration tab.
Thirdly, hit the down arrow key (located on the right bottom of the keyboard) 3 times to take you to the Boot Options sub menu and hit Enter
Hit the down arrow key once to highlight HP Quickweb and hit enter.
Select Disabled and hit Enter
Hit F10 (Yes should be selected) and hit Enter
DONE!!!

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 won't boot anymore

My Mac mini won't boot anymore. It's been running fine for months.
It's running Leopard Server 10.5.2 Build 9C31
It starts to boot, I get the first spinning gear with the gray screen, then the blue desktop blinks, then a second spinning gear on a gray screen and it appears to hang (the gear stops spinning).
I booted off the install DVD, ran disk utility, repaired the HD, repaired the permissions: the behavior is the same.
Safe mode doesn't work (same hang as above).
Single user mode does work.
I can connect to it via Server Admin while it appears hung.
The last few lines of the system log are:
May 15 18:38:58 server emond[67]: SetUpLogs: uid = 0 gid = 0
May 15 18:38:58 server emond[67]: SetUpLogs: opening /Library/Logs/EventMonitor/EventMonitor.error.log
May 15 18:38:59 server kextd[23]: writing kernel link data to /var/run/mach.sym
May 15 18:39:09 server KernelEventAgent[59]: tid 00000000 received unknown event (12)
May 15 18:39:20 server kernel[0]: display: Not usable
May 15 18:39:20 server com.apple.KerberosAutoConfig[126]: Kerberos configuration is up to date
May 15 18:39:20 server com.apple.ATSServer[125]: FODBCheck: New annex file created
May 15 18:39:21 server ARDAgent [130]: ******ARDAgent Launched******
May 15 18:39:21 server com.apple.KerberosAutoConfig[132]: Kerberos configuration is up to date
May 15 18:39:22 server ARDAgent [130]: call logout from LoginLogoutProxyCallBackFunction
May 15 18:39:22 server com.apple.launchd[1] (com.apple.RemoteDesktop.agent): Throttling respawn: Will start in 9 seconds
May 15 18:39:24 server loginwindow[58]: Login Window Started Security Agent
May 15 18:39:29 server servermgrd[53]: servermgr_calendar: created default calendar virtual host
May 15 18:39:31 server ARDAgent [146]: ******ARDAgent Launched******
May 15 18:39:32 server ARDAgent [146]: ******ARDAgent Ready******
May 15 18:39:33 server mdworker[109]: (Error) SyncInfo: Boot-cache avoidance timed out!
May 15 18:39:54 server Python[47]: CGImageSourceCreateWithData data parameter is nil
May 15 18:39:54 server com.apple.wikid[47]: Thu May 15 18:39:54 server.jeff.carpenter.name Python[47] <Error>: CGImageSourceCreateWithData data parameter is nil\n
May 15 18:39:56 server kernel[0]: AppleYukon2 - bad packet received. length: 1440, packet status bits: MII error
May 15 18:39:56 server kernel[0]: AppleYukon2: 00000000,00000001 sk98osx sky2 - - sk98osx_sky2::replaceOrCopyPacket tried N times
May 15 18:49:54 server kernel[0]: serialnumberd 194 FSWRITEDATA SBF /dev/dtracehelper 13 (seatbelt)
May 15 18:49:54 server kernel[0]: serialnumberd 194 FSREADDATA SBF /dev/autofs_nowait 13 (seatbelt)
May 15 18:49:54 server kernel[0]: serialnumberd 194 FSREADDATA SBF /usr/sbin 13 (seatbelt)
May 15 18:55:12 server kernel[0]: AppleYukon2 - bad packet received. length: 23, packet status bits: MII error
Any ideas?

Yes, it's been running Server since I purchased it.
I doubt the serial number is in use elsewhere: I purchased the 10-user version at a retail store in a sealed package and I've only installed it once.

Mini hangs at boot up screen

Similar Messages

Maybe you are looking for