Hi, not sure if I’m doing what’s needed ehre, but I’ve just attempted a fresh install/upgrade to Bullseye and on installing software ran into issues. I bug report was generated and sent, the reference for which is:
16705d79-7dce-48ec-8e33-75755a2ecf14
Do you then come back to me in this thread?
Many thanks
There is a reason why we have a troubleshooting template in the forum. Because access to bug reports is strictly limited to a very small number of people. Also, bug reports expire after a few days. If you are looking for support from a forum member, you will need to provide all the necessary details.
Apoogies - I wasn’t sure what I was supposed to do with the bug report reference, or how whoever looks at it (DietPi said it had been ‘submitted’) replies.
I’m just re-falshing my SD card so if I experience a similar problem, which on closer inspection appears to be related to the message below, I’ll come back with more details in the required template
E You Don’t Have Enough Free Space in /var/cache/apt/archives
Many thanks
So apperently you don’t have enough free space on your device to finish the installation. 
What kind of storage do you use and how large is it?
64Gb SD card.
I can boot up the system - it’s when I try and add software. It’s the same SD card that was working fine with Buster 
Can you share the output of
df -h
ls -lah -R /var/cache/apt/
The system said to use the following in a bug report:
Linux DietPi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linuxapt-get -y --allow-change-held-packages install plexmediaserverE: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.
Did the dpkg --configure -a command and got the following"
root@DietPi:~# dpkg --configure -a
Setting up perl-modules-5.32 (5.32.1-4+deb11u2) ...
Setting up binutils-common:arm64 (2.35.2-2) ...
Setting up libctf-nobfd0:arm64 (2.35.2-2) ...
**dpkg:** dependency problems prevent configuration of binutils:
binutils depends on binutils-aarch64-linux-gnu (= 2.35.2-2); however:
Package binutils-aarch64-linux-gnu is not installed.
**dpkg:** error processing package binutils (--configure):
dependency problems - leaving unconfigured
**dpkg:** dependency problems prevent configuration of libmono-system-core4.0-cil:
libmono-system-core4.0-cil depends on libmono-corlib4.5-cil (>= 4.0.0~alpha1); however:
Package libmono-corlib4.5-cil is not installed.
libmono-system-core4.0-cil depends on libmono-system4.0-cil (>= 4.0.0~alpha1); however:
Package libmono-system4.0-cil is not installed.
libmono-system-core4.0-cil depends on mono-runtime-common (>= 6.12.0.200); however:
Package mono-runtime-common is not installed.
**dpkg:** error processing package libmono-system-core4.0-cil (--configure):
dependency problems - leaving unconfigured
**dpkg:** dependency problems prevent configuration of perl:
perl depends on libperl5.32 (= 5.32.1-4+deb11u2); however:
Package libperl5.32:arm64 is not installed.
**dpkg:** error processing package perl (--configure):
dependency problems - leaving unconfigured
**dpkg:** dependency problems prevent configuration of mono-runtime-sgen:
mono-runtime-sgen depends on mono-runtime-common (= 6.12.0.200-0xamarin2+debian10b1); however:
Package mono-runtime-common is not installed.
**dpkg:** error processing package mono-runtime-sgen (--configure):
dependency problems - leaving unconfigured
Setting up libbinutils:arm64 (2.35.2-2) ...
**dpkg:** dependency problems prevent configuration of mono-runtime:
mono-runtime depends on mono-runtime-sgen (= 6.12.0.200-0xamarin2+debian10b1); however:
Package mono-runtime-sgen is not configured yet.
**dpkg:** error processing package mono-runtime (--configure):
dependency problems - leaving unconfigured
Setting up libgdbm6:arm64 (1.19-2) ...
Setting up libctf0:arm64 (2.35.2-2) ...
Setting up libgdbm-compat4:arm64 (1.19-2) ...
Processing triggers for libc-bin (2.31-13+rpt2+rpi1+deb11u7) ...
Errors were encountered while processing:
binutils
libmono-system-core4.0-cil
perl
mono-runtime-sgen
mono-runtime
root@DietPi:~# df -h
ls -lah -R /var/cache/apt/
Filesystem Size Used Avail Use% Mounted on
/dev/root 655M 570M 37M 94% /
devtmpfs 1.9G 0 1.9G 0% /dev
tmpfs 1.9G 0 1.9G 0% /dev/shm
tmpfs 769M 8.5M 761M 2% /run
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 1.9G 0 1.9G 0% /tmp
tmpfs 50M 12K 50M 1% /var/log
/dev/mmcblk0p1 127M 33M 95M 26% /boot
/var/cache/apt/:
total 28K
drwxr-xr-x 3 root root 4.0K Jan 22 23:06 .
drwxr-xr-x 6 root root 4.0K Jan 22 23:06 ..
drwxr-xr-x 3 root root 20K Feb 2 14:53 archives
/var/cache/apt/archives:
total 28K
drwxr-xr-x 3 root root 20K Feb 2 14:53 .
drwxr-xr-x 3 root root 4.0K Jan 22 23:06 ..
-rw-r----- 1 root root 0 Feb 2 14:38 lock
drwx------ 2 _apt root 4.0K Feb 2 14:47 partial
/var/cache/apt/archives/partial:
total 24K
drwx------ 2 _apt root 4.0K Feb 2 14:47 .
drwxr-xr-x 3 root root 20K Feb 2 14:53 ..
You have not enough sapce left:
/dev/root 655M 570M 37M 94% /
Please use dietpi-drive_manager to increase the file system, your root partition has just a size of 700MB .
So sorry for being such a Noob, but where/how in drive manager do I do this?
I’ve gone here and changed the Reserved Blocks value from 34 to 342 (which is said was the max)
/ : /dev/mmcblk0p2 | ext4 | Capacity: 654.6M | Used: 569.9M (87%)
I’ve also tried the Resize option, but neither is having the desired effect:
root@DietPi:~# df -h
ls -lah -R /var/cache/apt/
Filesystem Size Used Avail Use% Mounted on
/dev/root 655M 570M 0 100% /
devtmpfs 1.9G 0 1.9G 0% /dev
tmpfs 1.9G 0 1.9G 0% /dev/shm
tmpfs 769M 8.5M 761M 2% /run
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 1.9G 0 1.9G 0% /tmp
tmpfs 50M 8.0K 50M 1% /var/log
/dev/mmcblk0p1 127M 33M 95M 26% /boot
/var/cache/apt/:
total 28K
drwxr-xr-x 3 root root 4.0K Jan 22 23:06 .
drwxr-xr-x 6 root root 4.0K Jan 22 23:06 ..
drwxr-xr-x 3 root root 20K Feb 2 14:53 archives
/var/cache/apt/archives:
total 28K
drwxr-xr-x 3 root root 20K Feb 2 14:53 .
drwxr-xr-x 3 root root 4.0K Jan 22 23:06 ..
-rw-r----- 1 root root 0 Feb 2 14:38 lock
drwx------ 2 _apt root 4.0K Feb 2 14:47 partial
/var/cache/apt/archives/partial:
total 24K
drwx------ 2 _apt root 4.0K Feb 2 14:47 .
drwxr-xr-x 3 root root 20K Feb 2 14:53 ..
Do you even know what the reserved blocks are when you say, you are a noob?
Idk if you f**ked up now more, you can try to reboot and see.
How to resize:
Run dietpi-drive_manager, select / : /dev/mmcblk0p2, then select Resize.
if this does not work please share the output of
lsblk
lsblk -o name,fstype,label,size,ro,type,mountpoint,partuuid,uuid
Better use following
lsblk -o name,fstype,label,size,ro,type,mountpoint,partuuid,uuid
will give it a go.
Fair point on the reserved blocks point - as a Noob I thought it looked as though that’s were I should ake changes 
Still not behaving as required.
Here’s the output from
lsblk -o name,fstype,label,size,ro,type,mountpoint,partuuid,uuid
NAME FSTYPE LABEL SIZE RO TYPE MOUNTPOINT PARTUUID UUID
mmcblk0
│ 59.7G 0 disk
├─mmcblk0p1
│ vfat 128M 0 part /boot f8a5f4a0-01 2103-0375
└─mmcblk0p2
ext4 684.4M 0 part / f8a5f4a0-02 261ba0e4-bac2-4a31-a9a8-dc6c846a81df
Hmm, there was no error or message when you ran the resize function from dietpi-drive_manager?
Did you reboot the device after you applied the resize?
no error message from the Resize function, and the reboot was a requirement.
I reflashed my SD card (got worried the reserved block thing mnay have messed things up).
Got the same issues as before. Have run the Resize again, but still getting a tiny amount of space:
root@DietPi:~# df -h
ls -lah -R /var/cache/apt/
Filesystem Size Used Avail Use% Mounted on
/dev/root 655M 615M 0 100% /
devtmpfs 1.9G 0 1.9G 0% /dev
tmpfs 1.9G 0 1.9G 0% /dev/shm
tmpfs 769M 8.5M 761M 2% /run
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 1.9G 0 1.9G 0% /tmp
tmpfs 50M 0 50M 0% /var/log
/dev/mmcblk0p1 127M 33M 95M 26% /boot
/var/cache/apt/:
total 12K
drwxr-xr-x 3 root root 4.0K Jan 22 23:06 .
drwxr-xr-x 6 root root 4.0K Jan 22 23:06 ..
drwxr-xr-x 3 root root 4.0K Feb 2 17:16 archives
/var/cache/apt/archives:
total 12K
drwxr-xr-x 3 root root 4.0K Feb 2 17:16 .
drwxr-xr-x 3 root root 4.0K Jan 22 23:06 ..
-rw-r----- 1 root root 0 Feb 2 17:16 lock
drwx------ 2 _apt root 4.0K Feb 2 17:16 partial
/var/cache/apt/archives/partial:
total 8.0K
drwx------ 2 _apt root 4.0K Feb 2 17:16 .
drwxr-xr-x 3 root root 4.0K Feb 2 17:16 ..
root@DietPi:~#
The lsblk -o name,fstype,label,size,ro,type,mountpoint,partuuid,uuid command is pulling the same results as before
Can you share
cat /var/tmp/dietpi/logs/fs_partition_resize.log
ls /dietpi_skip_partition_resize
and run Check & Repair for the ext4 partion with dietpi-drive_manager please.
Hi there, this is what I got:
Removed /etc/systemd/system/local-fs.target.wants/dietpi-fs_partition_resize.service.
[ INFO ] Detected root drive /dev/mmcblk0 with root partition 2
[ INFO ] No DietPi setup partition found, last partition is: " "
lsblk: unknown column: MOUNTPOINTS
Removed /etc/systemd/system/local-fs.target.wants/dietpi-fs_partition_resize.service.
[ INFO ] Detected root drive /dev/mmcblk0 with root partition 2
[ INFO ] No DietPi setup partition found, last partition is: "ext4 "
lsblk: unknown column: MOUNTPOINTS
ls: cannot access '/dietpi_skip_partition_resize': No such file or directory
ran the Check & Repair process but still getting:
Filesystem Size Used Avail Use% Mounted on
/dev/root 655M 615M 0 100% /
devtmpfs 1.9G 0 1.9G 0% /dev
tmpfs 1.9G 0 1.9G 0% /dev/shm
tmpfs 769M 8.5M 761M 2% /run
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 1.9G 0 1.9G 0% /tmp
tmpfs 50M 8.0K 50M 1% /var/log
/dev/mmcblk0p1 127M 33M 95M 26% /boot
/var/cache/apt/:
total 12K
drwxr-xr-x 3 root root 4.0K Jan 22 23:06 .
drwxr-xr-x 6 root root 4.0K Jan 22 23:06 ..
drwxr-xr-x 3 root root 4.0K Feb 2 17:16 archives
/var/cache/apt/archives:
total 12K
drwxr-xr-x 3 root root 4.0K Feb 2 17:16 .
drwxr-xr-x 3 root root 4.0K Jan 22 23:06 ..
-rw-r----- 1 root root 0 Feb 2 17:16 lock
drwx------ 2 _apt root 4.0K Feb 2 17:16 partial
/var/cache/apt/archives/partial:
total 8.0K
drwx------ 2 _apt root 4.0K Feb 2 17:16 .
drwxr-xr-x 3 root root 4.0K Feb 2 17:16 ..
root@DietPi:~#
For some reason the script does not detect you partitions as a DietPi installation. Also this message is odd: lsblk: unknown column: MOUNTPOINTS
Any ideas @Joulinar @MichaIng ?
Maybe you can try with another SD card, if you have time and are willing to do so?
You also used this image, right?
DietPi_RPi-ARMv8-Bullseye.img.xz