Creating a bug report/issue
I have searched the existing open and closed issues
Required Information
- DietPi version | G_DIETPI_VERSION_CORE=10
G_DIETPI_VERSION_SUB=5
G_DIETPI_VERSION_RC=2
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’
- Distro version | trixie
- Kernel version | Linux DietPi 6.18.34-current-sunxi64 #1 SMP PREEMPT Mon Jun 1 15:51:08 UTC 2026 aarch64 GNU/Linux
- Architecture | arm64
- SBC model | NanoPi NEO Plus2 (aarch64)
- Power supply used 5V
- SD card used | SanDisk ultra
Additional Information (if applicable)
-
Software title | dietpi
-
Was the software title installed freshly
Can this issue be replicated on a fresh installation of DietPi? yes
-
Bug report ID | d0a798f3-f74c-481b-92a0-f395590d7353
Steps to reproduce
dietpi-update does succeed
apt upgrade will fail after apt update
Expected behaviour
Actual behaviour
Extra details
root@DietPi:~# apt upgrade
Upgrading:
armbian-firmware
Summary:
Upgrading: 1, Installing: 0, Removing: 0, Not Upgrading: 0
1 not fully installed or removed.
Download size: 31.1 MB
Space needed: 1548 kB / 13.4 GB available
Continue? [Y/n]
Get:1 https://dietpi.com/apt all/nanopineoplus2 all armbian-firmware all 26.08.0-trunk-dietpi1 [31.1 MB]
Fetched 31.1 MB in 4s (7102 kB/s)
(Reading database ... 16202 files and directories currently installed.)
Preparing to unpack .../armbian-firmware_26.08.0-trunk-dietpi1_all.deb ...
Unpacking armbian-firmware (26.08.0-trunk-dietpi1) over (26.05.0-trunk-dietpi4) ...
dpkg-deb (subprocess): decompressing archive '/var/cache/apt/archives/armbian-firmware_26.08.0-trunk-dietpi1_all.deb' (size=31062520) member 'data.tar': lzma error: compressed data is corrupt
dpkg-deb: error: <decompress> subprocess returned error exit status 2
dpkg: error processing archive /var/cache/apt/archives/armbian-firmware_26.08.0-trunk-dietpi1_all.deb (--unpack):
cannot copy extracted data for './lib/firmware/brcm/fw_bcm43456c5_ag.bin' to '/lib/firmware/brcm/fw_bcm43456c5_ag.bin.dpkg-new': unexpected end of file or stream
Errors were encountered while processing:
/var/cache/apt/archives/armbian-firmware_26.08.0-trunk-dietpi1_all.deb
Error: Sub-process /usr/bin/dpkg returned an error code (1)
looks the file download was not complete. Hopefully a temp issue.
Can you try following
apt update
apt upgrade
see attached file with log from initial install.
different SD card.
same issue.
maybe this helps locating the issue.
thanks
F
(attachments)
update-upgrade.txt (3.46 KB)
firstlog.txt (8.71 KB)
removing the file
/var/cache/apt/archives/linux-image-current-sunxi64_26.08.0-trunk-dietpi1_arm64.deb
did not solve the issue, it got downloaded again causing the same error.
however running
dpkg -i
/var/cache/apt/archives/linux-image-current-sunxi64_26.08.0-trunk-dietpi1_arm64.deb
did install the package and allowed for further completion of the setup.
Does/did the manual install of the armbian-firmware package work as well?
dpkg -i /var/cache/apt/archives/armbian-firmware_26.08.0-trunk-dietpi1_all.deb
Quite weird, since apt internally does exactly the same. Can you check for kernel errors?
dmesg -l 0,1,2,3
Does/did the manual install of the |armbian-firmware| package work as well?
dpkg -i /var/cache/apt/archives/armbian-firmware_26.08.0-trunk-
dietpi1_all.deb |
i only tried the file that got a complain after the initial root login
and setup.
I quit the setup and did a manual dpkg -i
then closed the session and ssh in again as root.
then the initial setup continued and everything went smooth from then on.
I did have to re-install dietpi as the upgrade from the previous version
got stuck and the machine would not startup again.
I now made a clone from the SD so at least I can start from this point
on instead of going through the complete ritual of editing the
dietpi.txt file.
Quite weird, since |apt| internally does exactly the same. Can you check
for kernel errors?
dmesg -l 0,1,2,3 |
dietpi@DietPi:~$ dmesg -l 0,1,2,3
[ 0.924110] mdio_bus mdio_mux-0.1: MDIO device at address 1 is missing.
[ 0.980749] WCN_ERR: dts node for bt_wake not found
Thanks for the fast response !
.Floris
The armbian-firmware package failed to extract as well based on your logs. But maybe a retry solved that one. If the setup went through, then all packages should be up-to-date.
I thought some I/O or filesystem error, undervoltage, or some OOM kill. The kernel log does not show any such error, but maybe you rebooted in the meantime.
If you face such again, check dmesg -l 0,1,2,3 directly, which then hipefully gives a clue.