Kernel Panic on CentOS - Google Compute Engine Instance
I'm getting a kernel panic error in a CentOS instance of Google Compute Engine. I'm able to see the error and already figure out how to solve it, but I can't get into the GRUB menu trough the serial console.
dracut: Mounted root filesystem /dev/sda1
dracut: Loading SELinux policy
type=1404 audit(1479929075.614:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
dracut: SELinux: Could not open policy file <= /etc/selinux/targeted/policy/policy.24: No such file or directory
/sbin/load_policy: Can't load policy and enforcing mode requested: No such file or directory
dracut Warning: Initial SELinux policy load failed.
dracut FATAL: Initial SELinux policy load failed. Machine in enforcing mode. To disable selinux, add selinux=0 t
o the kernel command line.
dracut Warning:
dracut Warning: Boot has failed. To debug this issue add "rdshell" to the kernel command line.
dracut Warning: Signal caught!
dracut Warning: Boot has failed. To debug this issue add "rdshell" to the kernel command line.
Kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: init Not tainted 2.6.32-642.11.1.el6.x86_64 #1
Call Trace:
[<ffffffff815482b1>] ? panic+0xa7/0x179
[<ffffffff8112aea0>] ? perf_event_exit_task+0xc0/0x340
[<ffffffff81081f97>] ? do_exit+0x867/0x870
[<ffffffff8119b735>] ? fput+0x25/0x30
[<ffffffff81081ff8>] ? do_group_exit+0x58/0xd0
[<ffffffff81082087>] ? sys_exit_group+0x17/0x20
[<ffffffff8100b0d2>] ? system_call_fastpath+0x16/0x1b
The CentOS version is 6.7 and this happened after a yum update. I'm just trying to get into GRUBs menu to append "selinux=0" to boot into Permissive mode, but it seems that it's not possible through the serial console. I would appreciate any help.
linux centos kernel-panic cloud
asked Nov 24 '16 at 13:09
João FelipeJoão Felipe
13
bumped to the homepage by Community♦ 5 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I'm getting a kernel panic error in a CentOS instance of Google Compute Engine. I'm able to see the error and already figure out how to solve it, but I can't get into the GRUB menu trough the serial console.
dracut: Mounted root filesystem /dev/sda1
dracut: Loading SELinux policy
type=1404 audit(1479929075.614:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
dracut: SELinux: Could not open policy file <= /etc/selinux/targeted/policy/policy.24: No such file or directory
/sbin/load_policy: Can't load policy and enforcing mode requested: No such file or directory
dracut Warning: Initial SELinux policy load failed.
dracut FATAL: Initial SELinux policy load failed. Machine in enforcing mode. To disable selinux, add selinux=0 t
o the kernel command line.
dracut Warning:
dracut Warning: Boot has failed. To debug this issue add "rdshell" to the kernel command line.
dracut Warning: Signal caught!
dracut Warning: Boot has failed. To debug this issue add "rdshell" to the kernel command line.
Kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: init Not tainted 2.6.32-642.11.1.el6.x86_64 #1
Call Trace:
[<ffffffff815482b1>] ? panic+0xa7/0x179
[<ffffffff8112aea0>] ? perf_event_exit_task+0xc0/0x340
[<ffffffff81081f97>] ? do_exit+0x867/0x870
[<ffffffff8119b735>] ? fput+0x25/0x30
[<ffffffff81081ff8>] ? do_group_exit+0x58/0xd0
[<ffffffff81082087>] ? sys_exit_group+0x17/0x20
[<ffffffff8100b0d2>] ? system_call_fastpath+0x16/0x1b
The CentOS version is 6.7 and this happened after a yum update. I'm just trying to get into GRUBs menu to append "selinux=0" to boot into Permissive mode, but it seems that it's not possible through the serial console. I would appreciate any help.
linux centos kernel-panic cloud
asked Nov 24 '16 at 13:09
João FelipeJoão Felipe
13
bumped to the homepage by Community♦ 5 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
2.6.32 is a very-very old kernel
– Ipor Sircer
Nov 24 '16 at 13:17
add a comment |
I'm getting a kernel panic error in a CentOS instance of Google Compute Engine. I'm able to see the error and already figure out how to solve it, but I can't get into the GRUB menu trough the serial console.
dracut: Mounted root filesystem /dev/sda1
dracut: Loading SELinux policy
type=1404 audit(1479929075.614:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
dracut: SELinux: Could not open policy file <= /etc/selinux/targeted/policy/policy.24: No such file or directory
/sbin/load_policy: Can't load policy and enforcing mode requested: No such file or directory
dracut Warning: Initial SELinux policy load failed.
dracut FATAL: Initial SELinux policy load failed. Machine in enforcing mode. To disable selinux, add selinux=0 t
o the kernel command line.
dracut Warning:
dracut Warning: Boot has failed. To debug this issue add "rdshell" to the kernel command line.
dracut Warning: Signal caught!
dracut Warning: Boot has failed. To debug this issue add "rdshell" to the kernel command line.
Kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: init Not tainted 2.6.32-642.11.1.el6.x86_64 #1
Call Trace:
[<ffffffff815482b1>] ? panic+0xa7/0x179
[<ffffffff8112aea0>] ? perf_event_exit_task+0xc0/0x340
[<ffffffff81081f97>] ? do_exit+0x867/0x870
[<ffffffff8119b735>] ? fput+0x25/0x30
[<ffffffff81081ff8>] ? do_group_exit+0x58/0xd0
[<ffffffff81082087>] ? sys_exit_group+0x17/0x20
[<ffffffff8100b0d2>] ? system_call_fastpath+0x16/0x1b
The CentOS version is 6.7 and this happened after a yum update. I'm just trying to get into GRUBs menu to append "selinux=0" to boot into Permissive mode, but it seems that it's not possible through the serial console. I would appreciate any help.
linux centos kernel-panic cloud
asked Nov 24 '16 at 13:09
João FelipeJoão Felipe
13
I'm getting a kernel panic error in a CentOS instance of Google Compute Engine. I'm able to see the error and already figure out how to solve it, but I can't get into the GRUB menu trough the serial console.
dracut: Mounted root filesystem /dev/sda1
dracut: Loading SELinux policy
type=1404 audit(1479929075.614:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
dracut: SELinux: Could not open policy file <= /etc/selinux/targeted/policy/policy.24: No such file or directory
/sbin/load_policy: Can't load policy and enforcing mode requested: No such file or directory
dracut Warning: Initial SELinux policy load failed.
dracut FATAL: Initial SELinux policy load failed. Machine in enforcing mode. To disable selinux, add selinux=0 t
o the kernel command line.
dracut Warning:
dracut Warning: Boot has failed. To debug this issue add "rdshell" to the kernel command line.
dracut Warning: Signal caught!
dracut Warning: Boot has failed. To debug this issue add "rdshell" to the kernel command line.
Kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: init Not tainted 2.6.32-642.11.1.el6.x86_64 #1
Call Trace:
[<ffffffff815482b1>] ? panic+0xa7/0x179
[<ffffffff8112aea0>] ? perf_event_exit_task+0xc0/0x340
[<ffffffff81081f97>] ? do_exit+0x867/0x870
[<ffffffff8119b735>] ? fput+0x25/0x30
[<ffffffff81081ff8>] ? do_group_exit+0x58/0xd0
[<ffffffff81082087>] ? sys_exit_group+0x17/0x20
[<ffffffff8100b0d2>] ? system_call_fastpath+0x16/0x1b
The CentOS version is 6.7 and this happened after a yum update. I'm just trying to get into GRUBs menu to append "selinux=0" to boot into Permissive mode, but it seems that it's not possible through the serial console. I would appreciate any help.
linux centos kernel-panic cloud
linux centos kernel-panic cloud
asked Nov 24 '16 at 13:09
João FelipeJoão Felipe
13
asked Nov 24 '16 at 13:09
João FelipeJoão Felipe
13
asked Nov 24 '16 at 13:09
João FelipeJoão Felipe
13
asked Nov 24 '16 at 13:09
João FelipeJoão Felipe
13
asked Nov 24 '16 at 13:09
João FelipeJoão Felipe
13
13
bumped to the homepage by Community♦ 5 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 5 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
2.6.32 is a very-very old kernel
– Ipor Sircer
Nov 24 '16 at 13:17
add a comment |
2.6.32 is a very-very old kernel
– Ipor Sircer
Nov 24 '16 at 13:17
2.6.32 is a very-very old kernel
– Ipor Sircer
Nov 24 '16 at 13:17
2.6.32 is a very-very old kernel
– Ipor Sircer
Nov 24 '16 at 13:17
add a comment |
1 Answer
1
active
oldest
votes
I've made a work around and got my instance running again. The basic problem is that, by default, linux instances on Google Cloud are set to zero timeout at GRUBs menu . So, you cannot access the menu, even through the serial console. I will describe the steps I made to restore my instance.
- Create a snapshot of the machine startup disk.
- Create a disk which the source is the snapshot created on the first step. Let's call it rescue-disk.
- Launch a new Linux instance. May be the micro instance and you can delete it later. Call it rescue-instance.
- Attach the rescue-disk to the rescue-instance.
- From the rescue-instance mount the rescue-disk and change the
<mount point>/etc/grub.confas follow:
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-642.11.1.el6.x86_64 ro root=UUID=23f78139-a1ac-4a7a-b608-05687cecfa37 selinux=0
- De-attach rescue-disk from the rescue-instance and delete that instance if you want.
- Launch a new instance which the source is the rescue-disk. You can do that in the disk.
If you already have another linux instance running on your gcloud you don't need to create a new instance, just use VM you have.
answered Nov 25 '16 at 13:34
João FelipeJoão Felipe
13
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f325743%2fkernel-panic-on-centos-google-compute-engine-instance%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I've made a work around and got my instance running again. The basic problem is that, by default, linux instances on Google Cloud are set to zero timeout at GRUBs menu . So, you cannot access the menu, even through the serial console. I will describe the steps I made to restore my instance.
- Create a snapshot of the machine startup disk.
- Create a disk which the source is the snapshot created on the first step. Let's call it rescue-disk.
- Launch a new Linux instance. May be the micro instance and you can delete it later. Call it rescue-instance.
- Attach the rescue-disk to the rescue-instance.
- From the rescue-instance mount the rescue-disk and change the
<mount point>/etc/grub.confas follow:
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-642.11.1.el6.x86_64 ro root=UUID=23f78139-a1ac-4a7a-b608-05687cecfa37 selinux=0
- De-attach rescue-disk from the rescue-instance and delete that instance if you want.
- Launch a new instance which the source is the rescue-disk. You can do that in the disk.
If you already have another linux instance running on your gcloud you don't need to create a new instance, just use VM you have.
answered Nov 25 '16 at 13:34
João FelipeJoão Felipe
13
add a comment |
I've made a work around and got my instance running again. The basic problem is that, by default, linux instances on Google Cloud are set to zero timeout at GRUBs menu . So, you cannot access the menu, even through the serial console. I will describe the steps I made to restore my instance.
- Create a snapshot of the machine startup disk.
- Create a disk which the source is the snapshot created on the first step. Let's call it rescue-disk.
- Launch a new Linux instance. May be the micro instance and you can delete it later. Call it rescue-instance.
- Attach the rescue-disk to the rescue-instance.
- From the rescue-instance mount the rescue-disk and change the
<mount point>/etc/grub.confas follow:
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-642.11.1.el6.x86_64 ro root=UUID=23f78139-a1ac-4a7a-b608-05687cecfa37 selinux=0
- De-attach rescue-disk from the rescue-instance and delete that instance if you want.
- Launch a new instance which the source is the rescue-disk. You can do that in the disk.
If you already have another linux instance running on your gcloud you don't need to create a new instance, just use VM you have.
answered Nov 25 '16 at 13:34
João FelipeJoão Felipe
13
add a comment |
I've made a work around and got my instance running again. The basic problem is that, by default, linux instances on Google Cloud are set to zero timeout at GRUBs menu . So, you cannot access the menu, even through the serial console. I will describe the steps I made to restore my instance.
- Create a snapshot of the machine startup disk.
- Create a disk which the source is the snapshot created on the first step. Let's call it rescue-disk.
- Launch a new Linux instance. May be the micro instance and you can delete it later. Call it rescue-instance.
- Attach the rescue-disk to the rescue-instance.
- From the rescue-instance mount the rescue-disk and change the
<mount point>/etc/grub.confas follow:
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-642.11.1.el6.x86_64 ro root=UUID=23f78139-a1ac-4a7a-b608-05687cecfa37 selinux=0
- De-attach rescue-disk from the rescue-instance and delete that instance if you want.
- Launch a new instance which the source is the rescue-disk. You can do that in the disk.
If you already have another linux instance running on your gcloud you don't need to create a new instance, just use VM you have.
answered Nov 25 '16 at 13:34
João FelipeJoão Felipe
13
I've made a work around and got my instance running again. The basic problem is that, by default, linux instances on Google Cloud are set to zero timeout at GRUBs menu . So, you cannot access the menu, even through the serial console. I will describe the steps I made to restore my instance.
- Create a snapshot of the machine startup disk.
- Create a disk which the source is the snapshot created on the first step. Let's call it rescue-disk.
- Launch a new Linux instance. May be the micro instance and you can delete it later. Call it rescue-instance.
- Attach the rescue-disk to the rescue-instance.
- From the rescue-instance mount the rescue-disk and change the
<mount point>/etc/grub.confas follow:
root (hd0,0)
kernel /boot/vmlinuz-2.6.32-642.11.1.el6.x86_64 ro root=UUID=23f78139-a1ac-4a7a-b608-05687cecfa37 selinux=0
- De-attach rescue-disk from the rescue-instance and delete that instance if you want.
- Launch a new instance which the source is the rescue-disk. You can do that in the disk.
If you already have another linux instance running on your gcloud you don't need to create a new instance, just use VM you have.
answered Nov 25 '16 at 13:34
João FelipeJoão Felipe
13
edited Nov 25 '16 at 13:39
answered Nov 25 '16 at 13:34
João FelipeJoão Felipe
13
answered Nov 25 '16 at 13:34
João FelipeJoão Felipe
13
answered Nov 25 '16 at 13:34
João FelipeJoão Felipe
13
13
add a comment |
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f325743%2fkernel-panic-on-centos-google-compute-engine-instance%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2.6.32 is a very-very old kernel
– Ipor Sircer
Nov 24 '16 at 13:17