You are not logged in.
Pages: 1
[ 0.604352] Call Trace:
[ 0.604418] [<ffffffff812fdf50] dump_stack+0x63/0x83
[ 0.604489] [<ffffffff81175de5] panic+0xe4/0x266
[ 0.604557] [<ffffffff81b235b2>] mount_block_root+0x28a/0x2c5
[ 0.604626] [<ffffffff81b228db>] ? set_debug_rodata+0x12/0x12
[ 0.604695] [<ffffffff81b23652>] mount_root+0x65/0x68
[ 0.604762] [<ffffffff81b23784>] prepare_namespace+0x12f/0x167
[ 0.604832] [<ffffffff81b231e0>] kernel_init_freeable+0x1e2/0x1f9
[ 0.604904] [<ffffffff815eb17e>] kernel_init+0xe/0x100
[ 0.604972] [<ffffffff815eb17e>] ret_from_fork+0x1f/0x40
[ 0.605041] [<ffffffff815eb170>] ? rest_init+0x90/0x90
[ 0.605120] Kernel Offset: disabled
[ 0.605182] ---[ end Kernel Panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
So, I just installed Arch onto my laptop's slave drive (/dev/sdb) using the installation guide in the wiki, then I went to the distro controlling the laptop's Grub bootup (LXLE on /dev/sda) and updated grub using the update-grub command and got this error when I tried to boot into Arch. When that didn't work I tried the grub-mkconfig -o /boot/grub/grub.cfg command and got the same error.
Any help would be appreciated.
Last edited by nikaido (2016-12-04 02:14:57)
Offline
At grub-mkconfig, verify that you point the right partitions.
First re-create your mbr, install os_prober and then update with grub-mkconfig.
EDIT: Is it bios of uefi system?
Last edited by alex.theoto (2016-12-04 13:43:20)
Offline
I'm no kernel-guy myself, but why don't you try and boot from whichever installation media(a USB stick) you used to install Arch and try fixing grub from there?
Mount your LXLE /boot partition(for instance at /mnt/boot)
Attempt
grub-install --boot-directory=/mnt/boot /dev/sda
and then do
grub-mkconfig -o /mnt/boot/grub/grub.cfg
That should fix it for you. If on that step grub will somehow fail to detect your other system(LXLE), you will need to manually add it to the grub.cfg
Offline
EDIT: Is it bios of uefi system?
Bios. My Aspire E5-573 has both a Legacy (traditional bios) and a UEFI setting. Currently using firmware version 1.31, still need to upgrade to 1.35.
Last edited by nikaido (2016-12-04 15:50:13)
Offline
look at the last line, google it - you'll also find results in this forum.
cause is usually either
* broken grub config
* root partition not flagged bootable
* bad installation (initramfs lacks or uses modules of another kernel version)
Offline
Thank you for giving me a list of possible causes to investigate. It makes things a lot easier.
Offline
Pages: 1