If you have "Other Input Sources" available at the top right of your login screen, select the one called Unicode Hex Input. This can be used to input emoji (or any other character) into the password field, as long as you know the Unicode Hex number of the character. This number can be found in the Character Viewer or on the internet.
Some items you find ...
Open up the Terminal and enter the command:
diskutil cs list
Or with APFS starting with 10.13
diskutil apfs list
With APFS the FileVault setup utility also shows health and this status:
You will see an output listing at least one Logical Volume Group, with a Logical Volume Family and Logical Volume nested below.
There is be a ...
I solved it by the solution Apple Support suggested to do, here are the steps I did:
Install OS X on an external drive from Recovery mode (Cmd + R while starting).
Boot from the external drive.
Install the Hex/Emoji keyboard to be able to type the relevant character.
Go to Disk Utility, choose the locked disk. Go to File -> Turn Off Encryption.
Enter your ...
Brian's answer was right on. The issue in my case was related to the backlight. Here's how I got around it:
While the password dialog is up, move your mouse cursor to the top of the screen until you get an apple menu.
Select "Restart" from the Apple menu
Use a flashlight to shine a light through the Apple on the back of your MacBook screen and you should ...
DaisyDisk (Free Trial, $9.99)
DaisyDisk is sort of like WinDirStat for Windows, in that you can see your files as a visual hierarchy and find out which ones are taking up the most space.
Where Daisy Disk excels is two places:
It's programmed to efficiently and using parallel processes rapidly search out all the special cases where Apple has filesystem ...
Every time you make the computer do something extra, in this case encrypting/decrypting all file access, it will take longer and the machine will slow down a bit.
FileVault 1 did slow things down noticeably, but with FileVault version 2 (Introduced in OS X 10.7 (Lion)) running on an SSD there is no noticeable decrease in reading or writing files. I have ...
Have you turned on FileVault 2 encryption? If you have, you can enable your third account by doing the following:
Open System Preferences
Click on Privacy & Security.
Click on the FileVault tab.
There should be an Enable users... button showing in the FileVault preference pane. Click it and you should be given the opportunity to enable the third ...
There's an OS X feature called authenticated restart that stores the FileVault key in the SMC for the duration of the reboot. Apple acknowledges in the manpage that it does reduce FileVault security for the duration of the restart:
On supported hardware, fdesetup allows restart of a FileVault-enabled system without requiring unlock during the subsequent ...
Since you have Filevault - that makes your situation precarious and a bit delicate.
Some good news, Apple has disabled emoji entry in the password pane for 10.11 El Capitan - I can't paste or get emoji in the Users & Groups preference pane.
Apple's official manner to get past this is to click the ? in the password field and reset your password. If you ...
This is much easier to do beginning in Mavericks. The fdesetup command was expanded to support recovery key changes and verification.
$ sudo fdesetup validaterecovery
Enter the current recovery key:
This will prompt you for the key, which should be entered in all caps with the hyphens.
true means you entered a valid recovery key.
The previous answer I gave here was wrong (as is bmike's answer).
The previous answer I gave was that if you have this as a problem, a workaround is to create an encrypted disk image that covers the entire AppleRaid set. This works, in theory, but is so horribly slow (like more than 10x as slow as the raw disk access) that it is basically unusable, which ...
To add an answer exactly fitting to your case I slightly modified my answer in the linked "duplicate" and posted it here again.
The second as well as the third partition of your internal disk got the wrong partition type, your data probably won't be lost.
A bootable OS X partition (except the Recovery HD) either has the GUID 48465300-0000-11AA-AA11-...
My own experience with File Vault 2 on Samsung 840 EVO on an early 2011 MacBook Pro running Mavericks is that the slowdown is not noticeable.
I took one speed reading before turning File Vault 2 with
time dd if=/dev/zero bs=1024k of=tstfile count=1024
That showed about 490 mb/s. After File Vault 2 was on and encryption was completed, another ...
On OS X 10.11.1 the output diskutil cs list shows encryption progress as:
+-- Logical Volume Group 19B060CE-52A6-4102-9F3D-E6108BD91316
Name: My harddrive
Size: 499113885696 B (499.1 GB)
Free Space: 18972672 B (19.0 MB)
Just bumped into this issue too, if you change password via
Settings > Users & Groups > Change Password ...
you will be prompted twice, once for the File Vault original password and again for the new account password. However if you change the password via
Settings > Security & Privacy > Change Password ...
both will be updated, noting ...
No, the backups will not be encrypted automatically, but it's very easy to enable for directly attached disks. Just check "Encrypt Backup Disk" in the Time Machine disk selection settings.
If you're backing up to another Mac, you can use Disk Utility on that Mac to erase non-boot drives and put an encrypted partition on them:
It seems strange OS X didn't present you the recovery key. Try:
sudo fdesetup changerecovery -personal
This awesome blog has probably all the info you desire. Look for the section "Managing individual and institutional recovery keys". You can use your Filevault2 password to change the recovery key. And you will have to use an Administrator account.
I've always wondered the same thing: how to keep OS X from storing the WPA passphrase (or PSK) in NVRAM.
Using 'nvram' I could never find the variable that I thought held these credentials. Today, I tried booting to a USB live image of Linux and running Chipsec. Its command to list EFI variables has many more results than I was getting by running nvram ...
Other answers here are correct - it is not possible to remotely access a freshly-booted Mac with FileVault enabled without physical access (FileVault operates 1 layer closer to actual software than a 'traditional' BIOS or firmware password).
It is, however, possible to remotely reboot a Mac and force it to allow remote access even with FileVault enabled, ...
The secure way to do it is to simply erase the dive, don't decrypt it first. That makes recovery of your data impossible - whereas if you decrypt it, there is a possibility it can be read later by a bad actor.
See Apple KB - What to do before you sell or give away your Mac
I understand that you're running into issues, so this is going to be more for others looking for info on this topic. Encrypting non-boot volumes should be a relatively easy process in OS X 10.8.x and later.
To encrypt a non-boot volume:
Right-click on the volume you want to encrypt
Select the Encrypt… command
When prompted, enter a password and (...
i like to do it this way.
while true; do diskutil cs list | grep 'Conversion Progress' ; sleep 30; done
will print out an updated progress every 30 seconds so you can just leave it running and glance over and instantly see where the progress is up to without having to run the command again.
No, it's not. Some say it's a benefit if you have geo-location and remote wipe configured (or other similar software) as it increases the chance that someone finding the Mac will connect it to the Internet.
What's happening is that you also have Find My Mac on. That enables a Safari-only guest account which will allow users to log in and run Safari. The ...
Filevault 2 supports Intel® Advanced Encryption Standard (AES). It's important to know if your Mac has an Intel processor which supports this, as it significantly reduces the CPU overhead. Search for you CPU here an look if is supports the New AES instructions.
My Macbook Pro 2011 got this feature enabled via a firmware update (Apple did not ...
I asked after this while attending WWDC 2015 and was told that the "Encryption Paused" issue was addressed in 10.10.3.
The root cause was a problem with resizing the CoreStorage volume during the encryption process. When the CoreStorage volume was unable to grow, the encryption was paused and could not resume until the resize issue was addressed.
To fix ...
Actually your mac is capable of encrypting that fast (perhaps you're confusing it with encryption+compression).
Your processor has a special Intel AES-NI instruction set, specifically designed to optimize encryption speed. Looking at some performance benchmarks for that processor, the AES test performs at a whopping 8.87 GB/s multi-core and 2.94 GB/s ...
You don't need any tools if you care to use Apple's included tools.
Start with System Information and the About this Mac Menu bar item in the Apple Menu.
select the Apple Menu
About this Mac
Storage (top left of the window between Displays and Memory)
This tool uses the spotlight data, so if it seems off you can reset spotlight and leave the mac ...
John Siracusa's detailed Lion review covers the new FileVault disk encryption feature in great detail:
To summarise, the new system is "volume" based. This means that not all volumes can be or are encrypted. The Lion recovery partition for example is not encrypted. Non Mac ...
After a bit of messing about, it turns out that there is a better compromise which doesn't seem to be clearly documented anywhere obvious, so I thought I'd share it here. I don't believe this is a duplicate but I'm happy to see this question closed if I've missed something.
The cost of the solution (which may be unacceptable to some) is that you need to ...