A different hang-on-boot problem

I have a mac mini that's about 1 month old. It was working great. Then I moved. I booted it up no problem, but the resolution on a different monitor was incorrect. So I clicked 'detect displays' and that's when the trouble started...
It didn't detect anything (monitor just sat there reporting no signal), so I was forced to switch it off via the power button.
Now it won't boot -- it just hangs on the apple-logo-with-spinning disk screen. Same thing happens when I try to boot from the install CD. In verbose mode it seems to hang just after the airport comes up. One forum suggested moving the relevant .kext files -- but that didn't help.
I can boot into single-user mode .. but nothing else.
Any help would really be appreciated!

I have the same problem. It started right after I reconfigured my network adding a time capsule. Other computers are OK, mini won't boot up.

Similar Messages

  • ACPI problem - random hang on boot

    Hi, I've just installed Arch 0.8.0 on my Sony PCG-XR1G laptop with Celeron 466Mhz and 128MB Ram. The installation CD hang at boot but I managed to get it work by using the kernel parameter acpi=off. After reboot, my new system still require the parameter acpi=off to boot correctly, or else 90% of the time it will hang (yes, 10% of the time it work perfectly). If I use acpi=off then I cannot shutdown my laptop completely, so I want to try not to use this parameter. Anyone have any idea? I'm running the newest kernel 2.6.20. Kernel 2.6.19 also have the same problem.

    Well, problem solved again, I think. My bios has a setting to turn on or off a feature to automatically lower the cpu speed on idle (quite funny with a celeron 466Mhz). Whenever I start the system and the kernel detect the CPU as 138Mhz (around that value), the system hang. Seldomly when it can get the correct value, it run perfectly. Still, I think there are some problem with the ACPI code in the 2.6 kernel. Or maybe it's just because my bios was too old, anyway.

  • [SOLVED] New installation hangs on boot at two different places

    Hello
    I recently made my another attempt at installing arch on a new desktop build. Previous successful attempts were old laptops.
    I followed the Beginner's Guide on the Arch wiki.
    Currently it stops at one of two places in the boot process:
    1. [ OK ] Found device Samsung_SSD_850_EVO_500GB BOOTARCH
        Starting File System Check on /dev/sdb6…
    2.  [ OK ] Started Journal Service
        [ OK ] Started udev Kernel Device Manager
    I can not consistently recreate either scenario, but it seems to be random which of the two places it stops. Cold boot and CTRL ALT Delete. I doubt that has anything to do with it, but thought I'd add it anyway.
    Current setup:
    Hardware:
    Motherboard - ASUS Z97 Pro (using ethernet adapter and sound on here)
    Processor - Intel 4790K
    Memory - 16 GB
    Graphics - Gigabyte G1 Nvidia GTX 970 SLI x2
    Storage - Samsung 850 SSD 500 GB and WD Black HDD 3 TB
    I've also configured it to use a static IP
    I started this journey by using the live Gparted CD to create partitions. I created two partitions on the SSD. One for windows 8.1 and one for linux. I then created two partitions on the HDD. One for windows, one for linux.
    I installed windows 8.1 first. It divided up the partition I gave it. I am able to run Windows. Once that was done I began installing Arch.
    I used the Feb 2015 ISO from the torrent.
    Current partition scheme for linux:
    sda1 /home
    sda3 /swap
    sda4 /var
    sdb1 /
    sdb6 /boot
    sda is the HDD and sdb is the SSD
    The other partitions not listed are for windows. To boot into windows, I use F8 to choose the windows boot manager partition. It currently defaults to the linux partition.
    During the install, I mounted the root partition first. I then created directories for each of the other partitions and then mounted them. Home, var, and root are all ext4. Boot is FAT32, and Swap is swap.
    I read where I made a couple of mistakes the first attempt on this computer and did a wipe and reinstall again. First mistake was not knowing that /boot needed to be FAT. I then learned that /swap does not need to be in the fstab. I also learned that a FAT partition can not use UUID in the fstab so I took that out and just used /dev/sdb6 instead.
    I have run out of things to search for at this point and need help to continue moving forward.
    Bellow is the current /etc/fstab. It was generated using
    genfstab -U -p /mnt >> /mnt/etc/fstab
    and then edited as noted above
    #/dev/sdb1 LABEL=archroot
    UUID=xxxxxxxxxxxxxxx / ext4 rw,relatime,data=ordered 0 1
    #/dev/sdb6 LABEL=BOOTARCH
    #UUID=xxxxxxxxx
    /dev/sdb6 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 2
    # /dev/sda1 LABEL=linux\134x20home
    UUID=xxxxxxxx /home ext4 rw,relatime,data=ordered 0 2
    #/dev/sda4 LABEL=archvar
    UUID=xxxxxxxxxx /var ext4 rw,relatime,data=ordered 0 2
    #/dev/sda3
    #UUID=xxxxxxxxxxxxxx none swap defaults 0 0
    Thanks for any help that can be provided
    Jason
    Last edited by p2ranger (2015-02-14 22:20:14)

    I tried removing gummiboot and installed GRUB2. That didn't work.
    As to the UUID's, I just typed in xxxxx's for the post because I didn't feel like transcribing random letters and numbers.
    So after reading Head_on_a_Stick's suggestion, I redid my partitions and reinstalled arch again following the Beginner's wiki page and using gummiboot
    New Partitions are as follows:
    sda1  /home
    sda3  /swap
    sda4  /var
    sdb1  /
    sdb3  /boot (originally created from windows install)
    Also, I took a screenshot from Gparted of the two disks if there is any info on there that may be of use
    http://cotting.us/gparted-sda.jpg
    http://cotting.us/gparted-sdb.jpg
    Below is the contents and output requested
    arch.conf
    title Arch Linux
    linux /vmlinuz-linux
    initrd /initramfs-linux.img
    options root=/dev/sdb1 rw
    loader.conf
    timeout5
    #default 875966af283d44de9e754c1d68848eab-*
    default arch
    gdisk -l /dev/sda
    GPT fdisk (gdisk) version 0.8.10
    Partition table scan:
    MBR: protective
    BSD: not present
    APM: not present
    GPT: present
    Found valid GPT with protective MBR; using GPT.
    Disk /dev/sda: 5860533168 sectors, 2.7 Tib
    Logical sector size: 512 bytes
    Disk identifier (GUID): E11d436B-ED6D-47AD-BCD0-F04384ED50B8
    Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 5860533134
    Partitions will be aligned on 2048-sector boundaries
    Total free space is 2925 sectors (1.4 MiB)
    Number Start (sector) End (sector) Size Code Name
    1 2048 45672447 21.8GiB 8300
    2 2871662592 5860532223 1.4 TiB 0700
    3 2854432768 2871662591 8.2 GiB 8200
    4 45672448 285443277 1.3 TiB 8300
    gdisk -l /dev/sdb
    GPT fdisk (gdisk) version 0.8.10
    Partition table scan:
    MBR: protective
    BSD: not present
    APM: not present
    GPT: present
    Found valid GPT with protective MBR; using GPT.
    Disk /dev/sda: 5860533168 sectors, 465.8 GiB
    Logical sector size: 512 bytes
    Disk identifier (GUID): DA9A6AF9-066B-4C1A-8778-93CCE5A68D97
    Partition table holds up to 128 entries
    First usable sector is 34, last usable sector is 976773134
    Partitions will be aligned on 2048-sector boundaries
    Total free space is 2029 sectors (1014.5 KiB)
    Number Start (sector) End (sector) Size Code Name
    1 2048 410247167 195.6 GiB 8300
    2 410247168 410861567 300.0 MiB 2700 Basic data partition
    3 410861568 411066367 100.0 MiB EF00 EFI system partition
    4 411066368 411328511 128.0 MiB 0C01 Microsoft reserved …
    5 411328512 976773119 269.6 GiB 0700 Basic data partition
    lsblk -f
    sda
    -sda1 /home
    -sda2
    -sda3 [SWAP]
    -sda4 /var
    sdb
    -sdb1 /
    -sdb2
    -sdb3 /boot
    -sdb4
    -sdb5
    sdd
    -sdd1
    -sdd2
    sr0
    loop0
    loop1
    -arch_airootfs /etc/resolv.conf
    loop2
    -arch_airootfs /etc/resolv.conf
    Since my fstab is changed, here is the new one
    # /dev/sdb1 LABEL=archroot
    UUID=xxxxxxxxxxxxxxxxxx / ext4 rw,relatime,data=ordered 0 1
    # /dev/sdb3
    #UUID=xxxxxxxx
    /dev/sdb3 /boot vfat rw,relatime,fmask=0022,dmask=0022, codepage=437,iocharset=iso8859-1, shortname=mixed, errors=remount-ro 0 2
    # /dev/sda1 LABEL=archvar
    UUID=xxxxxxxxxxxxxxxxxx /home ext4 rw,relatime,data=ordered 0 2
    # /dev/sda4 LABEL=archome
    UUID=xxxxxxxxxxxxxxxxx /var ext4 rw,relatime,data=ordered 0 2
    # /dev/sda3
    #UUID=xxxxxxxxxxxxxxx none swap defaults 0 0
    After another install, it still hangs on booting. Here are some of the last lines it displays:
    ( OK ) Started create system users
    Starting Create static device nodes in /dev...
    ( OK ) Started Journal service.
    ( OK ) Started create static device nodes in /dev.
    ( OK ) Reached target Local File systems (Pre).
    ( OK ) Started Rebuild hardware database
    Starting udev Kernel Device Manager....
    ( OK ) Started Rebuild Dynamic linker cache
    ( OK ) Started udev Kernel Device Manager
    I’m glad people like my setup. I spent a lot of time reading and comparing before I came up with what I bought.
    Thanks for your help
    Jason
    Last edited by p2ranger (2015-02-13 23:52:29)

  • Windows 7 hangs from boot menu

    Hi,
    my Windows 7 partition refuses to start from boot menu, system just hangs and does nothing. I've not made any changes to the disk layout, only thing I can think of is the upgrade to 10.9.4 which probably changed the recovery partition.
    History:
    - iMac Mavericks 10.9.3 with boot camp 5.1.2 and Windows 7, used to start into Windows by pressing Alt on start up, then reboot from Windows menu or from Windows boot camp application into OS X and back without problems
    - installed the 10.9.4 Build 13E28 upgrade some days ago
    - Change today: rebooted from the boot camp system tray app into OS X, worked without a problem
    - reboot from OS X into boot menu, select Windows 7 partition, system hangs
    I've found this thread, describing a similar problem Repairing Boot Camp after creating new partition I think, however since my Index output only lists 4 partitions I think my problem might be a bit different.
    Here's the output from: sudo gpt -r -vv show disk0
    gpt show: disk0: mediasize=500107862016; sectorsize=512; blocks=976773168
    gpt show: disk0: Suspicious MBR at sector 0
    gpt show: disk0: Pri GPT at sector 1
    gpt show: disk0: Sec GPT at sector 976773167
          start       size  index  contents
              0          1         MBR
              1          1         Pri GPT header
              2         32         Pri GPT table
             34          6        
             40     409600      1  GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B
         409640  816890832      2  GPT part - 48465300-0000-11AA-AA11-00306543ECAC
      817300472    1269536      3  GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC
      818570008       1256        
      818571264  158201856      4  GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
      976773120         15        
      976773135         32         Sec GPT table
      976773167          1         Sec GPT header
    and this one is from: sudo fdisk /dev/disk0
    Disk: /dev/disk0 geometry: 60801/255/63 [976773168 sectors]
    Signature: 0xAA55
             Starting       Ending
    #: id  cyl  hd sec -  cyl  hd sec [     start -       size]
    1: EE 1023 254  63 - 1023 254  63 [         1 -     409639] <Unknown ID>
    2: AF 1023 254  63 - 1023 254  63 [    409640 -  816890832] HFS+       
    3: AB 1023 254  63 - 1023 254  63 [ 817300472 -    1269536] Darwin Boot
    *4: 07 1023 254  63 - 1023 254  63 [ 818571264 -  158201856] HPFS/QNX/AUX
    and, just in case: diskutil list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *500.1 GB   disk0
       1:                        EFI EFI                     209.7 MB   disk0s1
       2:                  Apple_HFS Calimera                418.2 GB   disk0s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
       4:       Microsoft Basic Data Windows 7               81.0 GB    disk0s4
    I guess something mixed up the MBR since I would have expected line 4 of the fdisk output to show something 'Windows' like instead of HPFS/QNX/AUX, but even if that is correct, the question is how can the boot problem be fixed?
    The Windows partition is accessible from OS X, so copying the data is not a problem if everything else fails. As far as I remember, the boot camp version in windows is 3.3 (it's an older iMac model).
    GDisk is available, command line not a problem, if you need any further info let me know, any help appreciated.
    thanks,
    jk

    Hi,
    > Does the Bootcamp partition show up in Finder and can you see files in it?
    Yes, the partition shows up in Finder and I can see and copy files.
    > In Disk Utility, does the Bootcamp partition report as NTFS?
    Yes it does, "Get Info" from Finder also reports it as a NTFS volume.
    > Do you have any third party NTFS drivers?
    Yes I have, Paragon NTFS tools.
    > If you hold the ALT key can you boot into Windows?
    No, system just hangs and needs to be rebooted via power-off.
    > If you came from 10.9.3 to 10.9.4, the Recovery HD should have existed under 10.9.3.
    Yes it did, I did a clean install from USB media when Mavericks came out, the Recovery HD is also visible - and has been - in the boot menu.
    > The one strange part is that your volume says "Windows 7". Were any diskutil commands run to change volume names?
    No, just a left click on the Volume Name in Finder and then change Bootcamp to Windows 7.
    Output of dd:
    00000000  eb 52 90 4e 54 46 53 20  20 20 20 00 02 08 00 00  |.R.NTFS    .....|
    00000010  00 00 00 00 00 f8 00 00  3f 00 ff 00 00 68 ca 30  |........?....h.0|
    00000020  00 00 00 00 80 00 80 00  ff f7 6d 09 00 00 00 00  |..........m.....|
    00000030  00 00 0c 00 00 00 00 00  02 00 00 00 00 00 00 00  |................|
    00000040  f6 00 00 00 01 00 00 00  d7 f9 07 a2 27 08 a2 26  |............'..&|
    00000050  16 1d 72 73 fa 33 c0 8e  d0 bc 00 7c fb 68 c0 07  |..rs.3.....|.h..|
    00000060  1f 1e 68 66 00 cb 88 16  0e 00 66 81 3e 03 00 4e  |..hf......f.>..N|
    00000070  54 46 53 75 15 b4 41 bb  aa 55 cd 13 72 0c 81 fb  |TFSu..A..U..r...|
    00000080  55 aa 75 06 f7 c1 01 00  75 03 e9 dd 00 1e 83 ec  |U.u.....u.......|
    00000090  18 68 1a 00 b4 48 8a 16  0e 00 8b f4 16 1f cd 13  |.h...H..........|
    000000a0  9f 83 c4 18 9e 58 1f 72  e1 3b 06 0b 00 75 db a3  |.....X.r.;...u..|
    000000b0  0f 00 c1 2e 0f 00 04 1e  5a 33 db b9 00 20 2b c8  |........Z3... +.|
    000000c0  66 ff 06 11 00 03 16 0f  00 8e c2 ff 06 16 00 e8  |f...............|
    000000d0  4b 00 2b c8 77 ef b8 00  bb cd 1a 66 23 c0 75 2d  |K.+.w......f#.u-|
    000000e0  66 81 fb 54 43 50 41 75  24 81 f9 02 01 72 1e 16  |f..TCPAu$....r..|
    000000f0  68 07 bb 16 68 70 0e 16  68 09 00 66 53 66 53 66  |h...hp..h..fSfSf|
    00000100  55 16 16 16 68 b8 01 66  61 0e 07 cd 1a 33 c0 bf  |U...h..fa....3..|
    00000110  28 10 b9 d8 0f fc f3 aa  e9 5f 01 90 90 66 60 1e  |(........_...f`.|
    00000120  06 66 a1 11 00 66 03 06  1c 00 1e 66 68 00 00 00  |.f...f.....fh...|
    00000130  00 66 50 06 53 68 01 00  68 10 00 b4 42 8a 16 0e  |.fP.Sh..h...B...|
    00000140  00 16 1f 8b f4 cd 13 66  59 5b 5a 66 59 66 59 1f  |.......fY[ZfYfY.|
    00000150  0f 82 16 00 66 ff 06 11  00 03 16 0f 00 8e c2 ff  |....f...........|
    00000160  0e 16 00 75 bc 07 1f 66  61 c3 a0 f8 01 e8 09 00  |...u...fa.......|
    00000170  a0 fb 01 e8 03 00 f4 eb  fd b4 01 8b f0 ac 3c 00  |..............<.|
    00000180  74 09 b4 0e bb 07 00 cd  10 eb f2 c3 0d 0a 41 20  |t.............A |
    00000190  64 69 73 6b 20 72 65 61  64 20 65 72 72 6f 72 20  |disk read error |
    000001a0  6f 63 63 75 72 72 65 64  00 0d 0a 42 4f 4f 54 4d  |occurred...BOOTM|
    000001b0  47 52 20 69 73 20 6d 69  73 73 69 6e 67 00 0d 0a  |GR is missing...|
    000001c0  42 4f 4f 54 4d 47 52 20  69 73 20 63 6f 6d 70 72  |BOOTMGR is compr|
    000001d0  65 73 73 65 64 00 0d 0a  50 72 65 73 73 20 43 74  |essed...Press Ct|
    000001e0  72 6c 2b 41 6c 74 2b 44  65 6c 20 74 6f 20 72 65  |rl+Alt+Del to re|
    000001f0  73 74 61 72 74 0d 0a 00  8c a9 be d6 00 00 55 aa  |start.........U.|
    00000200
    So, you think running the Windows startup repair will fix the problem? Is there something that I should be aware of in terms of interfering with the OS X partition?
    jk

  • Yosemite hangs in booting after applying Update 2015-003.

    I have applied Update 2015-003 to Yosemite.
    After booting the progress bar hangs at about 30% for over an hour.
    The hardware is a MacBook Pro with a SSD harddrive.

    Take each of these steps that you haven't already tried. Stop when the problem is resolved.
    To restart an unresponsive computer, press and hold the power button for a few seconds until the power shuts off, then release, wait a few more seconds, and press it again briefly.
    Step 1
    The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
    There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
    a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
    b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
    c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
    d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
    Step 2
    If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
    Step 3
    Sometimes a startup failure can be resolved by resetting the NVRAM.
    Step 4
    If a desktop Mac hangs at a plain gray screen with a movable cursor, the keyboard may not be recognized. Press and hold the button on the side of an Apple wireless keyboard to make it discoverable. If need be, replace or recharge the batteries. If you're using a USB keyboard connected to a hub, connect it to a built-in port.
    Step 5
    If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
    Step 6
    Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
    Step 7
    If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
    Start up in safe mode. Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Post for further instructions.
    Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
    The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.
    If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
    If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
    Step 8
    Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
    This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
    Step 9
    If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.  
    Step 10
    Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
    Step 11
    Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
    Step 12
    This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
    Step 13
    If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

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

  • [SOLVED] System hangs on boot, reinstalling Arch doesn't help

    After a recent upgrade (including the kernel), my system hangs on boot.  I have an Asus K40IN laptop, about 2 years old.  I've been running Arch for the life of the computer and never had any (serious) problems.
    I booted into a live Arch environment, tried rebuilding the mkinitcpio image, didn't work.  Tried downgrading the kernel, didn't work.
    I then assumed it was just some software issue that I couldn't figure out, so I reinstalled Arch.  No change.
    Here's what my screen looks like when it hangs:
    Any ideas would be very much appreciated.  I'm completely stumped here.
    Last edited by noahsark1126 (2011-06-15 23:32:34)

    jnguyen: 
    I have another arch system, a desktop, that I tend to keep pretty much in sync with my laptop.  So I can look in the logs on that system to see what was upgraded.  The other notable packages in that upgrade were probably udev, initscripts, and mkinitcpio.  I will try downgrading those.
    Leonid.I:
    I'm using the 2010.05 arch release, which has kernel 2.6.33.  I see two cores in the live env, as I should, and there's nothing to suggest any problems in the logs.
    I'm actually now getting a completely different hang screen:
    Of course I don't know what this one means either...

  • P45 Platinum boot problem!!!

    PC specs in signature below!!
    Ok, this is a new system, and it has been running GREAT since I started it for the first time. I am running my RAM with manual settings of 5 5 5 18/1.8v/800. Nothing is overclocked!!
    Anyway, this morning I get to the office anxiously anticipating starting up my new system for a day of pristine computing. It starts up, the screen appears where you can hit "delete" to enter the bios. The screen hangs there for allot longer than I remember. Then, I get this message popping up on the screen: ''Reboot and select proper boot device or insert boot media in selected boot device''.
    The first thing I did was hit Ctrl/Alt/Del to reboot and enter the bios to check my boot order. Everything was set exactly the way it is supposed to be. CD/RW first, then my OS drive. I exit out, and it boots into windows just fine.
    Ok, later I decide to run check disk on my OS drive, thinking that maybe it's going bad, and the bios is having trouble seeing it. Check disk finishes, and it goes to boot into windows, and I get the ''Reboot and select proper boot device or insert boot media in selected boot device'' message again.
    So, once again I hit Ctrl/Alt/Del to reboot, and it hangs on the screen where you can enter the bios. I quickly hit delete this time to enter the bios to see if my operating system drive is recognized. When I do this, it enters the bios, but hangs for awhile where it detects the hardware. Finally I can get to all the features in the bios, so I check to see if my hardware is recognized. Both my SATA hard drives do not show up as being recognized. My SATA CD/RW shows up, but not my hard drives.
    So, I exit out of the bios, and it boots to windows just fine. I restart my system again to see what happens, and it boot just fine into windows.
    Anyway, I went ahead and shut down my system, pulled the power plug, and cleared the CMOS. I then started the system back, entered the bios and set up all my settings, and it boots right into windows fine.
    What do you think happened here?  At first I thought maybe my OS drive was going bad, but after discovering that the bios didn't see either one of my drives, I ruled that out. Plus check disk was fine on the OS drive.
    Any ideas??

    Ok, I am still having an issue with this boot problem described above. Now that I have used my system allot more, I have discovered some more details. This boot problem only occurs when I plug anything into the system that gets noticed in the "boot order" in the bios. Example: USB thumb drive, external hard drive, or even swapping out an internal drive. The next time I re-boot, it fails like I described above.
    Ok, here are some more experiences I have had. My system had been running great, and boot ups were working perfect. I decided I wanted to add a 3rd internal hard drive for storage. I already had my C operating system drive, and a D storage drive. I bought a large Seagate for a 3rd F storage drive. My CD/RW is listed as my E drive. So, I power my system off, and turn off the switch on the back of the PSU. I then add my 3rd hard drive and hook it all up. I power on my system. It boots to the bios screen where you hit delete to enter the bios. I enter the bios and I see all three of my hard drives. I check to make sure my boot order is correct, and save and exit the bios. As it booting, this time it hangs for a longer time at the screen where you can enter the bios. I hit the delete key to enter the bios, but it once again hangs while it tries to list all the hardware. Finally I can get to the bios setup screen, and both my C drive and D drive are not recognized, but my new Seagate is. For the record, my C drive is connected on the #1 SATA connection, my D drive is on the #2 SATA connection, and my new Seagate drive is on the #3 SATA connection. So, I select optimized defaults, save, and exit the bios. I re-enter the bios just fine and in the normal timely fashion. Now all my hardware is recognized. I set up my RAM again and other settings, and save, exit, and my system boots perfect.
    So, I go about a week of perfect boot ups and no problems. I decided to buy a new larger hard drive to replace my existing C operating system drive. My plan was to install the new drive, and simply restore from a current image made from my old hard drive. I get my new C drive installed, and plugged into the #1 SATA connection on the mobo just like before. Ok, same drill......I enter the bios, and all my drives are recognized. I set my boot order, save, and exit. AGAIN, when it gets to the bios screen where you hit delete to enter the bios.....it hangs for longer than usual. I know exactly what it's doing, so I hit delete. It lags again as it starts to list hardware. Again, when I get to the setup bios screen, my C drive, and D drive are not recognized, yet my F drive is......just like before. So, both the drives connected to the #1, and #2 SATA connections on the mobo are not seen in the bios, yet the hard drive on #3 is seen. I do the same thing again, which is load optimized defaults, save, exit, and re-enter the bios again just fine. All drives are seen, I set up my personal settings, and all is well again.
    The last time it happened was when I connected my USB thumb drive. Same exact scenario. The thumb drive shows up, and my F drive with the C drive and D drive missing again.
    Any ideas??  The system will run just great now the way it is. But, the second I stick my thumb drive in, or an external hard drive, my C and D drive will disappear on next boot. If I kept the thumb drive and external drive connected, and just loaded optimized defaults, then rebooted and loaded my personal setting, I would never have the boot problem again. It just doesn't like me disconnecting, and re-connecting hardware I guess.
    About the only thing I can think of to try is connecting my C and D drive to different SATA connections. But, even if that worked, it wouldn't fix the problem.

  • [Solved] Arch hangs at boot at random points

    Hello. First of all, sorry for the undescriptive title, but one of the main reasons that I came here is because of I don't know what's causing the hanging. The problem started one day to another, the pc worked well and one day I turned it on and it hanged.
    At first I thought it was fsck, but doing a little boot debugging (appended "debug" to the kernel parameters) I could notice that the problem comes from somewhere else. The problem is that every time that I try again, the boot stops at a different point, so I cannot know which is exactly the problem.
    I post the last 6 lines of 3 different boots (written by hand, so might have typos):
    [ OK ] Started Login Service.
    [ 24.258733] systemd-logind[252]: Watching system buttons on /dev/input/event2 (Sleep Button)
    [ OK ] Started GNOME Display Manager.
    Starting Accounts Service...
    Starting Authourization Manager...
    [ OK ] Started Authourization Manager.
    [ OK ] Started Accounts Service.
    [ OK ] Reached target Network.
    Starting Privoxy Web Proxy With Advanced Filtering Capabilities....
    Starting Network Time Service...
    Starting Anonymizing Overlay Network...
    Starting Samba NetBIOS name server...
    [ 27.601929] e1000e 0000:00:19.0: irq 51 for MSI/MSI-X
    [ 27.703150] e1000e 0000:00:19.0: irq 51 for MSI/MSI-X
    [ 27.703916] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
    [ OK ] Started Network Time Service
    And it never gets any further than that. The farthest it gets is "[  OK  ] Started Network Time Service". But I don't know even how to start fixing this.
    Thank you very much.
    If you need more logs ask for it.
    Last edited by TMalthus (2013-05-11 16:06:50)

    Try disabling as much as you can, disable graphical.target and gdm, and enable multi-user.target and work from there to see what's causing the problem.
    Slowly re-enable services again in multi-user mode, then if all goes well, disable multi-user.target and enable graphical again, and perhaps try lightdm as a display manager, just to try rule out gdm if you get to this stage.

  • MSI P45 Neo-f with intermittent boot problems

    Current system:
    *CPU: Intel core2duo 4300 1,80GHz
    Mobo: MSI P45 Neo-F LGA775
    *Memory: 1 Kingston 1GB PC2-5300 667MHz DDR2 and 1 Dane-Elec 1GB PC2-5300 667MHz DDR2
    Videocard: Club3D Nvidia 8800GT 512MB GDDR3
    *Hard drive: 120GB IBM deskstar 7200rpm Ultra-ATA/100 (yes I realize it is known as the deathstar, but it hasn't failed so far, I do back-up because I'm paranoid
    PSU: Real Silent Nexus NX-5000 500 watt
    *Soundcard: Soundblaster Audigy
    OS: Windows XP home, service pack 2
    *Lite-on IT dvd-rom drive
    *floppy disk drive
    I also have 3 case fans spinning away in a marginally large Chieftec Dragon tower.
    The parts I marked with an asterisk (*) are parts that I removed from my old rig and re-used.
    I'll try to give a clear rundown of my problem and the steps I've taken so far.
    3 days ago I acquired the P45 Neo and installed it into my system, together with the 8800GT videocard. I was still using my old PSU, a Chieftec 360watt. This PSU served me well for 7 years, but it was starting to build up noise while trying to keep up games on my old rig.
    I had some trouble getting the system to boot, I tried changing some of the 4 pins wires going to the hard drive and the dvd drive. I don't know if it was luck or if I managed to divide the load properly for the system to boot. But I succeeded into booting up, got into the bios and eventually installed WinXP.
    As soon as it was time to install the videocard drivers, it stopped responding. I assumed it was a power issue, since I could only install the 20pin and 4pin cpu, but my Chieftec PSU didn't have a 24pin plug to the mobo - and it needed replacing anyway! So I bought a new 500watt PSU that had all the required plugs and more wattage.
    I installed the new PSU, checked every connection and pressed the power button. 'Lo and behold, the computer starts up. I install the videocard drivers and it proceeds with no problems. I try to install the soundcard, but the cd says I don't have one installed. I fix that by going to the System list and install the drivers from there. I install a firewall. By then I have successfully rebooted the computer 3 or 4 times. I decide all is well and turn off the computer. But I realize I wanted to check up something on the internet.
    I press the powerbutton. The PC power light go up for just a fraction of a second. I can see the blue LED of one of the case fans switching on just as briefly - then it goes out. The computer keeps trying to turn itself on. It looks like it's hickupping to try and boot!
    I turn off the PSU power on the back-side because the computer keeps trying and wait for a bit. After 10 minutes, it still doesn't work. I leave the computer for a bit and return an hour later. The computer then starts up with no problems. I turn it off after a few hours, do a reset, start it up, no problems. But then the next day it happens again.
    It's pretty tough figuring out what the problem is because it looks..almost random. I considered it could be a heat issue, but sometimes it *does* start up just after it's been turned down. Checking the bios shows no strange temperature shifts.
    Hope anyone can help me, because I do not want to go back to my old Asrock mobo

    While powered down I cleared the cmos data, removed the Dane Elec DDR2 module and set the bios to optimized defaults. Computer restarted to WinXP with no problems (it has been off the whole night). I shut down WinXP, wait a few moments and then turn the computer back on. Alas, it won't start and starts hick-upping. I turn power off at the PSU again, so it stops.
    Now I try switching out the Kingston module instead. By now the computer has been off for 10 min (while I write this entry on laptop). I press the power button on the PSU and then the power button on the front. There is a short pause, lasting a second. The computer turns on, longer now, but it only lasts 2 whole seconds before it turns off again and goes on again (I believe now you can call it powercycling). It repeats this process until I shut off the PSU.
    I check to see if I have installed it properly and try again but it starts powercycling again.
    15 min pass, I put the Kingston module back in, press the power button and voila, this time it does start. WinXP shows up, no problems. I leave it on for a bit and then shut down. And when I press the power button again - the feeling of dread returns, when it starts hickupping again.
    I'm going to see if I can install one of the memory modules from my housemate. Then hopefully tommorrow, I'm going to try if I can test a different PSU, since I see someone else on the forum - who recently posted, has the exact same power supply and also has boot problems, coincidence... or not ^^;.

  • The mother of all re-boot problems.

    Hi All,
    I've got that re-boot problem that seems very common but the solutions out there aren't working.
    Basically the computer will turn on, chime, grey screen comes up, shortly after apple logo, and then the gear starts turning, about 2 minutes later restart, process repeats.
    I've tried.
    - Booting from CD/Recovery Disk - Won't happen
    - A million different key combinations, I've read about 10 different posts on key combinations and tried them all, including PRAM reset, boot from different source, etc.
    Basically it's like my keyboard commands aren't being heard at all, but to test if the keyboard was working I pressed the caps lock button and the light was going on and off which tells me its powered. The only kind of input I have been able to acheive is by holding the mouse button down to eject the CD, other than that I have absolutly no control what so ever.
    Would like any insight.
    Cheers,
    Jarrod.

    HI,
    If you've had your iMac for less then one year then it's covered by the one year limited warranty.
    Take it to an Apple store or an Apple certified repair provider.
    Carolyn
    Message was edited by: Carolyn Samit

  • 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)

  • HP Pavilion Media Center m8300f Hangs on boot

    I have a HP Pavilion Media Center m8300f which came loaded with Vista Home Premium. About 18 month sold. Recently the computer would hang on boot up. I used the system restore and went back to a safe install. This worked ok until Windows added more patches which caused the same problem to occur again. After one or two of these episodes I was not longer able to return to a safe install. I ran the system recovery several times to check the hardware. Everything turned up good. Since I did not have a good set of recovery disks I decided to install XP on the computer and then upgrade to Vista. XP installed without a single problem. I purchased a NEW Vista Home Premium because I could later upgrade free to Windows 7. I tried to install Vista over XP. The process would start and then hang. So I reformated the hard drive using an external USB unit on another computer, replaced the drive and tried to install Vista off the DVD. It would not boot up. As a test using the Vista DVD I purchased, I upgraded XP on a separate computer to Vista. Worked very nice.
    I ordered a set of the recovery DVDs and tried them. They would not boot up. I replaced the hard drive with a new SEAGATE SATA drive because I felt the connectors were not locking in. I still could not get the recovery DVDs to run. I went back to the XP and it installed. So here I am with a computer that willl not run or install Vista but will run XP. Also HP does not provide the XP drivers for the hardware on this computer.
    Does anyone know why Vista will not install or how to get it on this computer?
    I installed a NEW Seagate SATA hard drive for drive "C" because the connectors where not locking in place. rmated the hardI purchased the Recovery DVDs from HP and tried to reinstall it.

    I had the same problem with computer halting with blue screens, black screens, etc.  Motherboard had 6 capacitors with bulging tops.  I found a replacement Nettle 2 motherboard from seller diypc2008 on E-Bay for the cost of $75.00 with free shipping.  Installed new motherboard and computer works like new. 
    It appears like at around 2 years, this problem occurs from what I read on this forum.  Look for capacitors on the motherboard with bulging tops.  I fixed my computer by replacing motherboard after running many hours of diagnostics, replacing power supply, and changing out drives.

  • IMac with 10.4.8 hangs on boot

    My wife runs a non-profit parenting organization using an iMac (700 MHz, G4, flat panel) with OS 10.4.8. Last Friday on startup, it hung within a few seconds of starting to startup. Kernel panic text covered the screen. Retry to startup gave same result. But will start and run ok in Safe Boot mode although the bootup take very, very long --and can't use search to find files and can't print --maybe other limitations with Safe Boot mode will showup. This past weekend, while running in Safe Boot mode, I was able to backup all of her files onto 8 CDs. I could just reinstall everything beginning with the OS and continue through the various applications (MSOffice, Appleworks, Photoshop Elements, etc.) but I would like to find something that wasn't so drastic to try first. Also I would like to have some idea of what happened so that this would not (hopefully) re-occur. Note --no new software or hardware has been installed in many months except for every Apple update that comes along. It does not have an AirPort card and can access the Internet using ethernet and a DSL connection. Since it started into Safe Boot, I understand that some level of disk repair has taken place. What things should I try before I wipe and reinstall?
    iMac G4 700 MHz Flat Screen   Mac OS X (10.4.8)  

    Hello --
    Thanks for the suggestions. I repaired the disk. I repaired the permissions. And I ran the Apple Hardware Test Disk. The disk was fine. Many, many permissions were repaired. And the Hardware Test Disk found nothing. But, at that point, the "Hang on Boot kernel panic" continued. I then went to the suggestions in Dr. Smokes "Resolving Kernel Panics" article. Using "Cocktail" to flush the caches did the trick. The computer is booting fine again and running faster that before. As an added plus, several other annoying problems and issues have gone away. It seems clear to me that there was a problem in one or more of the caches (I have no clue as to which one) and, therefore, very early in the boot sequence, bad data was drawn upon or an attempt to find data was not possible because of damage to one of the caches. At any rate, Thank you for the suggestions --the computer is fine. (And my wife, on behalf of her non-profit parenting support program, sends you many thanks as well. She also swears that she will now carefully backup her files AT LEAST once a week.)

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

Maybe you are looking for