Install of the Fedora-32 templateVM failed

[TheGardner]

Currently try to install the Fedora-32(-testing) template on my Qubes-OS and it always fail during the initial download (after around 350mb).

Question now is - is the disk space of my updateVM full? And if - can I check this with a command?

Downloading the 1.3G file manually works, but I dunno, how to install the downloaded .noarch.rpm.file...?

The cache should be empty, cause a 'dnf clean packages' always brings up a 'files 0' message.

Reboot also done several times...

Anyone an idea?

Thanks!

[TheGardner]

No chance!

Whatever I do, it always breaks after around 360mb. Really feels like there isn't enough space. Wonder where I can see this.

- Setting the space up to 4096 on sys-firewall > same result

- setting the boost and minimal cube emory (for dom0) up > same result

Anyone which an idea, what I'm doing wrong?

[dhorf-hfre...@hashmail.org]

On Mon, May 18, 2020 at 03:33:02AM -0700, TheGardner wrote:
> - Setting the space up to 4096 on sys-firewall > same result

the default download location in udaptevm is /var/lib/qubes/dom0-updates
so with a default appvm layout that is inside the rootfs (or its overlay).
you can check if this is the limiting factor by running
"df -h /var/lib/qubes/dom0-updates" in your updatevm (sys-firewall).

to temporarily make more space available there, you can try ...
sudo mkfs.ext4 /dev/xvdc3
sudo mount /dev/xvdc3 /var/lib/qubes/dom0-updates
sudo chown user.user /var/lib/qubes/dom0-updates

[TheGardner]

Okay, df -h /var/lib/qubes/dom0-updates delivered the following:

[user@sys-firewall ~]$ df -h /var/lib/qubes/dom0-updates
Filesystem      Size  Used Avail Use% Mounted on
/dev/xvda3      9.6G  8.7G  450M  96% /

so, clear now! Thanks a buch!

After:

sudo mkfs.ext4 /dev/xvdc3
sudo mount /dev/xvdc3 /var/lib/qubes/dom0-updates

it already worked like a charm and download the 1.3G file.

Do I have to change (back) somethings, after I installed the template and removed the noarch.rpm file from dom0-updates ?

Cheers :)

[dhorf-hfre...@hashmail.org]

On Mon, May 18, 2020 at 02:38:34PM -0700, TheGardner wrote:
> [user@sys-firewall ~]$ df -h /var/lib/qubes/dom0-updates

> /dev/xvda3 9.6G 8.7G 450M 96% /

> sudo mkfs.ext4 /dev/xvdc3
> sudo mount /dev/xvdc3 /var/lib/qubes/dom0-updates

> Do I have to change (back) somethings, after I installed the template and
> removed the noarch.rpm file from dom0-updates ?

xvdc is the "volatile" volume.
so this change will vanish on its own the next time you restart
sys-firewall.

[TheGardner]

understood.

Guess I have to do some backups, which I have to move to my NAS. The new machine will take two months longer. Have to come out with the current space until then.

[brenda...@gmail.com]

On Monday, May 18, 2020 at 6:01:13 PM UTC-4, TheGardner wrote:

understood.

Guess I have to do some backups, which I have to move to my NAS. The new machine will take two months longer. Have to come out with the current space until then.

Is it possible that you haven't invoked the --clean parameter (sudo qubes-dom0-update --clean) to ensure the local cache in your updatedvm (sys-firewall) is cleared before the next download?

Brendan