Error when uploading ISO image

[wxh98]

When I upload an image, if the upload speed is too fast, the progress will get stuck and an error will occur. However, I can see the traffic change in the Windows Task Manager, and the /var/tmp space is sufficient and the permissions are correct. What could be the problem?Error as shown in the figure。

proxmox-ve: 8.1.0 (running kernel: 6.5.11-7-pve)
pve-manager: 8.1.3 (running version: 8.1.3/b46aac3b42da5d15)
proxmox-kernel-helper: 8.1.0
pve-kernel-6.2: 8.0.5
proxmox-kernel-6.5: 6.5.11-7
proxmox-kernel-6.5.11-7-pve-signed: 6.5.11-7
proxmox-kernel-6.5.11-6-pve-signed: 6.5.11-6
proxmox-kernel-6.2.16-20-pve: 6.2.16-20
proxmox-kernel-6.2: 6.2.16-20
pve-kernel-6.2.16-3-pve: 6.2.16-3
ceph-fuse: 17.2.6-pve1+3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx7
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.0.7
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.1.0
libpve-guest-common-perl: 5.0.6
libpve-http-server-perl: 5.0.5
libpve-network-perl: 0.9.5
libpve-rs-perl: 0.8.7
libpve-storage-perl: 8.0.5
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve4
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.1.2-1
proxmox-backup-file-restore: 3.1.2-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.2
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.1.3
pve-cluster: 8.0.5
pve-container: 5.0.8
pve-docs: 8.1.3
pve-edk2-firmware: 4.2023.08-2
pve-firewall: 5.0.3
pve-firmware: 3.9-1
pve-ha-manager: 4.0.3
pve-i18n: 3.1.5
pve-qemu-kvm: 8.1.2-6
pve-xtermjs: 5.3.0-3
qemu-server: 8.0.10
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.2-pve1

 

[wbk]

Hi wxh98,

Did you ever solve your problem?

I couldn't remember how (or if) I ever uploaded an image for an ISO, but now I needed to and couldn't figure out how. After I added a storage type that accepts ISO images, I did not have any trouble uploading an image. In trying to help you out, I do have trouble trying to match your screenshots with my experience.

1. From where to where do you upload an image?
   1. The screenshot with "Error '0'.." in front hides a lot of information. What I _can_ see, is an ominous c:\fakepath\... ; _is_ it actually fake?
   2. What kind of media backs your storage on Proxmox? Is it on spinning disks via SAS, PCIe flash, an USB stick?
2. What kind of image are you trying to upload?
   1. can you upload any other type or smaller size successfully?
3. Does your infrastructure have IPv4 as well as IPv6, or only IPv6?
4. Is ::ffff:192.168.233.169 the IP of your client machine?
   1. I have trouble placing the source of the screenshot with the timeouts. What do we see here?

I hope you didn't give up, it has been over 3 months after all. If your problem is already solved, even better!


PS: also have a look at : https://forum.proxmox.com/threads/h...le-receiving-the-document.144907/#post-653696

/var/tmp space is sufficient

Could you post the output of df -h?

 

[LaWLi]

I play around with Proxmox and run into the same error.

df -h

Debian GNU/Linux comes with permitted by applicable law root@pve:~# cd /var/trnp root@pve:/var/trnp# df -h    ABSOLUTELY    NO WARRANTY, to the extent
Filesystem    Size    Used    Avail    Use%    Mounted on
udev    929M    0    929M    0%    /dev
trnpf s    193M    1020K    192M    1%    /run
/dev/mapper/pve-root    5.4G    5.1G    0    100%    /
trnpf s    962M    43M    919M    5%    /dev/shrn
trnpf s    5.0M    0    5.0M    0%    /run/lock
efivarfs    256K    27K    225K    11%    /sys/firmware/efi/efivars
/dev/sda4    S9G    52K    34G    1%    /mnt/pve/Speicher-Dir
/dev/sda2    511M    12M    500M    3%    /boot/efi
/dev/fuse    128M    16K    128M    1% /etc/pve
trnpf s
root@pve:/var/trnp# _
193M    0    193M    0%    /run/user/0

My disk

/dev/sda    unknown    partitions    107.37 GB
    /dev/sda 1    partition    BIOS boot    1.03 MB
    /dev/sda2    partition    EFI    536.87 MB
    /dev/sda3    partition    LVM    10.20 GB
    /dev/sda4    partition    ext4    96.63 GB

 

[LaWLi]

ah, it seems, that an uploaded ISO is cached in /temp of root. And if space is empty. the failed upload is not removed from /tmp.
(If I uplad but abord, it does)

 

[Dunuin]

Its stored in /var/tmp which is in contrast to /tmp persistent across reboots. So if you for example want to upload a 8GB ISO to the "local" storage the root filesystem needs at least 2x8=16GB of free space.

Your root filesystem is full, so PVE shouldn't run properly and be in read-only mode. And 5.4GB for the root filesystem is way too small in my opinion. I would use at least 16GB or even better 32GB.

 

[LaWLi]

Yes, I increased the disk size.
The Problem, that the file does not get deleted if aborted. Is there maybe a need for a bug report?
I'm not sure but maybe otherwise also a ticket for pre-check if enough disk space is available is needed (if that's possible).