Inconsistent Device Names Across Reboot Cause Mount Failure or Incorrect Mount (Doc ID 563711.1)

Last updated on JUNE 10, 2009

Applies to:

Linux Kernel - Version: 4.6 to 5.1
Linux Kernel - Version: 1.2 to 1.2.8
Linux x86-64


A disk partition does not mount after a system boot, whether planned or unplanned.  Before the reboot, the disk partition was mounted and working properly.  The disk has mounted correctly after other system reboots, but no longer works.

This behavior can happen regardless of the type of file system on the partition and is unrelated to the file system type.  Failures of disks with EXT3 or OCFS2 file systems have been reported, but can happen with any file system type.

A typical entry in the /etc/fstab file could be similar to:

/dev/sda1          /mydir    ext3   defaults  0 0
/dev/mapper/mpath2 /otherdir ocfs2  _netdev   0 0
or various combinations of these.


Reboot of either the SAN or the client machine.  Note that both planned and unplanned reboots are susceptible to this issue.


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