Closed MDAR closed 2 years ago
Many thanks for your report.
I checked your bug report:
dpkg: error processing archive /tmp/apt-dpkg-install-mgmNpt/041-libllvm11_1%3a11.0.1-2_arm64.deb (--unpack):
cannot copy extracted data for './usr/lib/aarch64-linux-gnu/libLLVM-11.so.1' to '/usr/lib/aarch64-linux-gnu/libLLVM-11.so.1.dpkg-new': failed to write (No space left on device)
...
dpkg: error processing archive /tmp/apt-dpkg-install-mgmNpt/045-libgl1-mesa-dri_20.3.5-1_arm64.deb (--unpack):
cannot copy extracted data for './usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so' to '/usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so.dpkg-new': failed to write (No space left on device)
...
Can you check the free filesystem space, please:
df -h /
Well spotted.
When I'm finished what I'm doing, I'll drop in another eMMC card and try that
But please verify that the used space really is 16 GiB already. It would be also possible that the partition/filesystem expansion failed for some reason. df -h /
would reveal this. This could be easily solved.
Yep
There's the problem
root@DietPi:~# df -h /
Filesystem Size Used Avail Use% Mounted on
/dev/mmcblk0p2 740M 577M 149M 80% /
and for completeness
root@DietPi:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 1894152 0 1894152 0% /dev
tmpfs 380112 10272 369840 3% /run
/dev/mmcblk0p2 757680 590456 152092 80% /
tmpfs 1900556 0 1900556 0% /dev/shm
tmpfs 5120 0 5120 0% /run/lock
tmpfs 4096 0 4096 0% /sys/fs/cgroup
tmpfs 1900544 0 1900544 0% /tmp
tmpfs 51200 52 51148 1% /var/log
/dev/mmcblk0p1 261868 23492 238376 9% /boot
and for clarity
This is using a brand new 16GB eMMC card (not one I've used previously today) and a new Odroid C4 board, with the Image I downloaded this afternoon
Indeed, can you check:
cat /var/tmp/dietpi/logs/fs_partition_resize.log
To expand it:
sfdisk --no-reread --no-tell-kernel -fN2 /dev/mmcblk0 <<< ',+'
partprobe /dev/mmcblk0
sleep 0.5
resize2fs /dev/mmcblk0p2
Wow, that was a fast reply.
Thanks.
root@DietPi:~# cat /var/tmp/dietpi/logs/fs_partition_resize.log
Removed /etc/systemd/system/local-fs.target.wants/dietpi-fs_partition_resize.service.
Disk /dev/mmcblk0: 14.56 GiB, 15634268160 bytes, 30535680 sectors
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: 0x03823826
Old situation:
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 2048 526335 524288 256M e W95 FAT16 (LBA)
/dev/mmcblk0p2 526336 2039567 1513232 738.9M 83 Linux
/dev/mmcblk0p2:
New situation:
Disklabel type: dos
Disk identifier: 0x03823826
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 2048 526335 524288 256M e W95 FAT16 (LBA)
/dev/mmcblk0p2 526336 30535679 30009344 14.3G 83 Linux
The partition table has been altered.
resize2fs 1.46.2 (28-Feb-2021)
resize2fs: No space left on device While checking for on-line resizing support
Filesystem at /dev/mmcblk0p2 is mounted on /; on-line resizing required
old_desc_blocks = 1, new_desc_blocks = 1
I'm not sure I did the right thing next.
I did try to copy your instructions into a script and run it, but got an error saying "Redirection expected"
So out of sheer devilment, I pasted your instructions into the command line and pressed enter
I got this
root@DietPi:/opt# sfdisk --no-reread --no-tell-kernel -fN2 /dev/mmcblk0 <<< ',+'
partprobe /dev/mmcblk0
sleep 0.5
resize2fs /dev/mmcblk0p2
Disk /dev/mmcblk0: 14.56 GiB, 15634268160 bytes, 30535680 sectors
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: 0x03823826
Old situation:
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 2048 526335 524288 256M e W95 FAT16 (LBA)
/dev/mmcblk0p2 526336 30535679 30009344 14.3G 83 Linux
/dev/mmcblk0p2:
New situation:
Disklabel type: dos
Disk identifier: 0x03823826
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 2048 526335 524288 256M e W95 FAT16 (LBA)
/dev/mmcblk0p2 526336 30535679 30009344 14.3G 83 Linux
The partition table has been altered.
resize2fs 1.46.2 (28-Feb-2021)
Filesystem at /dev/mmcblk0p2 is mounted on /; on-line resizing required
old_desc_blocks = 1, new_desc_blocks = 1
resize2fs: No space left on device While checking for on-line resizing support
and just out of curiosity, I ran the df -h /
command
root@DietPi:/opt# df -h /
Filesystem Size Used Avail Use% Mounted on
/dev/mmcblk0p2 740M 576M 150M 80% /
Curiosity will be the death of me
I ran your
systemctl start dietpi-fs_partition_resize.service
this added a repeat of the entries in the resize log
resize2fs: No space left on device While checking for on-line resizing support
I remember the exact same happened on the legacy Odroid C2 image: #5008 No idea where this is coming from, probably it has to do with the journal recreation we do, but it never was an issue with any other image and the modern Odroid images. I repacked the Odroid C4 image yesterday to add some kernel command-line parameter required for Docker to work, and other applications which require some cgroupv2 features that this old kernel does not support: https://github.com/MichaIng/DietPi/issues/5269#issuecomment-1038150039 I remember it become a little smaller. While 20% and more free space look pretty sufficient for any action, probably some specific part became too small for this kernel to perform a filesystem resize somehow.
I'll now work on the new C4 image. Working on images anyway currently. Let's see how fast I can set this up based on the Odroid N2 work that has been done already.
If there is anything I can do to help, please just ask.
I'm happy to give you remote access to a machine if that helps you.
FYI
fdisk /dev/mmcblk0p2
followed by p
returns this
Welcome to fdisk (util-linux 2.36.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
The device contains 'ext4' signature and it will be removed by a write command. See fdisk(8) man page and --wipe option for more details.
Device does not contain a recognized partition table.
Created a new DOS disklabel with disk identifier 0x04224d6c.
Command (m for help): p
Disk /dev/mmcblk0p2: 14.31 GiB, 15364784128 bytes, 30009344 sectors
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: 0x04224d6c
and for mmcblk0p1 returns this
Disk /dev/mmcblk0p1: 256 MiB, 268435456 bytes, 524288 sectors
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: 0x01b14692
FYI
Just thought I'd see what happens now if I tried to add Chromium, Apache and openSSH
It still failed at the xfont-base x11-server-utils x11-util etc stage
root@DietPi:/opt# dietpi-software
[ OK ] DietPi-Software | Initialised database
[ OK ] DietPi-Software | Reading database
[ OK ] DietPi-Software | Setting in /boot/dietpi/.installed adjusted: INDEX_WEBSERVER=0
[ OK ] DietPi-Software | Setting in /boot/dietpi/.installed adjusted: INDEX_BROWSER=-2
[ OK ] DietPi-Software | DietPi-Userdata validation: /mnt/dietpi_userdata
DietPi-Software
─────────────────────────────────────────────────────
Step: Checking for conflicts and missing inputs
DietPi-Software
─────────────────────────────────────────────────────
Step: Checking for prerequisite software
[ INFO ] DietPi-Software | OpenSSH Client will be installed
[ OK ] DietPi-Software | Checking network connectivity
[ OK ] DietPi-Software | Checking DNS resolver
[ OK ] Network time sync | Completed
[ SUB1 ] DietPi-Services > unmask
[ OK ] DietPi-Services | unmask : cron
[ SUB1 ] DietPi-Services > stop
[ OK ] DietPi-Services | stop : cron
[ INFO ] DietPi-Software | APT update, please wait...
Hit:1 https://deb.debian.org/debian bullseye InRelease
Hit:2 https://deb.debian.org/debian bullseye-updates InRelease
Hit:3 https://deb.debian.org/debian-security bullseye-security InRelease
Hit:4 https://deb.debian.org/debian bullseye-backports InRelease
Hit:5 https://dietpi.com/meveric bullseye InRelease
Hit:6 https://dietpi.com/meveric all InRelease
Reading package lists...
[ OK ] DietPi-Software | APT update
[ OK ] DietPi-Software | mkdir -p /mnt/dietpi_userdata/Music /mnt/dietpi_userdata/Pictures /mnt/dietpi_userdata/Video /mnt/dietpi_userdata/downloads /var/www /opt /usr/local/bin
[ OK ] DietPi-Software | chown dietpi:dietpi /mnt/dietpi_userdata/Music /mnt/dietpi_userdata/Pictures /mnt/dietpi_userdata/Video /mnt/dietpi_userdata/downloads
[ OK ] DietPi-Software | chmod 0775 /mnt/dietpi_userdata/Music /mnt/dietpi_userdata/Pictures /mnt/dietpi_userdata/Video /mnt/dietpi_userdata/downloads
DietPi-Software
─────────────────────────────────────────────────────
Step: Installing OpenSSH Client: Feature-rich SSH, SFTP and SCP client
[ INFO ] DietPi-Software | APT install for: openssh-client, please wait...
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package libedit2:arm64.
(Reading database ... 15668 files and directories currently installed.)
Preparing to unpack .../libedit2_3.1-20191231-2+b1_arm64.deb ...
Unpacking libedit2:arm64 (3.1-20191231-2+b1) ...
Selecting previously unselected package libcbor0:arm64.
Preparing to unpack .../libcbor0_0.5.0+dfsg-2_arm64.deb ...
Unpacking libcbor0:arm64 (0.5.0+dfsg-2) ...
Selecting previously unselected package libfido2-1:arm64.
Preparing to unpack .../libfido2-1_1.6.0-2_arm64.deb ...
Unpacking libfido2-1:arm64 (1.6.0-2) ...
Selecting previously unselected package openssh-client.
Preparing to unpack .../openssh-client_1%3a8.4p1-5_arm64.deb ...
Unpacking openssh-client (1:8.4p1-5) ...
Setting up libedit2:arm64 (3.1-20191231-2+b1) ...
Setting up libcbor0:arm64 (0.5.0+dfsg-2) ...
Setting up libfido2-1:arm64 (1.6.0-2) ...
Setting up openssh-client (1:8.4p1-5) ...
Processing triggers for libc-bin (2.31-13+deb11u2) ...
[ OK ] DietPi-Software | APT install for: openssh-client
DietPi-Software
─────────────────────────────────────────────────────
Step: Installing OpenSSH Server: Feature-rich SSH server with SFTP and SCP support
[ OK ] DietPi-Software | systemctl stop dropbear
[ INFO ] DietPi-Software | APT install for: openssh-server, please wait...
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package ucf.
(Reading database ... 15739 files and directories currently installed.)
Preparing to unpack .../archives/ucf_3.0043_all.deb ...
Moving old data out of the way
Unpacking ucf (3.0043) ...
Selecting previously unselected package libwrap0:arm64.
Preparing to unpack .../libwrap0_7.6.q-31_arm64.deb ...
Unpacking libwrap0:arm64 (7.6.q-31) ...
Selecting previously unselected package openssh-sftp-server.
Preparing to unpack .../openssh-sftp-server_1%3a8.4p1-5_arm64.deb ...
Unpacking openssh-sftp-server (1:8.4p1-5) ...
Selecting previously unselected package runit-helper.
Preparing to unpack .../runit-helper_2.10.3_all.deb ...
Unpacking runit-helper (2.10.3) ...
Selecting previously unselected package openssh-server.
Preparing to unpack .../openssh-server_1%3a8.4p1-5_arm64.deb ...
Unpacking openssh-server (1:8.4p1-5) ...
Setting up runit-helper (2.10.3) ...
Setting up openssh-sftp-server (1:8.4p1-5) ...
Setting up libwrap0:arm64 (7.6.q-31) ...
Setting up ucf (3.0043) ...
Setting up openssh-server (1:8.4p1-5) ...
Creating config file /etc/ssh/sshd_config with new version
Creating SSH2 RSA key; this may take some time ...
3072 SHA256:2saGVmzeah3WIVdBAZLQzKRCSaVvIZfBhFYCrEqWa4M root@DietPi (RSA)
Creating SSH2 ECDSA key; this may take some time ...
256 SHA256:bPaC22EtyrSMNf5bEGSzXLpIhFC0p5Ce718oFVr06Lo root@DietPi (ECDSA)
Creating SSH2 ED25519 key; this may take some time ...
256 SHA256:gdPk1bwjZgXsCNePaT3+JQmqK+sh43mymsy6ohyVijg root@DietPi (ED25519)
Created symlink /etc/systemd/system/sshd.service → /lib/systemd/system/ssh.service.
Created symlink /etc/systemd/system/multi-user.target.wants/ssh.service → /lib/systemd/system/ssh.service.
rescue-ssh.target is a disabled or a static unit, not starting it.
Processing triggers for libc-bin (2.31-13+deb11u2) ...
[ OK ] DietPi-Software | APT install for: openssh-server
[ OK ] DietPi-Software | Comment in /etc/ssh/sshd_config converted to setting: PermitRootLogin yes
[ OK ] DietPi-Software | systemctl enable ssh
DietPi-Software
─────────────────────────────────────────────────────
Step: Uninstalling Dropbear: Lightweight SSH server
[ INFO ] DietPi-Software | APT purge for: dropbear*, please wait...
(Reading database ... 15852 files and directories currently installed.)
Removing dropbear (2020.81-3) ...
Removing dropbear-bin (2020.81-3) ...
Removing libtomcrypt1:arm64 (1.18.2-5) ...
Removing libtommath1:arm64 (1.2.0-6) ...
Processing triggers for libc-bin (2.31-13+deb11u2) ...
(Reading database ... 15813 files and directories currently installed.)
Purging configuration files for dropbear (2020.81-3) ...
[ OK ] DietPi-Software | APT purge for: dropbear*
DietPi-Software
─────────────────────────────────────────────────────
Step: Finalising uninstall
[ INFO ] DietPi-Software | APT autopurge, please wait...
[ OK ] DietPi-Software | APT autopurge
[ OK ] DietPi-Software | systemctl daemon-reload
DietPi-Software
─────────────────────────────────────────────────────
Step: Uninstall completed
DietPi-Software
─────────────────────────────────────────────────────
Step: Finalising install
[ OK ] DietPi-Software | systemctl daemon-reload
2022-02-14 18:23:05 [ INFO ] DietPi-RAMlog | Storing /var/log to /var/tmp/dietpi/logs/dietpi-ramlog_store...
2022-02-14 18:23:05 [ OK ] DietPi-RAMlog | Stored /var/log to /var/tmp/dietpi/logs/dietpi-ramlog_store.
[ SUB1 ] DietPi-Services > dietpi_controlled
[ OK ] DietPi-Services | dietpi_controlled : cron
DietPi-Software
─────────────────────────────────────────────────────
Step: Install completed
[ OK ] DietPi-Survey | Sending survey data
[ SUB1 ] DietPi-Services > restart
[ OK ] DietPi-Services | restart : cron
[ INFO ] DietPi-Software | Starting installed services, not controlled by DietPi-Services
[ OK ] DietPi-Software | systemctl start ssh
root@DietPi:/opt# dietpi-software
[ OK ] DietPi-Software | Initialised database
[ OK ] DietPi-Software | Reading database
[ OK ] DietPi-Software | DietPi-Userdata validation: /mnt/dietpi_userdata
DietPi-Software
─────────────────────────────────────────────────────
Step: Checking for conflicts and missing inputs
DietPi-Software
─────────────────────────────────────────────────────
Step: Checking for prerequisite software
[ INFO ] DietPi-Software | ALSA will be installed
[ INFO ] DietPi-Software | X.Org X Server will be installed
[ OK ] DietPi-Software | Checking network connectivity
[ OK ] DietPi-Software | Checking DNS resolver
[ OK ] Network time sync | Completed
[ SUB1 ] DietPi-Services > unmask
[ OK ] DietPi-Services | unmask : cron
[ SUB1 ] DietPi-Services > stop
[ OK ] DietPi-Services | stop : cron
[ INFO ] DietPi-Software | APT update, please wait...
Hit:1 https://deb.debian.org/debian bullseye InRelease
Hit:2 https://deb.debian.org/debian bullseye-updates InRelease
Hit:3 https://deb.debian.org/debian-security bullseye-security InRelease
Hit:4 https://deb.debian.org/debian bullseye-backports InRelease
Hit:5 https://dietpi.com/meveric bullseye InRelease
Hit:6 https://dietpi.com/meveric all InRelease
Reading package lists...
[ OK ] DietPi-Software | APT update
[ OK ] DietPi-Software | mkdir -p /mnt/dietpi_userdata/Music /mnt/dietpi_userdata/Pictures /mnt/dietpi_userdata/Video /mnt/dietpi_userdata/downloads /var/www /opt /usr/local/bin
[ OK ] DietPi-Software | chown dietpi:dietpi /mnt/dietpi_userdata/Music /mnt/dietpi_userdata/Pictures /mnt/dietpi_userdata/Video /mnt/dietpi_userdata/downloads
[ OK ] DietPi-Software | chmod 0775 /mnt/dietpi_userdata/Music /mnt/dietpi_userdata/Pictures /mnt/dietpi_userdata/Video /mnt/dietpi_userdata/downloads
DietPi-Software
─────────────────────────────────────────────────────
Step: Installing ALSA: Advanced Linux Sound Architecture
[ SUB1 ] DietPi-Set_hardware > soundcard (default)
[ INFO ] DietPi-Set_hardware | Checking for required APT packages: alsa-utils
[ INFO ] DietPi-Set_hardware | APT update, please wait...
Hit:1 https://deb.debian.org/debian bullseye InRelease
Hit:2 https://deb.debian.org/debian bullseye-updates InRelease
Hit:3 https://deb.debian.org/debian-security bullseye-security InRelease
Hit:4 https://deb.debian.org/debian bullseye-backports InRelease
Hit:5 https://dietpi.com/meveric bullseye InRelease
Hit:6 https://dietpi.com/meveric all InRelease
Reading package lists...
[ OK ] DietPi-Set_hardware | APT update
[ INFO ] DietPi-Set_hardware | APT install for: alsa-utils, please wait...
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package libasound2-data.
(Reading database ... 15808 files and directories currently installed.)
Preparing to unpack .../0-libasound2-data_1.2.4-1.1_all.deb ...
Unpacking libasound2-data (1.2.4-1.1) ...
Selecting previously unselected package libasound2:arm64.
Preparing to unpack .../1-libasound2_1.2.4-1.1_arm64.deb ...
Unpacking libasound2:arm64 (1.2.4-1.1) ...
Selecting previously unselected package libatopology2:arm64.
Preparing to unpack .../2-libatopology2_1.2.4-1.1_arm64.deb ...
Unpacking libatopology2:arm64 (1.2.4-1.1) ...
Selecting previously unselected package libgomp1:arm64.
Preparing to unpack .../3-libgomp1_10.2.1-6_arm64.deb ...
Unpacking libgomp1:arm64 (10.2.1-6) ...
Selecting previously unselected package libfftw3-single3:arm64.
Preparing to unpack .../4-libfftw3-single3_3.3.8-2_arm64.deb ...
Unpacking libfftw3-single3:arm64 (3.3.8-2) ...
Selecting previously unselected package libsamplerate0:arm64.
Preparing to unpack .../5-libsamplerate0_0.2.1+ds0-1_arm64.deb ...
Unpacking libsamplerate0:arm64 (0.2.1+ds0-1) ...
Selecting previously unselected package alsa-utils.
Preparing to unpack .../6-alsa-utils_1.2.4-1_arm64.deb ...
Unpacking alsa-utils (1.2.4-1) ...
Setting up libgomp1:arm64 (10.2.1-6) ...
Setting up libasound2-data (1.2.4-1.1) ...
Setting up libasound2:arm64 (1.2.4-1.1) ...
Setting up libsamplerate0:arm64 (0.2.1+ds0-1) ...
Setting up libatopology2:arm64 (1.2.4-1.1) ...
Setting up libfftw3-single3:arm64 (3.3.8-2) ...
Setting up alsa-utils (1.2.4-1) ...
alsa-restore.service is a disabled or a static unit, not starting it.
alsa-state.service is a disabled or a static unit, not starting it.
Processing triggers for libc-bin (2.31-13+deb11u2) ...
[ OK ] DietPi-Set_hardware | APT install for: alsa-utils
[ INFO ] DietPi-Set_hardware | Resetting all sound card settings...
alsa-lib parser.c:2179:(load_toplevel_config) Unable to find the top-level configuration file '/usr/share/alsa/ucm2/ucm.conf'.
alsa-lib main.c:1014:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2
Found hardware: "ODROID-HDMI" "" "" "" ""
Hardware is initialized using a generic method
[ INFO ] DietPi-Set_hardware | Applying new sound card settings...
[ OK ] DietPi-Set_hardware | Setting in /boot/dietpi.txt adjusted: CONFIG_SOUNDCARD=default
[ OK ] DietPi-Set_hardware | alsactl -g store
[ OK ] soundcard default | Completed
DietPi-Software
─────────────────────────────────────────────────────
Step: Installing X.Org X Server: aka X11 - X Window System implementation
[ OK ] DietPi-Software | cd /tmp/DietPi-Software
[ OK ] DietPi-Software | Checking URL: https://raw.githubusercontent.com/MichaIng/DietPi/master/.conf/dps_6/98-dietpi-disable_dpms.conf
[ INFO ] DietPi-Software | G_THREAD_START_0 | curl -sSfL https://raw.githubusercontent.com/MichaIng/DietPi/master/.conf/dps_6/98-dietpi-disable_dpms.conf -o 98-dietpi-disable_dpms.conf
[ INFO ] DietPi-Software | APT install for: xserver-xorg-core xserver-xorg-input-libinput xinit dbus-x11 xfonts-base x11-xserver-utils x11-utils libgl1-mesa-dri mesa-utils mesa-utils-extra, please wait...
Giving this error screen
──────┤ DietPi-Software ├──────────────────────────────────────────────────┐
│ APT install for: xserver-xorg-core xserver-xorg-input-libinput xinit dbus-x11 xfonts-base x11-xserver-utils
│ x11-utils libgl1-mesa-dri mesa-utils mesa-utils-extra
│ - Command: apt-get -qq --allow-change-held-packages install xserver-xorg-core xserver-xorg-input-libinput xinit
│ dbus-x11 xfonts-base x11-xserver-utils x11-utils libgl1-mesa-dri mesa-utils mesa-utils-extra
│ - Exit code: 100
│ - DietPi version: v8.1.2 (MichaIng/master) | HW_MODEL: 16 | HW_ARCH: 3 | DISTRO: 6
│ - Image creator: DietPi Core Team
│ - Pre-image: Meveric
│ - Error log:
│ debconf: delaying package configuration, since apt-utils is not installed
│ Selecting previously unselected package libexpat1:arm64.^M
│ (Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(Reading database ... 15%^M(Reading datab
│ ... 20%^M(Reading database ... 25%^M(Reading database ... 30%^M(Reading database ... 35%^M(Reading database ... 40%^M(
│ database ... 45%^M(Reading database ... 50%^M(Reading database ... 55%^M(Reading database ... 60%^M(Reading database .
│ (Reading database ... 70%^M(Reading database ... 75%^M(Reading database ... 80%^M(Reading database ... 85%^M(Reading
│ database ... 90%^M(Reading database ... 95%^M(Reading database ... 100%^M(Reading database ... 16006 files and directo
│ currently installed.)^M
│ Preparing to unpack .../000-libexpat1_2.2.10-2+deb11u1_arm64.deb ...^M
│ Unpacking libexpat1:arm64 (2.2.10-2+deb11u1) ...^M
│ Selecting previously unselected package dbus.^M
│ Preparing to unpack .../001-dbus_1.12.20-2_arm64.deb ...^M
│ Unpacking dbus (1.12.20-2) ...^M
│ Selecting previously unselected package libisl23:arm64.^M
│ Preparing to unpack .../002-libisl23_0.23-1_arm64.deb ...^M
│ Unpacking libisl23:arm64 (0.23-1) ...^M
│ Selecting previously unselected package libmpfr6:arm64.^M
│ Preparing to unpack .../003-libmpfr6_4.1.0-3_arm64.deb ...^M
│ Unpacking libmpfr6:arm64 (4.1.0-3) ...^M
│ Selecting previously unselected package libmpc3:arm64.^M
│ Preparing to unpack .../004-libmpc3_1.2.0-1_arm64.deb ...^M
│ Unpacking libmpc3:arm64 (1.2.0-1) ...^M
│ Selecting previously unselected package cpp-10.^M
│ Preparing to unpack .../005-cpp-10_10.2.1-6_arm64.deb ...^M
│ Unpacking cpp-10 (10.2.1-6) ...^M
│ Selecting previously unselected package cpp.^M
│ Preparing to unpack .../006-cpp_4%3a10.2.1-1_arm64.deb ...^M
│ Unpacking cpp (4:10.2.1-1) ...^M
│ Selecting previously unselected package libxau6:arm64.^M
│ Preparing to unpack .../007-libxau6_1%3a1.0.9-1_arm64.deb ...^M
│ Unpacking libxau6:arm64 (1:1.0.9-1) ...^M
│ Selecting previously unselected package libxdmcp6:arm64.^M
│ Preparing to unpack .../008-libxdmcp6_1%3a1.1.2-3_arm64.deb ...^M
│
│ Retry : Re-run the last command that failed ↑
│ DietPi-Config : Edit network, APT/NTP mirror settings etc ▮
Is this the key line ?
dpkg: error processing archive /tmp/apt-dpkg-install-eHAT9a/071-libxmu6_2%3a1.1.2-2+b3_arm64.deb (--unpack):
cannot copy extracted data for './usr/lib/aarch64-linux-gnu/libXmu.so.6.2.0' to '/usr/lib/aarch64-linux-gnu/libXmu.so.6.2.0.dpkg-new': failed to write (No space left on device)
root@DietPi:/dev# df --human-readable
Filesystem Size Used Avail Use% Mounted on
udev 1.9G 0 1.9G 0% /dev
tmpfs 372M 5.4M 366M 2% /run
/dev/mmcblk0p2 740M 725M 0 100% /
tmpfs 1.9G 0 1.9G 0% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 4.0M 0 4.0M 0% /sys/fs/cgroup
tmpfs 1.9G 4.0K 1.9G 1% /tmp
tmpfs 50M 84K 50M 1% /var/log
/dev/mmcblk0p1 256M 23M 233M 9% /boot
No need to retry as long as the filesystem has not been expanded 😉. What fdisk
shows you is not the filesystem size but the partition size, which has been expended successfully. It is only the contained ext4 filesystem which fails to be expanded.
It is only the contained ext4 filesystem which fails to be expanded.
I'm not entirely sure I follow, but I get the general idea.
I'll go back to using a previous image I have and leave you to do your magic in your own time. (I'll just not update past V7)
There's no pressure from me.
Thanks a million Michal
The issue is not with updating DietPi. It's the first run setup that did not expand the partition correctly. Question is why? This is something to find out.
I'm not gonna invest further time into this resizing issue, since it only affects the legacy Odroid images and we already tried everything on Odroid C2, without success. Better have the new image ready. Good thing is that boot configuration is exactly the same as for Odroid N2. But Armbian offers two different bootloaders (and images) for C4 and HC4. I hope their are identical, especially that they load the correct device tree OOTB. We'll see, else we need to split the images as well 😢.
Image ready for testing: https://dietpi.com/downloads/images/
Image ready for testing: https://dietpi.com/downloads/images/
Trying it right now......
On first boot this is roughly what I saw on the monitor.
It seems to have hung. I can't get a Prompt from the local terminal and it isn't present on the LAN so I can't try a SSH.
But the Blue LED is still pulsing happily.
thermal thermal_zone0:
[ 2.041373] reg-fixed-voltage regulator-flash_1v8 : failed to register
[ 2.043935] reg-fixed-voltage regulator-vcc_1v8 : failed to register
(Repeated a lot, as well as something about temperature but that scrolled off the top of the screen before I could read it properly)
Gave up waiting for root file system device. comon problems:
- boot args (cat / proc/cmdline)
- - check rootdelay = (did the system wait long enough?)
- Missing modulees (cat /proc/modules; ls /dev)
- ALERT! UUID=3ccf3790-5e80-44b9-83be-17e3b21083d9 does not exist. Dropping to a shell!
(initramsfs)
UUID=3ccf3790-5e80-44b9-83be-17e3b21083d9 does not exist. Dropping to a shell!
Let me see.
Ah, I missed to edit the part in PREP where the UUID and root filesystem type are adjusted in /boot/dietpiEnv.txt
. I just updated the image accordingly (same link).
If you have a possibility to mount that ext4 filesystem and check its UUID on another system, you can edit it yourself. It's the line starting with rootdev=UUID=
and the value should be the output of what on Linux this gives (with the device path adjusted, in case):
lsblk -no UUID /dev/mmcblk0p1
I just updated the image accordingly (same link).
I very nearly tried to edit the file, until I re-read your post to see that you said you made the change anyway.
SO....
it has now booted up really quickly and pushed me in startup script
let's see what happens......
okay, so Node-RED is running well.
Chromium loaded, but I can't get it to load on boot. (or indeed load as a stand-alone at all)
Initially, it looked like Xterm wasn't installed, but adding that made no difference.
Normally,, I would run this command from a command prompt and all would work perfectly.
sudo xinit /usr/bin/chromium ---kiosk --test-type --window-size=1920,1080 --start-fullscreen --start-maximized --window-position=0,0 --no-user-gesture-required --app=http://bbc.co.uk -- -nocursor
But what I get is a blank screen, as if it is trying to load Xinit and Chromium.
then it returns to the command prompt.
I have tried using the dietpi-config option to set Chromium to start at boot, but I just get the same behaviour.
Quick flash of an xinit session, then a command prompt.
X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
Build Operating System: linux Debian
Current Operating System: Linux DietPi 5.10.81-meson64 #21.08.6 SMP PREEMPT Mon Nov 22 11:21:51 UTC 2021 aarch64
Kernel command line: root=UUID=28046172-8741-4334-96cd-b24d158eec46 rootfstype=e xt4 rootwait console=tty1 loglevel=4 consoleblank=0 coherent_pool=2M ubootpart=2 c2a3e4f-01 libata.force=noncq usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u net.ifnames=0
Build Date: 16 December 2021 05:08:23PM
xorg-server 2:1.20.11-1+deb11u1 (https://www.debian.org/support)
Current version of pixman: 0.40.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Feb 15 18:14:54 2022
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
xinit: connection to X server lost
waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.
if I just run xinit
then I get the small white terminal appear.
But trying to run /usr/bin/chromium
returns an error
Trace/breakpoint trap
Hmm, so X11 with xterm works but not with Chromium. What does cat /var/log/Xorg.0.log
show after trying to start xinit /usr/bin/chromium
?
I wonder whether its the same as here: https://dietpi.com/phpbb/viewtopic.php?p=43184#p43184
Through other/additional error messages are thrown, not sure whether those are visible on primary console only (kernel logs), which should then be seen via dmesg
elsewhere.
Hmm, so X11 with xterm works but not with Chromium. What does
cat /var/log/Xorg.0.log
show after trying to startxinit /usr/bin/chromium
?
brace yourself... this is a long log
Followed by dmesg log
It is like Chromium is simply stopping immediately after being started. No error messages from the X server, just a regular shutdown after startup finished 🤔. The other error messages on the forum thread may not even be related.
Does it work when you install a desktop and start Chromium from there?
Does it work when you install a desktop and start Chromium from there?
Thanks Michal
I'm away for a few days, as soon as I get back I'll give it a try.
Does it work when you install a desktop and start Chromium from there?
Hi
I'm back...
Here's what I have tried so far.
I ran dietpi-software
and added LXDE
But I DIDN'T change the autoboot option from Chromium.
When rebooting I get a screen full of
login as: root
root@192.168.178.75's password:
Linux DietPi 5.10.81-meson64 #21.08.6 SMP PREEMPT Mon Nov 22 11:21:51 UTC 2021 a arch64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Feb 18 11:07:04 2022
─────────────────────────────────────────────────────
DietPi v8.1.2 : 11:14 - Fri 02/18/22
─────────────────────────────────────────────────────
- Device model : Odroid C4/HC4 (aarch64)
- CPU temp : 33 °C / 91 °F : Cool runnings
- LAN IP : 192.168.178.75 (eth0)
- MOTD : DietPi v8.1 is here, check out the release notes:
https://dietpi.com/docs/releases/v8_1/
─────────────────────────────────────────────────────
DietPi Team : https://github.com/MichaIng/DietPi#the-dietpi-project-team
Image by : DietPi Core Team (pre-image: from scratch)
Patreon Legends : Camry2731, Chris Gelatt
Website : https://dietpi.com/ | https://twitter.com/DietPi_
Contribute : https://dietpi.com/contribute.html
Web Hosting by : https://myvirtualserver.com
dietpi-launcher : All the DietPi programs in one place
dietpi-config : Feature rich configuration tool for your device
dietpi-software : Select optimised software for installation
htop : Resource monitor
cpu : Shows CPU information and stats
root@DietPi:~# dietpi-config
[ OK ] DietPi-AutoStart | Setting in /boot/dietpi.txt adjusted: SOFTWARE_CHROM IUM_AUTOSTART_URL=https://www.dietpi.com/
[ OK ] DietPi-AutoStart | Desired setting in /boot/dietpi.txt was already set: AUTO_SETUP_AUTOSTART_LOGIN_USER=root
[ OK ] DietPi-AutoStart | mkdir -p /etc/systemd/system/getty@tty1.service.d /e tc/systemd/system/console-getty.service.d
[ OK ] DietPi-AutoStart | systemctl daemon-reload
root@DietPi:~# find / -iname chromium*
/etc/chromium
/etc/chromium.d
/usr/bin/chromium
/usr/share/doc/chromium-common
/usr/share/doc/chromium
/usr/share/bug/chromium
/usr/share/man/man1/chromium.1.gz
/usr/share/bash-completion/completions/chromium-browser
/usr/share/bash-completion/completions/chromium
/usr/share/chromium
/usr/share/gnome-control-center/default-apps/chromium.xml
/usr/share/lintian/overrides/chromium
/usr/share/icons/hicolor/24x24/apps/chromium.png
/usr/share/icons/hicolor/256x256/apps/chromium.png
/usr/share/icons/hicolor/48x48/apps/chromium.png
/usr/share/icons/hicolor/16x16/apps/chromium.png
/usr/share/icons/hicolor/128x128/apps/chromium.png
/usr/share/icons/hicolor/64x64/apps/chromium.png
/usr/share/icons/hicolor/32x32/apps/chromium.png
/usr/share/pixmaps/chromium.png
/usr/share/applications/chromium.desktop
/usr/lib/chromium
/usr/lib/chromium/chromium
/var/lib/dietpi/dietpi-software/installed/chromium-autostart.sh
/var/lib/dpkg/info/chromium.md5sums
/var/lib/dpkg/info/chromium.postinst
/var/lib/dpkg/info/chromium-common.md5sums
/var/lib/dpkg/info/chromium.prerm
/var/lib/dpkg/info/chromium.list
/var/lib/dpkg/info/chromium-common.list
/var/lib/dpkg/info/chromium.conffiles
/root/.config/chromium
/root/.cache/chromium
root@DietPi:~# sh /var/lib/dietpi/dietpi-software/installed/chromium-autostart.sh
X.Org X Server 1.20.11
X Protocol Version 11, Revision 0
Build Operating System: linux Debian
Current Operating System: Linux DietPi 5.10.81-meson64 #21.08.6 SMP PREEMPT Mon Nov 22 11:21:51 UTC 2021 aarch64
Kernel command line: root=UUID=28046172-8741-4334-96cd-b24d158eec46 rootfstype=ext4 rootwait console=tty1 loglevel=4 consoleblank=0 coherent_pool=2M ubootpart=2c2a3e4f-01 libata.force=noncq usb-storage.quirks=0x2537:0x1066:u,0x2537:0x 1068:u net.ifnames=0
Build Date: 16 December 2021 05:08:23PM
xorg-server 2:1.20.11-1+deb11u1 (https://www.debian.org/support)
Current version of pixman: 0.40.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Feb 18 11:16:01 2022
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
[2681:2712:0218/111604.748835:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknow n address type (examples of valid types are "tcp" and on UNIX "unix")
[2681:2712:0218/111604.749343:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknow n address type (examples of valid types are "tcp" and on UNIX "unix")
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[2681:2712:0218/111604.788022:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknow n address type (examples of valid types are "tcp" and on UNIX "unix")
[2681:2712:0218/111604.788140:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknow n address type (examples of valid types are "tcp" and on UNIX "unix")
[2681:2712:0218/111604.891078:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknow n address type (examples of valid types are "tcp" and on UNIX "unix")
[2681:2712:0218/111604.891201:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknow n address type (examples of valid types are "tcp" and on UNIX "unix")
*** stack smashing detected ***: terminated
[2681:2681:0218/111605.014512:ERROR:gpu_process_host.cc(978)] GPU process exited unexpectedly: exit_code=6
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[2681:2681:0218/111605.095049:ERROR:gpu_process_host.cc(978)] GPU process exited unexpectedly: exit_code=6
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[2681:2681:0218/111605.113204:ERROR:gpu_process_host.cc(978)] GPU process exited unexpectedly: exit_code=6
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[2681:2681:0218/111605.128790:ERROR:gpu_process_host.cc(978)] GPU process exited unexpectedly: exit_code=6
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[2681:2681:0218/111605.144491:ERROR:gpu_process_host.cc(978)] GPU process exited unexpectedly: exit_code=6
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[2681:2681:0218/111605.165640:ERROR:gpu_process_host.cc(978)] GPU process exited unexpectedly: exit_code=6
[2681:2681:0218/111605.165751:FATAL:gpu_data_manager_impl_private.cc(448)] GPU process isn't usable. Goodbye.
[2719:2736:0218/111605.262777:ERROR:ssl_client_socket_impl.cc(995)] handshake failed; returned -1, SSL error code 1, net_error -3
xinit: connection to X server lost
waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.
root@DietPi:~#
What I'm seeing on the device's monitor is the white start screen of Chromium, but only for a few ms.
I'll start the desktop and see if Chromium works
Okay, good test
Chromium won't start from LXDE either.
After clicking on either of the Chromium shortcuts, I see the "working" version of the cursor for a while.
I quick flash (as if Chromium starts and closes) then back to the desktop
A bit more "working" cursor, then resting
What do you suggest I try next?
FYI
Firefox does work in LXDE
Trying to run each stage manually,
Command prompt login run xinit start chromium from Xinit
I see this kind of error in Xinit
[2681:2712:0218/111604.891078:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknow n address type (examples of valid types are "tcp" and on UNIX "unix")
[2681:2712:0218/111604.891201:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknow n address type (examples of valid types are "tcp" and on UNIX "unix")
*** stack smashing detected ***: terminated
[2681:2681:0218/111605.014512:ERROR:gpu_process_host.cc(978)] GPU process exited unexpectedly: exit_code=6
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[2681:2681:0218/111605.095049:ERROR:gpu_process_host.cc(978)] GPU process exited unexpectedly: exit_code=6
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[2681:2681:0218/111605.113204:ERROR:gpu_process_host.cc(978)] GPU process exited unexpectedly: exit_code=6
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[2681:2681:0218/111605.128790:ERROR:gpu_process_host.cc(978)] GPU process exited unexpectedly: exit_code=6
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[2681:2681:0218/111605.144491:ERROR:gpu_process_host.cc(978)] GPU process exited unexpectedly: exit_code=6
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
*** stack smashing detected ***: terminated
[2681:2681:0218/111605.165640:ERROR:gpu_process_host.cc(978)] GPU process exited unexpectedly: exit_code=6
FATAL:gpu_data_manager_impl_private.cc(448) GPU process isn't usable. Goodbye
handshake failed; returned -1, SSL error code 1, net_error -3
Is it.... This last line and the GPU error that needs attention?
Curiously, Firefox will start in an Xinit session
But there was a brief point where I saw a similar error message about the GPU
I'll see if I can find it
Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest:libpci missing (t=2.11504) [GFX1-]:glxtest:libpci missing
installing libpci3
resolved that
The missing libpci3
dependency has already been reported to Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993308
Though no reaction so far, I'll try to give this a push.
Definitely an ARMv8 related bug in Chromium, I'll try to replicate and in case report at the Debian bug tracker as well.
I'll try to replicate and in case report at the Debian
That's very kind of you.
If you don't have a C4 to work with, please let me know
Firefox warning appears on all distro versions from Buster to Bookworm. I added it to dietpi-software
, might help with Firefox internal render decisions: https://github.com/MichaIng/DietPi/commit/5e2dda0
Gave the bug report a bump, but at least our end it is solved: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993308
According to Chromium, I see *** stack smashing detected ***: terminated
on an x86_64 VM as well, together with attempts to access the CPUFreq API, which isn't available on VMs. Probably another things to report to Debian, and in case forward upstream, so that it is checked first whether CPUFreq is available at all before it is tried to read it.
But Chromium works regardless, which indicates that indeed this error message is not related to the crash on C4 or ARMv8 in general.
I'll mark this as closed. Let's concentrate on Chromium ARMv8 in a dedicated issue: https://github.com/MichaIng/DietPi/issues/5300
Failure to complete first run
Required Information
DietPi version |
cat /boot/dietpi/.version
Distro version |
echo $G_DISTRO_NAME $G_RASPBIAN
Contents of.version
G_DIETPI_VERSION_CORE=8 G_DIETPI_VERSION_SUB=1 G_DIETPI_VERSION_RC=2 G_GITBRANCH='master' G_GITOWNER='MichaIng' G_LIVE_PATCH_STATUS[0]='applied' G_LIVE_PATCH_STATUS[1]='applied' G_LIVE_PATCH_STATUS[2]='not applicable' G_LIVE_PATCH_STATUS[3]='not applicable'Kernel version |
uname -a
- Unable to obtain a command promptSBC model | Odorid C4
Power supply used | 12V 2.5Amp
SD card used | eMMC 16GB
Additional Information (if applicable)