You are not logged in.
File: /usr/lib64/
Size: 4096 Blocks: 8 IO Block: 4096 directory
Device: 807h/2055d Inode: xxxx Links: 2
Access: (0755/drwxr-xr-x) Uid: ( 0/ root) Gid ( 0 / root )
Access Time: yesterday
Currently downloading another iso so I actually can copy paste stuff out...
Offline
That should be a symlink to /usr/lib (as should be /lib and /lib64) ... see the link in my other post.
Offline
$ stat /usr/lib64
File: /usr/lib64 -> lib
Size: 3 Blocks: 0 IO Block: 4096 symbolic link
Device: fe00h/65024d Inode: 1179660 Links: 1
Access: (0777/lrwxrwxrwx) Uid: ( 0/ root) Gid: ( 0/ root)
Access: 2017-03-14 00:05:27.055277133 +0000
Modify: 2016-12-05 23:43:55.000000000 +0000
Change: 2017-03-05 18:08:53.780134239 +0000
That would be the difference
Should be confirmed by
$ pacman -Qkk filesystem
from within the chroot
Offline
Did that, reinstalled filesystem still broken..., same error.
Offline
What is the output of ( trying to find out how many symlinks are missing )
$ pacman -Qkk filesystem
reinstalling the filesystem will not fix it as that would require pacman to delete /usr/lib64 in order to create the symlink.
edit:
grammar "many are" should be "many symlinks are"
edit2:
Also do not just delete /usr/lib64 Is it empty? If not please provide a listing for it.
Last edited by loqs (2017-03-14 23:49:09)
Offline
@loqs yes I know, I have deleted the folder before doing this. It is a symlink now, but for some reason I still run into a kernel panic I am looking at what is wrong right now.
Still no copy and paste here sry though. The output of Qkk filesystem left only warnings about size mismatches for files like /etc/fstab which is expected.
Last edited by wzrdtales (2017-03-14 23:52:36)
Offline
$ pacman -Qkk
Look for missing symlinks, missing files, size mismatches etc. Please post the output if you can.
Edit:
Did you run `mkinitcpio` after fixing the first missing symlink?
Last edited by loqs (2017-03-14 23:54:46)
Offline
Oh, yes I did forgot to... Sry for that.., I have however initiated a reinstall of all packages on the system, to ensure everything is like it should be. Will let you know if there is something else open. Thanks a ton for your help here
Last edited by wzrdtales (2017-03-15 00:03:40)
Offline
Chroot in but with /dev/sda1 mounted to /mnt/boot reinstall linux and GRUB#Generate_the_main_configuration_file
Reboot and there should be no panic.
Then unmount /boot/efi delete the contents of /boot change the /etc/fstab entry from /boot/efi/ to /boot then mount /boot
0. I have mounted /boot and /boot/efi and deleted everything.
1. Changed boot partition from /etc/fstab to point to /boot.
2. Reinstalled grub on my boot partition, reinstalled linux (4.10.2) and generated main grub configuration file.
Also, before all this I saw the posts mentioning /usr/lib64 so I did a check. I didn't have any /usr/lib64 directory so I reinstalled filesystem and now it's there.
Rebooted and everything it's back to normal.
Thanks for the support guys!!
Offline
There's been a number of people without /usr/lib64/. I'm guessing it's because of a updated that was --force'd. Don't do that.
Offline
There's been a number of people without /usr/lib64/. I'm guessing it's because of a updated that was --force'd. Don't do that.
I've done that just before this kernel panic.
I'll keep in mind to not do this anymore
Offline
Thanks for all your replies. Before updating there was indeed an issue with /usr/lib64. I then removed and recreated the symlink. But when I just verified (chroot), /usr/lib64 was gone. I recreated /usr/lib64 (ln -s /usr/lib /usr/lib64) and mkinitcpio afterwards. Now the system boots again!
Offline
deleted msg
Last edited by regenwald343434 (2017-03-20 23:36:01)
Offline
Welcome to the arch linux forums regenwald343434
Code_of_conduct#How_to_post
If a thread is marked as [SOLVED], do not reply stating the equivalent of "I am having a similar issue.."; start a new thread and link to the [SOLVED] thread, if relevant.
In the new thread please also include the exact commands you used to try to mount the ESP and their outputs.
Edit:
Also the output of
# blkid
Last edited by loqs (2017-03-20 23:24:08)
Offline
There's been a number of people without /usr/lib64/. I'm guessing it's because of a updated that was --force'd. Don't do that.
I faced with the same problem and this topic helped me to solve it. Thanks to all the people who wrote the useful tips here.
Offline
Glad to hear, however please don't necrobump old topics: https://wiki.archlinux.org/index.php/Co … bumping%22
Closing.
Offline