Can't turn on FileVault on Lion after clean install

Morsh, your disk has reverted successfuly from CoreStorage to HFS+ with error code 0:

So I don't see any problems in your system.

w95014 wrote:

Morsh, your disk has reverted successfuly from CoreStorage to HFS+ with error code 0:

corestoraged: exiting csdFinishRevert, err is 0

So I don't see any problems in your system.

It it true that it got reverted properly, but the problem is that it does it at all: "FileVault cannot be turned on". If I understand correctly, the HFS+ volume needs to be converted to a corestorage volume, thus the machine needs the first reboot. However it sees some problems finishing the conversion and does the revert operation (which works properly as you stated) which then results in the second reboot. Because of this we will then see that FileVault is still turned off, because the operation was reverted successfully. I conclude that the problem is the initial conversion to a corestorage volume.

paulimausi: if you search your /var/log/kernel.log for CoreStorage, you should be able to find related log messages about why encryption failed before it starts reverting.

Morsh: if you post earlier log messages (maybe in /var/log/kernel.log.1.bz2, /var/log/kernel.log.2.bz2, etc) containing CoreStorage, it should also tell you why the encryption was failed.

It is likely that your hard drive has serious I/O errors which prevented File Vault from encrypting your disk.

paulimausi wrote:

OK, I strikes me that I, too, have a

WDC WD7500BPVT-22HXZT1

hard disk.

Is there anyone who has the problem who has a different disk, i.e. not a Western Digital disk?

This sounds suspicious, mine is also a WDC WD7500BPVT-22HXZT1. I'm currently checking the harddrive for read errors by using the command

>sudo dd if="/dev/rdisk0" of="/dev/zero" bs=8m

This will need some time, but the harddisk worked reliable in the past, thus I don't expect to find anything. However I found one strange thing: even under different OSes (Windows 7 and Ubuntu 10.10) it seems that the MacBook turns off the harddrive very often. Smartctl also has shown a high number of spinups (but also I think that this is a different problem not related to the current one)

hi, i have the same problems.

But i Have a other HD is a TOSHIBA MK1059GSM 1TB

IOAHCIBlockStorageDevice/IOBlockStorageDriver/TOSHIBA MK1059GSM Media/IOGUIDPartitionScheme/Macbook Pro@2/CoreStoragePhysical/CoreStorageGroup/Macbook Pro@s0

Jul 27 10:11:27 FBD09CZ0 kernel[0]: thr 0x6eac7f0 CoreStorage: read_volume_headers: vol_header 0 at 0 invalid checksum

Jul 27 10:11:27 FBD09CZ0 kernel[0]: CoreStorage: fsck has finished successfully for lvg "E3F0E965-3603-4312-BBE6-87AD997314BB"

Jul 27 10:11:27 FBD09CZ0 kernel[0]: thr 0x75e9000 CoreStorage: read_volume_headers: vol_header 0 at 0 invalid checksum

Jul 27 10:11:27 FBD09CZ0 kernel[0]: CoreStorageGroup::handleOpen(0x90cb200) client 0x90cb200 pv CC253E91-768F-490A-977A-BB0A41846954 failed to open for LVG "Macbook Pro" (E3F0E965-3603-4312-BBE6-87AD997314BB).

Jul 27 10:11:27 FBD09CZ0 kernel[0]: CoreStorageGroup::adminDoneGated failed to start LVG

Jul 27 10:12:07 localhost kernel[0]: thr 0x6703000 CoreStorage: read_volume_headers: vol_header 0 at 0 invalid checksum

Jul 27 10:12:07 localhost kernel[0]: CoreStorageFsck: LVG on disk0s2 was repaired

Jul 27 10:12:07 localhost kernel[0]: CoreStorageFsck: <Volume Recognition : disk0s2 : Volume Header (head)> unsupported format

Jul 27 10:12:07 localhost kernel[0]: CoreStorage: fsck has finished successfully for lvg "E3F0E965-3603-4312-BBE6-87AD997314BB"

Jul 27 10:12:07 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@1F,2/AppleAHCI/PRT2 @2/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDri ver/TOSHIBA MK1059GSM Media/IOGUIDPartitionScheme/Macbook Pro@2/CoreStoragePhysical/CoreStorageGroup/Macbook Pro@s0

Jul 27 10:12:54 FBD09CZ0 kernel[0]: CoreStorageFamily::commitFamilyProperties: lv_commit_properties returned 30

Jul 27 10:12:54 FBD09CZ0 kernel[0]: CoreStorageGroup::updateFamily: commitFamilyProperties returned 30

Jul 27 10:13:20 FBD09CZ0 kernel[0]: CoreStorageFamily::commitFamilyProperties: lv_commit_properties returned 30

Jul 27 10:13:20 FBD09CZ0 kernel[0]: CoreStorageGroup::updateFamily: commitFamilyProperties returned 30

I hope its a bug form Apple

w95014 wrote:

Morsh: if you post earlier log messages (maybe in /var/log/kernel.log.1.bz2, /var/log/kernel.log.2.bz2, etc) containing CoreStorage, it should also tell you why the encryption was failed.

It is likely that your hard drive has serious I/O errors which prevented File Vault from encrypting your disk.

I checked the harddrive intensively, first I read in the whole disk using dd

>sudo dd if="/dev/rdisk0" of="/dev/zero" bs=8m

89425+1 records in

89425+1 records out

750156374016 bytes transferred in 14618.910268 secs (51314110 bytes/sec)

No read errors at all. Then I installed smartmontools to get more detailed information

>sudo smartctl -a /dev/disk0

...

ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE

1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0

3 Spin_Up_Time 0x0027 205 164 021 Pre-fail Always - 750

4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1874

5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0

7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0

9 Power_On_Hours 0x0032 096 096 000 Old_age Always - 3561

10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0

11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0

12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 248

191 G-Sense_Error_Rate 0x0032 012 012 000 Old_age Always - 88

192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 60

193 Load_Cycle_Count 0x0032 194 194 000 Old_age Always - 20446

194 Temperature_Celsius 0x0022 118 106 000 Old_age Always - 29

196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0

197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0

198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0

199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0

200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0

...

Besides the load-cycle count nothing points to a problem with the harddisk or its interface. Thus I think we can exclude serious I/O errors. But perhaps there are still other (firmware) incompatibilities.

I searched through the mentioned earlier log files, but there are no more CoreStorage or I/O errors: it remains a mystery.

Is there the possibility to boot up in single-user and/or verbose mode and execute the FileVault control panel actions by hand and without a reboot so that we get a chance to see what's going on in detail?

Morsh, your File Vault was turned off since the partition type is all HFS+, not CoreStorage. I cannot tell what errors you got from the log. Can you please turn it on again and attach the related part of /var/log/kernel.log?

I am having the exact same problem with FileVault. I have tried 3 different drives. Fresh install on 400GB drive and FileVault works. Fresh install on 1.5TB drive FileVault fails and has before mentioned problem. Fresh install on 2TB drive fails with same problem. I will pull and newer 2TB drive from my Drobo tomorrow and see if I still get a fail from FileVault. Anybody find a fix to this yet?

Apple won't fix this since its a third party drive and seems to not be a very high percentage of user with this error. Let's see if I'm wrong that no fix will be offered in 10.7.1

Is it an issue with the drives or with the OS? I have Seagate Barracudas rangeing from 400GB to 2TB. Anything under 1TB works. Over 1TB does the double boot fail mentioned at the beginning of this post.

It is an issue with the I/O errors of the drives. In many of the logs, there are I/O errors which forced File Vault to stop encrypting, because further encrypting may cause data loss.

My disk doesn't have any i/o errors and I can't use filevault. It is a 1.5g WD that is fine and has been rigorously tested prior to use. No excess bad sectors or r/w issues of any kind. I have tried clean install, install over previous installation of SL, deletion of sophos anti-virus. Nothing works. System stalls on second reboot and refuses to continue install of fvault. The only solution is a manual restart after which fvault is not installed. I'm stuck at this point.