Epap R16.2 - Upgrade Accept Fails Due To Mdadm: Cannot Open /dev/sdb1: Device Or Resource Busy

Asset ID:	1-71-2395355.1
Update Date:	2018-05-07
Keywords:

Solution Type Technical Instruction Sure

Solution 2395355.1 : Epap R16.2 - Upgrade Accept Fails Due To Mdadm: Cannot Open /dev/sdb1: Device Or Resource Busy

Applies to:

Oracle Communications EAGLE (Software) - Version EPAP 16.2 and later
Information in this document applies to any platform.

Goal

False alarm "upgrade not accepted" showing after upgrade

Solution

Symptoms:
Accept was performed earlier. Initially an error is logged as below.

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 >>>
mdadm: Cannot open /dev/sdb1: Device or resource busy

Later everything looks fine.

cat /proc/mdstat shows both disks are synched.

> 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

Resolved the false situation by the following.
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".
You will see the following alarm in alarmStatus.
alarmMgr --alarmStatus
SEQ: 7 UPTIME: 356 BIRTH: 1524100682 TYPE: SET ALARM: TKSPLATMI33|tpdServerUpgradePendingAccept|1|32532|Processing Error|Configuration Error

To clear the alarm, run the following command:

alarmMgr --clear TKSPLATMI33

Attachments

This solution has no attachment