You are not logged in.
"shred" means "torn to pieces" (it's just to say that the file got damaged) - and according to pacman -Qkk systemd, that's not the case either.
Are you being asked to decrypt the root partition before the error shows up?
Can you boot if you edit the kernel parameters and add "init=/bin/bash"?
No. It doesn’t ask for decrypt password but all partitions are well! I can normally chroot and install packages over pacman or yay.
In Arch.conf under options init=/bin/bash
Ok. I will give a try tomorrow. I’m really desperated.
Offline
"shred" means "torn to pieces" (it's just to say that the file got damaged) - and according to pacman -Qkk systemd, that's not the case either.
Are you being asked to decrypt the root partition before the error shows up?
Can you boot if you edit the kernel parameters and add "init=/bin/bash"?
It's ending in a kernel panic and say requested init=/bin/bash not found
@seth any thoughts?
Offline
Check (on the chroot)
ldd /bin/init
stat /lib /lib64 /usr/lib /usr/lib64Try passing "rootwait" to the kernel commandline.
There's an MCE error but if the HW had issues you couldn't mount it from the iso.
Online
Check (on the chroot)
ldd /bin/init stat /lib /lib64 /usr/lib /usr/lib64Try passing "rootwait" to the kernel commandline.
There's an MCE error but if the HW had issues you couldn't mount it from the iso.
ldd /bin/initnot a dynmaic executable
stat /lib /lib64 /usr/lib /usr/lib64stat: cannot statx /usr/lib64 ?!
Under rd.options=discard rootwait ?!
Last edited by Morta (2022-01-25 14:54:56)
Offline
stat: cannot statx /usr/lib64 ?!
That's one of your issues - /usr/lib64 is supposed to be a symlink to "lib" (ie. finding /usr/lib)
not a dynamic executable
That's the next issue - what is it:
file /bin/init
file $(realpath /bin/init)Under rd.options=discard rootwait ?!
Anywhere in the kernel options, but for now let's focus on your broken filesystem and questionable bin/init…
Online
Ok i do
ln -sf /usr/lib /usr/lib64 ?
not a dynamic executable
That's the next issue - what is it:
file /bin/initfile $(realpath /bin/init)Under rd.options=discard rootwait ?!
Anywhere in the kernel options, but for now let's focus on your broken filesystem and questionable bin/init…
Ok. I deleted init=/bin/bash and added rootwait
Last edited by Morta (2022-01-25 15:13:46)
Offline
ln -s lib /usr/lib64ldd /usr/lib/systemd/systemdBut it's probably the missing lib64
Online
ln -s lib /usr/lib64ldd /usr/lib/systemd/systemdBut it's probably the missing lib64
And what is with /bin/init ?
ldd /bin/initOk, now mkinitcpio -P and bootctl install ?
And then reboot?
Last edited by Morta (2022-01-25 15:25:58)
Offline
/lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007f6e9acbc000)Just rebooting will likely do, but feel free to recreate the initramfs as well.
Online
/lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007f6e9acbc000)
This is just a information?! What was wrong?
Just rebooting will likely do, but feel free to recreate the initramfs as well.
Have I to do something else?
Ok. How can this happened?
I think it happens because of deinstalled Debian package with dpkg
I will spend some money to ArchLinux with my next salary for the support.
That should be fine now?
PS: What is with the noauto option for the bind mount in /etc/fstab?
PSS: Stil no ESP Drive
bootctl | nc termbin.com 999How I can set it?
Last edited by Morta (2022-01-25 15:50:08)
Offline
Just for information why bin/init wasn't resolvable - ld-linux-x86-64.so.2 could not be resolved.
Does the re/boot now work?
I've no idea how exactly that happened - it was more common when users could throw "--force" at pacman.
"deinstalled Debian package with dpkg" certainly sounds capable of such, but you absolutely should not use dpkg as package manager.
I am the Pacman thy Package Manager
Thou shalt have no other package managers before me
Edit: termbin is 404
Last edited by seth (2022-01-25 15:51:58)
Online
It's give a solution to morph RPM an DEB packages to Pacman packages like alien on Debian based systems? Or should I use a PKGBUILD script instead before I install a package with dpkg or yum?
Sorry, for the fault
Last edited by Morta (2022-01-25 15:56:59)
Offline
https://archlinux.org/packages/extra/any/rpmextract/
https://aur.archlinux.org/packages/deb2targz/
dpkg also allows you to extract files and leverage that in a PKGBUILD, but using it as a secondary package manager is a recipe for a disaster.
Do you only concern
✗ Boot loader sets ESP information
ESP: n/aor is there still an active problem w/ booting the system?
Online
https://archlinux.org/packages/extra/any/rpmextract/
https://aur.archlinux.org/packages/deb2targz/dpkg also allows you to extract files and leverage that in a PKGBUILD, but using it as a secondary package manager is a recipe for a disaster.
Do you only concern
✗ Boot loader sets ESP information ESP: n/aor is there still an active problem w/ booting the system?
It's working! NICE!!! THANKS MAN!
Offline
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Then we return to the nfs situation…
Online