Vault-appvm empty after Debian-8 template dist-upgrade

[Essax]

I upgrade my Debian-8 template with sudo apt-get dist-upgrade.  The only problem I had after the upgrade was my vault-appvm was emply when I launched it. I searched through every directory trying to find my data base with no luck.

Fortunately I was able to follow the instructions in the  Qubes Documentation and roll back the changes to my TemplateVM. Once I did that my vault data base was back to normal. If this happens to you and you want to revert the changes to your Debian-8 TemplateVM you would type this command in your Dom0 terminal.

qvm-revert-template-changes debian-8

Please note It requires that all AppVMs based on this template be halted during this operation.

For the technical details about how this command works and the steps it performs, see here

Obviosly another solution would be to restore from backups or download a new TemplateVM.  Just be aware if your vault-appvm is based off debian to cautious if your dist-upgrade

Essax

Sent with ProtonMail Secure Email.

[cooloutac]

sweet command!

[Chris Laprise]

On 06/21/2017 08:46 PM, 'Essax' via qubes-users wrote:
> I upgrade my Debian-8 template with /sudo apt-get dist-upgrade. /The
> only//problem I had after the upgrade was my vault-appvm was emply when

> I launched it. I searched through every directory trying to find my data
> base with no luck.
>
> Fortunately I was able to follow the instructions in the Qubes

> Documentation <https://www.qubes-os.org/doc/software-update-vm/> and

> roll back the changes to my TemplateVM. Once I did that my vault data
> base was back to normal. If this happens to you and you want to revert
> the changes to your Debian-8 TemplateVM you would type this command in
> your Dom0 terminal.
>

> /qvm-revert-template-changes/ debian-8

>
> Please note It requires that all AppVMs based on this template be halted
> during this operation.
>
>
> For the technical details about how this command works and the steps it
> performs, see here
>
> Obviosly another solution would be to restore from backups or download a
> new TemplateVM. Just be aware if your vault-appvm is based off debian

> to cautious if your /dist-upgrade/

This seems to indicate a nasty bug in the Debian 8 code that checks and
mounts the private.img. If you wish to use current releases you could
try Debian 9 instead; I have been using it for about a year without such
issues.

Only catch is you currently have to follow the Qubes doc for upgrading a
Debian 8 template to 9.

--

Chris Laprise, tas...@openmailbox.org
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886

[Unman]

yes, I'd be far more worried about the absence or 'disappearance' of
the database.
I don't believe there's anything in the "Debian 8 code" that would be
responsible for this. Principally because I've successfully transitioned
to Stretch on a number of machines without losing the keepass data.
It would be useful if you could clone your vault and Debian-8, and
repeat the operation. That will give you a chance to do some research
without risking your data at all. As Chris suggests, focussing on what
is mounted would be a good start.

unman