RSA Authentication Manager server fails to boot starting Dracut Emergency shell
8 days ago
Article Number
000073571
Applies To

RSA Product Set: ID Plus
RSA Product/Service Type: Authentication Manager

RSA Version/Condition: AM 8.7 SP1, 8.7 SP2, 8.8

Fixed in AM 8.8 patch 2, but problem observed again in AM 8.9 and AM 8.9 Patch 1

Issue

RSA Authentication Manager server fails to boot Entering Emergency Mode (Dracut Emergency shell) - with a warning /dev/sda3 does not exist 

Cause

/dev/sda3 is defined as root. Sometime restart fails with error "/dev/sda3 does not exist". 

This is a recognized behavior/bug in SUSE, where the disk partition label changes dynamically. At times, it does not match the label used during the Linux installation, which can lead to restart failures.

https://www.suse.com/support/kb/doc/?id=000018449

 

Resolution

Reboot the virtual machine. This restart should automatically fix the issue. 

It is observed that when rebooting the Virtual Machine from vSphere, you may bypass Emergency Mode; however, you will be unable to interact with anything while the start job for /dev/sda3 is running indefinitely.

In that case - Turn off the virtual machine via VMware vSphere or Hyper-V, and then restart it.

Note: The anticipated release of RSA Authentication Manager 8.8 P2 is provisionally set to incorporate the SUSE fix.

 

Workaround

If you find that you are frequently affected - Due to your scheduled maintenance activities necessitating regular server reboots - RSA support uses a workaround suggested by SUSE 
https://www.suse.com/releasenotes/x86_64/SUSE-SLES/15-SP2/index.html#jsc-SLE-11117

The RCA and workaround, are provided by SUSE and not by RSA for implementation. 

Below are steps to apply the changes in VM :

1. Find the storage drive name 

       lspci -nnk | grep -A3 -i "storage|sata|nvme"

2.  Edit grub file 

     vi /etc/default/grub

3. Look for the line:

GRUB_CMDLINE_LINUX_DEFAULT=

4.  Append the kernel parameter:  scsi_mod.disable_async_probing=mptspi 

     Keep the quotes and make sure there are no line breaks.

5. Save the file 

6. update the Gurb Config

    grub2-mkconfig -o /boot/grub2/grub.cfg

7. Reboot the VM

8. Verify the applied changes 

    cat /proc/cmdline