Epap R16.2 - Upgrade accept failed with error mdadm: Cannot open /dev/sdb1: Device or resource busy

Asset ID:	1-72-2395287.1
Update Date:	2018-05-14
Keywords:

Solution Type Problem Resolution Sure

Solution 2395287.1 : Epap R16.2 - Upgrade accept failed with error mdadm: Cannot open /dev/sdb1: Device or resource busy

Applies to:

Oracle Communications EAGLE (Software) - Version EPAP 16.2 and later
Tekelec

Symptoms

On : EPAP 16.2 version, EPAP (Production)

Problem Details:
==========

EPAP Failed to accept upgrade on R16.2

ERROR
=====

[admusr@mps-xxx ~]$ sudo su - platcfg
Called with options: --accept
Loading Backout::BackoutType::SPLIT_MIRROR
Accepting Upgrade
Re-joining raid mirrors.
Adding /dev/sdb2 to /dev/md1
mdadm: added /dev/sdb2
Adding /dev/sdb1 to /dev/md2
ERROR: Command Failed!
ERROR: Child process has exited with:
CMD: '/sbin/mdadm --add /dev/md2 /dev/sdb1'
RC: 1
SIGNAL: 0
CORE: no
<<< CMD OUTPUT >>>

alarmMgr showed following alarm

====================

Changes

Cause

it appears the accept action failed to update the /etc/motd. The RAID was rejoined, but there was no additional logging in the upgrade logs.

syscheck and mdstat are clean:

[root@mps-xxx ~]# syscheck
Running modules in class disk...
OK
Running modules in class hardware...
OK
Running modules in class net...
OK
Running modules in class proc...
OK
Running modules in class services...
OK
Running modules in class system...
OK
Running modules in class upgrade...
OK
LOG LOCATION: /var/TKLC/log/syscheck/fail_log

multiple-disk, RAID configurations are good.

[root@mps-5131-xxx]# cat /proc/mdstat
Personalities : [raid1]
md1 : active raid1 sdb2[2] sda2[0]
262080 blocks super 1.0 [2/2] [UU]

md2 : active raid1 sdb1[1] sda1[0]
292631552 blocks super 1.1 [2/2] [UU]
bitmap: 2/3 pages [8KB], 65536KB chunk

unused devices: <none>

Solution

Resolved the false situation by the following.

For TAC Only -

1. Blankout the /etc/motd file > /etc/motd

2. Add an entry "export POST_UPGRADE_ACTION=done" in the file /var/TKLC/log/upgrade/upgrade.conf

3. Clear the false alarm "TKSPLATMI33" - alarmMgr --clear TKSPLATMI33

Attachments

This solution has no attachment