Maybe the system just went corrupt, or something similar.
Have you tried inserting your installer disc, and booting up while holding down the C key (or is it the C and D keys?)? That should force it to boot up from the disc. From there you should be able to open Disk Utility from one of the top menus and run some repairs, or at least be able to recover the data from your HD.
Do you have a friend with a Mac laptop? Get them to come over and mount your machine using “FireWire target mode.” You will most likely be able to recover all of your documents that way.
Once you have your documents back, you can go ahead and try standard recovery techniques (Disk Warrior, re-install, etc.)
invalid sibling link
underlying task reported failure on exit
Any words of wisdom?
ETA: No friends that can come over tonight- it’s good idea for next week to begin recovery.
We have four computers in this house but only ONE hooked up to the printer. The MAC.
Arrgh. So after we redo the data we have to get it hooked up to the printer.
All you need to do is boot up from your installation disc, and begin a new install. At some point during the beginning of the process, it’ll give you a few options (such as, Clean Install). Make sure you select “Archive and Install”. What this will do, is archive your old system, and move over all your prefs, bookmarks, email accounts, apps, documents folder and such, and put it into a fresh, new system folder.
When you buy a new Mac, and turn it on for the first time, it asks you if there’s an older computer you want to move the data from. If you say yes, you hook up a firewire cable, and it works its magic.
That said, find a mac tech, they will probably be able to pull your drives and offload them in a jiffy. Might set you pack a couple hundred they might be able to fix your existing machine so you don’t need to do any kind of trick recovery work.
Yeah, that will probably be the plan. Right now the utility disk is in the drive but we get an error when it tries to fix anything. I can’t seem to bypass it or get it to eject.
That being said, as an owner of 2 PC laptops and my Mac, I still love my Mac best. I just want it to get better!
Nurse Carmen- I tried your trick, but I can’t get it to not reboot off the utility disk, which doesn’t work, so I’m kinda in a loop.
Ejecting a disk at startup; when you hear the startup chime, hold down the mouse button until the disc ejects
It sounds to me like a corrupted system on the hard drive, as reccomended above, boot off your original install disc (or the current install disc if you’ve updated to a newer Mac OS) by holding down the letter “C” at boot, if this does not work, reboot the machine, and hold down the “Option” key to get to the boot manager, click on the icon for the installer disc then click the arrow to proceed booring off this disc
when you arrive at the installer screen, select the main language, and on the next screen, click the “Options” button in the lower left of the window, select the "Archive and Install option, and the “save original items” option, then proceed with the reinstall
if you want to save some space on the hard drive, on the next screen, click the “custom install” button, and de-select the language packages and extra fonts, that prevents the installer from installing the international language packs, click the triangle next to “Printer Drivers” and de-select the printer manufacturers you don’t use
then proceed with the reinstall, good luck, it should work fine
MacTech, I respect your opinion because I know you are a mac geek. But I still think an fsck is the best option here, only because I’ve seen it work several times. If he ejects the disk and boots into single user, he will boot directly into the kernal, and I have found that with THIS particular issue (gray screen reaches the darker gray apple, then goes no further) the fsck then a reboot works incredibly well. In fact, when I first got here, a satellite office of the IT department here at the U was running a craptacular Webstar server on a G4 running 10.4, and this exact issue was happening over and over, and all we did was boot to single user, fsck it, and reboot. Worked like a charm every single time.
Eventually, once he gets past the mitzvah, he can fix it right, but for now, he just wants to get up and running. And I think for that, skip the CD and go to the kernal. If that doesn’t work, then use the CD. (well, if you want to be specific, DVD)