Leopard Unable To Boot, Loops In Verbose Mode

Hi everyone,
I really hope someone can help me out here!
I recently backedup(Leopard), partitioned(my internal HDD) and restored Leopard
but now when booting it just stalls at the Apple screen with the loadnig circle at the bottom. I have done resores numerous times before and this is the first problem i have had.
No matter how long I leave it loading (+5 hours, to test) it never loads.
It doesnt start in safe mode, single user mode and when in Verbose mode it infinetly loops at this portion:
configd[36] <info>: hostname(multicast DNS) = MYMAC
mDNSResponder[280] <error>: ERROR: udsserver_init: bad file descriptor
mDNSResponder[280] <error>: ERROR: Daemon start: udsserver_init failed
configd[36] <info>: NetBIOS name (multicast DNS) = MYMAC
rpc.statd[280] <Error>: can't open statd.notify pidfile: no such file or directory (2)
rpc.statd[280] <Notice> statd.notify exiting 2
configd[36] <info>: NetBIOS name (multicast DNS) = MYMAC
InternetSharing[280] <Info>: InternetSharing starting
InternetSharing[280] <Info>: failed to add 192.168.2.1 to en0, device not configured
InternetSharing[280] <Info>:child process 533 exiting with sttaus 1
InternetSharing[280] <Notice>:DNS server 9named) exited, shutting down
InternetSharing[280] <Notice>: InternetSharing shutting down
mDNSResponder mDNSResponder-176.3 (Sep 30 2008 16:59:38)[588] <Error> starting
mDNSResponder[618] <Error>L launchdate_array_getindex(skt,0) returned null
configd[36] <info>: network configuration changed
mDNSResponder[684] <Error>:ERROR:blind(listenfd,(struct sockaddr *) &laddr, sizeof(laddr));
Faild no such file or directory
I have a small backup partition of Tiger and it workd fine, i can see the resored drive and all its contents(Applications etc.) and disk utility reports no problems when verify and repairing the disk.
I have also run Hardware diagnostics at startup and it reported no errors.
Any help you can offer would be greatly appreciated as I do not want to loose Leopard and all my files.
Thanks.

See if you can boot into the Leopard DVD. Insert DVD, reboot and hold down "C" key.
After language screen, in menu top left under Utilities, you will find disk utility.app (DU)
Run DU and first verify/repair HD and then repair permissions on the Leopard volume.
Reboot and see what happens or report back with any problems or errors you get.
Also, since one backup is SuperDuper! can you boot into that? Hold down Option key on boot and see if it shows up. If it does, does it boot normally?
Message was edited by: nerowolfe

Similar Messages

Snow Leopard booting in unwanted Verbose mode

Hi,
Just bought a 2nd hand Mac Mini on which I clean installed Snow Leopard. Whenever I boot the screen goes black and fills with white text with information about the boot process. Verbose Mode, I presume. After the GUI comes in the Mac Mini boots and functions as normal. My question is how do I turn this off. I have tried: "sudo nvram boot-args=" to no effect. Is there another way to stop Verbose mode?

Try resetting PRAM http://support.apple.com/kb/HT1379

How to permanently boot up in verbose mode?

Hi,
I want to always boot up OS X Mavericks (10.9.2) in verbose mode (debug mode) as I pressed Cmd+V everytime.
I remember an old command which I used on Snow Leopard for doing this:
« sudo nvram boot-args="-v" »
but I don't know if it's still valid on Mavericks!!
The command « nvram -p » works and doesn't show any "-v" verbalization in the "boot-args" section, so I'm currently thinking my command is still valid (it does still show other commands, though).
But I need your help, Apple experts! Can you confirm this?
Thanks in advance,
Tyrexionibus
Message was edited by: Tyrexionibus

Restart the computer. At the chime press and hold down the SHIFT key until you see the spinning gear below the Apple Logo. You should also see a progress bar appear. Booting into Safe Mode takes much longer than a normal startup.

Help! G4 PowerBook will only boot up in Verbose mode(?!)

Whenever I switch on my PowerBook, it won't get past the chime/black screen unless I press Option-V.
Without Option-V, the hard disk starts up and sounds normal, but after approx. 10-15 seconds of black screen I hear a high-pitched squeak as it appears to shut down the power. (Tried removing battery and plugging into mains power.)
I tried lots of different key combinations (e.g. boot from Tiger) but even the DVD drive appears to die and shut down.
However, when trying verbose mode to trace the problem through the logs, I have found that Option-V causes it to boot normally. I don't see any log information at all(!) - the PowerBook goes through the normal startup process to the Apple logo and then successfully onto the finder.
Has anybody got any idea what could be wrong?
(The PowerBook is 2-years old and there were no visible warning signs leading up to this problem.)

First:
Repairing the Hard Drive and Permissions
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. Then select Disk Utility from the Installer menu (Utilities menu for Tiger.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now shutdown the computer for a couple of minutes and then restart normally.
If DU reports errors it cannot fix, then you will need Disk Warrior (4.0 for Tiger) and/or TechTool Pro (4.5.2 for Tiger) to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
If the hard drive is OK per the above then reinstall OS X by doing an Archive and Install. Archive and Install will install a fresh copy of OS X without erasing the hard drive. Of course you must have sufficient free space on the hard drive to do this (8-10 GBs during installation.) Your old system will be archived in a Previous System Folder located at the root directory of hard drive.
Please carefully read the information on Archive and Install before proceeding.
Why reward points?(Quoted from Discussions Terms of Use.)
The reward system helps to increase community participation. When a community member gives you (or another member) a reward for providing helpful advice or a solution to their question, your accumulated points will increase your status level within the community.
Members may reward you with 5 points if they deem that your reply is helpful and 10 points if you post a solution to their issue. Likewise, when you mark a reply as Helpful or Solved in your own created topic, you will be awarding the respondent with the same point values.

KB2919355 has crippled my machine- boot loop to repair mode

Running Server 2012R2, installed KB2919355 manually using DISM as part of a series of manual updates recommended by following a rabbit hole beginning
here to address a problem I was having with gdi32.dll. Upon rebooting after installing this package (2919355), I entered a loop into Repair Mode. Further research found
this hotfix, which seems to be exactly my problem (my system boots from a SAS RAID array using an LSI1068E controller). I have tried diligently to follow the instructions, however I cannot get
far enough along in order to actually install the hotfix. Here's the main problem:
Using repair mode, I attempt to modify the BCD to limit memory to 4GB, but the change does not seem to persist after rebooting. I have tried the same procedure from the command line after booting from the installation DVD, but I seem to be restricted
to a greatly reduced set of executables (do I not have admin privileges when using the installation media?), so things like bcdedit just throw an "unrecognized command" error. I'm tempted to just pull RAM sticks to get below 4GB, but that's
a lot of tedious labor.
Noteworthy (I hope) facts:
1. chkdisk gives no errors.
2. sfc /scannow yields "There is a system repair pending which requires reboot...", so it aborts without giving me any info.
3. Bitlocker was not being used.
4. Attempting the "last known state" restore simply returns to repair mode after reboot.
I am really in trouble, so any help would be greatly appreciated.

Yes, I have explored this already. Unfortunately, I require a disk large enough to hold the image file (.wim) from my system drive before I can inject the repair package. I tried creating an image the other night, and it ran for several hours
before telling me my target drive was full. I am constrained by the following problems:
1. The only drives I have available that are large enough are externally connected to an HBA requiring special drivers to be loaded, which I can't do in WinRE/WinPE, which are the only modes I can use at this point.
2. The aforementioned drives are 4k native drives formatted in ReFS, which I understand is not supported by WinRE & WinPE (correct me if I'm wrong).
I am on the verge of performing a clean install at this point. If I were billing for my hours spent on this crap, I'd be in a new tax bracket this year.
The real question is: why is KB2919355 still available for install even with the issues that have been known for over a year? I only installed it because it was pointed to as a fix for a different problem. The cross-linking and updating of hotfixes
and patches is a minefield that reflects a very poor culture of quality. It's a good thing MS doesn't make pharmaceuticals or medical devices.

Z77A-GD65 (mostly) unable to boot usb in legacy mode

So I already made a post about this issue over in the BIOS forum back when I assumed it was something to do with the forum flash tool, but upon closer examination I was able to replicate this problem with other bootable usb sticks when I attempted to boot them in legacy mode instead of UEFI mode (and while this is viable for the Windows 8 image usb it isn't for the flash tool since when I try to boot that drive in UEFI mode it hands off to the Windows bootloader).
I am not sure where I'm going wrong here (or where to start) because this behavior doesn't seem entirely consistent and I haven't recognized any pattern in which it occurs. Basically whenever I try to boot a bootable usb device from the efi boot menu in legacy usb mode I'm presented with a black screen with a blinking white cursor in the top left corner. The inconsistency that I describe is that every so often the usb will actually boot, sometimes after only a few seconds of the blinking cursor, sometimes after leaving the screen up for an hour or so, and sometimes even if I leave the screen up overnight it still will not boot (this is what happens the majority of the time, regardless of the time interval).
I've used the "fix my stick" option in the forum tool. I've used the HP utility. Since it can be replicated across multiple usb drives I am fairly certain it isn't a geometry issue and has got something to do with my bios settings or my usb controller itself (although the only other problem I've had regarding usb is my wifi adapter only working properly on a specific port and I believe that to be unrelated).
Obviously something is amiss here. Any settings I should check out? I'm currently running no OC and I'm trying to recover my BIOS A after something went awry with the flash tool (long story as to why I was flashing in the first place, not really worth going through unless prompted...but this issue has been going on since at least early january).

I did have some issues with the ME fw at the beginning of January after a bad M-flash, but I thought I had recovered. After seeing someone with a similar problem (but with more symptoms of bad usb) had success with booting from usb after disabling the sata controller temporarily. So I've been doing that and it seems to work for now, even if it is kind of a roundabout way.

Unable to boot normal, in safe mode or from install DVD

When I walked into my office this morning and hit my keyboard to wake my Mac all I saw on the screen was a white mouse arrow and a black screen. I held down the power button to restart, it starts to boot and then stops at a gray screen telling me to hold down the power button and restart. Doing this brings me to the same screen. I have attempted the following:
Booting while holding the Shift key - this takes a bit longer but takes me to the same gray screen
Booting with the install DVD in and holding the "c" key - DVD spins a bit then gray screen
Booting while holding "option" and selecting the install DVD - DVD spins a bit then gray screen
Booting in Single User mode and ran "/sbin/fsck -fy" it returned - *** FILE SYSTEM WAS MODIFIED ***, ran it again and returned - ** The volume Macintosh HD appears to be OK
I am not sure where to go from here, and advice would be much appreciated.
Thanks,
Bob

I posted in the wrong forum, I am using 10.5, I have reposted this in that forum.

Imac boots up in verbose mode after been left overnight!

Hello
I have recently bought a used Imac 2010 model and have upgraded to Mountain Lion all was fine for a few days.
Know if I leave my computer overnight and reboot it comes on in text mode which I have to exit to get to the GUI.
Also when shutting down I ge text in the top left corner.
Any ideas please?
Many thanks John.

Restart it with the Option, Command, P, and R keys held down, and release them upon the second chime.
(68389)

How to start up MAC mini only in the verbose mode (command line) , no GUI

Can anyone let me know how I can set up the mac mini to ALWAYS boot into a verbose mode only, no GUI interfaces at all?
Mac Mini Mac OS X (10.4.6)
Mac Mini Mac OS X (10.4.6)

Hi, Andy your replies are really helpful. I did tried your method and also followed the link http://www.oreillynet.com/pub/h/348
Now my mac mini - Tiger seems hanging forever at the boot up screen. A Apple log showed up with a message "Starting Mac OS X ..." and now almost 5 minutes passed, nothing happened ...

HT1492 Nowhere does this article define what verbose mode is so I know if I want it or not.

Nowhere does this article define what verbose mode is so I know if I want it or not. I wanted to make this observation a comment about the article, but I don't see a way to do that. The article needs to be revised.

Thanks, WZZZ and baltwo. Your combined contributions clear it up: Verbose is what I call Terminal mode. (Maybe my term is better, because one needs a Verbose reboot after a Terminal crash ; ^ ) I now know I have had no need to use it on startup.
My point was as a writer: If I want to explain how someone can get into Verbose mode, I first explain what it is and its value. The article leaves me asking exactly what WZZZ says: Why would I want to use Verbose mode—preceded by: What is it? I'm hoping that Apple will see my topic and fix it, but I'm not holding my breath....
Even the osxdaily article only hints at the value of Verbose, but that was enough to provide the clarity the original article lacks. I have the Terminal alias on my dock, but I don't think I've used it more than once in four years. I'm no geek, and when those things happen I just march to the Genius Bar, where THEY boot up in Verbose mode. To me it's a testament to the stability of the evolved OS—or more to the fact that I haven't changed how I use my MBP in years or download strange new third-party apps.
Again, thanks for the help.

Verbose Mode Always On

I just got my 15 inch Powerbook G4 1.67 GHz (running OS X 10.4.6, Tiger) back from the factory. They had to repair the lower memory slot because it was failing to recognize the memory in the lower slot (hence the name, haha). My computer seems to continually be booting up in "Verbose Mode." (I found that out after much research on what I might call this issue.)
So... HOW DO I TURN VERBOSE MODE OFF ON MY POWERBOOK G4??? Please help me. I have searched, but I just could not find out how to turn it off. Thank you!

I figured out how to turn off Verbose Mode. Be careful when doing it! The link to the website is...
http://www.oreillynet.com/pub/h/348
Here's what I did to turn it OFF:
1. Opened program "Terminal" (Applications > Utilities > Terminal)
2. Copied and pasted in the command given in the website to turn Verbose Mode ON (yes, ON). Pressed Return key.
3. Typed the admin. access password (as defined by you, the administrator). Pressed Return key.
4. Copied and pasted in the command given in the website to turn Verbose Mode OFF. Pressed Return key.
5. Closed Terminal
6. Restarted my computer.
* Verbose Mode OFF!
Note: During the Restart process the Verbose Mode still showed up, but upon starting up, it was OFF, back to showing the little spinning gear under the Apple (gray/grey screen).
Hope this helps others!

Windows 2008 Server boot loop and unable to log on in Safe mode

The Situation: I used msconfig to reboot Windows 2008 Server r2 into safe mode. On rebooting, boot progresses ok and the log in screen appears very quickly, then disappears and the machine reboots. I've tried typing the password very quickly and whether
I get it wrong or just can't get enough typed in time, I don't know, but the reboot loop continues. So, i can't log on and can't change safe boot back to normal.
I know Server 2008 uses bcdedit and no longer has a boot.ini, so I don't know if it is still possible manually to amend a boot file so it starts in normal mode again. Can anyone help me to break out of this boot loop without having to resort to anything
major, such as reinstallation?
Just to make clear, I haven't updated the system and the only change made was with msconfig to require safe boot on restarting.
Thanks

from the safemode try this syntax
Syntax: bcdedit /deletevalue {default} safeboot
http://technet.microsoft.com/en-us/library/cc721886(WS.10).aspx
http://www.virmansec.com/blogs/skhairuddin
How on earth is that a good answer? Sorry for the necrosis here of bringing up a post 9 months later, but I just ran in to this issue again. The OP said that he was STUCK IN A BOOT LOOP having placed himself in SAFEMODE already.
How is he supposed to type this in if he can't log in?
What worked for me was to keep striking F8 like a cobra during boot and telling it to use the Last Known Good Configuration option, after the 4th autoreboot, it let me log in and let me switch it back out of the safe mode and back to the normal boot. Yes,
I am aware this is quite lucky and now I don't have to rebuild all my server set up, and that your mileage may vary here, but, keep trying, you might be lucky.

Unable to boot snow leopard on 32 bit mode

I'm using Macbook pro with Mac Os X 10.6.2. And it has no problem to boot under 64 bit mode, but fails under the 32 bit mode. Is there any suggestion? Thanks.

Since most 3rd party drivers are not ready for a 64bit kernel, it is possible that when booting the 64bit kernel, a 3rd party driver, that is not compatible with 32 bit Snow Leopard, is not being loaded.

Unable to boot normally - Always need to boot with Single User Mode

Hi Community,
Since last few days, I am unable to boot my Macbook Pro normally, running latest version of OS X Yosemite. When I boot, it goes to grey screen with Apple logo and progress bar, once the progress completes to 100% (after 5-10 minutes which is very longer than usual), it asks me to 'Select language' which seems like fresh installation of OS X. In that case, when I click next and it doesn't detect my SSD (blank list of select installation disk/drive).
After reading some threads, I found work-around and always need to boot into Single user mode (by pressing Command+S during power on) and then need to run following commands...
/sbin/fsck -fy
/sbin/mount -uw /
"device is write protected" numerous times
reboot
and then only it loads OS X and displays login screen. This happens all the times and I need to follow above steps always to get login screen.
How can I fix this?

Please help me out here. I tried booting it off a USB flash drive with ATV flash but that gave me some errors and prompted me to login with username [email protected] with password frontrow
But I am not sure how to get to login using a suitable input. I tried to telnet it using my PC over network but I dont think it has initialized anything (like wifi or network) at the prompt. Would it take USB keyboard input? All I can do is remove the power and restart it with the usb flash out and get into then get into the recovery loop. I am not sure replacing the hard-drive would help. Any help would be greatly appreciated.
Thanks
Sinu

TS2570 iMac won't boot, GSOD with Flashing Question Mark, safe/verbose mode not possible

I have an iMac 24", just over 2 years old running OS X v10.5 (Leopard). Mighty Mouse and bluetooth keyboard, no peripherals.
It slowed enormously over the last few weeks and has now ceased to boot.
On switching on I hear the chime (blank grey screen initially), the grey screen hangs for approx 30sec before the flashing folder/?mark icon appears.
There is no further progress.
Boot key combination results:
Can reset NVRAM (Option-Command-P-R)
Cannot boot to safe mode
Cannot boot to startup manager
Cannot boot to verbose mode
Cannot boot from target media (DVD etc)
Cannot boot to AHT mode
Cannot boot to single user mode
I have followed the steps here http://support.apple.com/kb/TS2570
Disconnect, test peripheral devices and network cables - done - de-powered and rebooted. No difference.
Perform a Safe Boot- this does not work. I am familiar with the boot combinations and timings. The safe boot leads to the same flashing folder/?mark icon. I have also tried verbose, single user, AHT and startup manager with the same result.
Reset the NVRAM / PRAM - done - this worked and kicks the system into an auto-reboot after 3-5 seconds. This also demonstrates the Keyboard is fine. The subsequent boot fails at the same point via normal, safe or verbose boot instructions.
Start from your Mac OS X Install disc; use Disk Utility – I never received an OSX install disk. I have the original box with receipts etc, the only disk present is an unsealed version of iLife (yeah thanks Apple). Where would I get one?
Check your cables and power source – done - all fine.
Remove third-party RAM and internal hardware – not applicable.
Perform an Archive and Install installation of Mac OS X – how would I do this when I cannot boot the device?
Perform an Erase and Install installation of Mac OS X as a last resort – how would I do this when I cannot boot the device?
To me the problem looks like a HDD failure. I had windows (dual boot) professionally installed when I bought the iMac and since the Windows boot option is also not visible (startup manager itself does not work) I suspect the system can’t find bootable media because the HDD isn’t spinning.
An OS corruption would generally affect one or the other but presumably not both Operating Systems simultaneously.
It's hard to be certain, but I’m sure it used to make more noise.
I had a look into opening it up and troubleshooting the physical components but it’s hard to know where to start. There are no obvious ways in and I’m not a professional so decided to post a question here rather than hack it open.
I'd be grateful if you could suggest next steps here, or is it time to go dig a hole in the garden? I certainly expected more than 2yrs life from a £1200 unit.
Many Thanks,
Ryan

Thanks for the response,
I bought the iMac new, 17th Jan 2010, all receipts intact but no extended warrenty. I declined the Applecare Plan for two reasons.
(1) The sales rep seemed very confident in the product build. In fact the main justification of the price tag was the quality of the device. I'd also never had an apple device malfunction at that stage.
(2) The incumbent EU regulations are quite fair in so much as legislation dictates electrical goods should be manufactured to function for a 'reasonable' lifetime. I would be morally uncomfortable paying for rights I theoretically already have.
I triple checked on the OS X disks you mentioned but no joy. Unusual as it may be, the box has not been used and it's contents reflect the day of purchase.
I'm happy to order the OS X v10.5 DVD and attempt a boot to the disk utility, I don't mind risking a few bucks on a potential fix. I'll need to figure out where to order the disk, the call centre is closed ATM so watch this space.
What I'd really be interested in is; (a) is there a known diagnostic routine to determine the HDD functionality and (b) it is possible to replace/upgrade the HDD? This for me is where the iMac loses ground against a conventional PC in terms of motherboard/component access. It's far superior from an asthaetics perspective while things are running smoothly and the OS is great but the first sign of a hardware malfunction and there seems little or no scope to self-medicate the device.
The disk has around 40-60 GB free space.
I don't have a second Mac, nor any friends or family with a Mac to 'borrow' for the disk utility test you mentioned. I'll hunt around this afternoon/week but my instinct tells me finding a locally accessable Mac running 3 yr old OS X might not be possible. Again, watch this space, I'll post any further developments.
In the meantime any further assistance or answers to the above questions on determining HDD status would be much appreciated. No progress has yet been made on the original issue of failing to boot.
Many Thanks
Ryan

Leopard Unable To Boot, Loops In Verbose Mode

Similar Messages

Maybe you are looking for