The Mac Observer

Skip navigational links

DealsOnTheWeb Daily Deal: OneCall's Weekend Sale - 20 Great Items at Great Prices All Weekend Long

Keep Your Mac Healthy and Happy in 2005

by

- Episode 33 - January 7th, 2005

This is my first column of the year, so it's chock full of resolutions to help you keep your Mac (and yourself) healthy and happy in 2005.

* Resolve to buy more RAM if you have less than 256MB.

More RAM means Mac OS X has more room to stretch its legs; when it has enough legroom it will run noticeably faster. Plus, you can have more programs open and those programs will run faster.

RAM is cheap; don't spend another year suffering; if you don't already have enough of the stuff, buy some in 2005.

* Resolve to back up important files religiously and regularly.

I know I recommend this so often I'm beginning to sound like a GarageBand loop, but you'd be shocked at how many e-mails and phone calls I get that start out with, "I know I should have backed up, but..."

No ifs, ands, or buts about it-you have to back up files you care about. Your hard disk (and most media) will fail someday. If you don't have multiple copies of important files, you may never see them again.

Can you live without them? I thought not.

So back it up now, and back it up regularly.

Hard disk prices have never been lower so consider external FireWire drives as your backup media rather than slower optical CD or DVD discs or tape. It's fast, efficient, and cost-effective to back up to hard disks these days.

Moving right along, if you automate the backup process, it will work religiously even when you don't.

I'm a huge fan of Retrospect and its scripts. I merely schedule my backups to run unattended; all I have to do after that is leave my Mac on and make sure the disks or discs have space available. I have more than a dozen different backup scripts that run unattended 24/7 on my Mac. One backs up my Writing folder every two hours, copying files modified since the last backup; one backs up my Home folder every 12 hours; one backs up my Applications folder each week; and I even have a script that clones my entire hard disk to a second hard disk every morning at 2 A. M., so I always have a bootable duplicate of my startup disk handy if I need it.

Most of the scripts back up the files to one of my four external FireWire drives; a handful back up files to DVDs, which I store off-site for disaster recovery.

Finally, remember these two rules for effective and efficient backups and you'll never go wrong:

Rule #1: One backup is never enough.

This one is absolutely immutable: One backup is never enough for any important document. Here's why: Say you have a document file. It is a perfectly good document file one day; a few days later you discover it's damaged and won't open. If you only have one backup, it's very possible you have two bad copies of the file and no good ones. If you have multiple backups, there's a much better chance of you recovering a recent, undamaged version of it.

Here's another reason one backup isn't enough: Let's say you're diligent and you always backup your important files on a hard disk, optical disc, tape, cartridge, or whatever. Now, imagine that one day that disk, tape, cartridge, or whatever, disintegrates. Poof-it's gone!

Again, multiple backups would more than likely have saved your bacon.

So I recommend at least three backups of every file you care about.

Rule #2: At least one backup should be stored off-site.

If all of your backups are stored in the same room, or even the same building as your Mac, you run the risk of losing everything to fire, flood, earthquake, or other acts both natural and unnatural, including but not limited to theft and acts of aggression. Losing data this way more or less defeats the purpose of backing up, so keep at least one recent backup in a different physical location.

No matter what you are backing up, from a single document to your entire hard disk, it's a bad idea to keep your only backup in the same room (or even the same building) as your Mac.

I have a set of backup DVDs at my neighbor's house. I also have a safe deposit box at the bank with a recent set of backup DVDs in it. So even if my office were flooded, burnt down, vandalized, or even vaporized, the files in the safe deposit box would be, well, safe.

* Resolve to run Apple's Disk First Aid or the Unix file system check (fsck) once a week or more.

Disk Utility is a little program that can, among other things, check your hard disk for damage and then repair it using its First Aid function. This can go a long way toward keeping your Mac running smoothly and it only takes a few minutes a week to do. It can't hurt and just might help.

Alas, to run Disk First Aid on your hard disk, you need to boot from a CD or DVD such as the Mac OS X installer disc that came with your Mac. Finding that CD or DVD, booting from it, launching Disk Utility, running First Aid, and then restarting again afterwards, can be somewhat inconvenient. Fortunately, there is a faster alternative-the Unix file system check, which you can run without booting from a CD or DVD.

You will have to start up your Mac in single user mode and type a command or two, but it's really quite easy and since it does pretty much the same thing as First Aid, it might save you time.

Here's how to run fsck on your Mac:

1. Restart your Mac.

2. Immediately press and hold the Command and S keys down until you see a bunch of text begin scrolling on your screen. In a few more seconds, you'll see the Unix command line prompt (#).

Now that you're at the # prompt, here's how to actually run fsck:

3. Type "fsck -y" (that's fsck-space-minus-y).

Note: If you are using a disk with Journaling enabled (e.g. Mac OS X 10.3), you'll need to type "fsck -f" instead of "fsck -y")

4. Press Return.

If you see a message that says: ***** FILE SYSTEM WAS MODIFIED *****.- and this is extremely important - you must repeat Steps 3 and 4 again and again until that message no longer appears. Having to run fsck more than once is normal, because the first run's repairs may uncover additional problems.

When fsck finally reports that no problems were found, and the # prompt reappears:

5. Type "reboot" or "exit."

6. Press Return.

Your Mac should proceed to start up normally to the login window or the Finder.

* Resolve to run Disk Utility's Repair Disk Permissions regularly.

For whatever reason, Mac OS X can become confused about which files can be managed by which users. That's why savvy Mac users run Disk Utility's Repair Disk Permissions function often. I run it after I install ANY piece of software, and I run it once every couple of weeks, just in case.

It's fast and easy and doesn't require you to boot from a CD or DVD. And, you don't have to restart your Mac, either. Just launch Disk Utility (from your Applications/Utilities folder), click your boot disk in the list on the left side of the window, click the First Aid tab, and then click the Repair Disk Permissions button. That's it. When repairs are completed (See Figure 1), just quit Disk Utility and get on with your work.


Figure 1: Disk Utility has finished repairing Disk Permissions on my boot disk, Boots.
(Click the image for a larger version)

* Resolve to join a user group or at least attend a User Group meeting.

Mac User Groups are one of the best resources in the world for Mac users and a great way to meet other Mac enthusiasts who share your passion. They're also a great way to learn more about how to use your Mac better, faster, and more elegantly. Most offer special interest groups for many applications, and question and answer sessions with experts, in addition to raffles, lectures, and much more.

If you're not already active in your local Mac user group, visit http://www.apple.com/usergroups/find/ and find the group in your neck of the woods and then join it (or at least attend a meeting or two).

That's all he wrote...

There is one more thing: Have a very happy and healthy New Year!

Bob "Dr. Mac" LeVitus has been a Macintosh user for a long, long time and has written 49 computer books including Mac OS X Tiger For Dummies and GarageBand for Dummies. He also offers expert technical help and training to Mac users, in real time and at reasonable prices, via telephone, e-mail, and/or unique Internet-enabled remote control software. For more information on Bob and his services, visit www.boblevitus.com.

Send polite comments to

Send impolite comments to DeleteWithoutReading@boblevitus.com, or post your comments below.

Most Recent Columns From Dr. Mac: Rants & Raves

Dr. Mac: Rants & Raves Archives

Observer Comments

Show: Subjects Only | Full Comments
Close Name:Mace Posts: 9604 Joined: 07 Aug 2003
Subject:

Thanks for the tips.

Close Name:Photodan -   TMO Staff Posts: 3112 Joined: 11 Jun 2001
Subject:

I used a shareware app named CronniX to set a cron job that automatically fixes my permissions a couple times per week at 3am. It deposits a small text file on my desktop to report the results.

It's something Apple should have the system do out of the box, IMHO.

-Dan

Close Name:Small White Car Posts: 1960 Joined: 02 Jul 2004
Subject:

Quote
Photodan wrote:
I used a shareware app named CronniX to set a cron job that automatically fixes my permissions a couple times per week at 3am. It deposits a small text file on my desktop to report the results.

It's something Apple should have the system do out of the box, IMHO.

-Dan


Tiger might. The "automator" function is made to do any task you tell it to again and again.

Now perhaps it won't be able to do that, but I'm hoping it will. That would solve this problem.

Close Name:jacrav Posts: 268 Joined: 04 Jul 2001
Subject: A lot of maintenance …

…is already done by the system. Not bad to have to do some of it ourselves …
In addition, I’m sure you can write an AppleScript that will automate any action you desire …
Thanks Dr Mac. Good suggestions, as usual.
Happy New Year to all
Can’t wait for Tuesday !!!

Close Name:Guest
Subject: Maintenance

Couple of things I was thinking about.

I wonder if the permissions mess isn't caused by installation programs? It's usually recommended that you run after installing programs or updating the system. Many installers ask you for your password right after you start them, including operating system updates.

I'm thinking when they do this, they are then allowed to run with the rights/permissions of an admin account, which gives them the right to change some permissions which are probably MEANT to be reset back after the install.

Instead, the permissions don't get reset and we are stuck having to run repair permissions every so often.

Anyone know if this is so?

Second, you can type fsck -fy all at once and it will work fine. I've also heard that booting into safe mode causes fsck to run during the boot process. You can see it in this article: http://docs.info.apple.com/article.html?artnum=107394

I'm assuming it's doing the same thing anyway, so if you can get into safe boot mode, you can skip the command line interface totally if it makes you nervous. Or if you have a non technical friend or relative, you can have them do this like once a month instead of talking them through running fsck.

Keep up the excellent work, oh mighty Dr. Mac!

Close Name:Guest
Subject: Reprint Permission

Do you allow reprints for User Group Newsletters?

Close Name:Guest
Subject: file system check

I sympathize with Harry Truman who longed for a one armed advisor.
On the 1 hand, Apple seems to recommend that the fsck not be used with Journaled (Panther) startup disks.

On the other hand, you and many others recommend using it regularly as you suggested. It would be nice to know which advise to follow.

DJ

Close Name:Guest
Subject: Another Useful Piece of Housekeeping

Probably been detailed before but I thought I'd add this. A lot of users don't leave their Macs on overnight and therefore miss out on the automatic housekeeping that Mac OS X does around 3am (clearing out log files and the like).
To perform these manually:-

Open a terminal session (from /Applications/Utilities/) and type the following:-

sudo periodic daily

Hit Return

(You'll be prompted for your password at this stage)

Enter Password

Hit Return and let it do it's thing until the command prompt returns.

Repeat for weekly and monthly as follows:-

sudo periodic weekly

sudo periodic monthly



Hope that helps.

Close Name:macjim Posts: 35 Joined: 23 May 2004
Subject: fsck too often?

There seems to be conflicting advice about how often to do these routines, and while I like the long uptimes with OS X, when having to shut down my iBook I use YASU to run the permissions and cron jobs, on occasion taking Randy Singer's suggestion to "restart your Mac with the Shift key held down, invoking Safe Boot mode. This will cause First Aid (also known as fsck, or file system check) to be run (invisibly, but it is being run). (Restart again immediately, in the normal way, after doing this.)" Must try the fsck routine next time.

Once a week seems awfully often, and somewhere I recently saw a recommendation to avoid doing the other things more than absoulutely necessary. No doubt a happy medium will emerge. Must back up now.

Close Name:Burnum -   TMO Staff Posts: 801 Joined: 17 Jun 2001
Subject: Repair Permissions Periodically?

John Gruber over at Daring Fireball Thinks Differently:
http://daringfireball.net/2004/12/software_update

Quote
Daring Fireball wrote:
However, just because a file’s current permissions differ from its original permissions as specified in the corresponding ‘.bom’ file, does not mean that the current permissions are “wrong”. The reason this feature exists is that sometimes, the permissions are wrong, causing some sort of problem, and running Repair Permissions solves the problem.


But if you are not experiencing any symptoms that would indicate permission-related problems, there is no reason to run Repair Permissions. Repair Permissions is not a periodic maintenance task or a preventative measure. (Although, to be fair to everyone who thinks that it is a periodic maintenance task, some of Apple’s own support documentation hints that it is.)

Close Name:Guest
Subject: Safe Boot not the same

"I've also heard that booting into safe mode causes fsck to run during the boot process."

Sort of. The types of checks done by fsck during Safe Boot are not the same as those that occur when fsck is run in single-user mode (or as used by Disk Utility). So if you want to check your drive for problems, a safe boot isn't comprehensive -- you need to use Disk Utility or fsck at startup as described by Bob.

As for the Daring Fireball article, it's an excellent piece on update voodoo, but with respect to John's views on repairing permissions, keep in mind that most of the experienced Mac troubleshooters disagree with him. Repairing permissions regularly is not going to cause problems unless you're a power user who has purposely changed the permissions on system-level files for a specific purpose. (And even then, if you've made such "incorrect" changes, you should know enough about what you've done so that you can change them again if repairing permissions "corrects" them.) In fact, Apple states quite clearly in at least three different Knowledge Base articles that repairing disk permissions is a good maintenance task that should be run after installing OS software.

Dan (MacFixIt Editor)

P.S. Hey, Bob

Close Name:Burnum -   TMO Staff Posts: 801 Joined: 17 Jun 2001
Subject:

Thank you Dan for adding your advice. It's helpful to receive this type of info from many sources.

Close Name:danfrakes Posts: 1 Joined: 09 Jan 2005
Subject: Sorry, mistake regarding fsck and safe boot!

[For some reason it won't let me log in to post.]

Sorry, the original post about safe boot was correct and I was incorrect. After posting the above about Safe Boot and fsck, it looked a little funny, as it was contrary to what I've actually written in books So I went back to the source -- the /etc/rc.boot script -- and verified that the standard, expected version of fsck is run during a safe boot. If you're curious, here's the important part:

if [ "${SafeBoot}" = "-x" ]; then
fsck -fy
else
fsck -p

Which basically means "If this is a Safe Boot, run fsck -fy; if not, run fsck -p" (The "-p" option is "preen" mode and is run at every normal startup to check for volumes that weren't properly put away at the previous shutdown/restart.)

Sorry for the confusion, and my apologies to "Guest" who was correct.

Dan

Close Name:macjim Posts: 35 Joined: 23 May 2004
Subject:

here's another wee contradictory piece of advice:
http://docs.info.apple.com/article.html?artnum=107250
describes fsck reporting benign error messages, and seems to recommend using safe mode rather than the command line option:

"With a journaled volume you do not need to start up into single user mode. When a volume is made available to the file system, the journal is replayed and the file system brought up to a consistent state. If you do run fsck, it is best if you use -n and -f flags so that it will not actually modify the volume. "

Think I'll go back to fairly frequent permissions repair, but not try forcing fsck -fy

Close Name:spxyu02 Posts: 1214 Joined: 04 Aug 2004
Subject:

not to be a jerk, but as a recent switcher, i like the idea of a fairly low maintenance computer like my powerbook; not that I myself an unable to handle things such as those described in this thread, but recommending that most/all mac users should do this kinda contradicts, in my mind, the image of the switcher who wanted to move away from that PC that he/she had to take care of more than the work they got done on it (I know this thread pales in comparison to spyware/adware/virus removal and general windows crapiness on a pc, but still...)

Comment on this Article


You cannot edit your comments.   You cannot delete your comments.
Log in | Register | Having Problems? Reset TMO Cookies & Try Again
Username:   Password:   Log me on automatically each visit   

You are not logged in, and this post will appear as "Guest." Log in with your username and password from the TMO forums. If you do not have a username, you can register here.
Please note that guests are limited to including a maximum of two URLs per post.


Post A Comment
  Subject


  Your Comments



Please enter the word exactly as you see it in the image above. Registered users aren't prompted for this. Having trouble reading the image get a new one.


Recent Headlines - Updated January 6th

Tue, 5:49 PM
Just a Thought - Macworld Travel Travasty
4:49 PM
Stock Watch - Piper Jaffray Finds Macworld Announcements “Underwhelming, As Expected”
3:54 PM
News - The Onion Shows Us Apple’s MacBook Wheel
3:30 PM
Editorial - Was Phil Greater Than the Sum of His Parts?
3:13 PM
Ted Landau's User Friendly View - Macworld Expo Keynote: Software Yes; Hardware No
2:06 PM
Games - Logitech Intros More G-Series Gaming Peripherals
1:50 PM
News - Mac Box Set Includes iLife ‘09, iWork ‘09, Leopard
1:36 PM
News - Apple Takes the Wraps Off New 17-Inch MacBook Pro
1:11 PM
News - Apple Introduces iWork ‘09
12:57 PM
News - Apple Debuts iLife ‘09
12:08 PM
News - Jing Allows Easy Sharing of Image, Video Captures
10:55 AM
News - Boingo Brings Skype Access to 100,000-Plus Wi-Fi Hotspots

The Mac Observer Reader Specials