- #VIRTUALBOX LINUX KERNEL PANIC NOT SYNCING HOW TO#
- #VIRTUALBOX LINUX KERNEL PANIC NOT SYNCING INSTALL#
Once successfully booted into a Live environment to properly diagnose an issue you need to change its working directories to your borked systems directories.
#VIRTUALBOX LINUX KERNEL PANIC NOT SYNCING INSTALL#
I imagine you created a Live environment to install your system from. On a bare metal system the live boot media is created by burning the Manjaro ISO to a USB device or a DVD. When a system doesn't boot the only real way to diagnose the issue is to boot into a Manjaro Live environment. What VirtualBox packages do you have installed? How did you install VirtualBox? From the Manjaro repos or from the Oracle website? You should always use Manjaro repos IMO. Is there a step by step command line procedure I can do? That make it easier for me to understand/progress. To be honest, I did not understand what exactly to do with this: I just did the recomended update trough Pamac. I did not specifically go in the AUR section in Pamac in the guest machine to update anything.
#VIRTUALBOX LINUX KERNEL PANIC NOT SYNCING HOW TO#
Thank you for your reply, don't know how to find out about my init being systemd or openrc. I would make a snapshot of your VM before doing all this, just in case. I think this install process creates a new initramfs and reconfigures GRUB to include the new kernel. You could boot into your Live environment by attaching the Manjaro Live ISO file to the VM optical device, reboot your VM, once there mount your VM system root partition to /mnt, manjaro-chroot to reassign your root directories to /mnt, and use mhwd to install another kernel (ie 4.8 or 4.9) to your VM system. It may.ĭo you have any other kernels installed in your Manjaro VM, other than 4.4 LTS? If so try and boot into it. What is your host OS? If your host system is Manjaro also, did you update VirtualBox Oracle Extensions to 5.12 from AUR during your upgrade? This would cause a version mismatch as Manajro Stable is still on 5.10, but not sure it would cause this type of booting issue. Is your init systemd or openrc? You are on Manjaro Stable repos for this VM? Others more expert with GRUB config and/or mkinitcpio could hopefully provide more clarity here. Your VM Manjaro initramfs could be borked, or it could be a simple GRUB error. Unfortuanately, I don't know enough to explain the exact nature of the error.