MichaIng / DietPi

Lightweight justice for your single-board computer!
https://dietpi.com/
GNU General Public License v2.0
4.84k stars 496 forks source link

Fresh new installation 8.22.3 `apt-get -y dist-upgrade` fail #6646

Open milapointe opened 1 year ago

milapointe commented 1 year ago

Details:

Steps to reproduce:

Fresh new installation on a RPi4 and cant get past this.

Expected behaviour:

Installed

Actual behaviour:

Crash on dist upgrade

Extra details:

First time user Kingston 64gb sdxc

Additional logs:

logs sent : b895d3fa-f285-443c-9cc4-94d2c4bbd58a

Joulinar commented 1 year ago

pls can you share the full output of following lines

apt update
apt upgrade
apt dist-upgrade
milapointe commented 1 year ago
root@DietPi:/tmp/DietPi-Software# apt update
Hit:1 https://deb.debian.org/debian bookworm InRelease
Get:2 https://archive.raspberrypi.org/debian bullseye InRelease [23.6 kB]
Get:3 https://archive.raspberrypi.org/debian bullseye/main arm64 Packages [308 kB]
Fetched 331 kB in 4s (83.1 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
N: Repository 'Debian bookworm' changed its 'non-free component' value from 'non-free' to 'non-free non-free-firmware'
N: More information about this can be found online in the Release notes at: https://www.debian.org/releases/bookworm/arm64/release-notes/ch-information.html#non-free-split
root@DietPi:/tmp/DietPi-Software# apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
Illegal instruction
root@DietPi:/tmp/DietPi-Software# apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
Segmentation fault

I'm reading its possible that corrupt occured....I will try a new run flashing the img....

ravenclaw900 commented 1 year ago

Yeah, errors like Illegal instruction and Segmentation fault generally indicate some sort of corruption in the filesystem / specific binary. If it still doesn't work after reflashing, you might want to consider trying a new SD card.

milapointe commented 1 year ago

Happened with my other SD Card. I'm buying brand new SD Card + SD Card Reader....

Joulinar commented 1 year ago

On a RPI4, you should be able to use a USB pen stick for testing instead of SD card.

MichaIng commented 1 year ago

Also check for kernel errors:

dmesg -l 0,1,2,3

Undervoltage, i.e. an insufficient PSU could be also the reason for such issues.

Btw, as I just had some discussion about whether SD card are generally suitable as OS boot root media or not, would you be open to share some meta data of your SD card(s) to check whether they are original or fakes?

cat /sys/block/mmcblk0/device/cid
cat /sys/block/mmcblk0/device/csd

The two codes can be decoded here: https://gurumeditation.org/1342/sd-memory-card-register-decoder/ It gives a bunch of information, and especially the serial number, device name, manufacturer ID and "oemid" can be easily compared with the actual manufacturer and what is expected for the card. If they do not match and/or the serial number is very low, it is mostly assured or very likely that it is a fake card, which is then expected to die earlier than the original would do.