I’ve used Balena Etcher to put the latest native PC BIOS Bullseye version onto a SSD. I boot the machine and can conneft fine with Putty etc… I go through the steps of changing the default passwords and then just run the install without selecting any software… Have tried a couple of times but just keep getting this…
Any help or tips would be appreciated… I have DietPi running on 2 raspberry Pis without any issues.
APT install for: amd64-microcode │
│ - Command: apt-get -qq --allow-change-held-packages install amd64-microcode │
│ - Exit code: 100 │
│ - DietPi version: v7.8.2 (MichaIng/master) | HW_MODEL: 21 | HW_ARCH: 10 | DISTRO: 6 │
│ - Image creator: DietPi Core Team │
│ - Pre-image: from scratch │
│ - Error log: │
│ debconf: delaying package configuration, since apt-utils is not installed │
│ Selecting previously unselected package amd64-microcode.^M │
│ (Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(Reading database ... 15%^M(Reading │
│ database ... 20%^M(Reading database ... 25%^M(Reading database ... 30%^M(Reading database ... 35%^M(Reading data │
│ 40%^M(Reading database ... 45%^M(Reading database ... 50%^M(Reading database ... 55%^M(Reading database ... 60%^M│
│ database ... 65%^M(Reading database ... 70%^M(Reading database ... 75%^M(Reading database ... 80%^M(Reading data │
│ 85%^M(Reading database ... 90%^M(Reading database ... 95%^M(Reading database ... 100%^M(Reading database ... 247 │
│ and directories currently installed.)^M │
│ Preparing to unpack .../amd64-microcode_3.20191218.1_amd64.deb ...^M │
│ Unpacking amd64-microcode (3.20191218.1) ...^M │
│ Setting up amd64-microcode (3.20191218.1) ...^M │
│ update-initramfs: deferring update (trigger activated)^M │
│ amd64-microcode: microcode will be updated at next boot^M │
│ Processing triggers for initramfs-tools (0.140) ...^M │
│ ln: failed to create hard link '/boot/initrd.img-5.10.0-9-amd64.dpkg-bak' => '/boot/initrd.img-5.10.0-9-amd64': │
│ Operation not permitted^M │
│ update-initramfs: Generating /boot/initrd.img-5.10.0-9-amd64^M │
│ ^M │
│ gzip: stdout: No space left on device^M │
│ E: mkinitramfs failure gzip 1^M │
│ update-initramfs: failed for /boot/initrd.img-5.10.0-9-amd64 with 1.^M │
│ dpkg: error processing package initramfs-tools (--configure):^M │
│ installed initramfs-tools package post-installation script subprocess returned error exit status 1^M │
│ Errors were encountered while processing:^M │
│ initramfs-tools^M │
│ E: Sub-process /usr/bin/dpkg returned an error code (1)
well your file system is full
gzip: stdout: No space left on device
probably the rootFS partition did not got extended? Can you share following.
lsblk -o name,fstype,label,size,ro,type,mountpoint,partuuid,uuid
df -h
as well the following log files located in /var/tmp/dietpi/logs
dietpi-firstboot.log
dietpi-firstrun-setup.log
fs_partition_resize.log
NAME FSTYPE LABEL SIZE RO TYPE MOUNTPOINT PARTUUID UUID
sda 14.9G 0 disk
├─sda1
│ vfat 128M 0 part /boot 5e6dffe7-01 C3E6-D424
└─sda2
ext4 14.8G 0 part / 5e6dffe7-02 4d7e9d38-16ca-4131-aa23-216cc12c9412
Filesystem Size Used Avail Use% Mounted on
udev 1.7G 0 1.7G 0% /dev
tmpfs 336M 4.9M 331M 2% /run
/dev/sda2 15G 1.3G 13G 9% /
tmpfs 1.7G 0 1.7G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 1.7G 8.0K 1.7G 1% /tmp
tmpfs 50M 56K 50M 1% /var/log
/dev/sda1 127M 82M 45M 66% /boot
Removed /etc/systemd/system/local-fs.target.wants/dietpi-fs_partition_resize.service.
Disk /dev/sda: 14.91 GiB, 16013942784 bytes, 31277232 sectors
Disk model: SanDisk SDSA6MM-
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x5e6dffe7
Old situation:
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 264191 262144 128M c W95 FAT32 (LBA)
/dev/sda2 264192 2623487 2359296 1.1G 83 Linux
/dev/sda2:
New situation:
Disklabel type: dos
Disk identifier: 0x5e6dffe7
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 264191 262144 128M c W95 FAT32 (LBA)
/dev/sda2 264192 31277231 31013040 14.8G 83 Linux
The partition table has been altered.
resize2fs 1.46.2 (28-Feb-2021)
Filesystem at /dev/sda2 is mounted on /; on-line resizing required
old_desc_blocks = 1, new_desc_blocks = 2
The filesystem on /dev/sda2 is now 3876630 (4k) blocks long.
[ INFO ] DietPi-FirstBoot | Setting time zone Europe/London. Please wait...
removed '/etc/localtime'
Current default time zone: 'Europe/London'
Local time is now: Thu Nov 18 10:57:08 GMT 2021.
Universal Time is now: Thu Nov 18 10:57:08 UTC 2021.
[ SUB1 ] DietPi-Set_hardware > eth-forcespeed (disable)
[ OK ] eth-forcespeed disable | Completed
[ OK ] DietPi-Change_hostname | Desired setting in /etc/hosts was already set: 127.0.1.1 DietPi
[ .... ] DietPi-Change_hostname | hostname DietPi
[ OK ] DietPi-Change_hostname | hostname DietPi
[ SUB1 ] DietPi-Set_software > apt-mirror (https://deb.debian.org/debian/)
[ OK ] DietPi-Set_software | Desired setting in /boot/dietpi.txt was already set: CONFIG_APT_DEBIAN_MIRROR=https:>
[ OK ] apt-mirror https://deb.debian.org/debian/ | Completed
removed '/etc/dropbear/dropbear_ecdsa_host_key'
Generating 256 bit ecdsa key, this may take a while...
Public key portion is:
ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBNbEIm2pUs7y8XtkaHuRBK7Lqf0mzlbJBE4RwDLHu6Y>
Fingerprint: sha1!! cd:a2:c9:b8:6f:58:99:68:ca:89:3b:11:10:ca:90:26:6f:d3:13:2d
removed '/etc/dropbear/dropbear_ed25519_host_key'
Generating 256 bit ed25519 key, this may take a while...
Public key portion is:
ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAILorZiuTt4OFNXoGYx/Cf903CJuk3Y+Z/cX/YruKPoXD root@DietPi
Fingerprint: sha1!! 35:5a:ec:58:65:14:64:de:24:5f:59:d2:c4:39:a7:cb:04:7e:47:ef
removed '/etc/dropbear/dropbear_rsa_host_key'
Generating 2048 bit rsa key, this may take a while...
Public key portion is:
ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCg6UkgdtXe6Y2KDGvcgOevzh8ohkp/l3p0PXUISygeEeOPRDodGD45WrEzMahCwXGdEWZDds193Vg>
Fingerprint: sha1!! c5:88:10:df:9c:b6:0f:b3:0b:48:15:52:e1:98:52:dc:12:9f:e3:ad
Initializing machine ID from random generator.
[ SUB1 ] DietPi-Set_hardware > wifimodules (disable)
[ OK ] wifimodules disable | Completed
[ SUB1 ] DietPi-Set_hardware > enableipv6 (enable)
[ OK ] DietPi-Set_hardware | Desired setting in /etc/hosts was already set: ::1 localhost ip6-localhost ip6-loopb>
[ OK ] DietPi-Set_hardware | Desired setting in /etc/hosts was already set: ff02::1 ip6-allnodes
[ OK ] DietPi-Set_hardware | Desired setting in /etc/hosts was already set: ff02::2 ip6-allrouters
[ OK ] DietPi-Set_hardware | Desired setting in /boot/dietpi.txt was already set: CONFIG_ENABLE_IPV6=1
[ OK ] enableipv6 enable | Completed
[ SUB1 ] DietPi-Set_hardware > preferipv4 (enable)
[ OK ] DietPi-Set_hardware | Desired setting in /etc/wgetrc was already set: prefer-family = IPv4
[ OK ] DietPi-Set_hardware | Desired setting in /boot/dietpi.txt was already set: CONFIG_PREFER_IPV4=1
[ OK ] preferipv4 enable | Completed
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth0/7c:d3:0a:19:84:c4
Sending on LPF/eth0/7c:d3:0a:19:84:c4
Sending on Socket/fallback
Created duid "\000\001\000\001)(\356\010|\323\012\031\204\304".
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
DHCPOFFER of 192.168.10.165 from 192.168.10.1
DHCPREQUEST for 192.168.10.165 on eth0 to 255.255.255.255 port 67
DHCPACK of 192.168.10.165 from 192.168.10.1
bound to 192.168.10.165 -- renewal in 34977 seconds.
Removed /etc/systemd/system/multi-user.target.wants/dietpi-firstboot.service.
Step:^[[0m Applying initial first run setup steps
^[[0m^[[0m
^[[J^[[90m[^[[0m^[[33m SUB1 ^[[90m]^[[0m DietPi-Set_software > passwords
^[[0m^[[?1049h^[[22;0;0t^[[1;52r^[[4l^[[?25l^[(B^[[m^[[37m^[[40m^[[1;52r^[[H^[[2J^[[1;1H^[[1m^[[37m^[[44m >
^[[K
^[[?1049l^[[23;0;0t^[[?1049h^[[22;0;0t^[[1;52r^[[4l^[[?25l^[(B^[[m^[[37m^[[40m^[[1;52r^[[H^[[2J^[[1;1H^[[1m^[[37m^[>
^[[K
^[[?1049l^[[23;0;0t^[[0m
^[[J^[[90m[^[[0m^[[32m OK ^[[90m]^[[0m passwords | Completed
^[[0m^[[?1049h^[[22;0;0t^[[1;52r^[[4l^[[?25l^[(B^[[m^[[37m^[[40m^[[1;52r^[[H^[[2J^[[1;1H^[[1m^[[37m^[[44m >
^[[K
^[[?1049l^[[23;0;0t^[[0m
^[[J^[[90m[^[[0m^[[33m SUB1 ^[[90m]^[[0m DietPi-Set_hardware > serialconsole (disable)
^[[0m^[[0m
^[[J^[[90m[^[[0m INFO ^[[90m]^[[0m ^[[90mDietPi-Set_hardware |^[[0m ^[[90mDisabling serial-getty on: /dev/ttyS0
^[[0m^[[0m
^[[J^[[90m[^[[0m ^[[90m]^[[0m ^[[90mDietPi-Set_hardware |^[[0m systemctl disable --now serial-getty@ttyS0^[[0m>
^[[J^[[90m[^[[0m^[[32m OK ^[[90m]^[[0m ^[[90mDietPi-Set_hardware |^[[0m systemctl disable --now serial-getty@ttyS0
^[[0mCreated symlink /etc/systemd/system/serial-getty@ttyS0.service → /dev/null.
^[[0m
^[[J^[[90m[^[[0m INFO ^[[90m]^[[0m ^[[90mDietPi-Set_hardware |^[[0m ^[[90mDisabling serial-getty on: /dev/ttyS1
^[[0m^[[0m
^[[J^[[90m[^[[0m ^[[90m]^[[0m ^[[90mDietPi-Set_hardware |^[[0m systemctl disable --now serial-getty@ttyS1^[[0m>
^[[J^[[90m[^[[0m^[[32m OK ^[[90m]^[[0m ^[[90mDietPi-Set_hardware |^[[0m systemctl disable --now serial-getty@ttyS1
^[[0mCreated symlink /etc/systemd/system/serial-getty@ttyS1.service → /dev/null.
^[[0m
^[[J^[[90m[^[[0m INFO ^[[90m]^[[0m ^[[90mDietPi-Set_hardware |^[[0m ^[[90mDisabling serial-getty on: /dev/ttyS2
^[[0m^[[0m
^[[J^[[90m[^[[0m ^[[90m]^[[0m ^[[90mDietPi-Set_hardware |^[[0m systemctl disable --now serial-getty@ttyS2^[[0m>
^[[J^[[90m[^[[0m^[[32m OK ^[[90m]^[[0m ^[[90mDietPi-Set_hardware |^[[0m systemctl disable --now serial-getty@ttyS2
^[[0mCreated symlink /etc/systemd/system/serial-getty@ttyS2.service → /dev/null.
^[[0m
^[[J^[[90m[^[[0m INFO ^[[90m]^[[0m ^[[90mDietPi-Set_hardware |^[[0m ^[[90mDisabling serial-getty on: /dev/ttyS3
^[[0m^[[0m
^[[J^[[90m[^[[0m ^[[90m]^[[0m ^[[90mDietPi-Set_hardware |^[[0m systemctl disable --now serial-getty@ttyS3^[[0m>
^[[J^[[90m[^[[0m^[[32m OK ^[[90m]^[[0m ^[[90mDietPi-Set_hardware |^[[0m systemctl disable --now serial-getty@ttyS3
^[[0mCreated symlink /etc/systemd/system/serial-getty@ttyS3.service → /dev/null.
^[[0m
^[[J^[[90m[^[[0m^[[32m OK ^[[90m]^[[0m ^[[90mDietPi-Set_hardware |^[[0m Setting in ^[[33m/boot/dietpi.txt^[[0m ad>
^[[0m^[[0m
^[[J^[[90m[^[[0m^[[32m OK ^[[90m]^[[0m serialconsole disable | Completed
^[[0m^[[0m
^[[J^[[90m[^[[0m ^[[90m]^[[0m ^[[90mDietPi-Software |^[[0m mount -o remount /var/log^[[0m^[[2G^[[1;33m. ^[>
^[[J^[[90m[^[[0m^[[32m OK ^[[90m]^[[0m ^[[90mDietPi-Software |^[[0m mount -o remount /var/log
^[[0m^[[0m
^[[J^[[90m[^[[0m^[[33m SUB1 ^[[90m]^[[0m DietPi-Set_software > ntpd-mode (2)
^[[0m^[[0m
^[[J^[[90m[^[[0m ^[[90m]^[[0m ^[[90mDietPi-Set_software |^[[0m systemctl unmask systemd-timesyncd^[[0m^[[2G^[[>
^[[J^[[90m[^[[0m^[[32m OK ^[[90m]^[[0m ^[[90mDietPi-Set_software |^[[0m systemctl unmask systemd-timesyncd
^[[0m^[[0m
^[[J^[[90m[^[[0m ^[[90m]^[[0m ^[[90mDietPi-Set_software |^[[0m systemctl enable systemd-timesyncd^[[0m^[[2G^[[>
^[[J^[[90m[^[[0m^[[32m OK ^[[90m]^[[0m ^[[90mDietPi-Set_software |^[[0m systemctl enable systemd-timesyncd
^[[0m^[[0m
^[[J^[[90m[^[[0m ^[[90m]^[[0m ^[[90mDietPi-Set_software |^[[0m systemctl stop systemd-timesyncd^[[0m^[[2G^[[1;>
^[[J^[[90m[^[[0m^[[32m OK ^[[90m]^[[0m ^[[90mDietPi-Set_software |^[[0m systemctl stop systemd-timesyncd
^[[0m^[[0m
^[[J^[[90m[^[[0m^[[32m OK ^[[90m]^[[0m ^[[90mDietPi-Set_software |^[[0m Setting in ^[[33m/boot/dietpi.txt^[[0m ad>
^[[0m^[[0m
^[[J^[[90m[^[[0m^[[32m OK ^[[90m]^[[0m ntpd-mode 2 | Completed
^[[0m^[[0m
^[[J^[[90m[^[[0m^[[32m OK ^[[90m]^[[0m ^[[90mDietPi-Software |^[[0m Applied initial first run setup steps
^[[0m^[[0m
/dev/sda1 seems very small? But then I’m not super talented with linux and dietpi so I’m not sure how big this is supposed to be…
ah I see. Issue is with BootFS partition. It seems to be to small to extract new kernel. Can you share
ls -la /boot
total 70892
drwxr-xr-x 4 root root 1536 Jan 1 1970 .
drwxr-xr-x 18 root root 4096 Nov 18 10:57 ..
-rwxr-xr-x 1 root root 83 Sep 23 21:35 System.map-5.10.0-8-amd64
-rwxr-xr-x 1 root root 83 Sep 30 20:36 System.map-5.10.0-9-amd64
-rwxr-xr-x 1 root root 236220 Sep 23 21:35 config-5.10.0-8-amd64
-rwxr-xr-x 1 root root 236055 Sep 30 20:36 config-5.10.0-9-amd64
drwxr-xr-x 4 root root 3072 Nov 18 11:13 dietpi
-rwxr-xr-x 1 root root 18092 Aug 14 16:24 dietpi-LICENSE.txt
-rwxr-xr-x 1 root root 14229 Aug 14 16:24 dietpi-README.md
-rwxr-xr-x 1 root root 2955 Aug 15 20:44 dietpi-wifi.txt
-rwxr-xr-x 1 root root 14987 Nov 18 11:13 dietpi.txt
drwxr-xr-x 5 root root 512 Nov 18 11:13 grub
-rwxr-xr-x 1 root root 29199153 Nov 18 11:12 initrd.img-5.10.0-8-amd64
-rwxr-xr-x 1 root root 29204846 Nov 18 11:13 initrd.img-5.10.0-9-amd64
-rwxr-xr-x 1 root root 6820832 Sep 23 21:35 vmlinuz-5.10.0-8-amd64
-rwxr-xr-x 1 root root 6833568 Sep 30 20:36 vmlinuz-5.10.0-9-amd64
MichaIng
could you have a look. Should we increase the BootFS? It seems to be to small to hold current kernel and to extract new one. Or is it possible to clean some of the old files? At least it seems to fail to extract initrd.img-5.10.0-9-amd64. Not sure if we could remove 5.10.0-8 already
It is safe to remove the old kernel, when you reboot directly. I suggest to do:
apt purge linux-image-5.10.0-8-amd64
reboot
And confirm to remove to running kernel.
I’ll update our x86_64 images to not contain a dedicated boot partition. This causes more issues than it solves, especially when no single kernel package is used like on RPi but a meta package, so that multiple kernel versions + related initramfs can be installed concurrently. RPi doesn’t even use an initramfs by default, so there it is not an issue.
Thanks for looking into this guys… In my machine’s current state… What commands or steps should I be doing to resolve the issue? Or is it better just wait for a possible new image without the dedicated boot partition?
try this as stated above
apt purge linux-image-5.10.0-8-amd64
reboot
Thanks! running that appears to resolve the issue… I will continue and hopefully this doesn’t bite me in the ass months down the track and I have to rebuild 
At least the solution will always be the same. When you install a new kernel and the space in /boot isn’t sufficient for some step, either remove the old kernel files manually (the initrd should always be sufficient as it is by far the largest file) or purge the old kernel package, then dpkg --configure -a and reboot.