Failure when booting after BTRFS snapshot rollback (Kernel panic)

Hi, I have identified this issue on Debian 9.6 with linux-kernel 4.18.0, snapper 0.8.2-1 and grub-common 2.02+dfsg1-8: The system will not boot a snapshot that was rolled back with snapper and run into Kernel panic when selecting default grub entry. Steps to reproduce the issue: 1. Boot

Failure when booting after BTRFS snapshot rollback (Kernel panic)

Hi, I have identified this issue on Debian 9.6 with linux-kernel 4.18.0, snapper 0.8.2-1 and grub-common 2.02+dfsg1-8: The system will not boot a snapshot that was rolled back with snapper and run into Kernel panic when selecting default grub entry. Steps to reproduce the issue: 1. Boot

Failure when booting after BTRFS snapshot rollback (Kernel panic)

Hi, I have identified this issue on Debian 9.6 with linux-kernel 4.18.0, snapper 0.8.1 and grub-common 2.02+dfsg1-8: The system will not boot a snapshot that was rolled back with snapper and run into Kernel panic when selecting default grub entry. Steps to reproduce the issue: 1. Boot snapshot

Re: kernel panic

Hello, perhaps you remember. Got a kernel panic when booting with grub from floppy, though the same kernel / system always did bootup ok with lilo (mbr). This was kernel 2.4.17 custom, then; a very early compile two years ago, when i didn't know about most of it's functions. So i recompiled

Re: kernel panic

The kernel error message ( an oops, as it is called ) is a kernel error ( bug ). Report it. The instructions for reporting are written in the kernel sources. ( the file BUGS or README I am not sure which ) As it is 99% a kernel error, fix it by upgrading to a never version, like 2.4.20. You may

Re: kernel panic

Hello, thanks for reply. I didn't pick up the task until now, but will in a few days. David Balazic [Monday, 24. March 2003 10:28]: | You may post your working lilo.conf , so we can compare it to your | (non-working) grub setup. So here it is.

Re: kernel panic

mi wrote: Hello, thanks for reply. I didn't pick up the task until now, but will in a few days. David Balazic [Monday, 24. March 2003 10:28]: | You may post your working lilo.conf , so we can compare it to your | (non-working) grub setup. So here it is. The first obvious difference is

kernel panic

. Unfortunateley both titles end up in a kernel panic. It's halted after 'freeing unused memory 224k', saying 'unable to read requested page' then spitting out a bunch of cryptic numbers. It's the same 2.4.17 from the harddrive, booting with lilo fairly well. I think the problem is i am not used

Re: [grub #33] Kernel panic error

, resulting in xconfig having the appropriate default kernel parameters that the kernel I presently boot has, I think) 5. using grub, I get the kernel panic error VFS = Cannot open root device LABEL=/ with only the newly compiled kernel 6. my grub.conf file should be correct - its paramters

Re: [grub #33] Kernel panic error

the appropriate default kernel parameters that the kernel I presently boot has, I think) 5. using grub, I get the kernel panic error VFS = Cannot open root device LABEL=/ with only the newly compiled kernel 6. my grub.conf file should be correct - its paramters exactly match the parameters for the kernel

Kernel panic: No init found

getting a kernel panic on mounting the root filesystem. Here are the boot messages: ... Mounting /proc (all the LVM stuff gets activated successfully - / is not under LVM BTW) Mounting root filesystem kjournald starting. Commit interval 5 seconds EXT3-fs: mounted filesystem with ordered data mode

Re: Kernel panic: No init found

is that I get the GRUB splash menu. The bad thing is that I'm getting a kernel panic on mounting the root filesystem. Here are the boot messages: ... Mounting /proc (all the LVM stuff gets activated successfully - / is not under LVM BTW) Mounting root filesystem kjournald starting. Commit

Re: Kernel panic: No init found

(hd0,0) chainloader +1 I did a grub-install /dev/hdc and rebooted. Good thing is that I get the GRUB splash menu. The bad thing is that I'm getting a kernel panic on mounting the root filesystem. Here are the boot messages: ... Mounting /proc (all the LVM stuff gets

Re: Kernel panic: No init found

/initrd-2.4.18-14.img title DOS rootnoverify (hd0,0) chainloader +1 I did a grub-install /dev/hdc and rebooted. Good thing is that I get the GRUB splash menu. The bad thing is that I'm getting a kernel panic on mounting the root filesystem. Here

Re: [grub #33] Kernel panic error

. Grub has nothing to do with this error. Hari From: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: BugCommunicator [EMAIL PROTECTED] Subject: [grub #33] Kernel panic error Date: Fri, 31 Jan 2003 12:35:05 +0900 Reporter: [EMAIL PROTECTED] Summary: Kernel panic error Version: grub-0.92-7.i386

[grub #33] Kernel panic error

Reporter: [EMAIL PROTECTED] Summary: Kernel panic error Version: grub-0.92-7.i386 Type: software bug Message: I Have a redhat 8.0 system, kernel 2.4.20 ( the kernel that I'm trying to boot). I compiled my 2.4.20 new kernel and when I try to boot I get this error message: VFS = Cannot open root

Kernel Panic

Hi... Wonder if someone can help..I have read the hoetos and mailed to various list with no joy I am using grub to boot from libranet linux on hdb3..I am also booting xp on hda1 and suse on hda4.Thes all boot ok..I am trying to boot hdb1 suse but get a message KERNEL PANIC VFS unable

Re: Kernel Panic

using grub to boot from libranet linux on hdb3..I am also booting xp on hda1 and suse on hda4.Thes all boot ok..I am trying to boot hdb1 suse but get a message KERNEL PANIC VFS unable to mount root fs on 03.41 These are my boot lines title Windows XP chainloader = (hd0,1)+1