My system won't boot past POST after I plugged in my new SATA drive. (SATA noob

 
I have a MSI K8n Neo 2 Platinum mobo with a Athlon64 +3500 and 1gig dual channel DDR 400. I currently have 2 drives set up a IDE primary (MAxtor 6Y120) and a IDE slave (Maxtor 6L080).
I recently purchased a Maxtor DiamondMax 10 6L300S0 300GB Serial ATA 7200RPM Hard Drive w/16MB Buffer.
It is my first SATA drive ever so non the less I am a newb. I want to use it as a non Raid media storage device while my primary IDE remains my boot OS drive.
I plugged the SATA in to the sata one port and powered it. I enabled the SATA in the bios with RAID disabled. When the system boots up it does the memory chech and lists all the IDE devices. Then it says "Detecting IDE drives..." and just hangs there. The new drive spins so it definatly has power but occasionaly it make occasional clicking sounds.
Once it actually booted up and windows detected it. I decided to reboot it just to play it safe but it never would get past post screen again. I can boot up the system normally when I unplug the SATA cable.
Please help I need to know if I am doing something wrong or I should RMA the drive. THANK YOU!

Got the same problem:
pata Maxtor Diamond Max =9 200 (40/160) Boot drive
AMD 64 x2 3800
Bios 1.2 090905 using MSi online auto update utility
2x 512 DDR double sided
X850 pro 128mb
PSU Sweetex 650w
Switched power supply
110/220 V switchable (220 V: 5 Amp/ 110V:10 Amp)   
+ 3.3 V    28 Amp
+    5 V    45 Amp
+  12 V    25 Amp
-5 V    0.5 Amp
-12 V    0.8 Amp
- 5 Vsb  2 Amp PEAK 2.5
Max. 650 Watt
CE, FC
Boots perfectly with 1 pata, adda sata to sata 1 or 2 or 3 or 4
Boot stalls in bios at Raid setup. Tried enable raid with no drives enable , system booted twice, turned off overnight, then failed to start the next day. Will only restart with a cold reboot. Hot reboot produces a long BEEEEEP & power is on but nothing happens no post nothing.
SATA drive was taked from a working system (ECS 755a  - AMD 64 3000 - PATA 200 / SATA 200), configured 40/160 40=OS Winxp 64 / 160 = data. System will not boot if this is the sole drive connected.

Similar Messages

  • System Won't Boot Past White Screen With Apple Logo

    I have a Power Mac G5 tower that someone gave me. No hard drive.
    I placed a NEW hard drive in and installed 10.4 onto it. When I finished I turned OFF the machine. When I now try and turn the machine ON, it will freeze-up during boot up at the white screen with the Apple logo. The little spinning ring/dial doesn't come up.
    The system is:
    Power Mac G5 (June 2004)
    Model ID: PowerMac7,3
    dual 2.5GHz
    512MB RAM (2x256MB)
    Using the Boot-up in Detailed SAFE Mode I was given the info below. Any help is greatly appreciated.
    using 1310 buffer headers and 1310 cluster IO buffer headers
    kld(): Undefined symbols:
    ZN11IOPCIBridge18compareAddressCellEmPmS0
    kldload_frommemory() failed for module com.apple.driver.AppleMacRiscPCI
    Failed to load extension com.apple.driver.AppleMacRiscPCI.
    Couldn't alloc class "AppleMacRiscPCI"
    kld(): Underfined Symbols:
    ZN11IOPCIBridge18compareAddressCellEmPmS0
    kldload_frommemory() failed for module com.apple.driver.AppleMacRiscPCI
    Failed to laod extension com.apple.driver.AppleMacRiscPCI.
    Couldn't alloc class "AppleMacRiscAGP"
    kld(): Undefined symbols:
    ZN11IOPCIBridge18compareAddressCellEmPmS0
    kldload_frommemory() failed for module com.apple.driver.AppleMacRiscPCI
    Failed to load extension com.apple.driver.AppleMacRiscPCI.
    Couldn't alloc class "AppleMacRiscHT"
    kld(): Undefined symbols:
    ZN11IOPCIBridge18compareAddressCellEmPmS0
    kldload_frommemory() failed for module com.apple.driver.AppleMacRiscPCI
    Failed to load extension com.apple.driver.AppleMacRiscPCI.
    Couldn't alloc class "AppleMacRiscDART"
    ApplePlatformExpert::getGMTTimeOfDay can not provide time of day RTC did not show up

    Does it boot into any of these modes?
    Target mode...
    http://support.apple.com/kb/HT1661
    Does it boot to Single User Mode, CMD+s keys at bootup, if so try...
    /sbin/fsck -fy
    Repeat until it shows no errors fixed.
    (Space between fsck AND -fy important).
    Resolve startup issues and perform disk maintenance with Disk Utility and fsck...
    http://docs.info.apple.com/article.html?artnum=106214
    We might get clues with verbose mode...
    http://support.apple.com/kb/HT1492

  • Btrfs: System won't boot anymore after unclean shutdown

    Hi,
    I have a problem with my ArchLinux (kernel 3.19.2-1-ARCH).
    I have my root partition as BTRFS and no /boot partition.
    After an unclean shutdown the system won't boot anymore.
    GRUB loads the kernel and the kernel starts but it hangs saying: Mounted /dev/sda3 on real root.
    Then, I have to start a Live CD and do:
    btrfsck /dev/sda3
    After that the system boots correctly.
    I've tried adding fsck to the HOOKS in the mkinitcpio.conf file and in fact it tries to fsck the filesystem (but with BTRFS, fsck.btrfs doesn't work...)
    What can I do?
    Thanks

    I'm also having this problem. I tried booting up the netinstall image to debug it, but I can't mount my btrfs volume from there either: mount just hangs. After a while, the kernel goes:
    [...] INFO: task mount:612 blocked for more than 120 seconds.
    [...] Not tainted 3.19.2-1-ARCH #1
    [...] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    [...] INFO: task btrfs-transacti:636 blocked for more than 120 seconds.
    [...] Not tainted 3.19.2-1-ARCH #1
    [...] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    From this post I guessed that I might just need to wait so that I could defrag the volume once it was mounted, but it's been hanging for over 15min now (the message above continues to come up periodically).
    Like the OP in the thread I linked to above, my btrfs volume is inside an LVM volume (which is on dm-crypt). Don't know whether that's relevant.
    Output of btrfs-check:
    Checking filesystem on /dev/pixie/btrfs
    UUID: e04cc661-e31a-4dbf-870d-664bc913e34a
    found 76855677062 bytes used err is 1
    total csum bytes: 72928436
    total tree bytes: 2092515328
    total fs tree bytes: 1888452608
    total extent tree bytes: 104644608
    btree space waste bytes: 357251032
    file data blocks allocated: 181197139968
    referenced 109440282624
    btrfs-progs v3.19
    dmesg output:
    [ 36.824998] Btrfs loaded
    [ 36.826713] BTRFS: device fsid e04cc661-e31a-4dbf-870d-664bc913e34a devid 1 transid 98618 /dev/dm-3
    [ 46.219014] BTRFS info (device dm-3): disk space caching is enabled
    [ 46.259830] BTRFS: detected SSD devices, enabling SSD mode
    [ 240.333313] INFO: task mount:539 blocked for more than 120 seconds.
    [ 240.335542] Not tainted 3.19.2-1-ARCH #1
    [ 240.337795] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    [ 240.340263] mount D ffff8800cf2837f8 0 539 453 0x00000000
    [ 240.340277] ffff8800cf2837f8 ffff8800cf2331b0 0000000000013f00 ffff8800cf283fd8
    [ 240.340286] 0000000000013f00 ffffffff81818540 ffff8800cf2331b0 ffff8802094f67a8
    [ 240.340291] 0000000000000004 ffff8800cf283758 ffffffffa0a2fc91 ffff8802094f67a8
    [ 240.340298] Call Trace:
    [ 240.340335] [<ffffffffa0a2fc91>] ? set_extent_buffer_dirty+0x71/0xc0 [btrfs]
    [ 240.340357] [<ffffffffa0a05796>] ? btrfs_buffer_uptodate+0x56/0x80 [btrfs]
    [ 240.340366] [<ffffffff8155e999>] schedule+0x29/0x70
    [ 240.340389] [<ffffffffa0a47745>] btrfs_tree_lock+0x65/0x200 [btrfs]
    [ 240.340396] [<ffffffff810b4380>] ? wait_woken+0x90/0x90
    [ 240.340410] [<ffffffffa09e5cd9>] btrfs_search_slot+0x799/0xaa0 [btrfs]
    [ 240.340425] [<ffffffffa09e79f5>] btrfs_insert_empty_items+0x75/0xd0 [btrfs]
    [ 240.340446] [<ffffffffa0a47a37>] btrfs_insert_orphan_item+0x67/0xa0 [btrfs]
    [ 240.340465] [<ffffffffa0a4a12e>] insert_orphan_item+0x5e/0x90 [btrfs]
    [ 240.340482] [<ffffffffa0a4c531>] replay_one_buffer+0x361/0x380 [btrfs]
    [ 240.340504] [<ffffffffa0a2f244>] ? alloc_extent_buffer+0x34/0x370 [btrfs]
    [ 240.340523] [<ffffffffa0a488f3>] walk_down_log_tree+0x1d3/0x410 [btrfs]
    [ 240.340540] [<ffffffffa0a48bfb>] walk_log_tree+0xcb/0x1d0 [btrfs]
    [ 240.340558] [<ffffffffa0a507f7>] btrfs_recover_log_trees+0x1e7/0x490 [btrfs]
    [ 240.340575] [<ffffffffa0a4c1d0>] ? replay_one_dir_item+0xf0/0xf0 [btrfs]
    [ 240.340596] [<ffffffffa0a08b3e>] open_ctree+0x17ae/0x2030 [btrfs]
    [ 240.340609] [<ffffffffa09dd633>] btrfs_mount+0x843/0x920 [btrfs]
    [ 240.340618] [<ffffffff8117b7aa>] ? pcpu_alloc+0x35a/0x680
    [ 240.340628] [<ffffffff811d5d68>] mount_fs+0x38/0x1c0
    [ 240.340634] [<ffffffff8117bb05>] ? __alloc_percpu+0x15/0x20
    [ 240.340641] [<ffffffff811f116b>] vfs_kern_mount+0x6b/0x120
    [ 240.340647] [<ffffffff811f4184>] do_mount+0x224/0xb40
    [ 240.340653] [<ffffffff811f4dae>] SyS_mount+0x7e/0xe0
    [ 240.340661] [<ffffffff81562809>] system_call_fastpath+0x12/0x17
    [ 240.340671] INFO: task btrfs-transacti:561 blocked for more than 120 seconds.
    [ 240.342927] Not tainted 3.19.2-1-ARCH #1
    [ 240.345175] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
    [ 240.348473] btrfs-transacti D ffff88020b88bd98 0 561 2 0x00000000
    [ 240.348483] ffff88020b88bd98 ffff880211edc590 0000000000013f00 ffff88020b88bfd8
    [ 240.348491] 0000000000013f00 ffff8802162289f0 ffff880211edc590 ffff8802094a70c8
    [ 240.348496] ffff8802094d8000 ffff880200000000 ffff8802094d8000 ffff880200000033
    [ 240.348501] Call Trace:
    [ 240.348511] [<ffffffff811b5d1a>] ? kmem_cache_alloc+0x16a/0x180
    [ 240.348525] [<ffffffffa09e07ca>] ? btrfs_free_path+0x2a/0x40 [btrfs]
    [ 240.348543] [<ffffffffa0a64213>] ? __btrfs_run_delayed_items+0xf3/0x1d0 [btrfs]
    [ 240.348550] [<ffffffff8155e999>] schedule+0x29/0x70
    [ 240.348568] [<ffffffffa0a0b555>] btrfs_commit_transaction+0x2a5/0xbe0 [btrfs]
    [ 240.348573] [<ffffffff810b4380>] ? wait_woken+0x90/0x90
    [ 240.348590] [<ffffffffa0a06fc5>] transaction_kthread+0x1d5/0x240 [btrfs]
    [ 240.348605] [<ffffffffa0a06df0>] ? btrfs_cleanup_transaction+0x5a0/0x5a0 [btrfs]
    [ 240.348611] [<ffffffff81091748>] kthread+0xd8/0xf0
    [ 240.348617] [<ffffffff81091670>] ? kthread_create_on_node+0x1c0/0x1c0
    [ 240.348624] [<ffffffff81562758>] ret_from_fork+0x58/0x90
    [ 240.348629] [<ffffffff81091670>] ? kthread_create_on_node+0x1c0/0x1c0
    Last edited by ouroboros8 (2015-04-02 12:37:25)

  • PowerBook G4 won't boot past blue screen

    I've read a couple of posts with similar problems. The jist is, I did a security update/restart earlier and now my laptop won't boot past the blue screen after the white screen with the gray apple. I think I'm on Mac OS 10.4.11 but I had it on auto-update so that could be incorrect.
    I've booted from the install disk and run a diagnostic from the First Aid bit in the Disk Utility. It says that there are no errors found and the S.M.A.R.T. status says "verified" as well. It won't let me boot into Safe Mode (although, I could be doing that wrong as I'm not exactly clear on how to do it - pressing S doesn't seem to do anything, but if I press Command + S it takes me to a text listy thing and I've run the "fsck -f" system check (which seems like the same as the disk utility check?) from there and also gotten the "volume is ok" message. There was also a suggestion to run some kind of diagnostic after booting with the D key from the install disk, but I was never able to get the disk to boot from the D key, only the C key.
    I'm sure that this is kind of the "same song, different verse," kind of post, but I've not read about volumes registering as okay. I'm a little wary of a archive-and-reinstall as I've not ever done that before (so, if that's the suggestion you have, I would really appreciate loads of specifics on how that works so I don't mess up!)
    I've read in several instances suspicion of a hard drive problem but I've not had any slow downs or any crashing. I did travel to the UK for about 10 days, but I didn't even change the time zone on my laptop while there, so I don't think that's it (but I suppose it could be.)
    Lastly, I did recently replace my keyboard. A few keys had become non-responsive so I replaced it and have had the new keyboard for a bit over a month.
    Suggestions? Ideas? Sorry if it's a repeat post -- just felt like the circumstance was a teensy bit different. And also, thanks very much for any info you can give.

    Linsey:
    If you can boot your computer into Firewire Target Disk Mode and you have access to a second Mac that supports firewire, you may be able to back up items that have not been backed up previously.
    If you are able to back everything up successfully, and you have tested your backup to be sure it is sound, then we can proceed with re-installation of the OS. The best option is to completely reformat and erase the HDD and then install the OS from disk. (I will post complete step by step directions). This will enable you to start with a clean slate/HDD. Your other option would be to use the Archive and Install option. Think it over and let me know how you want to proceed.
    cornelius

  • Macbook won't boot past main apple screen

    I was using my computer this morning (13" black Macbook that I've had since December) and it was working fine until I closed it to go get something to eat.
    When I got back and opened the lid again, the screen was black, as if it was off, but I could make out the outline of the Apple logo in the centre. So I turned it off, gave it some time and turned it back on. Now it won't boot past the main Apple screen, where the little timer thing spins and spins and spins while apparently nothing else happens.
    I left it alone for a couple of hours, thinking maybe it was overheated, but that didn't make a difference. I tried taking the battery out and restarting it, but that didn't work either. I called Apple, but my parents opted for Future Shop's warranty instead of Applecare, so they told me to search the website as "the issue is well-documented," since I have no tech support with them.
    I've searched around to see where this is posted or if it's been answered a billion times before, but it's 35C in here, and my rage/frustration are ruining my ability to be rational, haha.
    Anyone experienced this before / is there a resolution that doesn't involve me being without my computer (which is like sweet, sweet crack to me) for an undisclosed amount of time?
    Thanks in advance,
    Emy
    Oh, and I'm not sure about the operating system version beyond that it's OSX and I regularly install whatever updates they tell me to.

    Maybe Disk Utility can repair the disk this way:
    -Search your installation DVD's.
    -Insert the disc 1 and sthut down your Mac
    -Start your Mac again while holding down the C key
    -Now your Mac should boot from the CD, this can take some time.
    -After a while you will see a installation screen where you can chose a language.
    -Chose English and continue.
    -Then click some time's next and agree with the "Software Agreement".
    -Open Disk Utility. Top menu bar --> Utilities --> Open Disk Utility.
    -Select your hard disk in the list of disks and volumes on the left side
    -Go to the First Aid (tab somewhere on the right).
    -Click the button to verify the permissions.
    -Then Click the button to repair the permissions.
    -Click the button to verify the disk.
    -Then Click the button to repair the disk.
    -Exit the Disk Utility

  • K9A2 Plat. board won't boot past NVRAM check

    Just updated my K9A2 board from 1.5 to 1.9 hoping to solve some USB issues that were intermittently occurring when I connect my BB or other USB device (it would cause my primary video card to black out, the card's fan would race, thus forcing a reboot; after which it would be just fine).
    However, after a successful flash from MSI Live 4 using windows, a CMOS reset, the system will not boot past NVRAM check with the RAID (10) SB600 controller being used. I have seen it pass NVRAM check when the SB600 controller is off. I've even reset the RAID 10 and nothing is happening to get the BIOS past the NVRAM check.
    I've also attempted to use the MSI USB flash utility 1.18 however it stalls out 3/4 of the way through on my other k9A2 system (DOS window disappears at the last stage, last DOS box window shown here: https://forum-en.msi.com/moderator/usbguide/guide4.jpg)
    My other K9A2 system is at 1.8 and doesn't have the USB detection problems but it has a Sb600 problem in running all 4 discs detected normally (#4 disc always reports in error even though its running fine, could never figure out why it is not detected and have replaced it 2x, rebuilt it other times as well and it changes the failed disc in the array around so I'm thinking its the controller firmware).
    With that being said, is there any way around this NVRAM check? The BIOS looks fine in the system and RAID is detected normally and can be built/deleted etc; just this NVRAM check stalls it out.
    Please advise.

    Have you done this?
    Quote from: Svet on 26-January-10, 00:00:40
    Do >>Clear CMOS Guide<< with power cord removed.
    Also we don't known anything about your system yet....:
    Quote from: Svet on 26-January-10, 00:00:40
    Also read >>Posting Guide<<

  • System won't boot-no chime.

    Despite repeated attempts and resetting the CUDA button, the system won't boot when start button is pressed. In the first few seconds it seems to make normal sounds; but no chime and settles into simply fan noise. This is true even if using C (with an Install CD). or Shift key. Is there anything else I can try? (I know it's actually a G3 B&W Motherboard; but I had nowhwere else to post it)

    I do not remember exactly what was happening when it stopped. It may have been executing something , hung up, and wouldn't respond to the Command-Opt-Esc or I do remember one incident when it was booting up and stopped when it was partly thru "searching for local discs.
    I checked the ref. article and tried to measure the voltages on the power connector. I was never quite sure what pin was what, since the colors did not jive with those in the article. At any rate 2 were approx. + 5 V (one was 4.85), the rest were essentially zero (I believe 1 or 2 were about 300 mv). I did notice that when the power connector is reconnected and start up is attempted, 3 little green lights come on on the motherboard. One goes off after a while.
    I have tried the old Sonnet upgrade and have tried reseating all the RAM modules. All to no avail.
    The Hard drive and all other parts seemed to be working fine prior to the failure.

  • G4 won't boot past grey apple screen

    Hi. I have been having the same issues with my G4 15". I'm frustrated. The whole thing started with stalling during applications. So I decided to reinstall my OS X 10.5. After reinstall, I copied my saved files from my "My Book" drive back to my hard drive. Stalling issues returned. I reinstalled again. still had some stalling issues, so I performed disk utilities. I repaired permissions. SMART status is verified. System still ran extremely slow. So, I followed directions on apple support for resetting the PRAM and NVRAM. After I did this, the computer won't boot past the grey apple screen. I have reset the PRAM and the NVRAM again. Still nothing. I rebooted up from OS install disk. I performed disk utilities repairing permissions and repairing HD. I did this for both my drive and the computers drive. I choose restart and again the grey apple screen. I have been trying to get this thing going for a week now. I'm near tears. Cornelius or anyone, can you help me? It says no errors are found, SMART is verified. But I can't get the computer to boot unless it is from the CD. Is the computer confused on where to boot from? Or is it shot? HELP ME PLEASE, before I play frisbee with my dear beloved mac!!!! It seems like this ALL started happening after I installed the update 10.5.8. I had ZERO problem prior to any software updates!!!

    There have been report of some external drives/enclosures that do not work as a boot device. Not sure if the MyBook is in that category or not, just make sure that there is nothing else plugged into the Powerbook then try again.
    Does the WD need its own power to be plugged into an AC power source? Try the other firewire port
    I have one more question for ya... You were able to load OSX on this EHD using the OSX install disk in the Powerbook? And the installer saw the EHD with no problems?
    If non of the above works try booting while holding down the x-key, this should force it to look for an OSX volume, not sure if it works the same on an EHD but worth a shot.

  • 10.4.11 Server won't boot past hfs mount

    Any ideas how to repair an OS X Server 10.4.11 system that won't boot past the gray Apple logo/spinning bars? Verbose mode stalls after the line "hfs mount: enabling extended security on <startup volume name>"
    The machine will boot from the OS X Server install DVD (10.4.7 Universal). Disk Utility permissions and repair indicate no problems with the startup volume.
    If I am unable to resolve the problem with the existing system, what is the best method for re-installing the server OS without having to manually re-construct the network configuration, accounts and permissions? I have a configuration settings file and a relatively recent Open Directory Archive disk image.

    I have been unable to find any way to get past the boot stall, so I re-installed OS X Server 10.4 and restored from my Open Directory archive. Had to recreate shares.
    Any tips on what plists or other System components should be cleaned out to try recovering from boot problems like this were there is nothing wrong with the disk and you can't boot into single user mode?

  • My iMac won't boot past grey screen and it didn't come with a os x disk

    My iMac won't boot past grey screen with apple. I've tried booting in safemode but that didn't help and my iMac didn't come with a os x disk.

    Take each of these steps that you haven't already tried. Stop when the problem is resolved.
    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.”
    b. 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.
    c. 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 either of the techniques in Steps 1b and 1c 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 you use a wireless keyboard, trackpad, or mouse, replace or recharge the batteries. The battery level shown in the Bluetooth menu item may not be accurate.
    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, or if a firmware password is set, or if the startup volume is a Fusion Drive or 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 10. 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
    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 10
    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 11
    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 12
    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.

  • G4 Power Mac won't boot past gray screen

    I have a mirror door g4 power pc that had been having some issues with not turning on, and after testing the power supply, it failed miserably. We placed a refurbished power supply in it from a company in New York and the computer was working wonderfully. I went on a cruise last week and went to turn the computer on for the first time in a week and a few days. The CPU turns on, the unit chimes, the fan turns on and the computer starts to boot up, but it won't boot past the gray apple logo screen.
    Actually, the first few attempts to boot it resulted in a blue screen with gaint apple logo and spinner; it wouldn't advance further. After several restarts and resets, I got it to come up into the normal gray screen. On several attempts it wouldn't boot further than this. On two occasions now though, it has moved past the gray screen to normal operation (it takes about an hour for it to get to that point though) but with some kind of errors. I get the side bar, but the gray panel on to with "file" ect is gone and my HD icon never comes up. The icons on the sidebar do not respond when clicked.
    The computer will not boot from the OS X disc.
    What's going on, hard drive? Virus? Something else?

    You likely have hard drive directory issues or worse.
    Virus is just a hopeful whimsy.
    No virus.
    I hope that you have a backup of your data.
    Try a Safe Mode boot. This forces system repair of the directory (if possible).
    Hold Shift while starting to enter Safe mode. Be patient, as it can take several minutes to complete.
    Failure to boot to the OS X disc is not good. A severely damaged drive can prevent boot while connected.
    Disconnect your boot drive and try booting to the OS X disc.

  • IMac G5 Power PC won't boot past the grey apple and pinwheel

    After everything froze and having to shut down (holding the power button), it won't boot past the grey apple and pinwheel. After a few seconds, the fans speed up and then nothing else.
    *it won't boot into safe mode (holding shift)
    *booting to OS on DVD works but then freezes after select language and hit "continue"
    *disk utility shows the actual hard drive name but no disk image/partition is listed for me to repair or change
    *running the system hardware diagnostic CD returns a list of "passed" for all hardware
    I did have the logic board replaced during the extended warranty period a few years back and have not had any issues at all since.
    Any thoughts, suggestions, tricks/tips?

    Perfect diagnosis. I replaced the HD and reinstalled the OS. Back in business! Thanks!

  • IPod Nano Won't Boot Past Apple Logo...

    Sup all?
    ...Got an interesting problem here. Replaced an LCD in a Nano for a friend, installation went smooth & without problems (or so I thought). After installation was complete, I put the Nano back together & started loadin' & playin music on the Nano. About 2 days later, I decided to update it w/the new iPod Updater (can't remember the date). Now the iPod Nano won't boot past the Apple Logo. I can tell that the "menu" has been loaded 'cuz you can hear the clickin' sound when you operate the wheel.
    I've tried reformatting the iPod Nano (quick & full) & then trying to restore it, but it won't boot past the logo (after successful restoration?). Now I'm going to run the battery dead & then try to restore it again.
    Any suggestions/comments on this?

    The solution I see in your case is to go back and download an older iPod Updater.
    See this link -> iPod Updaters
    I suggest taking either the January 2006 iPod Updater, or March 2006 iPod Updater.
    IMHO, Some of these freezing issues occur because of a fault in the latest iPod Updater.
    I suggest going back to March (or January), and the nano could possibly work again for you.
    -Kylene
    If any post helps or solves your issue, please mark it that way accordingly. Thank you for helping the boards!

  • HP8540w (540M) ram upgrade, won't boot past bios

    I have recently acquired new RAM. First it was 2 x 8 gb but I found out later this is not supported by my specific model.
    But now I switched it with 2 x 4gb PC12800 CL11, from a newer hp model and it still won't boot past the BIOS, which has been upgraded to the latest version. 
    The Bios recognizes the RAM perfectly but still it won't boot into windows. When I see the windows 8.1 logo it gives a sudden shutdown which is followed by a restart. In theory the pc12800 should work, albeit clocked down to 10600 to match the motherboard & processor.
    It feels inadequate to have a 3 year old laptop which is not able to go past the 4gb, especially because I bought it since it was the elitebook version and military graded. I wanted to have something future proof, not a machine that needs to be replaced after 3 years. It feels like just threw 150 dollars out of the window.
    So I'm hoping that there's another solution that I might have overlooked.
    This question was solved.
    View Solution.

    Well the recommended memory is PC3-10600 aka DDR3-1333. On some models it actually downclocks to DDR3-1066 speed. I think the memory you have installed from a newer model is just not compatible. If it is DDR3-1600 it might even be low voltage memory which is almost certain not to work. 

  • System won't boot. INIT: No inittab file found Enter runlevel:

    After the latest update that changed how intel ucode is updated, my system won't boot.
    I think I missed a line when I edited "/etc/grub.d/10_linux" and ran grub-mkconfig -o /boot/grub/grub.cfg.
    Any ideas on how to fix this?
    I can't run grub-mkconfig from another machine, as it uses the live kernel info.
    Any help would be greatly appreciated. Otherwise I'll have to reinstall

    TheSaint wrote:
    SyXbiT wrote:
    But I still get the error:
    system won't boot. INIT: No inittab file found
    Enter runlevel:
    It seems to me that you've an old Arch version. inittab is deprecated AFAIK.
    What is the Arch iso version?
    That would probably be mid-2012 at the very latest I think as that's when I remember completely moving over to systemd...
    @SyXbiT: Are you using the current Arch install ISO?

Maybe you are looking for