[selowitch]

Someone showed me how to do the equivalent of Disk Utility without starting up from the CD-ROM that came with my iBook as follows:

• Start up my iBook in single-user mode (turn on the Mac with the power button, holding down Command-S until the logo screen comes up).
• After all the textual info is presented and you are given a prompt; type: /sbin/fsck -fy
• repeat after finished if you receive a message saying files were modified
• otherwise type: reboot

This seems to "work"— but is it proper procedure, and does it really make running Repair Disk via Disk Utility unnecessary?

[BKMaggert]

Originally Posted by selowitch

but is it proper procedure, and does it really make running Repair Disk via Disk Utility unnecessary?

Yes and yes. Old news actually.

My question...Can repairing permissions be done from the same screen?

[CatOne]

Originally Posted by selowitch

Someone showed me how to do the equivalent of Disk Utility without starting up from the CD-ROM that came with my iBook as follows:

• Start up my iBook in single-user mode (turn on the Mac with the power button, holding down Command-S until the logo screen comes up).
• After all the textual info is presented and you are given a prompt; type: /sbin/fsck -fy
• repeat after finished if you receive a message saying files were modified
• otherwise type: reboot

This seems to "work"— but is it proper procedure, and does it really make running Repair Disk via Disk Utility unnecessary?

Might I ask, why would you need to do either? Is there some specific problem you're trying to solve?

You can see what fsck does by reading the man page -- 'man fsck' from the terminal.

But really, fsck shouldn't be necessary, pretty much EVER, if you're running HFS+ (Journaled). Which you should be.

[allblue]

Applejack does that plus a whole lot more.
http://www.versiontracker.com/dyn/moreinfo/macosx/19596

[allblue]

Applejack does that plus a whole lot more.
http://www.versiontracker.com/dyn/moreinfo/macosx/19596

[Tesseract]

Permissions repairing can (and should) be run from Disk Utility while booted normally (into the GUI, from the hard disk). If you really want to do it at the command line (or in single user mode), here's how:

Code:
sudo diskutil repairPermissions /

[selowitch]

Originally Posted by Tesseract

Permissions repairing can (and should) be run from Disk Utility while booted normally (into the GUI, from the hard disk). If you really want to do it at the command line (or in single user mode), here's how:

Code:
sudo diskutil repairPermissions /

That's how I've been doing it, because I don't like having to find and launch Disk Utiltiy.

[selowitch]

Originally Posted by Tesseract

Permissions repairing can (and should) be run from Disk Utility while booted normally (into the GUI, from the hard disk). If you really want to do it at the command line (or in single user mode), here's how:

Code:
sudo diskutil repairPermissions /

That's how I've been doing it, because I don't like having to find and launch Disk Utiltiy.

[selowitch]

Originally Posted by CatOne

Might I ask, why would you need to do either? Is there some specific problem you're trying to solve? But really, fsck shouldn't be necessary, pretty much EVER, if you're running HFS+ (Journaled). Which you should be.

Well, I am running HFS+ Journaled; yet when I ran Disk Utility it said it repair one volume and couldn't repair the second (I have only one volume though). It also said I had an incorrect leaf count, whatever that is.

[Detrius]

Originally Posted by selowitch

Well, I am running HFS+ Journaled; yet when I ran Disk Utility it said it repair one volume and couldn't repair the second (I have only one volume though). It also said I had an incorrect leaf count, whatever that is.

If Disk Utility can't do it, booting into single-user mode isn't going to work any better. In fact, Disk Warrior is the best way to go for actual repairs of the directory structure. Also, running a surface scan isn't a bad idea either. I've been out of the tech world for more than six months, so I don't know what's changed in this field, but six months ago, Tech Tool Pro was fabulous for running a surface scan ( but nothing else, despite its numerous features ), and Disk Warrior is the best for repairing directory structures.

[steve626]

Originally Posted by selowitch

Well, I am running HFS+ Journaled; yet when I ran Disk Utility it said it repair one volume and couldn't repair the second (I have only one volume though). It also said I had an incorrect leaf count, whatever that is.

You may have a problem, but sometimes the messages you got are generated because someone uses a CD from before 10.3.9 on a Tiger volume. Only Disk Utility from 10.3.9 or later works properly with Tiger (you didn't say what version of the OS you were using). For instance, if you purchased computer with OS 10.3.2, and then upgraded to Tiger but are running Disk Utility from the original 10.3.2 CD, you can get such erroneous messages when checking a Tiger volume. You could get such messages even when nothing is wrong with your disk.

If you are using the right version, then the other poster's suggestion to use Disk Warrior is a good one.