Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Hardware - Troubleshooting and Discussion > Mac Notebooks > What causes a blinking *?* folder on startup?

What causes a blinking *?* folder on startup?
Thread Tools
Fresh-Faced Recruit
Join Date: Feb 2003
Status: Offline
Reply With Quote
Apr 14, 2003, 12:33 AM
 
I had this happen on my TiGigaBook tonight running 10.2.3. Freaked me out. I couldn't boot at all into my HD, so I tried holding down "Option"--didn't work, then "X"--didn't work, so then I rebooted holding down my "C" key with my OS X disk and ran disk utility from it. It found three or four problems which were immediately repaired when I chose the repair option, then I rebooted and it was fine. I didn't write down what the errors were, so I can't say what they were. I should've--might've helped diagnose later.

Nothing was out of the ordinary at all before I shut the computer down. I haven't even installed anything new for a couple weeks. I just shut it off because I wasn't planning on using it for a couple days. I properly shut it down (Apple menu-->Shut down...), and nothing was weird at all, but then I needed it back on, so I turned it on and got the blinking question mark folder. That means it's searching for a boot disk, right?

Once I got back up and running (nothing was lost, thank goodness), I did a search on these forums for this issue, and found a lot of people who've had it happen to them, but not many explanations as to why. Anyone know causes?

Thanks!

-sae
"Oh, I get it...It's very clever. How's that working out for you...being clever?"
     
Mac Elite
Join Date: May 2002
Location: SoCal
Status: Offline
Reply With Quote
Apr 14, 2003, 12:46 AM
 
Yeah. Alzheimer's. OS X is what, 2, 3 years old? That's ancient in computer life.

But seriously. Your boot directory or whateveritscalled was probably corrupt. Or it just freaked out. Which in turn freaked you out, which didn't really help the situation. But alas, you did the right thing. You are a good man. Go have a cookie and milk and you sleep well, you hear?
I, ASIMO.
     
Addicted to MacNN
Join Date: Sep 2001
Location: Toronto
Status: Offline
Reply With Quote
Apr 14, 2003, 02:50 AM
 
You did the right thing but it should not have happened in the first place.

I'd go and buy a copy of Disc Warrior, the finest disk utility on the market IMO. Run it once a month and it should keep your disk as healthy as it possibly could be.

Also, this illustrates once more the importance of frequent backups.
     
Dedicated MacNNer
Join Date: Nov 2002
Location: Hobart, Tasmania, Australia
Status: Offline
Reply With Quote
Apr 14, 2003, 03:58 AM
 
the blinking question mark folder is OpenFirmware trying to locate a bootable device. I know quite a few iMacs running OS9 (bleh) at a college i do work for every now and then drop the system folder, you need to do the magic rebless trick and it's all good again, but that's os9 for ya.
1Ghz Powerbook
40gb/1x512mb/combo/T68i
FireRAID 1 Host Independant Hotswap RAID 1 (80gb)
     
Forum Regular
Join Date: Sep 2002
Status: Offline
Reply With Quote
Apr 14, 2003, 11:44 PM
 
The blinking question mark is the Mac saying either "can't find the drive" or "can't get located correctly on a clearly-interpretable piece of your hard drive directory"

In my case, this happened because of what was probably a mechanical failure of the hard drive itself. Disk Warrior could not find my hard drive. Drive10 sort of found my hard drive, but after running it through 3 repair cycles for problems with the main node, the computer was still unbootable and unreadable, even in target mode from another mac, and my computer is now at Apple to get looked at.

Anyway, I agree that DiskWarrior is a good program to use, but it wont fix a mechanically problematic drive.
     
Dedicated MacNNer
Join Date: Jan 2001
Location: NYC
Status: Offline
Reply With Quote
Apr 15, 2003, 07:54 AM
 
Your BootX file could have been crunked up. When I got my 12", the first thing I did was throw on a new theme. The theme modified the BootX... problem was the 12" shipped with a newer build of the OS, so when I restarted, I got the blinky folder. After another time of reinstalling it, (with a theme), and getting the blinky folder again, I was all set to send it back to Apple (they were also convinced it was hardware...)

Then I remembered that whole BootX file. So I reinstalled, and installed a theme without it's BootX resource, and all is good. Voila! I let Apple know, and they actually said it is kinda silly that the modification of one file requires a whole new reinstall (since that file is invisible, it's not easy for the average user, or even above-average user, to go in and replace it...)
*justin

Isn't logic swell? It gives answers without really answering anything!
     
   
Thread Tools
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Top
Privacy Policy
All times are GMT -5. The time now is 06:57 AM.
All contents of these forums © 1995-2011 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.7 © 2000-2011, Jelsoft Enterprises Ltd., Content Relevant URLs by vBSEO 3.3.2