Unable to mount LUKS partition after updating dom0

[Chris Olin]

The errors I'm receiving are:

[FAILED] Failed to start Cryptography Setup for <disk>
See systemctl status systemd-cryptsetup@luks\<redacted>.service for details
[DEPEND] Dependency failed for Encrypted Volumes
dracut-initqueue: A dependency job for cryptsetup.target failed. See q journalctl -xn

[Chris Olin]

Apologies, this somehow posted while I was in the middle of typing.

I believe this was caused by an issue upstream. However, since I'm unable to mount /, I cannot get access to update dom0 again, which is probably the only way I'll be able to fix this. Normally, I'd boot from another partition or LiveCD and chroot in to fix the issue, but that doesn't seem possible with Qubes. Any advice on how to fix this?

[Marek Marczykowski-Górecki]

It *is* possible to access Qubes partition from any LiveCD, just like any
other Linux with encrypted "/".

Do you have enabled "current-testing" repository?

If you get shell prompt after that error message, try collect some additional
info:
1. Check output of "journalctl -xn" as error message suggests, search for
anything related to harddisk (sda?) or device-mapper.
2. Also check output of "udevadm info -q all -n sda2" (replace sda2 with your
encrypted partition) - there should be entries like ID_FS_UUID=... and
ID_FS_TYPE=crypto_LUKS.

--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

[Marek Marczykowski-Górecki]

On 26.06.2014 03:59, Chris Olin wrote:
> On Jun 25, 2014 7:47 AM, "Marek Marczykowski-Górecki" <

> marm...@invisiblethingslab.com> wrote:
>>
>> On 25.06.2014 10:21, Chris Olin wrote:
>>> Apologies, this somehow posted while I was in the middle of typing.
>>>
>>> I believe this was caused by an issue upstream. However, since I'm
> unable
>>> to mount /, I cannot get access to update dom0 again, which is probably
> the
>>> only way I'll be able to fix this. Normally, I'd boot from another
>>> partition or LiveCD and chroot in to fix the issue, but that doesn't
> seem
>>> possible with Qubes. Any advice on how to fix this?
>>
>> It *is* possible to access Qubes partition from any LiveCD, just like any
>> other Linux with encrypted "/".
>>
>> Do you have enabled "current-testing" repository?
>>
>> If you get shell prompt after that error message, try collect some
> additional
>> info:
>> 1. Check output of "journalctl -xn" as error message suggests, search for
>> anything related to harddisk (sda?) or device-mapper.
>> 2. Also check output of "udevadm info -q all -n sda2" (replace sda2 with
> your
>> encrypted partition) - there should be entries like ID_FS_UUID=... and
>> ID_FS_TYPE=crypto_LUKS.
>

> I don't get a shell prompt after that message. It just keeps prompting me
> for the passphrase.

Perhaps you've entered wrong disk passphrase?

> I was able to get into the Qubes partition from a Live CD, but dom0 is
> configured to get updates from the firewallvm, which obviously isn't
> running, preventing me from updating dom0 to try fixing this.

Temporary comment out "reposdir" option from /etc/yum.conf - this should
enable direct updates.

> I don't recall enabling the testing repository.

[Chris Olin]

Unlikely. I only get this error when I input the correct passphrase.

Adding the mailing list back. Forgot to reply all in my previously reply.