Main partition does not work

Question

Hello,
I have an iMac with a 2TB Hard Disk. It is partitioned to have a nearly 1,99 TB "Main Partition" with the System and everything on it. It has an addition partition, too.
With Lion, I set up FileVault/complete HardDisk encryption/CoreStorage.
Last week, I started the Mac, got the starting screen that shows the user und promts for a password to decrypt the hard disk, but after typing the password and pressing enter, the Mac does not boot (Something like a "No-Passing-Through"-Sign appeared on the screen).
I started from recovery partition and varified disk with Disk Utility. This is the log:
Verifying partition map for “Hitachi HDS722020ALA330 Media”
Checking prerequisites
Checking the partition list
Checking for an EFI system partition
Checking the EFI system partition’s size
Checking the EFI system partition’s file system
Checking all HFS data partition loader spaces
Checking Core Storage Physical Volume partitions
Checking storage system
Checking volume.
disk0s2: Scan for Volume Headers
disk0s2: Scan for Disk Labels
Logical Volume Group 42342140-D56E-4138-8DD3-78A32575FBB4 spans 1 device
Logical Volume Group has a 16 MB Metadata Volume with double redundancy
Start scanning metadata for a valid checkpoint
Load and verify Segment Headers
Load and verify Checkpoint Payload
Load and verify Transaction Segment
Incorporate 0 newer non-checkpoint transactions
Load and verify Virtual Address Table
Load and verify Segment Usage Table
Load and verify Metadata Superblock
Load and verify Logical Volumes B-Trees
Logical Volume Group contains 1 Logical Volumes
Load and verify B0422080-000A-4F4B-ACD4-0330C0C02178
Load and verify 5CA21B00-3DCF-4993-BCB2-3EE0795D4AED
Unable to bootstrap transaction group 15060: invalid field value
Continue scanning metadata for an older checkpoint
Load and verify Segment Headers
Load and verify Checkpoint Payload
Load and verify Transaction Segment
Load and verify Transaction Segment
Incorporate 1 newer non-checkpoint transactions
Load and verify Virtual Address Table
Load and verify Segment Usage Table
Load and verify Metadata Superblock
Load and verify Logical Volumes B-Trees
Logical Volume Group contains 1 Logical Volumes
Load and verify B0422080-000A-4F4B-ACD4-0330C0C02178
Load and verify 5CA21B00-3DCF-4993-BCB2-3EE0795D4AED
Unable to bootstrap transaction group 15058: invalid field value
Continue scanning metadata for an older checkpoint
Load and verify Segment Headers
Load and verify Checkpoint Payload
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Incorporate 2 newer non-checkpoint transactions
Load and verify Virtual Address Table
Load and verify Segment Usage Table
Load and verify Metadata Superblock
Load and verify Logical Volumes B-Trees
Logical Volume Group contains 1 Logical Volumes
Load and verify B0422080-000A-4F4B-ACD4-0330C0C02178
Load and verify 5CA21B00-3DCF-4993-BCB2-3EE0795D4AED
Unable to bootstrap transaction group 15055: invalid field value
Continue scanning metadata for an older checkpoint
Load and verify Segment Headers
Load and verify Checkpoint Payload
Load and verify Transaction Segment
Load and verify Transaction Segment
Load and verify Transaction Segment
Incorporate 2 newer non-checkpoint transactions
Load and verify Virtual Address Table
Load and verify Segment Usage Table
Load and verify Metadata Superblock
Load and verify Logical Volumes B-Trees
Logical Volume Group contains 1 Logical Volumes
Load and verify B0422080-000A-4F4B-ACD4-0330C0C02178
Load and verify 5CA21B00-3DCF-4993-BCB2-3EE0795D4AED
Load and verify Freespace Summary
Unable to bootstrap transaction group 15052: incorrect block type
No valid commit checkpoint found
The volume 42342140-D56E-4138-8DD3-78A32575FBB4 was found corrupt and needs to be repaired.
Problems were found with the partition map which might prevent booting
Error: Storage system verify or repair failed.
I tried to repair, but got the same log.
As the main partition is encrypted, no third party application can access it, repair it or copy file from it.
Before I give my Mac to TechSupport to replace the hard disk, I would appreciate of doing a useable copy/clone from the partition to get my data saved (I have time machine running, too, but it is not backup up everything and it is hard work to restore from there – so a clone would be best).
Best,
   Stefan

Answer 1

I have discovered the solution and it involves an issue I suspected. After the restore of my old Time Machine Lion files to my new MBP running ML, the restore restored my computer back to Lion. After an install of ML, my computer worked perfectly except the fancy Scroll and zoom featured we all love from the trackpad. Ha already installed ML on other partitions and the trackpad worked perfectly on them.  Even the guest login's trackpad worked perfectly but not the main admin account.
First thought was to create a new admin account and copy everything from the old admin to the new admin and then delete the old admin account. Hated the idea because all files had to be copied rather than moved.
So what was left to do. I had thought of deleting all the apple preferences from the library and replace them with the contents of the library on another partition in ML. First I deleted old preferences many of which were old Lion preferences. That didn't solve the issue.
I forgot that Lion and ML HIDE the user library so I was working on the wrong library. Discovered the Terminal command "chflags nohidden ~/Library" and I chose to reveal the user library on a ML partition.
Solution:
I booted into another ML partition. I guess that I could have booted into the new admin user account and changed the permissions  to access the old admin users Library But I chose to boot
from another ML partition: copy ALL the com.apple. XXXXX.plist files and the folder  BY Host. It has special hidden files. Other  way is to copy the Preferences folder we'll say into the Desktop.
I then proceeded to delete ALL the com.apple…….plist files and the Host folder into the trash. Then I copied all the apple.com…plist files and the Host folder and then rebooted. And now my wonderful Trackpad works as mountain Lion intended it to work.
I'm leaving this solution because there's someone else in the MacWorld with the same issue.
Ted