Quantcast
Channel: Raspberry Pi Forums
Viewing all articles
Browse latest Browse all 4935

Troubleshooting • Re: Raspberry Pi OS stops working after updating raspi-firmware

$
0
0
What does the following command return?
Hi bls,

thank you very much for a detailed response. By the way, yes, both eeprom config and /boot/firmware/config.txt are adjusted the way argon manual suggests. I have figured via trial and error the following information. On the vanilla system nvme-cli is not installed indeed:

Code:

$ sudo apt list nvme-cliListing... Donenvme-cli/stable 2.4+really2.3-3 arm64nvme-cli/stable 2.4+really2.3-3 armhf

Code:

$ sudo apt-cache rdepends nvme-clinvme-cliReverse Depends:  bfh-host  prometheus-node-exporter-collectors  libnvme1  ceph-osd  ceph-base

Code:

$ sudo aptitude why nvme-clii   mkvtoolnix  Depends  libdvdread8 (>= 4.1.3)   i A libdvdread8 Suggests libdvdcss2               p   libdvd-pkg  Provides libdvdcss2               p   libdvd-pkg  Depends  wget | devscripts        p   devscripts  Suggests autopkgtest              p   autopkgtest Suggests lxd                      p   lxd         Suggests ceph-common              p   ceph-common Suggests ceph                     p   ceph        Depends  ceph-osd (= 16.2.11+ds-2)p   ceph-osd    Suggests nvme-cli

Code:

$ sudo apt install nvme-cliReading package lists... DoneBuilding dependency tree... DoneReading state information... DoneThe following additional packages will be installed:  libnvme1 uuid-runtimeThe following NEW packages will be installed:  libnvme1 nvme-cli uuid-runtime0 upgraded, 3 newly installed, 0 to remove and 169 not upgraded.Need to get 647 kB of archives.After this operation, 1962 kB of additional disk space will be used.Do you want to continue? [Y/n] nAbort.
The problem lies meanwhile in something else. Updating raspi-firmware as well as some other packages launches update-initramfs -u, which causes the problem. It doesn't have anything to do with nvme-cli or any other package. After I booted on a fresh system and launched update-initramfs -u, the same problem appeared. The system didn't start correctly. Here is the code from this command:

Code:

$ sudo update-initramfs -uupdate-initramfs: Generating /boot/initrd.img-6.1.0-rpi7-rpi-v8update-initramfs: Generating /boot/initrd.img-6.1.0-rpi7-rpi-2712
After this command the system becomes unbootable. Note that it is vanilla system with no packages updated. Here are the complete logs:
boot.log: https://pastebin.com/hw39sSGQ
system.journal: https://pastebin.com/pakiSa5C
user-1000.journal: https://pastebin.com/RTN1kWD1

Then I chrooted into the system and ran via chroot update-initramfs -uv: https://pastebin.com/ViUFas8F
Surprisingly, I was able to boot into the system normally after that. Then I ran update-initramfs -uv on the system and it became nonfunctional again: https://pastebin.com/80yNe8aM
The weird is that the last two outputs are the same! Updating initramfs in the system makes it nonfunctional, updating initramfs makes it functional again, and there is no difference in logs!
One more weird thing I've noticed. After updating initramfs in the system the first time, I saw the following error in gparted:
Image

It looks like a bug for me, I will write a report unless someone tells me what I'm doing wrong.
Screenshot_2024-02-25_13-12-54.png

Statistics: Posted by ipo32jr — Sun Feb 25, 2024 2:22 pm



Viewing all articles
Browse latest Browse all 4935

Trending Articles