After Planned Server Restart Exalytics OVM Failing With Errors: "bond1.340 on EXALOVS4 is locked, description: Start Virtual Machine" (Doc ID 1961148.1)

Last updated on DECEMBER 01, 2016

Applies to:

Oracle Exalytics Software - Version 1.0.0.3.0 and later
Exalytics In-Memory Machine X3-4 - Version All Versions and later
Linux OS - Version Oracle Linux 5.5 and later
Information in this document applies to any platform.

Symptoms

Exalytics machine with four Oracle Virtual Machines (OVM) was gracefully shut down as part of a planned outage.  After restarting the machine, three of the VM's start successfully, but the fourth one fails to start.
It starts to load, but then fails with error like:

bond1.340 on EXALOVS4 is locked, description: Start Virtual Machine

Standard out shows error like:

Server error message: Command: ['xm', 'create',
'/OVS/repositories/0004fb0000030000fe8c6dc76a896e69/virtual Machines/0004fb000006000084d6d95be29917a7/vm.cfg']
failed (1): stderr: Error: Device 268439808 (vdb) could not be connected.
/dev/mapper/SATA_3E128-TS2-550B0_FL008Y1D does not exist.
stdout: Using config file
"/OVS/Repositories/0004fb0000030000fe8c6dc76a896e69/virtual Machines/0004fb000006000084d6d95be29917a7/vm.cfg".

 

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