IMac G3 won't boot after updating the firmware and upgrading the OS!

Hi! Everyone,
I have an iMac G3 333MHz (five flavors) which comes with 192MB of RAM and 6GB of hard drive. Originally, it was OS 8.5.1 installed, later upgraded to OS 9.2.2. Of course, the firmware has been updated by the appropriate method provided by the on-screen instructions before the installation of 9.2.2. After successfully updating the firmware and installing Mac OS 9.2.2, the system booted up and worked fine. However, after shutting it down and powering it up a few days later, I have encountered a critical problem:
1. At first, the iMac would chime and displayed a smiley-mac finder face.
2. No question mark appeared and the system halted because it stayed at the same screen for about 5 minutes! Also, the keyboard wouldn't respond. For instance, the LED signal light wouldn't light on when Caps Lock was pressed.
3. I assumed that this is just a typical crash and rebooted the machine via the "reset" button on the right side of the machine.
4. After restarting, well, no luck, the same condition. Therefore, I rebooted it again by using the method mentioned above.
5. The condition of sticking at the smiley-mac finder face occurred again! However, this time the iMac wouldn't chime and just displayed the mac face.
6. Another restart, well, it was getting worse... no chime and no smiley-mac finder face but a white screen.
7. I was frustrated then and shut the machine down forcefully by rebooting it again and pressing on the power bottom quickly before the screen appears. Also, I unplugged the power cord.
---------- After a few hours later ----------
8. Okay, I then plugged the power cord in and booted it up again, this time, it would chime but stuck at the white screen. => No smiley-mac finder face appeared!
9. Rebooted it again, the result was as same as step 8.
10. Another restart, the smiley-mac face finally appeared but still... stuck here and this time, no chime.
11. I then shut the machine forcefully by using the method mentioned above and let the machine rest for about a day with the power cord unplugged.
---------- After resting for a day ----------
12. I booted it up and it would chime, but no screen (the power button was orange, not green). I then forcefully shut down the machine.
13. Waited for about a minute and powered it up. This time, I tried to clear the PRAM, but no chime and gave me a white screen. => No luck! As mentioned, the keyboard's LED signal light wouldn't light on even though the Caps Lock key has been pressed.
*Note: The keyboard has been tested on the other computers and it worked. Also, I tried different USB ports to plug the keyboard in. => The USB ports were all in working condition, as I can know from the last successful start up.
14. Forcefully shut the machine down and tried to enter the Open firmware, no luck. It didn't enter and gave my a white screen.
15. Conclusion:
1) After resting for a while, the iMac would chime.
2) Rebooting too much times would cause the machine not to chime and leaded the screen to become white instead of the smiley-mac finder face.
3) However, rebooted the machine when the screen became white, the smiley-mac finder face would appear again without chime.
By the way, I could hear the hard disk spinning up so that means the hard disk is working.
Can anyone help me solve this problem? Is it related to the firmware update? Any suggestions will be appreciated! Thanks!
Andy

OK, I will try replacing the PRAM battery. Also, the PowerMac G3 and the other iMac 233MHz had the dead batteries. They are still working though... Should I replace them along with the iMac 333MHz? In case of not replacing, will they malfunction in future times? There are some symptoms on this two machines: 1. iMac 233MHz - No chime and no sound when adjusting system volume (the bi sound is not available), but iTunes and other applications can still use the audio device and output the sound via internal speakers; 2. PowerMac G3 450MHz - Will chime but sometimes hard to boot: 1) Chime but no screen; 2) No respond after pressing the power button => the power signal light won't light on. Every time I experienced this, I would open its case, pressing a small button (not quite understand what it does... anyway, just works if system halted.) near the PRAM battery and wait for about a minute, then close the case, and it boots. However, I have to reset "Date & Time"...

Similar Messages

  • Mac won't boot after updating to OSX 10.6.4

    I am on my 3rd Mac that won't boot after updating to OSX 10.6.4. One MacBook Pro and two iMacs. I fixed one but the last two are getting the better of me. HD is not fried. Have tried every keyboard shortcut on startup, Disk Warrior via. Target Disk, repairing permissions in single user mode. The machines will not boot off of a CD or DVD and it will not boot up in safe mode. Something in the startup files is preventing startup. I am suspecting Sophos antivirus. I tried to uninstall it and trash it but I think it's still blocking something. Any help would be appreciated.

    Got it! Not sure if removing Sophos had anything to do with it but here's what I did.
    1) boot dead machine in Target Disk Mode (iMac)
    2) boot good machine off Snow Leopard disk (MacBook)
    3) install OS to dead machine- I found this next part very curious. When the install was complete the MacBook restarted as the iMac.
    4) ran software updates
    5) shut down MacBook then shut down iMac
    6) rebooted iMac- all was good
    I actually did this twice because a co-worker had the exact same problem on her MacBook Pro. Got both fixed today.
    Thanks everyone for your help!

  • X99 Sli Plus Blue bios won't boot after update.

    Hello i tried to update the "blue bios" to the most recent Bios version.Following all the appropriate steps i updated the BioS and got the appropriate message (something like that,i can't remember the exact message) "Update was succesful your system now will reboot".After the reboot blue bios just won't boot.I cleared CMOS,i used the Multi BIOS switch (manual page en-30) to flash the blue bios trying all the versions from 1.7 down to 1.3  but nothing seems to work.The green BioS work fine on the default v1.3.My question is what should i do to make the blue bios work again?
    CPU: Intel - 5820k
    GPU: Radeon Sapphire R9 270x
    Ram: Crucial Ballistix Sport 8GB Kit (4GBx2) DDR4 2400 MT/s (PC4-19200) CL16 SR x8 Unbuffered DIMM 288-Pin Memory BLS2K4G4D240FSA

    I can't see anything about you preparing the stick as instructed.
    Quote from: flobelix on 22-February-15, 01:47:26
    A.) Download >>this<< bios archive and place it on your desktop. Do not decompress.
    B.) Download and install the >>MSI HQ Forum USB flasher<< .
    C.) Insert your FAT32 formatted usb stick.
    D.) Make sure that all win 8 options are disabled. (Fast Boot etc) Also make sure the legacy USB is enabled.
    E.) Start the forum flash tool and select option 1. Then point the tool at the compressed archive we downloaded earlier. Then to your USB Flash Drive.
    F.) Boot to the USB from working bios B.
    G.) Once it booted successfully switch to bios A without powering down or rebooting
    H.) Now follow the directions and let the tool flash bios A with version 1.7

  • Mac Mini won't boot after update

    I have a Mac Mini that won't boot after the most recent software update. Since the Mini has only a bluetooth keyboard and mouse, a number of the usual options (hold down shift, etc.) won't work. I've tried a reset, also no luck. At the moment, I can't locate my Tiger install CD either.
    When holding the power button on during boot, I get a series of flashes from the status light on the front (a set of very rapid flashes, followed by a slower set, followed by a slow set) but no startup chime, or fan, or video. My display and power source are both known-good (work fine with my Powerbook)
    Any suggestions, other than buying a hardwired keyboard/mouse?

    Welcome to Apple Discussions!
    The 'newer version of OS X" error occurs because the installer on the DVD you have booted to has by default been set to update the version of MacOS on the hard drive, which of course it can't do because the version of MacOS it is installing is newer. The only way to install in this situation is to select a different option. However, that isn't what you want to do at this point, because as it says, you'll loose your data if you do an 'erase and install'.
    Instead, you should see menus at the top of the screen when it's booted to that install disk. Click the Utilities menu, select Disk Utility, and then click the top entry for the internal hard drive on the left. Once done, click on the 'Repair Disk' button (not Repair Permissions). This will test the drive to make sure it's OK. If it reports errors, and then reports 'error or exit' with the drive not repaired, you will either need a 3rd party application such as Alsoft's Disk Warrior, or to perform an erase and install (which of course you don't want to do at this point because your data is not backed up).
    If the Repair Disk process completes with no errors, next select Repair Permissions, and let that process complete, then reboot the system as normal to see if you can now access the drive.

  • IMac won't boot after replacing hard drive and restoring from Time Machine

    I was having problems with my iMac but upgraded to Lion when it came out. Had a few good days and then my hard drive died.
    I had the drive replaced and the repair people put Snow Leopard on the new drive.
    I then tried to restore everything from my Time Machine backup. At first when I tried to log on the computer wouldn't accept my password (i know it was right).
    I decided to reinstall again using the snow leopard dvd i had. This time, the computer booted up (didn't ask me for a passord) and looked like it was in the process of setting things up. But Mail kept saying it was going to import messages but then quit and restarted a few seconds later. When i quit it it just came back again and again. I could see Chrome open behind it with my bookmarks in the toolbar and see other restored things, but the overall look was grey and not everything was there.
    When i restarted from the HD and not the dvd i could never get past various shades of grey and the circling progress indicator. Never booted up at all.
    I read about Lion having some restore hd functionality but it doesn't show up when i restart with option key. Am I in limbo between operating systems?
    Any advice as to steps to take? I don't know much about this stuff.
    Thanks for any help.

    Yes, if you picked a Snow Leopard backup, that's what you got. 
    You could pick a Lion backup, and it would restore it, but that wouldn't create the Recovery HD, which you will need, sooner or later.  See Using the Recovery HD.  You'll need to re-download Lion for that to be created.
    When you do that, after downloading but before installing Lion again, you might want to do this: Making a Lion Install disc or partition.  Then if you need to reinstall Lion again, you can do it from that, instead of having to download it again.

  • Imac won't boot after update

    hi guys i am new to macs I bought this for my daughter and tried to update.The update said to hold the program button and push power,well now she won't boot up just a grey sreen and what looks like a file with a blinking question mark and a face..
    I have a imac g3 400mhz with 256mb ram
    osx and 9.2 i belive any help appreciated

    The flashing folder icon is your iMac's way of saying, "where is my OS? I can't find an OS!" If this appears briefly and goes away, it's usually because the PRAM was reset recently. The 4.1.9 firmware does reset your PRAM in the process--but only if successful in its task. To fix this temporary hiccup, open the Startup Disk control panel and select the hard drive, then click Restart.
    If this icon continues to flash, there are some steps you can try.
    1. Reset the PRAM via Command (Apple)Option+PR at startup. Hold the keys down until the Mac chimes thrice. If your Mac starts normally after the third chime, end here.
    2. Reinitialize the firmware. Enter Open Firmware mode (CommandOption+OF) and issue the following, pressing Return after each command:
    reset-nvram
    set-defaults
    reset-all
    If successful, the Mac should reboot itself. Stop here if this solves the problem.
    3. If you have the iMac restore disc, or a disc with OS 9.1-9.2.1, boot it and run Disk First Aid from the Utilities folder to repair file structure errors. If you have DiskWarrior or TechTool Pro Classic, you will be able to do more thorough repairs.
    4. If all of the above fail, you can reinstall OS 9 if you still need to do the firmware upgrades, but you should reinitialize the hard drive with Drive Setup if you also want a clean install. Drive Setup can be found in the CD's Utilities folder.
    Nate

  • 17" iMac (Tiger) won't boot after latest software update

    I downloaded the latest Tiger software update on my 17" Intel Core Duo iMac a couple of days ago and after I hit Restart I can't get past the grey Apple loading screen.
    I've tried everything it tells me in the manual, pressing various combinations of keys as I turn the computer on, but to no avail. I also put Install Disk 1 in and tried to check hardware from that (pressing D) and tried pressing C too to boot from it, but nothing happens, just the grey apple loading screen. Of course, now the install disk is stuck in there too.
    Any clues as to how I can sort this out? I'm still under AppleCare, so if worst comes to worst I'll call UK support and see what they can do, but thought I'd try everything I could at home first.
    TIA.

    Hello,
    Try the Apple Hardware Test: http://support.apple.com/kb/HT1509
    Carolyn

  • IMac won't boot after updates,have to reinstall loin from recovery drive

    I have a 27" iMac running 10.7.1 and love it, but every time I do a software update it won't boot, it just goes to white screen with spinning gear forever! I let it set there for an hour and it never changed. I've tried restarting it but it just stops at that point,so I have to restart holding cmd-r to go to the recovery partition and have it reinstall loin,i've tried reparing the drive and perrmissions but it still wont boot unless i reinstall loin. I have five other macs running loin with no problem, so why just my imac?

    Hopefully you have AppleCare. If so, call Apple to see if this if you are afflicted with the dreaded motherboard problem.
    BTW, this area is for discussing iMac G4s. Since you have an iMac G5 you will probably want to make future posts in the iMac G5 discussion area.

  • IMac G4 won't boot after install of iTunes latest update

    I just updated my iTunes software via download. I have the iMac configured to ID when new updates are available. After download I selected the "restart" option. Computer shut off and upon power up will not proceed past blue start up screen with the progress bar and "starting MAC OSX...." text. I have tried power down/power up. It has been at least an hour and still on blue screen. I have never had a problem in 5 years. Any ideas?

    Hi Dean, and a warm welcome to the forums!
    Unbeknownst to you, you had problems on your HD before the update.
    Could be many things, we should start with this...
    "Try Disk Utility
    1. Insert the Mac OS X Install disc that came with your computer, then restart the computer while holding the C key.
    2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, you must select your language first.)
    Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.
    3. Click the First Aid tab.
    4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
    5. Select your Mac OS X volume.
    6. Click Repair. Disk Utility checks and repairs the disk."
    http://docs.info.apple.com/article.html?artnum=106214
    Then Safe Boot from the HD, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot.
    The usual reason why updates fail or mess things up, is if Permissions are not fixed before & after every update, with a reboot... you may get a partial update when the installer finds it doesn't have Permissions to change one obscure little part of the OS, leaving you with a mix of OS versions.
    Some people get away without Repairing Permissions for years, some for only days.
    If Permissions are wrong before applying an update, you could get mixed OS versions, if Directory is the slightest messed up, who knows!
    If many Permission are repaired, or any Directory errors are found, you may need to re-apply some the latest/biggest updates again, or even do an A&I if you have enough free disk space.
    An Archive & Install, which gives you a new OS, but can preserve all your files, pics, music, settings, etc...
    http://docs.info.apple.com/article.html?artnum=107120

  • Macbook pro won't boot after updating to 10.9.3

    I ran the update to 10.9.3 yesterday.  After reboot the Mail program gave me an error that it might not be compatible with the OS.  I restarted, now I get the a progress bar.  It goes for about 30 seconds then powers the macbook down.
    Here's what I've tried.
    1. Booting into recovery mode (both Internet recovery and regular recovery)
    2. I cant repair permissions or repair the disk.  It says that it needs to be reloaded, etc
    3. I tried a reinstall.  I'm getting a disk locked error on the Macintosh HD and recovery HD.
    4. Can't boot into safe boot.  I get a driver error and Mac OS Version: not set yet.
    5. I tried Turning off Encryption.  It won't turn off.
    6. When I choose the startup disk to boot to, it still shows 10.9.2, even though the app store showed that 10.9.3 was installed.
    Pretty much combed the forums, but I'm not really sure what to do at this point.  The machine is out of warranty and I don't have another Mac to do any cloning, usb startup disks, etc.  I made an appointment with the genius bar tomorrow but I wanted to see if there's something else I can try!  Any help would be greatly appreciated!
    Thanks.
    Dan

    Do you have a Time Machine backup? If so, erase the disk and reinstall OS X. HOWEVER, DO NOT CONTINUE UNLESS YOU HAVE A TIME MACHINE BACKUP!!! IF YOU DO NOT HAVE A BACKUP AND STILL DECIDE TO CONTINUE, BE AWARE THAT ALL YOUR DATA WILL BE LOST FOREVER!!!
    Erase and Reinstall OS X
    Note: This will delete all data on the disk. Back up important files before continuing.
    Erasing and then reinstalling OS X can give you a fresh start, making your computer exactly as it was whenever you received it from Apple. This can solve various problems such as corrupt system files.
    Shut down the computer by going to Apple () > Shut Down…
    Select Shut Down or allow the computer to shut down automatically.
    Plug in the MagSafe power adapter into a power source and then connect it to your Mac if you have not already done so.
    Press the Power Button to turn on the computer.
    Press and hold both the R and Command (⌘) keys on the keyboard until the Recovery partition loads. If this does not work, shut down the computer, press the Power Button to turn on the computer, and then hold in the Alt (⌥) button immediately after you press the power button. Then, select the Recovery HD partition to boot up in the Recovery HD partition.
    Select Disk Utility and then choose Continue.
    Select your startup disk (Macintosh HD by default) from the left.
    Select the Erase tab.
    Choose the Format pop-up menu and choose Mac OS Extended (Journaled), enter a name for your disk, and then click Erase.
    After the disk is erased, choose Disk Utility > Quit Disk Utility.
    Select Reinstall OS X and then choose Continue.
    Follow the instructions.
    I hope I helped.
    Austin

  • IMac, 2010, will not boot after update

    After downloading Yosemite, my 2010, 27" iMac will not reboot. It appeared to install ok but it stayed white screen, no text for more than an hour after it automatically rebooted. Idaes? 

    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.

  • MacBook won't boot after updates

    My girlfriend has a black 13" MacBook and we ran updates on it today and after it had installed all the updates and it went to reboot it now won't boot up. It turns on and you see the apple logo but then it comes up with a window saying that it needs to be restarted and in the background there is a few lines of "code." I am a PC user so I am doing my best to help her resolve this problem. I do love my iPhone and iTunes so don't hate me too much haha. I did some research on here and read how to boot up in safe mode and I tried to do this but it didn't work. Any help would be greatly appreciated.

    She bought the computer used so unfortunately she does not have the start up disk. She also has not backed up the information on the computer but we are more concerned about getting the computer to work because she cannot afford to buy a new one and she has barely had this one more than a year. The only thing that is connected to the computer is the power cord and the battery is shot so we cannot disconnect the power cord and use the computer. Well I read the instructions on starting up in safe mode so I hold the power button until I hear the obnoxious beep and then hold the shift key down until u see the little gear thing and apple logo. Well I get the apple logo but no gear and then I get the pop up window that I spoke of before telling
    Me to restart and there is the lines of "code" in the back ground.

  • System won't boot after update

    After installing the latest system update (from Leopard 10.5.1 to 10.5.2) on my Dual Processor PowerMac G5, I was able to restart then within 2 minutes a freeze. I couldn't force quit...had to power done.
    Upon powering on, my screen hangs on the gray screen for about a minute (with the clockwise powering up status symbol), then it shuts down on its own. It won't boot into safe mode. In single user mode, it tells me there is a "disk0s2: I/O error" ... Is my hard drive dead? I've tried resetting the PRAM, resetting the PMU button, unplugging all 3rd party devices, but to no avail.
    I'm hopeful I can recover files somehow. Where should I proceed? I'm not sure exactly how the internal drives work. Can I, for instance, unplug and remove the top internal drive and place the 2nd internal drive where the top one was and see if i can boot from that drive?? Thereby determining which drive has the issue? Any advice is appreciated.
    Thanks so much!
    Sean

    Can you boot off the leopard DVD and run the disk utility disk verification on the drive? If it's a hardware problem then there's probably not much you can do. If you have a TM backup of your system then you should be ok, since you can replace the drive and then restore your system to it from the TM backup.

  • RD230 - Won't boot after BIOS - Server beeps and the screen is blank.

    Hi there,
    I have a problem with one of our RD230.
    The Server seems to be ok. No Errors in BIOS. SATA Raid configured and so on...
    But the server simply won't boot from CD or USB Drive or HDD.
    After the whole BIOS Process the server gives a permanent beep and the Digitron shows code 00. The Screen just shows a blinking cursor top left.
    Nothing happens.
    Removing the RAID, CD Drive, Network Card doesn't help.
    Does anyone have an Idea whats going on with this server?
    Also setting the J45 Jumper doesn't help.
    Thanks in Advance,
    Cheers,
    Chris

    2 Things that can typically fix this issue. Please reseat the memory and if that does not fix it, please reseat the processor.
    Questions
    1 - Has this system worked prior to this or is this an out-of-box failure?
    2 - If it has worked in the past, what changes were made just prior to this issue? (ie Windows Update, BIOS Update, firmware update, driver(s) update, etc.)

  • Software raid won't boot after updating to "mdadm" in mkinitcpio.conf

    After a power outage I've discovetred the config I was using (with raid in mkinitcpio.conf) no longer works, it's mdadm now - that's fine.  I've updated that and re-run mkinitcpio successfully, however my system is unable to boot from the root filesystem /dev/md2 like so:
    Waiting for 10 seconds for device /dev/md2 ...
    Root device '/dev/md2' doesn't exist. Attempting to create it.
    ERROR: Unable to determine major/minor number of root device '/dev/md2'.
    You are being dropped to a recovery shell
        Type 'exit' to try and continue booting
    /bin/sh: can't access tty; job control turned off
    [ramfs /]#
    As far as I can see from reading various threads and http://wiki.archlinux.org/index.php/Ins … AID_or_LVM I'm doing the right things now (although I'm not using lvm at all, which makes the installation document a little confusing).
    I think I've included all the appropriate bits of config here that should be working.  I assume I've missed something fundamental - any ideas?
    menu.lst:
    # (0) Arch Linux
    title  Arch Linux  [/boot/vmlinuz26]
    root   (hd0,0)
    kernel /vmlinuz26 root=/dev/md2 ro
    initrd /kernel26.img
    mkinitcpio.conf:
    HOOKS="base udev autodetect pata scsi mdadm sata filesystems"
    fstab:
    /dev/md1 /boot ext3 defaults 0 1
    /dev/md2 / ext3 defaults 0 1
    mdadm.conf
    ARRAY /dev/md1 level=raid1 num-devices=2 metadata=0.90 UUID=7ae70fa6:9f54ba0a:21
    47a9fe:d45dbc0c
    ARRAY /dev/md2 level=raid1 num-devices=2 metadata=0.90 UUID=20560268:8a089af7:e6
    043406:dbdabe38
    Thanks!

    Hi magec, that's quite helfpul - I've certainly got further.
    Before I was doing this to set up the chroot (which is what is suggested in the wiki article about setting up software raid):
    mdadm -A /dev/md1 /dev/sda1 /dev/sdb1
    mdadm -A /dev/md2 /dev/sda2 /dev/sdb2
    mount /dev/md2 /mnt
    mount /dev/md1 /mnt/boot
    mount -o bind /dev /mnt/dev
    mount -t proc none /mnt/proc
    chroot /mnt /bin/bash
    But based on your suggestion it's working better
    mdadm -A /dev/md1 /dev/sda1 /dev/sdb1
    mdadm -A /dev/md2 /dev/sda2 /dev/sdb2
    mount /dev/md2 /mnt
    mount /dev/md1 /mnt/boot
    mount -t proc none /mnt/proc
    mount -t sysfs none /mnt/sys
    mount -n -t ramfs none /mnt/dev
    cp -Rp /dev/* /mnt/dev
    chroot /mnt /bin/bash
    The boot is now getting further, but now I'm getting:
    md: md2 stopped.
    md: bind<sdb2>
    md: bind<sda2>
    raid1: raid set md2 active with 2 out of 2 mirrors
    md2: detected capacity change from 0 to 32218349568
    mdadm: /dev/md2 has been started with 2 drives.
    md2: Waiting 10 seconds for device /dev/md2 ...
    unknown partition table
    mount: mounting /dev/md2 on /new_root failed: No such device
    ERROR: Failed to mount the real root device.
    Bailing out, you are on your own. Good luck.
    /bin/sh: can't access tty; job contol turned off
    [ramfs /]#
    The bit that really confuses me is this:
    [ramfs /]# cat /proc/mdstat
    Personalities : [raid1]
    md2 : active raid1 sda2[0] sdb2[1]
    31463232 blocks [2/2] [UU]
    md1 : active raid1 sda1[0] sdb1[1]
    208704 blocks [2/2] [UU]
    unused devices: <none>
    [ramfs /]# mount /dev/md2 /new_root
    mount: mounting /dev/md2 on /new_root failed: No such file or directory
    [ramfs /]# ls /dev/md2
    /dev/md2
    [ramfs /]#
    So the array is up, the device node is there but it can't be mounted?  Very strange.
    Last edited by chas (2010-05-02 11:24:09)

Maybe you are looking for

  • I bought a new mac with software installed and my username will not update from another account?

    I recently bought an new power mac with Logic Pro and Final Cut Pro Installed. When I updated to the new OS X operating system, they need to be updated as well. And will no longer work. But it says it is on another account. Not sure what account. How

  • I can't click on my Creative cloud icon

    I can't click on my Creative cloud icon, my cursor changes to spinning wheel when I hover it. Tried re installing, now getting an error 600, FRUSTRATING!

  • Can't transcode DVDs

    Hi all - This is a fresh install, using self-compiled kernel 2.6.12. I'm trying to rip a dvd I've ripped and transcoded successfully when I previously had arch installed. Since coming back to arch sometime later, I'm having all sorts of trouble - Usi

  • Migration from Distribution Point within an SCCM2012 SP1 environment

    Hi all, in an exisiting SCCM2012 SP1 CU2 environment (one CAS, four Primary sites and some DPs) we have the following problem: The schedule HW for the DPs are not available and we are planing to use another HW Model for a timeframe the correct model

  • Clarification Regarding swings

    Can you suggest me why this exception is coming in Swings?? java.lang.ArrayIndexOutOfBoundsException: 1 at javax.swing.text.BoxView.layoutMajorAxis(Unknown Source) at javax.swing.text.BoxView.setSpanOnAxis(Unknown Source) at javax.swing.text.BoxView.