You are not logged in.
Tried:
1) Reinstalling kernels, mkinitcpio.
2) Files are there.
Happens with all installed kernels(ck, latest and lts).
Ideas?
Edit: What happend here?
1) Gnucash 3.03 update had a conflicting files error. I forced the installation which deleted the /usr/lib64 link.
2) init could not be loaded.
3) I had to restore the link in arch-chroot and reinstall every package that was installed or updated after this forced update
ln -s /lib /usr/lib64
The list of packages can be found in pacman log (/var/log/pacman.log)
4) Since I reinstalled /boot, I also had to change it's UUID in fstab.
Bottom line: Don't use --force just like that. And if used write it down on paper and reboot after to see everything is ok.
Last edited by Tharbad (2018-04-07 00:36:27)
Offline
What does "files are there" mean? Are sure they are there? Do you use UEFI and are certain that the ESP partitiion was mounted to /boot during the update/reinstall and that you are not accidentally looking at the /boot directory that isn't hooked up to the ESP? And that you have enough space left on the ESP? Details of your partition setup?
Online
The esp is boot dir.
the EFI is there.
partitions:
sda1: boot. 250mb of 500mb are used
sda2 : root 20gb free
To clarify: I installed the esp into the boot partition
Last edited by Tharbad (2018-04-06 11:02:44)
Offline
Please post the output of `ls -la /boot`, provide all the relevant details on your bootloader and read the CoC and replace your screenshot with a thumbnail / link.
Offline
Bootloader is systed-boot
total 270156
drwxr-xr-x 4 root root 4096 Jan 1 1970 .
drwxr-xr-x 20 root root 4096 Mar 14 19:02 ..
drwxr-xr-x 4 root root 4096 Feb 27 2016 EFI
-rwxr-xr-x 1 root root 79750144 Apr 6 13:22 initramfs-linux-ck-ivybridge-fallback.img
-rwxr-xr-x 1 root root 8051712 Apr 6 13:21 initramfs-linux-ck-ivybridge.img
-rwxr-xr-x 1 root root 79818240 Apr 6 14:05 initramfs-linux-fallback.img
-rwxr-xr-x 1 root root 8055808 Apr 6 14:05 initramfs-linux.img
-rwxr-xr-x 1 root root 76397056 Apr 6 13:34 initramfs-linux-lts-fallback.img
-rwxr-xr-x 1 root root 7900672 Apr 6 13:34 initramfs-linux-lts.img
-rwxr-xr-x 1 root root 1668608 Mar 14 22:17 intel-ucode.img
drwxr-xr-x 3 root root 4096 Aug 20 2017 loader
-rwxr-xr-x 1 root root 5158768 Apr 1 04:01 vmlinuz-linux
-rwxr-xr-x 1 root root 5048176 Mar 31 23:14 vmlinuz-linux-ck-ivybridge
-rwxr-xr-x 1 root root 4757264 Mar 29 11:25 vmlinuz-linux-lts
Offline
Please post the output of `ls -la /boot`, provide all the relevant details on your bootloader and read the CoC and replace your screenshot with a thumbnail / link.
Is using systemd-boot the only fact you consider relevant regarding your bootloader setup? If yes, then think about to what extent a person can help you given only that piece of information.
Obviously I meant that you should also provide all configuration files (please make sure to read the wiki and include all the mentioned configuration files of systemd-boot). And while you're at it, also post the output of `lsblk -f -o +UUID`.
Offline
lsblk:
NAME FSTYPE LABEL UUID MOUNTPOINT UUID
loop0
sda
├─sda1 /boot
└─sda2 /
sdb
sdc
├─sdc1
└─sdc2
sdd
├─sdd1
├─sdd5
├─sdd6
├─sdd7
├─sdd8
├─sdd9
├─sdd10
├─sdd11
├─sdd12
├─sdd13
└─sdd14
sde
├─sde1
└─sde2
sdf
├─sdf1
└─sdf2
sdg
└─sdg1
sdh
└─sdh1 /mnt/a
loader conf:
timeout 5
#default 7d2aad8852f14338b948d338349ad189-*
default arch-ck
editor 1
entries (all look the same):
title Arch Linux ck Kernel
linux /vmlinuz-linux-ck-ivybridge
initrd /intel-ucode.img
initrd /initramfs-linux-ck-ivybridge.img
options root=PARTUUID=a2b11b43-3622-45ed-bddc-395cfe6d4267 rw scsi_mod.use_blk_mq=1
Thats all the files I know of. If I missed one, tell me
Last edited by Tharbad (2018-04-06 12:40:43)
Offline
I've reinstalled the boot directory using the setup in the wiki. Same kernel panic
Offline
All of this looks fine. Maybe this thread contains information that could help you?
Offline
Post your mkinitcpio.conf
Online
# vim:set ft=sh
# MODULES
# The following modules are loaded before any boot hooks are
# run. Advanced users may wish to specify all system modules
# in this array. For instance:
# MODULES="piix ide_disk reiserfs"
MODULES="bcache"
# BINARIES
# This setting includes any additional binaries a given user may
# wish into the CPIO image. This is run last, so it may be used to
# override the actual binaries included by a given hook
# BINARIES are dependency parsed, so you may safely ignore libraries
BINARIES=""
# FILES
# This setting is similar to BINARIES above, however, files are added
# as-is and are not parsed in any way. This is useful for config files.
FILES=""
# HOOKS
# This is the most important setting in this file. The HOOKS control the
# modules and scripts added to the image, and what happens at boot time.
# Order is important, and it is recommended that you do not change the
# order in which HOOKS are added. Run 'mkinitcpio -H <hook name>' for
# help on a given hook.
# 'base' is _required_ unless you know precisely what you are doing.
# 'udev' is _required_ in order to automatically load modules
# 'filesystems' is _required_ unless you specify your fs modules in MODULES
# Examples:
## This setup specifies all modules in the MODULES setting above.
## No raid, lvm2, or encrypted root is needed.
# HOOKS="base"
#
## This setup will autodetect all modules for your system and should
## work as a sane default
# HOOKS="base udev autodetect block filesystems"
#
## This setup will generate a 'full' image which supports most systems.
## No autodetection is done.
# HOOKS="base udev block filesystems"
#
## This setup assembles a pata mdadm array with an encrypted root FS.
## Note: See 'mkinitcpio -H mdadm' for more information on raid devices.
# HOOKS="base udev block mdadm encrypt filesystems"
#
## This setup loads an lvm2 volume group on a usb device.
# HOOKS="base udev block lvm2 filesystems"
#
## NOTE: If you have /usr on a separate partition, you MUST include the
# usr, fsck and shutdown hooks.
HOOKS="base udev autodetect modconf block bcache filesystems keyboard fsck"
# COMPRESSION
# Use this to compress the initramfs image. By default, gzip compression
# is used. Use 'cat' to create an uncompressed image.
#COMPRESSION="gzip"
#COMPRESSION="bzip2"
#COMPRESSION="lzma"
#COMPRESSION="xz"
#COMPRESSION="lzop"
#COMPRESSION="lz4"
COMPRESSION="cat"
# COMPRESSION_OPTIONS
# Additional options for the compressor
#COMPRESSION_OPTIONS=""
Also tried passing init path. same result.
robg: not the same problem ;(
Last edited by Tharbad (2018-04-06 13:38:48)
Offline
All of this looks fine. Maybe this thread contains information that could help you?
The only related thing is that both /lib and /lb64 point to /usr/lib.
Is that ok?
Offline
Indeed, that's fine, and unfortunately does not resolve your issue. Nonetheless I believe that the theme is the same, some init-related files cannot be found and hence your boot fails. What does `pacman -Qkk systemd` say?
Offline
This is unlikely to be related to the problem, but when is the last time you merged your pacnew files? mkinitcpio has been using arrays instead of stings for ~6 months now. Either you haven't updated in that time, or you have been neglecting your pacnew files.
Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
backup file: systemd: /etc/systemd/logind.conf (Modification time mismatch)
backup file: systemd: /etc/systemd/logind.conf (Size mismatch)
systemd: 1443 total files, 1 altered file
Offline
This is unlikely to be related to the problem, but when is the last time you merged your pacnew files? mkinitcpio has been using arrays instead of stings for ~6 months now. Either you haven't updated in that time, or you have been neglecting your pacnew files.
oops. but it's not related
Offline
Please post the system's pacman.log particularly the update that included the kernel related to this issue onwards also the output of the following adjusted as needed if you use live media to access the system
bsdcpio -itF /boot/initramfs-linux.img
Offline
pacman:
https://paste.ubuntu.com/p/ypzDhhnc8P/
bsdcpio:
https://paste.ubuntu.com/p/grC4Qq2xxN/
Last edited by Tharbad (2018-04-06 21:49:19)
Offline
[2018-04-06 12:08] [PACMAN] Running 'pacman -U --force mkinitcpio-busybox-1.27.2-1-x86_64.pkg.tar.xz'
What was the reason for the force?
The following should extract the init from the initrd it should match /usr/lib/initcpio/init
bsdcpio -iF /boot/initramfs-linug.img init
Can you also check on the systems / parition that /bin and /sbin are links to /usr/bin and /usr/bin/init is a link to ../lib/systemd/systemd
Offline
I think I did what c8c7 did here:
https://aur.archlinux.org/packages/gnucash/
How do I fix it?
Offline
After you chroot in what is the output of pacman -Qkk filesystem?
Offline
After you chroot in what is the output of pacman -Qkk filesystem?
Offline
[2018-04-06 12:08] [PACMAN] Running 'pacman -U --force mkinitcpio-busybox-1.27.2-1-x86_64.pkg.tar.xz'
What was the reason for the force?
The following should extract the init from the initrd it should match /usr/lib/initcpio/initbsdcpio -iF /boot/initramfs-linug.img init
Can you also check on the systems / parition that /bin and /sbin are links to /usr/bin and /usr/bin/init is a link to ../lib/systemd/systemd
force: downgrade.
That was done with chroot.
/usr/lib/initcpio/init and init have the same md5sum
The links are there
Offline
If you add the option break=postmount are you dropped to a shell with the root filesystem of the system mounted at /new_root ?
Offline
Ok. I've restored /usr/lib64 link, installed all the packages that were updated since that mistake and now It'll boot. But it can't access one of the disk so get emergency shell. I know the disk uuid but I can't find it with fdisk. It's the /boot partition. And since I reinstalled it, it has a new uuid which I forgot to change in fstab...
That's the system log:
https://paste.ubuntu.com/p/JfCYFmfHhV/
Last edited by Tharbad (2018-04-07 00:12:42)
Offline