FS#38447 - [grub] 2.02 kernel panic with one of the entries
Attached to Project:
Arch Linux
Opened by Charles Bos (Chazza) - Friday, 10 January 2014, 21:56 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 08 April 2014, 06:27 GMT
Opened by Charles Bos (Chazza) - Friday, 10 January 2014, 21:56 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 08 April 2014, 06:27 GMT
|
Details
Description:
The problem is that one of the menu entries generated with grub 2.02 gives me a kernel panic. This is my setup: Windows 7 on /dev/sda1 and /dev/sda2 Arch linux root partition on /dev/sda3 with both the linux and linux-lts kernels. Swap and home partitions contained in an extended partition. When I run grub-mkconfig -o /boot/grub/grub.cfg it produces a standard entry and a fallback entry for both the linux and linux-lts kernels as well as a Windows entry. These entries all work fine. But it also produces a couple of new menu entries: "Arch Linux" and "Advanced options for Arch Linux." The plain "Arch Linux" entry attempts to boot the lts kernel at which point there is a kernel panic. Additional info: * package version(s) grub 1:2.02.beta2-1 linux 3.12.6-1 linux-lts 3.10.25-1 os-prober 1.58-1 * config and/or log files etc. Steps to reproduce: Attempt to boot the "Arch Linux" menu entry in grub 2.02 |
This task depends upon
core/grub 1:2.02.beta2-1
trunk/grub 1:2.02.beta2-1
For me, it is 1:2.02.beta2-1 that causes the kernel panic with one entry and the following for the default boot entry:
"ERROR: Boot device mounted suffesscully but /sbin/init does not exist.
Bailling out, you are on your own. Good luck.
sh: can't access tty: job control turned off
[rootfs /]#"
I have attached two grub.cfg files generated by grub-mkconfig named for their respective versions. I hope these help you troubleshoot... they don't look as though the problem originates therein to me. This might be an upstream bug.
grub.cfg-1:2.02.beta2-1 (6.9 KiB)
As graysky says it IS beta2 that generates the menu that causes the kernel panic.
@graysky I am not familiar with the problems you are describing. I have not encountered any /sbin/init errors. perhaps yours is a seperate issue?
There is one very minor issue I should mention though. In the Advanced options for Arch Linux menu the entries are named something like 'Arch Linux with linux linux'
The entry boots just fine but the naming is a little odd.