My Oracle Support Banner

Exadata VM Goes To Reboot Loop Due to Existing Root Snapshot (Doc ID 2326897.1)

Last updated on OCTOBER 25, 2018

Applies to:

Oracle Exadata Storage Server Software - Version 11.2.1.2.0 and later
Information in this document applies to any platform.

Symptoms

 Exadata VM goes to a reboot loop with following console errors :

dracut Warning: No root device "block:/dev/disk/by-label/DBSYS" found

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.39-400.281.1.el6uek.x86_64 #1
Call Trace:
[<ffffffff8150b7fb>] panic+0xa6/0x1bd
[<ffffffff810618e2>] ? enqueue_entity+0x52/0x210
[<ffffffff81071deb>] forget_original_parent+0x32b/0x330
[<ffffffff8105b0af>] ? sched_move_task+0xaf/0x150
[<ffffffff81071e0b>] exit_notify+0x1b/0x190
[<ffffffff81072f0e>] do_exit+0x1fe/0x460
[<ffffffff810731c5>] do_group_exit+0x55/0xd0
[<ffffffff81073257>] sys_exit_group+0x17/0x20
[<ffffffff81516ba2>] system_call_fastpath+0x16/0x1b

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.