Guest VM Fails to Boot Due to Filesystem Corruption with 'EXT3-fs (xvda2): recovery required on readonly filesystem'

(Doc ID 2397530.1)

Last updated on MAY 25, 2018

Applies to:

Oracle VM - Version 3.0.1 and later
Linux x86-64

Symptoms

VM guest fails to boot due to filesystem corruption. Following appears on the console:

blkfront: xvda: flush diskcache: enabled; persistent grants: enabled; indirect descriptors: enabled;
xvda: xvda1 xvda2 xvda3
xen_netfront: Initialising Xen virtual ethernet driver
device-mapper: uevent: version 1.0.3
device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) initialised: dm-devel@redhat.com
EXT3-fs (xvda2): recovery required on readonly filesystem
EXT3-fs (xvda2): write access will be enabled during recovery
EXT3-fs: barriers not enabled
JBD: recovery failed
EXT3-fs (xvda2): error loading journal
Kernel panic - not syncing: Attempted to kill init!
Pid: 1, comm: init Not tainted 2.6.39-400.215.10.el5uek #1
Call Trace:
[<c045dd50>] ? printk+0x20/0x30
[<c045cce2>] panic+0x72/0x190
[<c045ef7e>] find_new_reaper+0x9e/0xa0
[<c0460f14>] forget_original_parent+0x34/0x160
[<c04a576c>] ? cgroup_exit+0xac/0xf0
[<c0461053>] exit_notify+0x13/0x140
[<c04613d2>] do_exit+0x252/0x3d0
[<c0461589>] do_group_exit+0x39/0xa0
[<c0461604>] sys_exit_group+0x14/0x20
[<c087b084>] syscall_call+0x7/0xb
[<c0870000>] ? early_init_amd+0xb0/0x120

 

Changes

 VM was rebooted, but failed to boot back.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms