Error details: Error downloading app update: short write: 0 < 16384

[toms-tech]

Disclaimer

• I have read and understood the disclaimer.

Application version

0.4.6

System version

0..2.5

Device model

JetKVM

Extension model

None

Remote device Hardware

Lenovo P620

Remote device OS

Windows 11

Bug description

Hi there,

When I go into JetKVM and try to upgrade from 0.4.6 to 0.4.8, the download happens, but the system then gives the error message,

Error details: Error downloading app update: short write: 0 < 16384

Not sure if this is a JetKVM device issue or something else.

Thank you,

--Thomas

[IDisposable]

That might be that the JetKVM is out of storage space. Would you like to try a factory reset and see if you can upgrade then?

[toms-tech]

All of my JetKVM's have had this issue. Just rebooting them clears it up.

Here is the df -k from before reboot,

/ # df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 499284 21604 461260 4% /
devtmpfs 102088 0 102088 0% /dev
tmpfs 102176 0 102176 0% /dev/shm
tmpfs 102176 8 102168 0% /tmp
tmpfs 102176 8 102168 0% /run
/dev/block/by-name/userdata
13830232 13813848 0 100% /userdata
/ # uptime
22:03:04 up 85 days, 4:41, 0 users, load average: 9.14, 9.10, 9.03

After reboot,

/ # df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 499284 21604 461260 4% /
devtmpfs 102088 0 102088 0% /dev
tmpfs 102176 0 102176 0% /dev/shm
tmpfs 102176 8 102168 0% /tmp
tmpfs 102176 8 102168 0% /run
/dev/block/by-name/userdata
13830232 13813848 0 100% /userdata
/ # uptime
22:03:04 up 85 days, 4:41, 0 users, load average: 9.14, 9.10, 9.03

Seem's that the last.log is never being trimmed.

/userdata/jetkvm # ls -al
total 13781692
drwxr-xr-x 5 root root 4096 Sep 26 22:01 .
drwxr-xr-x 5 root root 4096 May 17 19:08 ..
drwxr-xr-x 2 root root 4096 Jul 3 17:23 bin
-rw-r--r-- 1 root root 0 May 17 19:08 devmode.enable
drwxr-xr-x 2 root root 4096 Jan 1 2021 images
-rw-r--r-- 1 root root 0 Sep 26 22:01 jetkvm_app.update.unverified
-rw-r--r-- 1 root root 14067945472 Sep 26 22:06 last.log
drwxr-xr-x 2 root root 4096 Jul 2 13:46 ota_save
-rwxr-xr-x 1 root root 44482560 Jul 2 13:46 update_system.tar
/userdata/jetkvm # pwd

A reboot clears out last.log. I also on one of my JetKVM,s did a rm last.log and the update worked.

[toms-tech]

Err, this is the AFTER reboot,

/userdata/jetkvm # df -k
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 499284 21604 461260 4% /
devtmpfs 102088 0 102088 0% /dev
tmpfs 102176 0 102176 0% /dev/shm
tmpfs 102176 8 102168 0% /tmp
tmpfs 102176 8 102168 0% /run
/dev/block/by-name/userdata
13830232 83784 13304652 1% /userdata

[IDisposable]

I noticed a possible issue in the update logic in that it seems to leave the unverified file open even after computing the hash and confirming. I suspect that might prevent the rename (to remove the .unverified extension), which would then stop subsequent attempts to update as well. I have submitted a PR, but have NO idea how to test it :)