repair permissions in single user mode?

The command you need to enter is quite simple ( /usr/sbin/diskutil repairPermissions /) but I suggest that instead of that you install the free and excellent AppleJack with which you can do more than just Repair Permissions, with its simple instructions ("Choose 1", "Choose 2", etc) on screen even though you are in Single User Mode.


Andreas

I just caught my post in time to edit it with the repairPermissions command.

I am sure you will have already used fsck -fy, repeating until no error is reported, but I think that issuing the other commands without the protection offered by AJ could be asking for trouble. I have never before heard of AJ causing a crash. Have you tried (re-)installing the OS X 10.5.7 Combo Update? It might help to d/load it and then switch to Safe Boot Mode to install it. It may not help but it can't do any harm and it might just replace something that is corrupted.


Andreas

That's pretty much the sort of thing I meant by "I think that issuing the other commands without the protection offered by AJ could be asking for trouble". It sounds as if preparation needs to be made to be able to run diskutil in SU Mode and that is beyond me. I suggest that after re-running the Combo you see if AppleJack will work - it might pay to re-install it.

If you haven't already done so, I suggest you apply DiskWarrior to the drive to rebuild the Disk Directory and hopefully effect some repairs. It's best if you can install DW on another drive because running it from its CD is painfully slow - but better that than nothing. (BTW, if DW has problems, note its "Scavenge" mode - "Option" key down so that "Rebuild" changes to "Rebuild…").


Andreas

the ONLY way to run repair permissions in SUM is by using Applejack. why do you insist on doing it that way? can you do it while booted normally?

I think that the message you saw gives the explanation: links to the DiskManagement framework need to be in place before diskutil can run, and those links have not by default yet been established in SUM. Hence the need for AppleJack.

Now that you are up and running, as VK intimates, there is no point in running Repair Permissions other than in Disk Utility or Terminal, no advantage whatsoever. In fact, Repair Permissions is often advocated but rarely needed. It is not something that needs to be done as a routine. "Repair Permissions" is available in AppleJack primarily as something to try on those occasions when your Mac just refuses to boot normally.

I usually recommend that only AppleJack's items 1, 3 and 5 should be used without good reasons for 2 and 4. Even that can sometimes be overkill, even counter-productive - there is a fetish for clearing caches which usually only gives the user a slower Mac until certain caches have been rebuilt.

Anyway, I'm delighted that you seem to have solved your problem. 🙂

Why does permissions repair work from within disc utility or the terminal, but not from within single user mode?

because various things need to be loaded and in a very specific order before disk utility can run (even its command line version). leopard's startup sequence is quite complicated and it took applejack's devs something like a year to crack it and make it possible to run repair permissions from SUM. AFAIK nobody else has ever managed it or anything close to it. but there is absolutely zero advantage to repairing permissions from SUM if you can do it while booted normally. this might be needed only if you can not boot normally but still can from SUM.

I'm trying to start up a friend's (white) iMac in Single User mode, but it won't let me. (Yes I'm holding dow the correct keys - I perform an sbin/fsck -fy if the power is interrupted to my iMac or MBP). The Mac is running 10.5.8 and all the system software is up to date. I've checked the keyboard and it's OK.

Any ideas ?