Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'Login via Console' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Login via Console
Authored by: watersb on Mar 31, '05 02:00:25PM

You can log into the Console, and you will have a shell in multi-user mode without mounting the FileVault sparse image.

Then you can use the diskutil to mount an external disk (Firewire or USB) to restore your sparseimage backup (you *do* have a backup, right?) You can move your corrupted FileVault image out of the way by renaming it before restoring from your backup.

1) From System Preferences:Accounts:Login Options -- check the "user name and password" for the login panel, rather than the "list of users" option.

2) Log Out

3) When the login panel appears, type ">console" for the user name and hit Enter (no password). (And that is a greater-than character, then console, no spaces, no quotation marks.)

4) You will have a console with a login prompt; type your user name and password, and you'll be at a shell, where you can get your corrupted sparse image working again.

good luck...

[ Reply to This | # ]
Run diskutil repairVolume via console
Authored by: orca on Dec 07, '05 09:25:29AM

This console login trick is what worked for me. Disk Utility kept giving an error about being unable to finish the task when I logged in as another user to repair my FileVault sparseimage. I had my backups on hand, so I decided to drop to the console to resolve things:

  1. Enable user and password for the login screen
  2. Log out, then login as >console, then my user name
  3. Mount the image using hdiutilmount --stdinpass /Users/account/account.sparseimage (this lets you mount the disk without a graphical login)
  4. Run diskutil repairVolume /Volumes/account until no errors are reported. The first few attempts may state that repairs could not be completed, but as long as some repairs were done, you're making progress!
  5. Login normally. I noticed that some Desktop/Home icons were not correct, so I just logged out and back in once more
  6. Everything is ok!

This might be an avenue to try before paying for DiskWarrior. Manually running diskutil repairVolume seems to give a more determined effort than the GUI presented by Disk Utility's "Repair Volume" command.

[ Reply to This | # ]