Closed ephemient closed 8 years ago
The format of your image is not supported yet. Here the encrypted volume is likely split in 2 extents:
libfvde_encrypted_metadata_read_type_0x0405: entry: 00 block number : 0
libfvde_encrypted_metadata_read_type_0x0405: entry: 00 number of blocks : 65536
libfvde_encrypted_metadata_read_type_0x0405: entry: 00 data type : 0x00000009
libfvde_encrypted_metadata_read_type_0x0405: entry: 00 copy number : 0
libfvde_encrypted_metadata_read_type_0x0405: entry: 00 unknown1 : 0x00000000
libfvde_encrypted_metadata_read_type_0x0405: entry: 00 unknown2 : 0xfffffffffffffffe
libfvde_encrypted_metadata_read_type_0x0405: entry: 01 block number : 65536
libfvde_encrypted_metadata_read_type_0x0405: entry: 01 number of blocks : 24263264
libfvde_encrypted_metadata_read_type_0x0405: entry: 01 data type : 0x00000009
libfvde_encrypted_metadata_read_type_0x0405: entry: 01 copy number : 0
libfvde_encrypted_metadata_read_type_0x0405: entry: 01 unknown1 : 0x00000000
libfvde_encrypted_metadata_read_type_0x0405: entry: 01 unknown2 : 0x00000000
Changes are on their way to support this.
Thanks, that makes sense.
Experimental version 20160729 has basic support for these format changes.
This is the boot disk in a MBP, originally installed in 10.10, then resized to dual-boot Linux (where I'm running these commands from), and upgraded to 10.11.
fvdeinfo.txt