Rock5 - bookworm image - dist upgrade fails #6122
Comments
Can you share the bug report ID or simply the error log/output shown on the screen? |
|
|
"Reference code: ee141e35-d9ac-41e6-9710-5fc864df28f6" |
Your ls -al /boot |
|
saw that too, but more worried about the zstd / gzip issues, as I thought I read somewhere that Bookworm need zstd somewhere... root@DietPi:~# ls -al /boot
total 88991
drwxr-xr-x 4 root root 2048 Jan 1 1970 .
drwxr-xr-x 18 root root 4096 Jan 17 22:52 ..
-rwxr-xr-x 1 root root 0 Feb 1 11:36 .next
-rwxr-xr-x 1 root root 33823232 Feb 1 11:36 Image
-rwxr-xr-x 1 root root 7814657 Jan 23 22:03 System.map-5.10.110-rockchip-rk3588
-rwxr-xr-x 1 root root 2710 Jan 17 22:42 boot.cmd
-rwxr-xr-x 1 root root 2782 Jan 17 22:46 boot.scr
-rwxr-xr-x 1 root root 215508 Jan 23 22:03 config-5.10.110-rockchip-rk3588
drwxr-xr-x 4 root root 3072 Feb 1 11:38 dietpi
-rwxr-xr-x 1 root root 18092 Jan 15 22:29 dietpi-LICENSE.txt
-rwxr-xr-x 1 root root 15518 Jan 15 22:29 dietpi-README.md
-rwxr-xr-x 1 root root 3950 Jan 17 22:52 dietpi-wifi.txt
-rwxr-xr-x 1 root root 16271 Feb 2 11:53 dietpi.txt
-rwxr-xr-x 1 root root 349 Jan 17 22:42 dietpiEnv.txt
drwxr-xr-x 3 root root 512 Feb 1 11:36 dtb
-rwxr-xr-x 1 root root 7688883 Feb 1 11:36 initrd.img-5.10.110-rockchip-rk3588
-rwxr-xr-x 1 root root 7688947 Feb 1 11:36 uInitrd
-rwxr-xr-x 1 root root 33823232 Jan 23 22:03 vmlinuz-5.10.110-rockchip-rk3588 |
This was just a warning and not an issue. Can you share as well |
root@DietPi:~# df -h
Filesystem Size Used Avail Use% Mounted on
udev 1.7G 0 1.7G 0% /dev
tmpfs 374M 7.7M 366M 3% /run
/dev/nvme0n1p2 235G 486M 225G 1% /
tmpfs 1.9G 0 1.9G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/nvme0n1p1 127M 114M 13M 90% /boot
tmpfs 1.9G 9.7M 1.9G 1% /tmp
tmpfs 50M 32K 50M 1% /var/log |
It's two different things. grep CONFIG_RD_ZSTD /boot/config-5.10.110-rockchip-rk3588If this shows apt install zstdHowever, this is purely optional, the problem is the insufficient boot partition space. I see, on kernel upgrade, since it is a FAT partition, the Linux image image is created as copy and not as symlink (or hardlink) or instead of just being renamed. Hum, I think we should switch to rm /boot/{vmlinuz,initrd}-5.10.110-rockchip-rk3588
apt full-upgrade |
|
ah - thx... |
I'm no fans of wasting space no no reason. New images are currently built, also with |
|
Ill flash the new image on my test SD Card and let you know... Didnt see anything in dietpi.txt |
|
Not without creating/adjusting the respective config file manually: cat << '_EOF_' > /etc/apt/apt.conf.d/99-dietpi-cache
Dir::Cache "/tmp/apt";
Dir::Cache::archives "/tmp/apt/archives";
Dir::State "/tmp/apt";
Dir::State::extended_states "/var/lib/apt/extended_states";
Dir::State::status "/var/lib/dpkg/status";
Dir::Cache::pkgcache "";
Dir::Cache::srcpkgcache "";
_EOF_ |
|
then I am proposing a new Dietpi.txt entry... |
|
Yes, please do so. |
- CHANGELOG | ROCK 5B: New images with ext4 boot filesystem have been generated, to solve possible issues and limitations of the previously used FAT filesystem. Many thanks to @isarrider for reporting this issue: #6122
|
Original issues solved with new images. Let me know if you need instructions about how to migrate to ext4 boot partition on your system, i.e. copying boot filesystem content elsewhere, reformatting it to ext4, moving content back in, adjusting UUID in fstab. |
|
thanks - more like an easy way to edit the DietPi.txt on windows that I have to use ;) |
|
Just tested again with WSL2 |
|
this is why BTRFS might be a better choice: |
|
Interesting. I hope it works reliable. Any implementation of ext4 on Windows I tested works horribly unreliable, mostly breaking the filesystem when attempting to write to it. Any non-ext4 filesystem will be optional/non-default on DietPi: F2FS is for flash drives only, Btrfs is usually overkill and AFAIK slower than ext4, so only reasonable if your really need to additional features it provides. ext4 is and was the best and most reliable allrounder, but sadly neither on Windows nor on macOS (same problem as on Windows, horrible driver implementations only) safely accessible. |
|
I never have tested it exhaustively... |
Quite significantly in some test scenarios: https://www.phoronix.com/review/linux-50-filesystems
Of course, if you need/want the features. Most users however won't use them, and ext4 is the still most proven and overall very well performing solution 😉. Do not misunderstand me, I'm all fore offering Btrfs and F2FS images, even other filesystem types once support has been implemented, just not as the promoted default download. Btw: thanks for the zstd bench link. Pretty impressive how well it performs, with compression level from 1 - 9 depending on needs, defeating nearly all competitors. We are already implementing it as default for initramfs compression. More importantly, we need to use it for our zram-swap implementation. LZMA//7z/xz can still compress better, if compression is all what is relevant, respectively compression/decompression speed does not matter, so for our image and package downloads we'll stay with that. |
So wanted to help testing bookworm...
Rock5 - latest image (https://dietpi.com/downloads/images/DietPi_ROCK5B-ARMv8-Bookworm.7z)
1st boot: the normal apt-get look good, but the dist upgrade throws an error...
I sent a log a few hours ago...
(with bullseye all runs smooth)
Can update more details later...
The text was updated successfully, but these errors were encountered: