 |
 |
slooooow booting
|
 |
|
 |
|
Forum Regular
Join Date: Jul 2002
Location: boston
Status:
Offline
|
|
I recently erased my "previous systems folder" and ever since boot up has taken like three times longer.  What happened and how can i fix it. Im running a dual 1ghz mirror with 768 megs of ram.
Any help would be fantabulous
Trev
|
|
|
| |
|
|
|
 |
|
 |
|
Dedicated MacNNer
Join Date: Dec 2001
Location: Bolton, UK
Status:
Offline
|
|
In my experience, slow booting is caused by disk errors which fsck can't fix. Try booting off your MacOS X CD and running disk first aid until you get a report of no errors. If there's a problem which won't clear, you need a third-party disk repair program.
Barney.
|
|
|
| |
|
|
|
 |
|
 |
|
Mac Elite
Join Date: Jan 2003
Location: NYC
Status:
Offline
|
|
my 12" PowerBook takes just under 4 minutes to boot (and has since i got it)... do you think i should try that too?
|
|
|
| |
|
|
|
 |
|
 |
|
Dedicated MacNNer
Join Date: Dec 2002
Location: someplace
Status:
Offline
|
|
My computer takes under 45 seconds to boot and have a desktop. All of my login items have launched and I am ready to begin working in about 1.5 minutes.
(Dual 1GHz G4 tower)
|
|
|
| |
|
|
|
 |
|
 |
|
Fresh-Faced Recruit
Join Date: Oct 2002
Status:
Offline
|
|
Months back I had SLOOOOW booting problems on one of my B&Ws. Turned out to be a flaky USB hub (evidently USB problems are not something new...). Unplugged it, and the problem went away.
|
|
|
| |
|
|
|
 |
|
 |
|
Professional Poster
Join Date: Jul 2001
Location: New York, NY
Status:
Offline
|
|
booting can also be slow if:
you are booting 'cause you crashed - it does an fsck when you boot, and that takes longer if there's errors to fix.
you are booting without being connected to the internet - this can be really slow if you've got the option to set network time, etc. turned on.
you have all your ports/network services turned on. If you never connect via modem, or IR modem, turn those off, turn off airport or ethernet too if you don't use them. (This is done in Network Preferences). Turn off web sharing and appletalk if you dont use them. Open up Directory Services and turn off those services you aren't using.
All these things can speed up your boot-time.
|
|
cpac
|
| |
|
|
|
 |
|
 |
|
Mac Elite
Join Date: Mar 2003
Status:
Offline
|
|
Also I found that using Drive 10 or the like to de-fragment your disk can boost the booting. I went from 2 minutes to 55 seconds from the gong.
|
|
|
| |
|
|
|
 |
|
 |
|
Mac Elite
Join Date: Nov 2000
Location: Boston
Status:
Offline
|
|
Originally posted by MaxPower2k3:
my 12" PowerBook takes just under 4 minutes to boot (and has since i got it)... do you think i should try that too?
I've got a 12" PB and it's boot time is pitiful. My 3 year old Dual 500 boots in less than a minute. The 12" slow boot time has nothing to do with running fsck, though if you crash and have to restart, it will take even longer than 4minutes while it runs fsck.
|
|
-Toyin
13" MBA 1.8ghz i7
"It's all about the rims that ya got, and the rims that ya coulda had"
S.T. 1995
|
| |
|
|
|
 |
|
 |
|
Mac Elite
Join Date: Oct 2001
Status:
Offline
|
|
My iMac G4/700 was taking over 10 minutes to bootup and just a while ago I decided I was going to do something about it (I don't reboot much).
I did the most obvious and simple stuff, and ran the standard Unix daily/weekly/monthly tasks and made sure I didn't have any stupid startup items installed. But that didn't help at all. Nextly, I decided to restart and go into Verbose Mode (hold command and v until command line screen during startup) to see exactly what was causing such delay.
It turns out the "checking disk" stage was taking about 7 minutes. There were also some networking "warnings" that repeated for about a minute.
So I reconfigured some ethernet settings and then restarted again, this time in Single User mode (hold command and s until command line screen during startup). Then I ran fsck (type "/sbin/fsck -y" press return and repeat until it doesn't say "***** File System was modified *****") about 9 times over the course of an hour (ran fsck, waited for it to do it's thing, played video games for several minutes, returned and repeated) and then rebooted (type "reboot" and press return).
Wa-la. Startup time down to 2 minutes.
I'm sure I could get this to go even faster if I did some defragging and some other maintenance things, but as it is, this is sufficient for the time I invested into solving the problem.
Hope this helps!
|
|
|
| |
|
|
|
 |
 |
|
 |
|
|
|
|
|

|
|
 |
Forum Rules
|
 |
 |
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
 |
 |
 |
 |
|
 |
|