[SOLVED] error: failed xxx.. disk : expected download size exceeded

NuSkool · 2021-12-12 18:28:01

Any insight on what triggers this error in pacman?

I have a local AUR repo set up. Occasionally, I get the error in the subject line on certain packages. I have also seen a 'corrupt ... do you want to delete it' message.

In any case, I can always load the package with pacman -U. Since the package is already loaded in the AUR sync db, the package is not seen as foreign, and all is OK.

The packages are loaded into the AUR db using repo-add, and then pacsync to update only the AUR db and placed into the AUR cache when this error occurs.

I've tried a few different procedures such as using pacman -Sy before installing the package but it seems nothing so far solves this issue.

Should I just default to using pacman -U rather than -S ?

$ sudo pacman -S downgrade
resolving dependencies...
looking for conflicting packages...
Packages (1) downgrade-10.1.0-1
Total Installed Size:  0.05 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages...
downgrade-10.1.0-1-any.pkg.tar.zst failed to download
error: failed retrieving file 'downgrade-10.1.0-1-any.pkg.tar.zst' from disk : expected download size exceeded
warning: failed to retrieve some files
error: failed to commit transaction (download library error)
Errors occurred, no packages were upgraded.

Last edited by NuSkool (2021-12-13 20:09:29)

Xyne · 2021-12-12 19:19:43

NuSkool wrote:

I've tried a few different procedures such as using pacman -Sy before installing the package but it seems nothing so far solves this issue.

Don't do that. It will lead to unsupported partial upgrades and possibly system breakage.

Where is your local AUR repo? On the same system/disk? Where? How have you configured pacman to use the database? Directly via a file:// URL or through an intermediate webserver?
What is the output of e.g. pacman -Sp downgrade when the file is not in your cache?

Are you doing anything weird like trying to use the pacman cache directory as the AUR repo directory?
If you compare the "downloaded" AUR package in the pacman cache to the original, is it the same file? (same size, same checksum, etc).

You can also compare the real file size against the size stored in your AUR repo's database to see if that's the same.

Using a local repo is supported. There must be something wrong with your setup. Take us through all of the steps and commands that you've used to create and use the repo.

NuSkool · 2021-12-12 21:11:37

Don't do that.

Thanks for the reply and heads up, you're right. I didn't bother with all the details around testing if pacsync was somehow an issue leading to using pacman -Sy. I did make sure before testing that downgrade was not pulling in any depends, and followed up with a -Su. So yes, for a brief time my system was in partial upgrade. I didn't explain all this, and that I could fix potential breakage, to stay focused on the topic. I keep pacman-static installed for worse case, have backups, and could use any number of other alternative methods depending on the details to fix a broken system.... Sorry about that.

I'll collect data regarding package checksums and sizes. I don't have it at the moment. I wonder how could the package size could vary, from the time I copy it into the aur cache, to immediately entering it into the aur db? Could it be related to the version being replaced? I could see something going wrong in the copy process from chroot, more than the package changing size during entering the package into the aur db?

What is the output of e.g. pacman -Sp downgrade when the file is not in your cache?

File being the package? I'll get this data as well as I don't currently have it.

The aur cache is not sharing pacmans /var/cache/pacman/pkg cache and is located within my home directory. Build aur packages in a chroot using aurutils, which has it's own pacman aur cache. Copy the package from chroot to my local aur cache. I'm not using the devtools scripts and not building in a clean chroot. I reuse the chroot rather than rebuilding it for each package. I use a systemd-nspawn container for chrooting into rather than booting into for the builds.

I should mention this as well. Now I'm not 100% sure, but I may have started getting these errors around the time of the last pacman update. I can't verify that and have been working with a slight variation of this local aur repo without issues for several years. To be clear, I think I added the chroot building and moved my local aur repo 'around' the same time pacman may have went to 6.0. That being said, I need to gather the data I'm missing before considering a potential pacman issue.

Here's my pacman conf.

$ pacman-conf
[options]
RootDir = /
DBPath = /var/lib/pacman/
CacheDir = /var/cache/pacman/pkg/
CacheDir = /home/NuSkool/aur-builds/repo
HookDir = /etc/pacman.d/hooks/
GPGDir = /etc/pacman.d/gnupg/
LogFile = /var/log/pacman.log
HoldPkg = pacman
HoldPkg = glibc
IgnorePkg =
IgnorePkg =
IgnorePkg =
Architecture = x86_64
Color
CheckSpace
VerbosePkgLists
ParallelDownloads = 5
CleanMethod = KeepInstalled
SigLevel = PackageRequired
SigLevel = PackageTrustedOnly
SigLevel = DatabaseOptional
SigLevel = DatabaseTrustedOnly
LocalFileSigLevel = PackageOptional
LocalFileSigLevel = PackageTrustedOnly
[core]
Usage = All
Server = https://mirrors.ocf.berkeley.edu/archlinux/core/os/x86_64
Server = https://archmirror1.octyl.net/core/os/x86_64
Server = https://mirror.lty.me/archlinux/core/os/x86_64
Server = https://mirror.sfo12.us.leaseweb.net/archlinux/core/os/x86_64
Server = https://zxcvfdsa.com/arch/core/os/x86_64
Server = https://arch.hu.fo/archlinux/core/os/x86_64
Server = https://mirrors.sonic.net/archlinux/core/os/x86_64
Server = https://mirror.phx1.us.spryservers.net/archlinux/core/os/x86_64
Server = https://mirrors.radwebhosting.com/archlinux/core/os/x86_64
Server = https://plug-mirror.rcac.purdue.edu/archlinux/core/os/x86_64
[extra]
Usage = All
Server = https://mirrors.ocf.berkeley.edu/archlinux/extra/os/x86_64
Server = https://archmirror1.octyl.net/extra/os/x86_64
Server = https://mirror.lty.me/archlinux/extra/os/x86_64
Server = https://mirror.sfo12.us.leaseweb.net/archlinux/extra/os/x86_64
Server = https://zxcvfdsa.com/arch/extra/os/x86_64
Server = https://arch.hu.fo/archlinux/extra/os/x86_64
Server = https://mirrors.sonic.net/archlinux/extra/os/x86_64
Server = https://mirror.phx1.us.spryservers.net/archlinux/extra/os/x86_64
Server = https://mirrors.radwebhosting.com/archlinux/extra/os/x86_64
Server = https://plug-mirror.rcac.purdue.edu/archlinux/extra/os/x86_64
[community]
Usage = All
Server = https://mirrors.ocf.berkeley.edu/archlinux/community/os/x86_64
Server = https://archmirror1.octyl.net/community/os/x86_64
Server = https://mirror.lty.me/archlinux/community/os/x86_64
Server = https://mirror.sfo12.us.leaseweb.net/archlinux/community/os/x86_64
Server = https://zxcvfdsa.com/arch/community/os/x86_64
Server = https://arch.hu.fo/archlinux/community/os/x86_64
Server = https://mirrors.sonic.net/archlinux/community/os/x86_64
Server = https://mirror.phx1.us.spryservers.net/archlinux/community/os/x86_64
Server = https://mirrors.radwebhosting.com/archlinux/community/os/x86_64
Server = https://plug-mirror.rcac.purdue.edu/archlinux/community/os/x86_64
[aur-repo]
Usage = All
SigLevel = PackageOptional
SigLevel = PackageTrustAll
SigLevel = DatabaseOptional
SigLevel = DatabaseTrustAll
Server = file:///home/NuSkool/aur-builds/repo

Here's the commands I use to set up the aur repo.

I've scripted the aur repo setup. This is copy paste from the script editing out the vars with the actual values.

	sudo sed -i '$a\#'                         /etc/pacman.conf
	sudo sed -i '$a\# Path to aur.conf'        /etc/pacman.conf
	sudo sed -i '$a\Include = /etc/aur.conf'   /etc/pacman.conf

Results placed in bottom of pacman.conf.

# An example of a custom package repository.  See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#SigLevel = Optional TrustAll
#Server = file:///home/custompkgs
#
# Path to aur.conf
Include = /etc/aur.conf

Here's the file pointed to from my pacman.conf, /etc/aur.conf.

[options]
CacheDir    = /home/NuSkool/aur-builds/repo
CleanMethod = KeepInstalled

[aur-repo]
SigLevel = Optional TrustAll
Server = file:///home/NuSkool/aur-builds/repo

Here's the commands used to set up the aur repo.

	mkdir -p /home/NuSkool/aur-builds/repo
	install -d /home/NuSkool/aur-builds/repo -o NuSkool
	repo-add /home/NuSkool/aur-builds/repo/aur-repo.db.tar.gz
	sudo pacsync aur-repo

Last edited by NuSkool (2021-12-12 21:20:42)

NuSkool · 2021-12-13 01:20:57

OK, I removed downgrade and documented everything before/after reinstalling.

Problem is, is it installed without error this time. I'll still provide the info. If I could get details on what specifically to focus on, I'll monitor it next time the downgrade package is updated, or any aur package that has an update for that matter. I could eliminate collecting any unwanted data and put the requested data collection in a script and run it before/after I update any aur packages.

In system after removing downgrade from the system, aur database, and local aur cache:

$ pacman -Qi downgrade
error: package 'downgrade' was not found


$ sudo pacman -Sp downgrade
error: target not found: downgrade


$ ls -1 /var/lib/pacman/local/ | grep -E '^d|^e'
darkhttpd-1.13-1
dav1d-0.9.2-1
db-5.3.28-5
dbus-1.12.20-1
dbus-glib-0.112-2
dbus-python-1.2.18-1
dconf-0.40.0-1
ddcutil-1.1.0-1
deluge-2.0.4.dev56+g2e466101f-1
deluge-gtk-2.0.4.dev56+g2e466101f-1
desktop-file-utils-0.26-1
device-mapper-2.03.14-2
devtools-20210202-3
dfrs-0.0.7-1
dhcpcd-9.4.1-1
diffutils-3.8-1
djvulibre-3.5.28-3
dkms-3.0.2-1
dmidecode-3.3-1
dmraid-1.0.0.rc16.3-13
dnssec-anchors-20190629-3
dosfstools-4.2-1
double-conversion-3.1.6-1
e2fsprogs-1.46.4-1
eglexternalplatform-1.1-2
egl-wayland-2:1.1.9+r3+g582b2d3-1
elfutils-0.186-1
enca-1.19-4
enchant-2.3.1-2
evince-41.3-1
exiv2-0.27.5-1
exo-4.16.3-1
expac-10-5
expat-2.4.1-1

This is in the chroot aur repo after rebuilding downgrade:

$ pwd
/home/NuSkool/aur-builds/chroot/build


$ tar -axf aur.db.tar.gz downgrade-10.1.0-1    -O | grep -A1 -E 'FILENAME|SIZE|SUM'
%FILENAME%
downgrade-10.1.0-1-any.pkg.tar.zst
--
%CSIZE%
19909
--
%ISIZE%
50757
--
%MD5SUM%
5ebefe7d435b8027b16eb15f24b49c61
--
%SHA256SUM%
afda6e27736fec3aa61f7d4f4a3e2aa2e6826385b31947ebb3617a7f82702eb7


$ md5sum downgrade-10.1.0-1-any.pkg.tar.zst
5ebefe7d435b8027b16eb15f24b49c61  downgrade-10.1.0-1-any.pkg.tar.zst


$ sha256sum downgrade-10.1.0-1-any.pkg.tar.zst
afda6e27736fec3aa61f7d4f4a3e2aa2e6826385b31947ebb3617a7f82702eb7  downgrade-10.1.0-1-any.pkg.tar.zst


$ zcat -lv aur.db.tar.gz
method  crc     date  time           compressed        uncompressed  ratio uncompressed_name
defla 2671afbc Dec 12 16:02                8102               61440  86.8% aur.db.tar


$ stat downgrade-10.1.0-1-any.pkg.tar.zst
  File: downgrade-10.1.0-1-any.pkg.tar.zst
  Size: 19909     	Blocks: 40         IO Block: 4096   regular file
Device: 8,24	Inode: 13108498    Links: 1
Access: (0644/-rw-r--r--)  Uid: ( 1000/    NuSkool)   Gid: ( 1000/    NuSkool)
Access: 2021-12-12 16:02:34.615086378 -0800
Modify: 2021-12-12 16:02:34.341741084 -0800
Change: 2021-12-12 16:02:34.558417232 -0800
 Birth: 2021-12-12 16:02:34.315073251 -0800

In system after downgrade was rebuilt in chroot, placed in /home/NuSkool/aur-builds/repo/, and entered into /home/NuSkool/aur-builds/repo/aur-repo.db

$ pwd
/home/NuSkool/aur-builds/repo


$ zcat -lv aur-repo.db.tar.gz
method  crc     date  time           compressed        uncompressed  ratio uncompressed_name
defla ab57d804 Dec 12 16:02                8090               61440  86.9% aur-repo.db.tar


$ tar -axf aur-repo.db.tar.gz     downgrade-10.1.0-1    -O | grep -A1 -E 'FILENAME|SIZE|SUM'
%FILENAME%
downgrade-10.1.0-1-any.pkg.tar.zst
--
%CSIZE%
19909
--
%ISIZE%
50757
--
%MD5SUM%
5ebefe7d435b8027b16eb15f24b49c61
--
%SHA256SUM%
afda6e27736fec3aa61f7d4f4a3e2aa2e6826385b31947ebb3617a7f82702eb7


$ md5sum downgrade-10.1.0-1-any.pkg.tar.zst
5ebefe7d435b8027b16eb15f24b49c61  downgrade-10.1.0-1-any.pkg.tar.zst


$ sha256sum downgrade-10.1.0-1-any.pkg.tar.zst
afda6e27736fec3aa61f7d4f4a3e2aa2e6826385b31947ebb3617a7f82702eb7  downgrade-10.1.0-1-any.pkg.tar.zst


$ stat downgrade-10.1.0-1-any.pkg.tar.zst
  File: downgrade-10.1.0-1-any.pkg.tar.zst
  Size: 19909     	Blocks: 40         IO Block: 4096   regular file
Device: 8,24	Inode: 12983782    Links: 1
Access: (0644/-rw-r--r--)  Uid: ( 1000/    NuSkool)   Gid: ( 1000/    NuSkool)
Access: 2021-12-12 16:02:35.228446547 -0800
Modify: 2021-12-12 16:02:34.888431671 -0800
Change: 2021-12-12 16:02:34.888431671 -0800
 Birth: 2021-12-12 16:02:34.888431671 -0800


$ pacman -Sl aur-repo | grep downgrade
aur-repo downgrade 10.1.0-1


$ pacman -Si downgrade
Repository      : aur-repo
Name            : downgrade
Version         : 10.1.0-1
Description     : Bash script for downgrading one or more packages to a version in your cache or the A.L.A.
Architecture    : any
URL             : https://github.com/pbrisbin/downgrade
Licenses        : GPL
Groups          : None
Provides        : None
Depends On      : pacman-contrib
Optional Deps   : sudo: for installation via sudo
Conflicts With  : None
Replaces        : None
Download Size   : 19.44 KiB
Installed Size  : 49.57 KiB
Packager        : Unknown Packager
Build Date      : Sun 12 Dec 2021 04:02:24 PM PST
Validated By    : MD5 Sum  SHA-256 Sum


$ pacman -Sp downgrade
file:///home/NuSkool/aur-builds/repo/downgrade-10.1.0-1-any.pkg.tar.zst


$ sudo pacman -S downgrade
[sudo] password for NuSkool: 
resolving dependencies...
looking for conflicting packages...

Package (1)         New Version  Net Change

aur-repo/downgrade  10.1.0-1       0.05 MiB

Total Installed Size:  0.05 MiB

:: Proceed with installation? [Y/n] 


:: Retrieving packages...
 downgrade-10.1.0-1-any                                            19.4 KiB  19.0 MiB/s 00:00 [#######################################################] 100%
(1/1) checking keys in keyring                                                                [#######################################################] 100%
(1/1) checking package integrity                                                              [#######################################################] 100%
(1/1) loading package files                                                                   [#######################################################] 100%
(1/1) checking for file conflicts                                                             [#######################################################] 100%
(1/1) checking available disk space                                                           [#######################################################] 100%
:: Processing package changes...
(1/1) installing downgrade                                                                    [#######################################################] 100%
Optional dependencies for downgrade
    sudo: for installation via sudo [installed]
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...


$ pacman -Q downgrade
downgrade 10.1.0-1


$ ls -1 /var/lib/pacman/local/ | grep -E '^d|^e'
darkhttpd-1.13-1
dav1d-0.9.2-1
db-5.3.28-5
dbus-1.12.20-1
dbus-glib-0.112-2
dbus-python-1.2.18-1
dconf-0.40.0-1
ddcutil-1.1.0-1
deluge-2.0.4.dev56+g2e466101f-1
deluge-gtk-2.0.4.dev56+g2e466101f-1
desktop-file-utils-0.26-1
device-mapper-2.03.14-2
devtools-20210202-3
dfrs-0.0.7-1
dhcpcd-9.4.1-1
diffutils-3.8-1
djvulibre-3.5.28-3
dkms-3.0.2-1
dmidecode-3.3-1
dmraid-1.0.0.rc16.3-13
dnssec-anchors-20190629-3
dosfstools-4.2-1
double-conversion-3.1.6-1
downgrade-10.1.0-1
e2fsprogs-1.46.4-1
eglexternalplatform-1.1-2
egl-wayland-2:1.1.9+r3+g582b2d3-1
elfutils-0.186-1
enca-1.19-4
enchant-2.3.1-2
evince-41.3-1
exiv2-0.27.5-1
exo-4.16.3-1
expac-10-5
expat-2.4.1-1

Last edited by NuSkool (2021-12-13 01:22:59)

Xyne · 2021-12-13 02:04:28

The next time that the problem occurs, compare the csize entry from the downloaded AUR repo database under /var/lib/pacman/sync to the actual file size of the package in the AUR repo dir. I suspect that one of the two was corrupted.

If it's the database that was corrupted, check the original in the AUR repo directory to determine if the corruption occurred when pacman retrieved it.
If both the original and downloaded databases contain incorrect csize values for the package then something is wrong with the creation of the database. Are there any warnings or error messages when you run repo-add to add the package?
If the original contains the correct value then it was somehow corrupted while being retrieved via the file:// url. I would start checking for disk errors in dmesg and the various system logs. Run a full disk check with smartctl too.

If the package is corrupted in the AUR repo dir then recheck the process of building and adding the package to the AUR repo to make sure that nothing is corrupting the package (e.g. accidentally appending data). Check the package archive for errors and extract it to check its contents.
If the package in the AUR repo dir is correct, check the one that pacman downloaded. Compare sizes and checksums. Regardless of the state of the package file in the package cache, I would recommend checking for disk errors in this case too as mentioned above.

NuSkool · 2021-12-13 04:17:38

How would I go about getting the csize of the actual package without relying on data? Where does the csize come from? Is it calculated or measured when the package is built? I poked around in a package and didn't see it listed.

I've written a script to record the csize listed in the aur db in the chroot /var/lib/pacman/sync, where the packages are built, then the same from the db of my local aur repo and save it to file. Seems it should be available in the local aur db to be causing pacman to error?

Are there any warnings or error messages when you run repo-add to add the package?

Not that I've noticed so far. It's only happened a few times and I've not looked into it because pacman -U seemed to bypass the problem.

Check the package archive for errors and extract it to check its contents.

Could you possibly point me to info on how to properly do this?

Xyne · 2021-12-13 05:18:16

NuSkool wrote:

How would I go about getting the csize of the actual package without relying on data? Where does the csize come from? Is it calculated or measured when the package is built? I poked around in a package and didn't see it listed.

The csize is the size of the package archive generated by makepkg, i.e. the file that you pass to repo-add when adding the package to the database.

NuSkool wrote:

I've written a script to record the csize listed in the aur db in the chroot /var/lib/pacman/sync, where the packages are built, then the same from the db of my local aur repo and save it to file. Seems it should be available in the local aur db to be causing pacman to error?

You're building in the chroot's /var/lib/pacman/sync directory? Why? Reading that I realized that I skimmed over your previous posts a bit too lightly when i saw that it was working. Going back I noticed this:

[options]
CacheDir    = /home/NuSkool/aur-builds/repo

If pacman's cache directory is set to the same as the repo's package directory then you may get unexpected behavior if pacman decides to download the file. Normally the package should match the info in the database so pacman should skip the download. However, if for some reason it doesn't then it will try to replace the file with itself. Whether or removes the cached package before trying to download the new one, or simply tries to overwrite it, it won't work. It may be able to resolve file:// urls and detect the collision but I don't know. I don't know if that's related to your issue but I would avoid it, at least until everything else works.

o far. It's only happened a few times and I've not looked into it because pacman -U seemed to bypass the problem.

NuSkool wrote:

Check the package archive for errors and extract it to check its contents.
Could you possibly point me to info on how to properly do this?

The package is just a compressed tar archive. You can export it with e.g.

mkdir pkgfiles
cd pkgfiles
bsdtar -xf /path/to/package

If bsdtar fails to open it, then the file is corrupted. Once it's extracted, you can look at the files in it, but that probably won't be very informative. They should be the same as what you end up with in the pkg directory when first building the package.

NuSkool · 2021-12-13 06:19:15

NuSkool wrote:
I've written a script to record the csize listed in the aur db in the chroot /var/lib/pacman/sync, where the packages are built, then the same from the db of my local aur repo and save it to file. Seems it should be available in the local aur db to be causing pacman to error?
You're building in the chroot's /var/lib/pacman/sync directory? Why? Reading that I realized that I skimmed over your previous posts a bit too lightly when i saw that it was working. Going back I noticed this:

I'm sorry Xyne, it's getting late here and I'm tired. That's really quite the word salad I wrote after rereading it. Let me take another shot at it.

I build AUR packages in the chroot, in buildusers home directory. The chroot local AUR repo is set up in /build directory.

I've written a script to record the data listed in chroots aur repo db located at: /var/lib/pacman/sync/aur.db. because I thought you had suggested it.

The script will also record the data listed in the aur repo db of system I'm having issues on, located at /home/NuSkool/aur-builds/repo/aur-repo.db.tar.gz, and send it to a log file so I can compare it. I have rewritten the script since posting the last time to gather the file name, size and the sha256sum as well.

It seems Pacman has two sync db's for local pacman repos, one located in with other sync db's at /var/lib/pacman/sync, and a copy? within the local repo.
One in /var/lib/pacman/sync is not a tar archive, and the other is a tar.gz archive.

So a really long winded, no, I'm not building packages in the chroot's /var/lib/pacman/sync directory, but I see how you came to that conclusion from what I wrote.

EDIT:

I added to record the 'measured size of the package' along with the above, and wrapped pacman with the script to record upon error. I'll followup with the data when it becomes available.

stat -c %s <package>

This is solved. Hey, look over there, you see than, is that a SSD going bad? Quietly fix's script to add pkgs to db, EVEN when rebuilding, reinstalling same versions. Nothing to see here, move along.

Appreciate the help Xyne.

Last edited by NuSkool (2021-12-13 20:07:00)

Xyne · 2021-12-13 21:29:34

NuSkool wrote:

It seems Pacman has two sync db's for local pacman repos, one located in with other sync db's at /var/lib/pacman/sync, and a copy? within the local repo.
One in /var/lib/pacman/sync is not a tar archive, and the other is a tar.gz archive.

The databases under /var/lib/pacman/sync should all be compressed tar archives, but without the .tar.* extension. The file should match the database created by repo-add, as that is what pacman downloads. Repo-add should create the database with the full file extension (*.db.tar.* or *.files.tar.*) in the repo directory and then create symlinks to those files in the same directory without the extensions (just *.db or *.files). The latter are what pacman downloads, so it's normal to end up with duplicates on the system, with one copy in the repo dir and one in pacman's sync database dir.

The only files that should be in /var/lib/pacman/sync are compressed tar archives with file extensions .db or .files and possibly matching signature files with extensions .db.sig and .files.sig.

NuSkool wrote:

This is solved. Hey, look over there, you see than, is that a SSD going bad? Quietly fix's script to add pkgs to db, EVEN when rebuilding, reinstalling same versions. Nothing to see here, move along.
Appreciate the help Xyne.

I'm glad that you managed to identify the origin of the error. It's too bad that it's a hardware issue.

Arch Linux

#1 2021-12-12 18:28:01

[SOLVED] error: failed xxx.. disk : expected download size exceeded

#2 2021-12-12 19:19:43

Re: [SOLVED] error: failed xxx.. disk : expected download size exceeded

#3 2021-12-12 21:11:37

Re: [SOLVED] error: failed xxx.. disk : expected download size exceeded

#4 2021-12-13 01:20:57

Re: [SOLVED] error: failed xxx.. disk : expected download size exceeded

#5 2021-12-13 02:04:28

Re: [SOLVED] error: failed xxx.. disk : expected download size exceeded

#6 2021-12-13 04:17:38

Re: [SOLVED] error: failed xxx.. disk : expected download size exceeded

#7 2021-12-13 05:18:16

Re: [SOLVED] error: failed xxx.. disk : expected download size exceeded

#8 2021-12-13 06:19:15

Re: [SOLVED] error: failed xxx.. disk : expected download size exceeded

#9 2021-12-13 21:29:34

Re: [SOLVED] error: failed xxx.. disk : expected download size exceeded

Board footer