My Oracle Support Banner

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

Last updated on OCTOBER 25, 2023

Applies to:

Linux OS - Version 1.2.0-1 to 1.2.8-2 [Release OCFS2]
Linux OS - Version Oracle Linux 4.6 to Oracle Linux 5.1 [Release OL4U6 to OL5U1]
Oracle Cloud Infrastructure - Version N/A and later
Linux x86-64
Linux x86
Linux Kernel - Version: 1.2 to 1.2.8
Linux x86-64


A disk partition does not mount after a system boot, whether the reboot was 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:

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.


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
 Mounting By Label
 Mounting By UUID
 Using UDEV Rulesets

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