System Crash: Can't mount filesystem (Doc ID 2162974.1)

Last updated on AUGUST 11, 2016

Applies to:

Oracle VM - Version 3.0.1 and later
Information in this document applies to any platform.

Symptoms

An Oracle Linux 6 VM guest crashed with the following call trace:

EXT4-fs (xvda2): mounted filesystem with ordered data mode. Opts: (null)
dracut: Remounting /dev/disk/by-uuid/b072e1e9-05a9-4544-a4dd-b15ba49cea2f with -o localalloc=16,ro
EXT4-fs (xvda2): Unrecognized mount option "localalloc=16" or missing value
dracut: mount: wrong fs type, bad option, bad superblock on /dev/xvda2,
dracut: missing codepage or helper program, or other error
dracut: In some cases useful info is found in syslog - try
dracut: dmesg | tail or so
dracut:
dracut Warning: Can't mount root filesystem
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! exitcode=0x00000100

Pid: 1, comm: init Not tainted 3.8.13-118.2.1.el6uek.x86_64 #2
Call Trace:
[<ffffffff8159dae9>] panic+0xc4/0x1e4
[<ffffffff81124eee>] ? __perf_cgroup_move+0xe/0x20
[<ffffffff81064eac>] find_new_reaper+0x17c/0x180
[<ffffffff810657a5>] forget_original_parent+0x45/0x1d0
[<ffffffff81124ee0>] ? perf_cgroup_switch+0x190/0x190
[<ffffffff81065947>] exit_notify+0x17/0x140
[<ffffffff81067343>] do_exit+0x223/0x490
[<ffffffff81067605>] do_group_exit+0x55/0xd0
[<ffffffff81067697>] sys_exit_group+0x17/0x20
[<ffffffff815a99f9>] system_call_fastpath+0x16/0x1b

 

Changes

An invalid entry was added into /etc/fstab. After this, the VM guest was rebooted.

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