"encrypted.block" mount error in CROS boot process.

52 views
Skip to first unread message

Albert

unread,
Feb 10, 2016, 9:27:06 PM2/10/16
to Chromium OS dev
I modified CROS's kernel, for general CPUs.
when it boot in 'Intel Core2' PC(Fujitsu), it was fine.

But when it boot in 'Intel Pentium M' PC(IBM), it couldn't boot.
I guess "encrypted.block"(in STATE partition) can't mount by mount-encrypted(/usr/sbin/mount-encrypted, binary file).
"/usr/sbin/mount-encrypted" is called by "/usr/share/cros/startup_utils.sh", and "/usr/share/cros/startup_utils.sh" is called by "/sbin/chromeos_startup"

Below is error log of mount-encrypted in 'Intel Pentium M' PC(IBM).

[pid:266] Starting.

[pid:266] VFS mount state sanity check ok.

[pid:266] Using UUID as system key.

ERROR[pid:266] keyfile_read (../../../cryptohome-0.0.1/platform2/cryptohome/mount-helpers.c, 688): EVP_DecryptFinalerror:06065064:digital envelope routines:EVP_DecryptFinal_ex:bad decrypt

[pid:266] /mnt/stateful_partition/encrypted.needs-finalization does not exist.

[pid:266] Generating new encryption key.

Illegal instruction


And below is normal log of mount-encrypted in 'Intel Core2' PC(Fujitsu).

[pid:475] Starting.

[pid:475] VFS mount state sanity check ok.

[pid:475] Using UUID as system key.

[pid:475] Loopback attaching /mnt/stateful_partition/encrypted.block (named encstateful).

[pid:475] Setting up dm-crypt /dev/loop0 as /dev/mapper/encstateful.

[pid:475] Mounting /dev/mapper/encstateful onto /mnt/stateful_partition/encrypted.

[pid:475] Started filesystem resizing process 1110.

[pid:475] Bind mounting /mnt/stateful_partition/encrypted/var onto /var.

[pid:1110] Resizer spawned.

[pid:475] Bind mounting /mnt/stateful_partition/encrypted/chronos onto /home/chronos.

[pid:475] Done.

[pid:1114] Resizing started in 2 second steps.

[pid:1114] Resizing filesystem on /dev/mapper/encstateful to 70281.

[pid:1114] Resizing finished.

[pid:1114] Done.


What is the problem? Why this happens?
What should I do?
Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages