You are not logged in.
Hi, I updated my system and got this.
Last edited by datxinitric (2017-12-10 12:09:13)
why use vim when there is vis?
Offline
What was updated? What is the pacman.log for the update? Is there an init present for the kernel to find? Is the bootloader passing correct options to find the init?
Offline
That message probably indicates that /boot was not properly mounted during a kernel upgrade but we really need to see more information, please supply complete details of your boot management strategy.
Jin, Jîyan, Azadî
Offline
What do you need to see
why use vim when there is vis?
Offline
Using live media mount all of the system's filesystem hierarchy under /mnt ready for chroot in then post the output of .
# findmnt /mntThen chroot in and please post the output of the following
# pacman -Q linux
# file /boot/initramfs-linux
# blkidThe systems pacman.log is located in /var/log/pacman.log please post the log from the update that caused this issue onward.
Details of what bootloader / boot manager the system uses as already requested and is the system using BIOS boot or EFI boot?
Offline
Mod note: moving to NC.
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
I reinstalled the grub and the problem is solverd
why use vim when there is vis?
Offline
PLease mark your thread as such.
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
If you consider the issue solved please mark it as such by prepending [SOLVED] to the thread title by editing your first post.
Edit:
beaten by WorMzy
Last edited by loqs (2017-12-10 11:28:01)
Offline