Sup720 booting into rommon mode

new sup720 drops into rommon mode. config reg is 2102 and boot system command points to right image located in sup-bootflash:

You might need to upgrade your ROMMON. We did with our brand new Sup720's. Below is the procedure we use. Please pardon the formatting. If you see "invalid ..." after the "show rom slot n sp" you need to load ROMMON code (available from Cisco's downloads). Good luck.
ROM Upgrade (650x)
1 sh rom slot 5 sp Display current ROM settings
2 copy tftp:c6ksup3-rm2.srec.8.4.2 sup-bootflash:c6ksup3-rm2.srec.8.4.2 TFTP the file to the 650x
3 upgrade rom slot 5 sp pref region[1 | 2] Command to switch regions to boot ROMMON from. Upgrade that too or leave at old version.
4 upgr rom slot 5 sp file sup-bootflash:c6ksup3-rm2.srec.8.4.2 Upgrades current preferred ROMMON region
5 repeat step 3 for other region After successfully upgrading to the new version do the other one too.
6 reload Reload (once for each ROMMON region) to test
rommon invalidate F1 Command to invalidate a ROMMON region

Similar Messages

Cisco 6500 with sup720 booting to rommon

Please how can I solve this problem. This cisco 6500 boots to rommon mode, I can't see any error showing why its booting to rommon.

Here is the boot process:
System Bootstrap, Version 8.5(4)
Copyright (c) 1994-2009 by cisco Systems, Inc.
Testing lower main memory - data equals address
Testing lower main memory - checkerboard
Testing lower main memory - inverse checkerboard
Clearing lower memory for cache initialization
Clearing bss
Clearing autoboot state machine
melody_present_reg: 1st read w/ 0x5555
melody_present_reg: 2nd read w/ 0xaaaa, reversed: 0x5555
Bootdisk adapter is detected, enabling bootdisk access...
Reprogramming CS1 w/ Melody value...
Reading monitor variables from NVRAM
Reset reason for CPU board 0xffff , BaseBoard 0x281ffff, display 0x20000System Reset by Software.
Enabling interrupts
Initializing TLB
Initializing cache
Initializing required TLB entries
MOBILE dimm - rev 0.15
Initializing main memory
Sizing NVRAM
Initializing PCMCIA controller
Initializing USB2.0 controller
Exiting init
Cat6k-Sup720/SP processor with 1048576 Kbytes of main memory
Autoboot: failed, BOOT string is empty
Autoboot executing command: "boot "
Initializing ATA monitor library...
string is bootdisk:s72033-ipbasek9-mz.122-33.SXJ2.bin
Loading image, please wait ...
Initializing ATA monitor library...
Stack pointer       : 0x8FFFFF80
monstack            : 0x800FFFC0
monra               : 0xBFC26EC4
edata : 0x80108580
magic : 0xFEEDFACE
memsize             : 0x10000000
uncomp_size         : 0x05090C00
comp_size           : 0x05090C00
comp_checksum       : 0x98ECBE18
uncomp_checksum     : 0x98ECBE18
CZIP_MEM_BASE       : 0x80000000
_end       : 0x8010BA00
Self extracting the image...
IOS compressed src copy is     : 0x80108594
czip + IOS tar size is :0x00E01FA8
czip + IOS Tar image is now :0x80108794
cptr is now :0x8010BB00
IOS compressed dest copy is     : 0x8010BB00
[OK]
image_entry :0x80100000
image_entry :0x80100000
__start : 0x80100000
tar_avail_size is now :0x0428EA00
Tar image address is             : 0x80F0DB00
tar_size is           : 0x0428E600
cpu type                   : 0x00000019
uncomp_size                : 0x05090C00
monstack                   : 0x800FFFC0
image_info.entry_point   = 0x80100000
image_info.section_count = 0x00000005
image_info.monstack      = 0x800FFFC0
image_info.monra         = 0xBFC26EC4
image_info.param0        = 0x00000002
image_info.param1        = 0x00000000
image_info.param2        = 0x800066A8
image_info.param3        = 0x80100000
image_info.reg_k0        = 0x80F0DB00
image_info.reg_k1        = 0x0428E600
Section Index = 0x00000000
    source    = 0x8010BC1C
    dest      = 0x80100000
    bytes     = 0x00010000
Section Index = 0x00000001
    source    = 0x8011BC1C
    dest      = 0x80110000
    bytes     = 0x00000720
Section Index = 0x00000002
    source    = 0x8011C33C
    dest      = 0x80110720
    bytes     = 0x00000020
Section Index = 0x00000003
    source    = 0x8011C35C
    dest      = 0x80110740
    bytes     = 0x00DF1730
Section Index = 0x00000004
    source    = 0x80F0DA8C
    dest      = 0x80F01E70
    bytes     = 0x00000000
reg_v0: 0x00000000
reg_k0: 0x80F0DB00
reg_k1: 0x0428E600
tar_start: 0x00000000
tar_size: 0x00000000
Tar image address is             : 0x80F0DB00
tar size is :0x00B6130E
Tar magic : ustar Tar filename : C2LC memsize             : 0x10000000
Tar gid         : 035231Tar uncomp_size         : 0x00B6130E
Tar mtime         : 11672344432 Tar username          : ccaiTar comp_checksum       : 0x0000125F
Tar group name    : buildTar prefix    : tar_size in czip         : 0x0428E600
Stack pointer       : 0x8FFFFF80
monstack            : 0x800FFFC0
monra               : 0xBFC26EC4
edata : 0x80110740
magic : 0xFEEDFACE
memsize             : 0x10000000
uncomp_size         : 0x02B3E7F0
comp_size           : 0x00DF171C
comp_checksum       : 0xE917F280
uncomp_checksum     : 0xD094D890
Compressed IOS src copy is     : 0x80110754
tar_dest is :0x8BD69200
tar_size is :0x0428E600
Compressed IOS dest copy is     : 0x8AF77AE4
Tar src before IOS decompression is     : 0x80F0DB00
Tar dest before IOS decompression is     : 0x8BD69200
compressed IOS src is     : 0x8AF77AE4
IOS uncompressed dest copy is     : 0x8013C160
Self decompressing the image : ############################################################################################################################################################################################################################## [OK]
e_shoff :
0x02B3E660
e_flags : 0x10001001
e_phnum :
0x00000001
Source elf_hdr->e_shnum = 0x0000000A
Setting up to copy ELF section 0x00000001
to image_info section 0x00000000
sh_name = 0x0000000B
sh_type = 0x00000001
sh_flags = 0x00000007
sh_addr = 0x80100000
sh_offset = 0x00000060
sh_size = 0x02640000
sh_link = 0x00000000
sh_info = 0x00000000
sh_addralign = 0x00000020
sh_entsize = 0x00000000
Setting up to copy ELF section 0x00000002
to image_info section 0x00000001
sh_name = 0x00000011
sh_type = 0x00000001
sh_flags = 0x00000003
sh_addr = 0x82740000
sh_offset = 0x02640060
sh_size = 0x00373440
sh_link = 0x00000000
sh_info = 0x00000000
sh_addralign = 0x00000008
sh_entsize = 0x00000000
Setting up to copy ELF section 0x00000003
to image_info section 0x00000002
sh_name = 0x00000017
sh_type = 0x00000001
sh_flags = 0x00000003
sh_addr = 0x82AB3440
sh_offset = 0x029B34A0
sh_size = 0x0003EEE4
sh_link = 0x00000000
sh_info = 0x00000000
sh_addralign = 0x00000004
sh_entsize = 0x00000000
Setting up to copy ELF section 0x00000004
to image_info section 0x00000003
sh_name = 0x00000024
sh_type = 0x00000001
sh_flags = 0x10000003
sh_addr = 0x82AF2324
sh_offset = 0x029F2384
sh_size = 0x0000423C
sh_link = 0x00000000
sh_info = 0x00000000
sh_addralign = 0x00000010
sh_entsize = 0x00000000
sh_type = 0x00000008
sh_flags = 0x10000003
sh_addr = 0x82AF6560
sh_offset = 0x029F65C0
sh_size = 0x00000940
sh_type = 0x00000008
sh_flags = 0x00000003
sh_addr = 0x82AF6EA0
sh_offset = 0x029F65C0
sh_size = 0x021FE100
tar file start = 0x84D02F50
cpu type                   : 0x00000019
uncomp_size                : 0x02B3E7F0
monstack                   : 0x800FFFC0
image_info.entry_point   = 0x80100000
image_info.section_count = 0x00000005
image_info.monstack      = 0x800FFFC0
image_info.monra         = 0xBFC26EC4
image_info.param0        = 0x00000002
image_info.param1        = 0x00000000
image_info.param2        = 0x800066A8
image_info.param3        = 0x80100000
image_info.reg_k0        = 0x84D02F50
image_info.reg_k1        = 0x0428E600
Section Index = 0x00000000
    source    = 0x8013C1C0
    dest      = 0x80100000
    bytes     = 0x02640000
Section Index = 0x00000001
    source    = 0x8277C1C0
    dest      = 0x8274CFB0
    bytes     = 0x00373440
Section Index = 0x00000002
    source    = 0x82AEF600
    dest      = 0x82AC03F0
    bytes     = 0x0003EEE4
Section Index = 0x00000003
    source    = 0x82B2E4E4
    dest      = 0x82AFF2D4
    bytes     = 0x0000423C
Section Index = 0x00000004
    source    = 0x8BD69200
    dest      = 0x84D02F50
    bytes     = 0x0428E600
data_size in czip         : 0x00001000
bss end of IOS is         : 0x84D01F50
              Restricted Rights Legend
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
           cisco Systems, Inc.
           170 West Tasman Drive
           San Jose, California 95134-1706
Cisco IOS Software, s72033_sp Software (s72033_sp-IPBASEK9-M), Version 12.2(33)SXJ2, RELEASE SOFTWARE (fc4)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Compiled Thu 15-Dec-11 01:29 by prod_rel_team
Image text-base: 0x4010132C, data-base: 0x4274CFB0
Active crashed three times, disabling auto-boot and dropping to rommon
Firmware compiled 15-Nov-11 14:23 by integ Build [100]
*Jan 1 02:27:12.643: %PFREDUN-6-ACTIVE: Initializing as ACTIVE processor for this switch
*Jan 1 02:27:13.459: %PFREDUN-4-SUP_FORCE_TO_ROMMON: Supervisor forced to rommon with reason: Active crashed three times in a row
System Bootstrap, Version 8.5(4)
Copyright (c) 1994-2009 by cisco Systems, Inc.
Cat6k-Sup720/SP processor with 1048576 Kbytes of main memory
rommon 1 >

How do I boot into recovery mode with wireless keyboard

I am unable to boot into recovery mode using either cmd-R or holding down the alt key. How is it supposed to work?
Message was edited by: Niklas Brunberg (better title)

I understand your concerns - I'm glad both of my machines are dual bootable (just in case) and I have my Snow Leopard install disks..... However, this is what Apple has decided, so we need to find the best way to deal with it. Personally, I've tested the recovery mode several times and, at least on my machine, it was not reliable (i.e. it wouldn't work - I tried it again and it did, but it spent more than an hour downloading the entire 4 GB installer again and then another 30 minutes installing it), and on a third try, I found that it had vanished because I had cloned by drive. When you clone, only your system is cloned, not the extra partition.
So, I've decided to rely on a) my bootable clones and b) a copy of the installer (.dmg) in case my clones fail. I don't feel comfortable relying on something that requires an internet connection and a full download to work. But, that works for me; you may want to take a different approach.

Hard drive won't boot into safe mode

My mid 2010 Macbook Pro has suddenly decided to not boot up after installing BitDefender and running a scan.
I installed it on a whim when I saw minor malware that hijacked Safari, and decided to run a scan. While I was working on Photoshop, the scan must have finished because all of my windows disappeared and I was left with my desktop and the spinning gray loading at the bottom of my screen. I waited 20 minutes, realized it wasn't going anywhere and force shut down the Macbook by power button.
Now, I cannot successfully get it past the grey apple loading screen. Attempting to boot into safe mode still leaves it at the same screen. Tried to reset the PRAM, still can't get past the loading screen. I still have my OS disk, however it is Snow Leopard and my current is Mavericks and I'm unsure if it is a wise idea.
15 inch mid 2010 Macbook Pro running OS X Mavericks, how dead in the water am I and how much would this cost me to "fix"?

Use the original Snow Leopard installation disk and start the MBP as if you were going to reinstall the OSX. Early in the process you should see a menu bar on the top of the display. Click on UTILITIES and from the dropdown menu select Disk Utility. Run Disk Utility>First Aid, Verify and Repair. If it is not successful, the HDD will have to be replaced.
Ciao.

Can't boot into safe mode or prompt login window, need help.

Hello all,
This is cross-posted from the installations and set-up list.
Can anyone suggest a remedy for what's ailing this powerbook. its a g4 powerbook, i don't have much more info other than that. all indications are that it is running 10.2.6, although i was told that it had been updated to 10.2.8, its possible that it was updated only to 10.2.6. following the update, you get to the apple and spinning pinwheel screen and it will not proceed. literally, the pinwheel will spin for 24 hours+.
it looks like it gets to the point of the startup(login) items and hangs indefinitely. ie it will
if i start in verbose mode it will, give some clues:
truncated or malformed library: /System/Libray/Frameworks/Security.frameworks/Versions/A/Security
Some starup items failed to launch due to conflicts
/usr/libexec/crashreporterd: crashdump terminated by signal 5
init: getty repeating too quickly on port /dev/console, sleeping
/usr/libexec/crashreporterd: crashdump terminated by signal 5
last message repeated 10 times
/usr/libexec/crashreporterd: crashdump terminated by signal 5
init: getty repeating too quickly on port /dev/console, sleeping
/usr/libexec/crashreporterd: crashdump terminated by signal 5
last message repeated 5 times
this will continue to be repeated and i assume a new core.## file is sent to the /cores folder, until the hard drive is maxed out.
I can boot in single user mode and everything is fine but i cannot boot into safe mode.
fsck says the disk is fine, as does disk first aid, i have also corrected permissions, and followed many of the things that have been previously posted.
It looks like ther are conflicts with some startup items, what can i move from the starup folder and is best not to be touched?
what about the truncated library message?
also can i update to 10.2.8 from the single user mode, if i cannot get into safe mode?
any suggestions?
thanks in advance-
todd

I have solved this problem. I mounted the laptop in target mode and replaced this file:
/System/Library/Frameworks/Security.framework/Versions/A/Security
with the equivalent file from a machine running 10.2.8.
It booted all the way through then i upgraded to 10.2.8.

Won't boot into safe mode

My 2012 iMac 27" was randomly rebooting itself, while in Sleep. I assumed this was due to the cheap 32 GB memory I bought, but before I could change it back to the original memory, to test, the Mac booted into Safe Mode (I assume - a progress bar showing at the bottom of the boot screen, below the Apple logo), and did not get further than a half the way, and then shut down. I swapped the memory to the original 8GB. I tried booting again, no buttons held down, as then it wouldn't get further than a quarter of the way. Further attempts to boot do not work, even when holding down Option to choose the boot disk, pressing Shift for Safe Mode, or Option-S for Single User Mode. I assume it's trying to boot in Safe Mode, but failing?
I also tried using a good Mac with the bad Mac as the Target Disk boot mode - the good Mac does not see the bad Mac...
I have an external DVD drive, but that isn't an option as I can't go into boot drive select mode. What are my options, apart from sending the iMac back?

Booting into the Recovery HD should allow you to effect repairs - that's the point of it, so it's a bit concerning that it won't allow you to. The Recovery HD is a partition on the internal drive that should allow you to effect repairs to the Macintosh HD, albeit part of the same physical disk.
I'm no expert, but I'd be concerned that the hard disk is on the way out. Do you have backup of everything - Time Machine or a bootable clone, perhaps?
Maybe have another try with Command+r. If it fails I'm not sure what would be the best next step - it depends if you have a full and up-to-date backup of your disk so that you can restore.
One of the options of the Recovery HD is to allow you to re-install the OS, which won't delete your data.
The more extreme step would be Internet Recovery which would involve erasing everything and re-installing via the internet.
Worth reading this carefully before proceeding: http://support.apple.com/kb/HT4718
Disk Warrior from Alsoft (not cheap) is another possibility for recovering damaged disks, although it's not a guaranteed solution.

OS hangs at grey startup screen, won't boot into safe mode

I rebooted my G5 this morning and when it came back up, it hung on the grey screen with the Apple logo and the spinning 'gear' progress bar. I tried rebooting several times, but that didn't help. I tried booting from the install DVD (which it did) and ran disk utility (both verify & repair on the start up drive and on permissions. It claims to have found permission errors and fixed them.) I hunted for answers online and tried to boot into safe mode, which did not work.
Someone mentioned booting into verbose mode and I saw that the load sequence was choaking on the login.
What could the problem be and how can I fix it?

Hi Yosarian,
Minor permissions repairs are no concern: The good news is that your data is probably OK.
Three things can be happening: Some of the machines boot settings are corrupted, or the OS files or settings are damaged, or there's a hardware problem.
Resetting the machines power management chip, called a PMU or SMU, depending on your computer, and the PRAM will resolve machine boot settings problems. Run a google search for your model of Mac plus reset pmu OR smu for instructions. After that, reboot your computer and hold Option-Apple-P-R down as you power on. Hold all 4 keys until you hear the startup chime a second time.
You can test your hardware with the grey disk that came with it that ays AHT in little letters. Boot from the CD and run the extended test. Be patient: AHT can take a long time to boot and run.
If you reset your PMU and PRAM and pass a hardware diagnostic but still can't boot normally, in safe mode, or in single-user mode, the problem is system software. Reinstall from your latest installer, checking off Archive and Install and Preserve Users and Settings from the Options screen available at the screen where you choose which disk to install to.
Good luck,
John

Can I ssh to a Mac that's booted into Safe Mode?

I'm needing to ssh to a Mac that's been booted into Safe Mode (I'm already able to ssh to it in normal boot mode, and I know how to boot it into Safe Mode from the command line, i.e. sudo nvram boot-args="-x", then sudo reboot).
I can't just test this for myself, as it has to work first time, otherwise I'll be locked out of the remote Mac. If ssh would still work in Safe Mode, the plan is to then ssh to it and issue the command to set it back to normal boot mode (with sudo nvram boot-args="") and then reboot... job done.
Ideally, but not too important, I could VNC to it in Safe Mode instead, but ssh would do fine.
Does anyone know (for sure!) please?
In case anyone wondered, I'm wanting to do the Safe Boot because I'm told it can cure an issue with Adobe CS apps freaking out and locking up, crashing etc. I want to try this over the w/e, and have no physical access to the Mac. I've already set it to power on later (via pmset) - something I do routinely.
I thought an answer to this would be easy to find, but after Googling I've drawn a blank. Can't find it in any Apple docs either.
Thanks in advance!

If this was already covered somewhere else, I
apologize. I did some browsing for this topic but had
no luck finding anything...
Anyhoo, I'm trying to log in to my wife's B&W G3
(running Jaguar) from my G4 (running 10.4.2) using
secure shell but she doesn't have a password set up
on her computer. When I enter the ssh command in
Terminal, it asks for a password — I don't enter
anything and just hit the Return key. It returns with
a massage saying "Permission denied, please try
again." What can I do to log in w/o setting up her
machine with a password first?
If you want to use SSH securily I would suggest you disable password authenticaiton altogher. If you setup public key authentication it is more secure and better than using passwords anyway.
see how to setup ssh with public keys

Booting into 64bit mode with Mac Pro 2009

I am trying to boot into 64bit mode with a 2009 Mac Pro 2.93 Quad core machine. I tried holding down 6 and 4 when restarting but no luck, it staill says no in the profiler. Any ideas why?

If you'd like your Mac to always start up in 64 bit mode without having to hold down any keys, do this:
Here's the configuration file approach for always booting into 64-bit. This is the best way to make your Mac always start up 64 bit as the only thing necessary is to alter one line of a configuration file. You can do that by opening the Terminal and entering:
sudo defaults write /Library/Preferences/SystemConfiguration/com.apple.Boot 'Kernel Flags' 'arch=x86_64'
To return to 32 bit mode, you would repeat the command but enter an empty string, which would just be the single quotes (where arch=x86_64 is) with nothing in between.
sudo defaults write /Library/Preferences/SystemConfiguration/com.apple.Boot 'Kernel Flags' ''
These commands are all one line, they're just wrapping here.
If at any point you find you need to start up in 32 bit mode for a single use, just as you held down the 6 and 4 keys for 64 bit, you can hold down the 3 and 2 keys for a temporary change. No need to keep changing the config file over and over.

Why doesn't Photoshop CS6 boot into Extended Mode? My GPU is Supported!

Ok got a new laptop, quad core and went to install the trial of Photoshop CS6 Extended and it will not boot into extended mode but rather the original Photoshop mode, and I know this by the splash screen with the circles and the fact there is no 3D menu. A friend did the same on his laptop (different hardware) and his booted into Photoshop CS6 Extended. We used the same Adobe Download Assistant to do our installs. My GPU is the ATI Radeon 6520G and it has support for both Open GL & Open CL. It appears in the Performance preferences with GPU checked and Open CL is selectable in advanced. Now my question is why can't I get into Extended Mode? Why can't we just force it to do so? I have seen this issue all over the place and it seems to be related mostly to ATI/AMD chipsets. Any help is appreciated, I would like to try out the 3D options.
I even tried installing the latest ATI Radeon drivers which are beta 2.7, same issue.
Thanks,
Michael

Did you download the trial version of the software directly from Adobe.com?
What Chris is trying to say is that there's no known reason why the legitimate trial version from Adobe shouldn't enable the 3D features on a system that supports GPU operations, as you've said yours does:
My GPU is the ATI Radeon 6520G and it has support for both Open GL & Open CL. It appears in the Performance preferences with GPU checked and Open CL is selectable in advanced
-Noel

Combuter boots into script mode! How do I perform regular start up?

I was on my computer (ibook G4) when the screen went black. It was still lit, but completely black. After closing it and opening it a few times, nothing changed, so I turned it off.
When I booted it back up again, it booted into the manual, black screen, white text script
mode, and I can't get out of it. All it says is :/ root #
After others did internet research for me and called Apple tech support (who weren't very helpful), these are the things I've tried that haven't worked:
typing /bin/fsck -fy after the :/ root#
(it ended up saying the HD volume was okay, and then i typed reboot, and it rebooted into
script mode still)
I also held down the following just after hitting the power button
to turn the computer on:
x
command
command + s
command + v
command + option + p + r (this is the only one that made the start up sound happen twice, but it still booted into script mode)
Every attempt either brought be to the :/root# screen again, or gave me more white text without ever helping me boot to my normal desktop. I've tried typing exit and reboot after the attempts, but to no avail.
I am from the US, but in Italy for the time being, and this is my only form of communication so I am panicking a little bit right now. This also means I DO NOT have my start up disk with me. Any help would be seriously appreciated.
-marissa

Put the disk in the computer and restart while holding the C key down. You pretend you want to reinstall the OS and go through the first two steps, until the screen just after the language selectiion screen.
On this screen you will see a menu bar. Click Utilities in the menu bar, and select Disk Utility. When DU is up and running, do this:
In the list at the left, select your start up disk- the item you want to repair. (Be sure to select an item that’s indented to the right in the list, not an item at the far left.)
Click First Aid.
If Disk Utility tells you the disk is about to fail, back it up and replace it. You can’t repair it.
Click Repair Disk.
When the repair is completed, quit DU and restart the computer.

HT201262 Will not boot into safe mode

Hello,
My MacBook pro 2012 crashed last night. Could not force quite so closed it down. On restart it would get halfway then stop. I have japped p-ram (I know it is my called this anymore) but then loads halfway and the turns off. I booted into disk repair and it found a couple of problems so repaired successfully. On restart it still gets halfway then turns off.
From reading the apple support it seems other people have the same problem. All mention booting into safe mode. For the life of me I cannot get my machine to boot into safe mode!
I do exactly like the instructions say but it always just goes to the page where I choose whether to log in as me or a guest.
What am I doing wrong?!
I am on a MacBook pro running Yosemite.
Many thanks for any help.
Chris.

Startup Issues - Resolve
Startup Issues - Resolve (2)
Startup Issues - Resolve (3)

No reboot after booting into safe mode

For a few years I've just ignored the problem but thought I should take time to mention it now.
When I boot into Safe Mode (holding down the shift key during boot up) I can always click on restart when the password screen comes up and the computers will restart.
But if I log in after safe boot and let the system boot up past the login screen THEN try a restart I get hours of beach ball. I've left various computers running over night and it is always the same in the morning, no restart, no beach but lots of beach ball.
So I do a force shutdown (hold the on/off button for 10 seconds) or a forced restart.
This has been the case from Leopard OSX10.5 and up including Snow Leopard. And on five different Intel Core 2 Duo Macs including 2GHz & 2.4 GHz iMacs and Macbooks.
The common theme is that I have migrated my setup through all these Macs so maybe there is some legacy thing in my software.
Suggestions?

Well… some improvement.
Here’s what I did: (note that I did a restart and sometimes safe boot after each and every step.
1 – use FontNuke (free shareware) to blast away font cache files. It found 8 some dating from 2002.
2 – use Apple’s Font Book to reconcile duplicate fonts.
Those two steps fixed my slow down problems with playing movie files in Quicktime and VLC.
But not Skype video. The biggest CPU load with Skype is with the transmitted picture oddly enough.
Then for good measure I zapped the PRAM and PMU. No noticeable improvement from doing those. Obliviously repair permissions and verify disk was done long long ago and redone.
I still have the problem of not being able to reboot from safe mode.
The Startup folders are clean except for Qmaster which I do not believe is the cause of not being able to reboot out of safe mode.
Does anyone know of other files/locations that put 3rd party startup items? I remember finding things from Western Digital and Symantic a few years ago in unexpected places. Symantic was especially hard to track down and eliminate.

I cannot boot into safe mode

I cannot boot into safe mode
I ran onxy, all appeared ok,
I booted from installer DVD,- repaired the drive, - nothing wrong with the drive,
and repaired disk permissions, twice, as a few permissions were incorrect
The only app which automatically logs in user account is KeyCue, and has done so always, and I don't know what what it belongs to. Nothing logs in automatically in the admin account.
I intermittently have a problem with DVDs not mounting, and a safe boot fixes the problem.

further to being unable to boot in safe mode-
normally when i boot in safe mode, when its starts up and reaches the login screen, above this are the words in red safe boot. As the words were missing from the login screen I had assumed that I was not in safe boot. I currently have about 94 GB of HD space. Other than this booting process appears to be normal. What prompted the safe boot was a DVD which mounted ok on insert, had unmounted when I went to eject, a restart and holding down the shift key ejected the disk, and I then tried to do the safe boot. Since I ran disk utility from the installer disk the same DVD has mounted and ejected just fine. The vanishing disk problem started 4-5 months ago, and has always been fixed by a safe boot

Unable to boot into safe mode with FileVault 2 enabled

I was trying to boot into safe mode earlier to try and fix a few things. It looks like I can't and I suspect it is because of FV2.
When the system starts I press shift after the tone, but then I have to release shift and enter the password and then Lion will only boot into normal mode.
I've also tried with sudo nvram boot-args="-x" from the terminal, but while it seesm that this way Lion starts to boot into safe mode, after a while it just restarts as if something crashed etc and then again, I have to enter the password for FV and all again as in a loop, i.e. Lion won't even start this way.
So I went into the recovery mode and I could make Lion start again at least in normale mode with sudo nvram boot-args="".
Any idea of what could be preventing Lion from entering safe mode?
Thanks in advance

The symptom may be unrelated to FileVault 2. I encountered the symptom with FileVault 2 disabled and with backward conversion (decryption) complete.
Apple reference for my bug report: 152162960. If the symptoms on your Mac compare to those on mine: progress may seem to cease during safe fsck.
Vito, as you are comfortable with the nvram command, please try the following:
sudo nvram boot-args="-v -x"
Restart the computer and note the last verbose lines that appear before you sense that progress has ceased. Then please add a note of those lines to this topic.
Additional questions
What model is your Mac?
What type of disk for the startup volume?
How many files on that volume?
Approximately how large are the attributes file and catalog file? (You might gain this information with a demo version of iDefrag.)
My current envronment
MacBookPro5,2
8 GB memory
startup from internal 320 GB rotational disk, Serial-ATA, Hitachi HTS723232L9SA62 (probably Travelstar 7K320)
3,961,791 files
495,744 folders /* not including the root folder */
catalog file 3.0 GB, not fragmented
attributes file 2.2 GB, not fragmented.
At http://www.wuala.com/grahamperrin/public/2012/01/09/a/?mode=gallery file speedy.txt includes details of the volume.

Sup720 booting into rommon mode

Similar Messages

Maybe you are looking for