You are not logged in.
when I try to look at the contents of initrd.img-5.10.0-9-amd64 with lsinitrd I get errors after some lines of reasonable output:
[...]
ERROR: src/skipcpio/skipcpio.c:144:main(): Corrupt CPIO archive!
ERROR: src/skipcpio/skipcpio.c:144:main(): Corrupt CPIO archive!
xzcat: (stdin): File format not recognized
Version:
Arguments: ERROR: src/skipcpio/skipcpio.c:144:main(): Corrupt CPIO archive!
xzcat: (stdin): File format not recognized
dracut modules:
ERROR: src/skipcpio/skipcpio.c:144:main(): Corrupt CPIO archive!
xzcat: (stdin): File format not recognized
========================================================================
cpio: premature end of archive
========================================================================
why?
Offline
Where did you get "lsinitrd" from ? It's not the default tool to examine Debian initramfs files. You should rather use:
$ sudo lsinitramfs <initrdfile>
Offline
Where did you get "lsinitrd" from ? It's not the default tool to examine Debian initramfs files.
hmm, lsinitrd was under EndlessOS, but lsinitramfs under Q4OS gives not that much different output (except lsinitrd being a little bit more verbose):
$ sudo lsinitramfs -l initrd.img-5.10.0-9-amd64
drwxr-xr-x 2 root root 0 Apr 25 2021 kernel
drwxr-xr-x 2 root root 0 Apr 25 2021 kernel/x86
drwxr-xr-x 2 root root 0 Apr 25 2021 kernel/x86/microcode
drwxr-xr-x 2 root root 0 Apr 25 2021 kernel/x86/microcode/.enuineIntel.align.0123456789abc
-rw-r--r-- 1 root root 4609024 Apr 25 2021 kernel/x86/microcode/GenuineIntel.bin
cpio: premature end of file
apparently the maintainers of EndlessOS adopted Redhats lsinitrd in favor of Debians initramfs due to being a little bit more verbose about what it is doing ... (see enclosed listing of
diff -uw $EndlessOS/lsinitrd $Q4OS/lsinitramfs).
Last edited by bernhard (2024-03-08 10:35)
Offline
It looks like your initramfs is corrupted some way. Please post more info about your system, see https://www.q4os.org/forum/viewtopic.php?id=3502
Offline
This is a Q4OS Gemini installation with Trinity desktop on an USB stick, see also here (it is the installation, which boots with good speed and I am trying to dig into a squashfs/overlayfs configuration for the slow stick), there and there. Output of reportq4 and inxi -Fxxx > inxi.txt 2>&1 attached.
The supposedly corrupt initramfs boots fine.
Last edited by bernhard (2024-03-08 11:45)
Offline
It's not clear to us why are you trying to examine 5.10.0-9 initrd. The log shows you have booted 5.10.0-28 kernel. You could check it with the command:
$ uname -a
and then run:
$ sudo lsinitramfs -l /boot/initrd.img-5.10.0-28-amd64
Offline
thanks, that works.
Sorry, I assumed that q4os/grub fetches the initial ram-disk from the EFI partition, i.e. /boot/efi/EFI/Q4OS/initrd* and did not look up what is in /boot. I should have checked the grub configuration, which clearly shows that it fetches the initrd from /dev/sdb2 mounted on / and then from /boot/initrd.img-5.10.0-28-amd64.
Last edited by bernhard (2024-03-19 18:31)
Offline