P205-s6237 Hangs during boot to recovery after replace HDD

I replaced a bad HDD and the machine hangs during boot to the recovery disk. it gets past the inspecting screen and then hangs when the VISTA dots appear. the dots continue to scroll left to right but nothing ever happens. Any ideads on getting it past this point?

Similar Messages

K8N Neo 2 Platinum -- Hanging during boot --RESOLVED--

Heres the problem...
My system will hang during boot at anytime, from bios initalization to full windows boot (No BSOD ever and where the pc hangs in the boot proccess is totally random). And the only way to get past the hang is do a soft reset. I have to restart my system up to 3 times before I get a good boot, but once the pc is up and running, it stay running till I shut it down. (no hangs)
Now if I shut it down after the system has been running for a while, the pc will restart normally without any hangs. The hangs only occur after the pc has been down for a time.
I have reseated all the connectors, the memory (even tried different slots), add-in cards, cpu.
I have a clean install of Windows XP Pro (hard drives have been repartitioned and reformatted as NTFS)
All fans are spinning up fine, all temps are within norm, power supply voltages are within norm.
No phsysical signs of bad caps on the system board.
I ran ran Memtest86 for 18 hours striaght with no errors.
Ran CPU stress test with no problems.
No IRQ,DMA,etc conflicts found.
Windows records no errors during a freeze and I have checked for unwanted services/proccess as well.
I have tried min install to no avail.
Bois is retaining its settings (so bios battery is good)
I do not over clock anything. Bios is set to discover all important setting automaticly. (Bios setting are the same now as they were 6 months ago)
I am down to a possible cold solder joint on the system board?
This problem started to occur about a month ago.
If someone has seen this exact problem and has a resolution, well I would appreciate it if you passed along your knowladge
I am down to my last option of RMAing my system board. No. I have not replaced any components due to the fact I don't have extras lieing around nor can I spend the money just to troubleshoot :(
Specs..
Athlon 64 3500+
2 gig (pqi TURBO 1GB 184-Pin DDR SDRAM DDR 400 (PC 3200) Unbuffered System Memory Model PQI3200-1024SB) Ran in Dual config
Geforce 6800 (BFG 6800 GT oc)
Creative X-Fi XtremeMusic
Antec NeoPower 480
2 WD 36gig SATA Raptors in raid 0 (system partition)
2 WD 120gig IDE in raid 0 (data partition)
Windows XP Pro
all drivers and bios are manufacture ref and up-to-date.
Ok I won't go into all the details of why I missed this but it turns out the northbridge heatsink fan had stopped spinning and thus the hangs during boot due to overheating (hhmmm, when I step back and look at this the symptoms point right to overheating).
This also expains why after several attempts at booting up, once the pc was up it would run like a champ. The chip would of course overheat and cause random freezes. Now due to the placement of the chip and the design of the heatsink once there was enough airflow over the heatsink the chip would remain cool enough to prevent further freezing of the system.
What helped to facilitate this is that I have a ducted fan system installed in the bottom of my case which directs a substantal amount of fresh air to the pci slots, the chip set and the AGI slot as well.
So what have we learned class?
1. check the obvious
2. do a complete physical inspection of your system
3. KISS -- keep it simple stupid

Is this your ram:
Quote
Part Number: PQI3200-1024SB
Quality Control: Comprehensively and rigorously tested
Package: 1024MB single pack
Organization: 128M x 64-bit
CAS Latency: 3-4-4-8
Test Voltage: 2.6 V
PCB Board: 8 Layers PCB
Heat Spreader: Mirrored Black Copper
Speed: DDR 400 MHz (PC3200)
Type: 184-pin DDR SDRAM
Error Checking: Non-ECC
Registered/Unbuffered: Unbuffered
Warranty: Lifetime
This is a quote from MSI web site:
Quote
Main Memory
• Supports dual channel DDR 266/333/400, using four 184-pin DDR DIMMs.
• Supports the memory size up to 4GB
• Supports 2.5v DDR SDRAM DIMM
Due to the High Performance Memory design, motherboards or system configurations may or may not operate smoothly at the JEDEC (Joint Electron Device Engineering Council) standard settings (BIOS Default on the motherboard) such as DDR voltage, memory speeds and memory timing. Please confirm and adjust your memory setting in the BIOS accordingly for better system stability.
Example: Kingston HyperX DDR500 PC4000 operates at 2.65V, 3-4-4-8, CL=3.
For more information about specification of high performance memory modules, please check with your Memory Manufactures for more details.
Manually adjust your ram voltage to 2.65 volts and then manually adjust your ram timings to 3-4-4-8-2T.
If that does not work then do as Richard suggested and strip down to a bar-bone system, this is CPU+fan, 1 stick of ram (try other stick and different slots as one may be bad), graphic card and PS-2 keyboard, if it boots fine without any problems then add one device at a time until you find the problem.
Post back results as there are more things one can try but lets start with the simple stuff and work up.

Ultra 5 Hangs During Boot

My Ultra 5 hangs during boot at the following point....
setting default ipv4 interface......
I have tried resetting my router, unplugging the network cable, and nothing seems to work.
John

jmorrissey3, is this a system that just suddenly stopped working, or is this a "new" system (it's not like Ultra 5s are really new) that you're trying to bring up?
If this is a new system for you to tinker with, you should just go ahead and reinstall the operating system. This will blow everything away, of course, but it's good experience if you've never done it before and it will guarantee that the system is clean.
If the data on there must be retained, you can boot from CD-ROM, mount the / partition, and look at some of the configuration files to try to isolate the problem. I would agree that it either is set up for DHCP and there is no DHCP server or there is an invalid NFS mount that is trying to take place.

Hangs during boot after upgrading to Kernel 2.6.39

I have just installed Arch on a new computer. It works fine until I upgrade to Kernel 2.6.39. After that it hangs on boot.
The end of /var/log/everything.log is posted below.
Jul 26 23:52:06 localhost kernel: [ 6.036766] [drm] nouveau 0000:04:00.0: Parsing VBIOS init table at offset 0x85F3
Jul 26 23:52:06 localhost kernel: [ 6.129046] adt7475 1-002e: ADT7473 device, revision 1
Jul 26 23:52:06 localhost kernel: [ 6.138997] [drm] nouveau 0000:04:00.0: Detected monitoring device: adt7473
Jul 26 23:52:06 localhost kernel: [ 6.139000] [drm] nouveau 0000:04:00.0: 1 available performance level(s)
Jul 26 23:52:06 localhost kernel: [ 6.139002] [drm] nouveau 0000:04:00.0: 0: memory 405MHz core 270MHz shader 540MHz
Jul 26 23:52:06 localhost kernel: [ 6.139233] [TTM] Zone kernel: Available graphics memory: 12371030 kiB.
Jul 26 23:52:06 localhost kernel: [ 6.139236] [TTM] Zone dma32: Available graphics memory: 2097152 kiB.
Jul 26 23:52:06 localhost kernel: [ 6.139238] [TTM] Initializing pool allocator.
Jul 26 23:52:06 localhost kernel: [ 6.139252] [drm] nouveau 0000:04:00.0: Detected 5376MiB VRAM
Jul 26 23:52:06 localhost kernel: [ 6.139260] mtrr: type mismatch for d0000000,8000000 old: write-back new: write-combining
Jul 26 23:52:06 localhost kernel: [ 6.150626] [drm] nouveau 0000:04:00.0: 512 MiB GART (aperture)
Jul 26 23:52:06 localhost kernel: [ 6.152371] [drm] nouveau 0000:04:00.0: failed to load fuc409d
Jul 26 23:52:06 localhost kernel: [ 6.176193] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
Jul 26 23:52:06 localhost kernel: [ 6.176195] [drm] No driver support for vblank timestamp query.
Jul 26 23:52:06 localhost kernel: [ 6.228800] No connectors reported connected with modes
Jul 26 23:52:06 localhost kernel: [ 6.228802] [drm] Cannot find any crtc or sizes - going 1024x768
Jul 26 23:52:06 localhost kernel: [ 6.231002] [drm] nouveau 0000:04:00.0: allocated 1024x768 fb: 0x8020000, bo ffff880608d97800
Jul 26 23:52:06 localhost kernel: [ 6.233786] Console: switching to colour frame buffer device 128x48
Jul 26 23:52:06 localhost kernel: [ 6.235094] fb0: nouveaufb frame buffer device
Jul 26 23:52:06 localhost kernel: [ 6.235094] drm: registered panic notifier
Jul 26 23:52:06 localhost kernel: [ 6.235098] [drm] Initialized nouveau 0.0.16 20090420 for 0000:04:00.0 on minor 0
Jul 26 23:52:06 localhost kernel: [ 6.255449] HDA Intel 0000:04:00.1: PCI INT B -> GSI 17 (level, low) -> IRQ 17
Jul 26 23:52:06 localhost kernel: [ 6.255451] hda_intel: Disable MSI for Nvidia chipset
Jul 26 23:52:06 localhost kernel: [ 6.255599] HDA Intel 0000:04:00.1: setting latency timer to 64
Jul 26 23:52:06 localhost kernel: [ 7.663482] EXT4-fs (sda3): re-mounted. Opts: (null)
Jul 26 23:52:06 localhost kernel: [ 7.807508] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)
Jul 26 23:52:06 localhost kernel: [ 7.851401] Adding 265068k swap on /dev/sda2. Priority:-1 extents:1 across:265068k
Jul 26 23:52:06 localhost kernel: [ 8.569682] r8169 0000:08:00.0: eth0: link down
Jul 26 23:52:06 localhost kernel: [ 8.569687] r8169 0000:08:00.0: eth0: link down
Jul 26 23:52:06 localhost dhcpcd[747]: eth0: waiting for carrier
Jul 26 23:52:08 localhost dhcpcd[747]: eth0: carrier acquired
Jul 26 23:52:08 localhost kernel: [ 10.301736] r8169 0000:08:00.0: eth0: link up
Jul 26 23:52:08 localhost dhcpcd[747]: eth0: broadcasting for a lease
Jul 26 23:52:12 localhost dhcpcd[747]: eth0: offered 131.181.53.42 from 131.181.127.32
Jul 26 23:52:13 localhost dhcpcd[747]: eth0: acknowledged 131.181.53.42 from 131.181.59.48
Jul 26 23:52:13 localhost dhcpcd[747]: eth0: checking for 131.181.53.42
Jul 26 23:52:18 localhost dhcpcd[747]: eth0: leased 131.181.53.42 for 43200 seconds
Jul 26 23:52:18 localhost dhcpcd[747]: forked to background, child pid 774
Jul 26 23:52:18 localhost crond[823]: /usr/sbin/crond 4.5 dillon's cron daemon, started with loglevel info
Jul 26 23:53:01 localhost crond[823]: FILE /etc/cron.d/prune-cronstamps USER root PID 835 job prune-cronstamps
Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 836 job sys-hourly
Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 837 job sys-daily
Jul 26 23:53:01 localhost crond[823]: FILE /var/spool/cron/root USER root PID 838 job sys-weekly
Any help fixing this would be greatly appreciated.

I have been trying to isolate the problem a little further. I re-installed (with just the base and sudo) and after upgrading pacman rebooted and it worked without fail. Then I installed libusb and libusb-compat which where required when I tried to upgrade just the kernel using
pacman -S kernel26
which initially failed because of the missing dependencies libusb and libusb-compat. I then re-booted and that worked without a problem.
I then upgraded to Kernel 2.6.39 using the above command and then it hung on rebooting. I saved the logs at each stage.
The additional logs in errors.log in the reboot that failed are as follows.
ul 26 16:28:39 O313 kernel: [ 5.120698] [drm] nouveau 0000:04:00.0: Pointer to BIT loadval table invalid
Jul 26 16:28:39 O313 kernel: [ 5.360508] [drm] nouveau 0000:04:00.0: failed to load fuc409d
Jul 26 16:28:39 O313 kernel: [ 5.808016] sd 20:0:0:0: [sdb] Assuming drive cache: write through
Jul 26 16:28:39 O313 kernel: [ 5.809960] sd 20:0:0:0: [sdb] Assuming drive cache: write through
Jul 26 16:28:39 O313 kernel: [ 5.812116] sd 20:0:0:0: [sdb] Assuming drive cache: write through
Jul 26 16:28:35 O313 udevd[369]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'
The end of kernel.log is as follows:
Sat Jul 9 14:57:41 CEST 2011
Jul 26 16:28:39 O313 kernel: [ 0.000000] Command line: root=/dev/disk/by-uuid/e4733c60-3e54-4001-a83e-415b690dfcb0 ro
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-provided physical RAM map:
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000000000000 - 000000000009f800 (usable)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000000100000 - 00000000cfed0000 (usable)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfed0000 - 00000000cfed1000 (ACPI NVS)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfed1000 - 00000000cfee0000 (ACPI data)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000cfee0000 - 00000000cff00000 (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000f0000000 - 00000000f4000000 (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 00000000fec00000 - 0000000100000000 (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] BIOS-e820: 0000000100000000 - 0000000630000000 (usable)
Jul 26 16:28:39 O313 kernel: [ 0.000000] NX (Execute Disable) protection: active
Jul 26 16:28:39 O313 kernel: [ 0.000000] DMI 2.4 present.
Jul 26 16:28:39 O313 kernel: [ 0.000000] DMI: Gigabyte Technology Co., Ltd. X58A-UD5/X58A-UD5, BIOS FD 02/01/2011
Jul 26 16:28:39 O313 kernel: [ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved)
Jul 26 16:28:39 O313 kernel: [ 0.000000] e820 remove range: 00000000000a0000 - 0000000000100000 (usable)
Jul 26 16:28:39 O313 kernel: [ 0.000000] No AGP bridge found
Jul 26 16:28:39 O313 kernel: [ 0.000000] last_pfn = 0x630000 max_arch_pfn = 0x400000000
And this is the end of daemon.log
Jul 26 16:27:49 O313 init: Switching to runlevel: 6
Jul 26 16:27:50 O313 dhcpcd: received SIGTERM, stopping
Jul 26 16:27:50 O313 dhcpcd: eth0: removing interface
Jul 26 16:28:39 O313 2.352592] udevd[87]: starting version 171
Jul 26 16:28:39 O313 4.531007] udevd[370]: starting version 171
Jul 26 16:28:39 O313 dhcpcd: version 5.2.2 starting
Jul 26 16:28:39 O313 dhcpcd: eth0: waiting for carrier
Jul 26 16:28:35 O313 udevd[369]: error: runtime directory '/run/udev' not writable, for now falling back to '/dev/.udev'
Jul 26 16:28:39 O313 init: Entering runlevel: 3
Please let me know if any further information would be useful in tracking down this problem. Also ignore any timings in my initial post they were incorrect.
Last edited by TheStatsMan (2011-07-26 07:40:48)

Mountain Lion hangs during boot sequence after reinstall

I am running Mountain Lion on a late-2012 Mac Mini (the newest one at this writing), and my system got messed up after I tried to reset my primary uid to 501 (I know, first mistake) after having migrated the system from an older Mac Mini. This worked partially, but I continued to have issues accessing some files and got tired of resetting the permissions manually.
I tried reinstalling Mountain Lion and since then, the system fails to boot completely. I can get as far as seeing the desktop, Finder menu, Dock, etc., but then one or more error windows pop up relating to specific resources (I think Calendar Agent was one of them, I can't remember because I then saw the spinning disk icon and the system stopped responding). I tried restarting by turning the computer off and then on again, but continue to get similar errors after it gets almost all the way through booting.
Although I have much of my data on the hard drive backed up to an external Seagate drive on my home network, I had not been able to do a complete backup because I have many old (pre-OS X) files that contain slashes or other characters no longer allowed in filenames, and it has proven too cumbersome to update all the filenames to make it worthwhile. Thus, I am not able to wipe the hard drive and start from scratch.
I know how to boot in Single-User mode, which does work, but don't know enough BSD/Darwin to pinpoint the source of this problem and fix it.
Any advice about how to diagnose and/or solve this problem? I would like to be able to correct any uid and gid conflicts that may be causing this, which I believe would work, but am not sure how to do this. I am writing this from Safari after booting in Recovery mode.
Thanks for any help with this. - Klingon725

Back up all data.
This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
Step 1
If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box marked Allow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.
Triple-click the following line to select it. Copy the selected text to the Clipboard (command-C):
{ sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -Rh $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V). You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
Step 2 (optional)
The first step should give you usable permissions in your home folder. This step will restore special attributes set by OS X on some user folders to protect them from unintended deletion or renaming. You can skip this step if you don't consider that protection to be necessary.
Boot into Recovery by holding down the key combination command-R at startup. Release the keys when you see a gray screen with a spinning dial.
When the OS X Utilities screen appears, select
Utilities ▹ Terminal
from the menu bar. A Terminal window will open.
In the Terminal window, type this:
resetpassword
That's one word, all lower case, with no spaces. Then press return. A Reset Password window will open. You’re not going to reset a password.
Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select
 ▹ Restart
from the menu bar.

Arch Live CD x64 hanging during boot at "triggering uevents"

Hello!
I recently was recommended Arch by a friend, and after I followed the 'Newbies Guide' and burning a live CD to install Arch with, it appears to hang during Live CD boot at "installing uevents."
I am trying to install Arch as a dual boot on a late 2008 MacBook Pro which is currently running x64 Windows 7. I have plenty of HD space (100gb free and 100gb unallocated to install Arch onto).
Here is a picture:
http://i.imgur.com/Y8P41nf.jpg
I get the same error weather I try to install x64 or i686 (I think that's what it's called). Is there any reason for this?
Thank you!
-- mod edit: read the Forum Etiquette and only post thumbnails http://wiki.archlinux.org/index.php/For … s_and_Code --
(Sorry, missed that. My bad!)
Last edited by RalphORama (2013-09-07 03:09:13)

frank604 wrote:
You can try nomodeset. Seems to be a failure in loading a driver for your hardware. To read more on similar issues, there's a few posts with more info and suggestions by googling it.
Google result: http://lmgtfy.com/?q=halt+at+triggering+uevent
Results:
https://bbs.archlinux.org/viewtopic.php?id=151259
https://bbs.archlinux.org/viewtopic.php?id=140426
Thanks! I tried googling it myself but got mostly answers that didn't work. I'll try this!

Multiple cPCI Graphics cards - System Hangs during Boot

We have 2 Kontron dual output CP332 cPCI graphics cards to install into a NI PXI rack in order to give us 4 graphics outputs.
When one card is installed it acts as the Primary graphics card and it is required to disable to NI on-board graphics card in order for this to boot and function correctley.
If a 2nd Kontron CP322 card is added the system will hang during WinXP boot, as it switches from VGA to SVGA mode.
Disabling the 2nd card via device manager allows the system to boot.
Re-enabling the 2nd card once booted, then configuring with the ATI driver application allows the 4 graphics output to work as expected.
If the system is re-powered it will once again hang during WinXp booting.
Is there anything that can be configured on the NI Embedded PC (BIOS) to prevent this ?
Is there anything in windows that can be set to prevent this ?
Can we control the windows device manager from labview in order to enable/disable the 2nd card after power-on and before shutdown.
many thanks

Hi Scott,
I have some more information for you regarding your issue. We have tested the Kontron CP332 with the PXI-8196.
However when we tested the setup, we had 3 monitors working, the on-board graphics and the dual output from the card.
Until we get the on-board graphics working with a single CP332 I don't think we will get bot CP332's working.
So these are the steps to get on-board graphics working with a single Kontron card the steps come from talking to our PXI Product Support Engineer:
"The first thing you need to make sure is that you are using the
driver for Windows XP, and not the one for Windows 2000. Here's a link
to the driver download page:
http://us.kontron.com/index.php?searchword=cp+332&id=363
Notice that the first two driver downloads look just the same, but if
you hover over them and look at the url, you'll notice that the first
one is for Windows 2000 (w2k), and the second one is for Windows XP
(wxp). So, just make sure you are using the second one. The PSE did
mention that she was initially using the Win 2k driver, and was having
some issues with it hanging and all. Here's the information she sent me
about how she was able to get things working:
"Here is the info. My controller has BIOS version 1.3 but have him try this first before updating the BIOS.
The Kontron Board is the CP 332. I was able to get all three monitors working with the PXI-8196.
Configuration steps:
1) Insert both the controller and the kontron board in the chassis.
Note: When the computer is starting it will give you the Windows boot
up screen on the DVI 1 on the Kontron board and then give you the login
screen on the monitor connected to the 8196 so make sure you still have
a monitor connected to the controller.
2) Cancel the NI installation wizard if it comes up.
3)
Unzip the drivers and run the setup.exe file. Make sure you install
both the ATI display driver and the ATI Control Panel. (Check the zip
name to make sure you have the xp version of the driver)
4) After
restart go to the Display Properties and under the Settings tab you
should have monitors 1 and 2 on Mobility Radeon 9000 (Kontron CP-332)."
If you don't have BIOS version 1.20 or higher, please upgrade to BIOS version 1.30, if you need to upgrade the BIOS please make sure you fully understand the readme file. Then follow the steps above to enable triple output on the graphics cards.
When you have this working please try adding the second Kontron card.
Regards
JamesC
NIUK and Ireland

Mac Mini keeps hanging during boot

My ~3 year old Mac Mini keeps freezing during booting with the error message "You need to restart your computer. Hold down the Power button...". This happens every time. Booting in safe mode works.
This happened with Mac OS X Tiger but keeps happening even after I have completely reformatted that hard disk and reinstalled Leopard from scratch. There are no external devices connected to the computer besides the monitor and a bluetooth mouse and keyboard.
After reading some discussion forums I have already tried starting into Open Bootware and running "reset-nvram" and "reset-all" but to no avail.

Welcome to Apple Discussions!
What you are suffering is a Kernel Panic, and given you have reformatted your drive and reinstalled MacOS, it would tend to suggest the issue is hardware related - most common culprit being RAM.
http://docs.info.apple.com/article.html?artnum=106227 explains what kernel panics are, and http://www.thexlab.com/faqs/kernelpanics.html and http://www.index-site.com/kernelpanic.html may give some assistance in working through the problem to determine the cause.
The one good thing is that your system appears sufficiently stable to allow you to boot to the Leopard installer and complete a full install. This makes it less likely there is a fundamental issue with the most expensive component of the system, the logic board.

OSX hangs during boot or install

Hello all,
I'm writing this because I'm not really sure where else to post this at to get an indepth answer. Currently I have a dual G4 450mhz AGP PowerMac that I bought used. When I purchased it, it had 768mb of ram and the only thing it didn't have was a working hard drive. After putting in a new hard drive the system worked great when i intially installed OS9 and later OSX for fun.
However I had to remove the 768mb of RAM because a client PC needed it and that took priority over my dual G4 at the time. Just the other week I purchased 2 x 256mb of RAM from Omni Technologies (omnitechnologies.biz) which guarantees working ram for specified Apple systems.
Upon receiving that ram and installing it, I powered on the G4 only to find it would "hang" when booting OSX (10.3.9). The symptoms are as follows: When powering on I hear the normal chime and the white screen with gray apple logo appears. Seconds later the spinning progress indicator shows up spinning in circles as OSX is booting. However after about 5 minutes with no DVD/hdd activitity, the system then hangs. The gray apple logo changes to a gray 'prohibited' logo. It's the logo of the circle with the slash through it. Like the kind you see over no-smoking signs.
I figured the hard drive was messed up and I decided to reinstall OSX cleanly. However when I booted from the CD by pressing 'c', the EXACT SAME symptoms above happened. It was at this point I started getting really worried. So I decided to remove the hard drive temporarily and boot from the CD just to make sure it really was booting from the CD. Unfortunately the exact same symptoms happened.
Out of desperation to make sure that my hardware was OK, I decided to install OS 9.2.1 which installed and WORKED perfectly. I also installed UbuntuPPC and Slackintosh versions of linux which also installed and worked perfectly.
The issue appears to reside with OSX. I've borrowed friends cd's of 10.2-10.3 and all of them will NOT install. They start to boot from the CD, but never even make it to the first window.
Help!!
Brad

Actually trying one stick in each individual slot was one of the first things I did. Unfortunately that did not provide a resolution for me.
Thanks for the links regarding the broken folder/prohibitory sign. I read those and they made mention of resetting the nvram and pram. I just did that a bit earlier today but logging into the open firmware by pressing Option-Command-F-O and typing: reset-nvram; set-defaults; reset-all.
Upon the reboot and after I plugged the hdd with OSX on it back into the system, the resolution was a bit off as I figured. But this time there was no progress indicator. Instead only the gray apple logo showed and there was no response from the hdd or cdrom drive.
I also noticed that the USB mouses red light went out within the first 45 seconds of booting. I swapped out keyboards and mice and the new ones did the same thing as well. I also tested the memory in an imac I have and OSX that is installed ont heimac works gerat with that stick of memory. I'm leaning towards the fact that the memory I have is fine, being that it was ordered from a company that specifically guaranteed it to work on macs of all kinds.
Any other thoughts or ideas?

Mac Mini w/ Sony V2500 Hangs During Boot After Upgrading to 10.4.10

I searched the the threads for something similar on this topic. but I could not find anything, so I am putting the question out to the forum.
I have an interesting situtation after I upgraded my Mini to 10.4.10 last night. It seems that when the Mini boots up while connected to my Sony KDL-40V2500 LCD, the Mini will hang in the boot squence. If I disconnect the DVI connection (I have a DVI to HDMI connection) at the hanging point in the boot, the Mini will continue to boot fine and then when I reconnect the DVI cable to the Mini, the display works fine with no issues.
Has anyone else experience this unique issue and are there any recommendations.
Thanks in advance for any help!
Brandon
Mac Mini & MacBook Pro Mac OS X (10.4.10) Mac Mini Intel C2D, DVI to HDMI connection, Sony KDL-40V2500 LCD
Mac Mini & MacBook Pro Mac OS X (10.4.10)

Hi SwimRef and hplus-
Thank you both for your suggestions. I did try to boot with the Airport turned off and I was able to boot without any issue. However, when I turned the Airport back on, the ballon was spinning for a good period of time and then I gave up and turned off the machine.
However, the Mini still boots without a problem when the DVI cable is not attached, so for the mean time, I'm gonna stick with the process of booting without the cable until I have time to reinstall a fresh OS (no archive and reinstall).
I will put this tidbit out there that seems odd. When I was trying to figure out the issues yesterday, I did hook the Mini up to my 20" Cinema Display and all loaded well without any issues. In addition to the no issue load, I noticed that my screen background was not the same, but all of my other settings were just the same as if I have booting using the Sony TV. Any thoughts on if the two are connnect?
Thanks again everyone for your support!
Brandon
Mac Mini & MacBook Pro Mac OS X (10.4.10)

648 Max Hangs during boot after upgrading memory

:confused2:Can someone please help me.
I recently decided to upgrade my memory to 1 gig by adding a further 512mb ddr ram to my system. I already have 512mb pc2700 ram and found that pc3200 ram is cheaper so bought that to add, shouldn't be a problem as the manual says it should work with "333 and up". I used all the tried and tested safety methods for fitting ram so I know there has been no ESD (I have built several machines in the past so it is not a stupid error on my part (I hope))
I fitted the ram in the usual manner and turned on the system to find it would beep once (sounds like normal POST to me it always beeps once, however Ami bios beep codes say it could be dram refresh failure? but 1 beep is also POST ok?) and then hangs. No display no nothing. Fans are all running so power is there but no boot.
I looked on the D-Bracket and it has two red lights down the left side 2 green down the right which indicates it is testing memory. That is as far as it gets.
I had to use rather a lot of force in my attempt to fit the memory and feel I may have either cracked the motherboard, or pushed it so hard that it touched the casing underneath and shorted out (Oh dear, ESD). I have tried stripping out every component except ram,display and hard drive but still nothing. I have also tried putting just the old ram back in as it was before, no joy there either.
Could this be the motherboard is dead or the memory or both?
Any help greatly appreciated
DUCKULA

I finally decided to rip out my Mobo and have a good look around. I fiddled with it a while and then put it back and tried to boot up again. I discovered that if I push out the mobo in the opposite direction to the one I used to try and push the memory in, it will boot. Therefore it has to be a crack in one of the tracks in the mobo itself, although I can't see anything, it could just be a hairline crack, but that would be enough.
The lesson learned is, put your memory in before fitting the Mobo into your case, or at least try and support the underside better, whilst you push
I'm off to the shop for a new one (and a power supply).
Thanks guys for the helpful tips, at least I know what to look for next time

Hangs during boot after Security Update 2007-006 Installed

Hello out there,
As I said in the Subject, I installed Security Update 2007-006 on my MacBook Pro running OSX 10.4.9 and now it wont boot. just from playing around with it in single user mode I think it hangs sometime when configd is starting, but I don't know exactly when or why it's not booting correctly.
Any suggestions on what to do? Any help would be greatly appreciated.
MacBook Pro Core Duo Mac OS X (10.4.9)
Mac OS X (10.4.9)

The A&I, saving user and network settings, installation, just moves all current OS required stuff into a previous system folder and installs all new OS stuff. Afterwards, you'll have to bring it up to the latest version. It doesn't wipe the HD. If that doesn't work, then you can try via the other computer. If neither work, then you'll be forced to do an erase and install. That's why a bootable backup/clone is so valuable.

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

BB Torch 9860 Hangs during booting

I bought a BB Torch 9860 a week back. Yesterday night the handset got switched off as the battery had exhausted. In the morning when I was trying to switch it on it was not coming on. I put on charging, there was no indication of charging for some time then it started booting. The booting indicator (the line which indicates that the handset is being booted) went half way and stopped. The system did not respond to switch off button. The battery was removed and put back to restart. Every time it boots to half line and hangs. Would request someone to extend help please.
Regards, Tom

Hey thomas_k_s,
Welcome to the BlackBerry® Support Community Forums.
I would suggest to do a clean reload of the BlackBerry® device software as shown here: http://btsc.webapps.blackberry.com/btsc/KB11320, please test before restoring any data to the device.
If this resolves the issue do a selective restore of essential data (Address Book, Calendar, Task, Memos, BBM contacts etc.)
How to use BlackBerry Desktop Software to restore data to a BlackBerry smartphone from a backup file
http://btsc.webapps.blackberry.com/btsc/KB10339
If the issue still persists after the reload, further investigation might be required. To help further diagnose the cause, contact your wireless service provider or BlackBerry® Technical Support Services for further review and support.
Thank you.
-HB
Come follow your BlackBerry Technical Team on twitter! @BlackBerryHelp
Be sure to click Kudos! for those who have helped you.Click Solution? for posts that have solved your issue(s)!

T61 sometimes hangs during boot

Sometimes when booting my T61 it hangs about 4 sec into it after displaying one icon in the system tray. After that the only activity is the hard drive indicator blicking about once every 5 seconds. When I manually turn off the computer then reboot sometimes it repeats this and sometimes not. Sometimes it takes 3 or 4 manual reboots before it starts booting normally again. The last time it started right after I removed the AC power and went on battery then rebooted but the problem has occurred regardless of power source.

speedkreature, welcome to the forum,
what you have experienced is definitely not normal, I'd go as far as saying weird.
Does the same happen running without the battery? Has your RAM also been swapped out? If you are running with two sticks of RAM, does the same happen running with one, (swapping sticks and slots etc.)?
All that would then remain would be to remove the WLAN and BT cards.
Andy ______________________________________
Please remember to come back and mark the post that you feel solved your question as the solution, it earns the member + points
Did you find a post helpfull? You can thank the member by clicking on the star to the left awarding them Kudos Please add your type, model number and OS to your signature, it helps to help you. Forum Search Option T430 2347-G7U W8 x64, Yoga 10 HD+, Tablet 1838-2BG, T61p 6460-67G W7 x64, T43p 2668-G2G XP, T23 2647-9LG XP, plus a few more. FYI Unsolicited Personal Messages will be ignored.
Deutsche Community Comunidad en Español English Community Русскоязычное Сообщество
PepperonI blog

P205-s6237 Hangs during boot to recovery after replace HDD

Similar Messages

Maybe you are looking for