Backup restore result in dom0 storage damage

User Support
, ,
1

A reproducible test was conducted by restoring a ~100GB Qubes backup in verification mode to collect evidence and logs. Two failures occurred:

  1. sys-usb startup failure - Storage-related error requiring manual removal of qubes_dom0/vm-sys-usb-private(known issue)
  2. dom0 boot failure - Post-reboot, dom0 could not boot and entered maintenance mode

Anyone familiar with such issue or it something new that should be reported to team?

2

AFAIK, backup of dom0 includes its private volume only.

3

You mean home directory.

I face ssd memory over flaw, it’s not a first time and not a new bug as I know.

Few basic actions can damage dom0 storage space:

  1. Copy to dom0 disk image for installation as .iso and cast it to .raw during copy.

  2. Verification restore of big backup file.

4

Yeah, home. I wish it was possible to backup at least /etc too.

It is difficult to understand how you restored dom0 and ended up in the described state. I didn’t even know it was possible to restore dom0 on top of existing dom0. I have always restored backup to qubes with new names.

5

I’ve restored several qubes from backup file. However, the entire restoration process takes effect in dom0.

(We talk about backup verification mode, not about real data restore)

6

(We talk about backup verification mode, not about real data restore)

Which makes it even more strange.