Appliance console shows "[DEPEND] Dependency failed for xxx" and "[ TIME ] Timed out waiting for device xxx" when booting OS on RSA SecurID Hardware Appliance Model 230(A230/R240)

[#1]

Article Number

000044492

Applies To

RSA Product Set: RSA SecurID
RSA Product/Service Type: Authentication Manager
RSA Version/Condition: 8.4.0, 8.5.0
Platform: SUSE Linux Enterprise Server
Platform (Other): RSA SecurID Hardware Appliance 230 based on the Dell PowerEdge R240 Server(A230)
O/S Version: 12 SP3

Issue

After booting SecurID Hardware Appliance 230 out of box, the appliance console shows "[DEPEND] Dependency failed for xxx" and "[ TIME ] Timed out waiting for device xxx" bellow:

Image description

In addition, messages log file in /var/log also records "[DEPEND] Dependency failed for xxx" and "[ TIME ] Timed out waiting for device xxx".

e.g) /var/log/messages

2020-10-01T20:30:47.885209+09:00 pri43 systemd[1]: dev-disk-by\x2did-scsi\x2d3500a0751277a985c\x2dpart2.device: Job dev-disk-by\x2did-scsi\x2d3500a0751277a985c\x2dpart2.device/start timed out.
2020-10-01T20:30:47.885374+09:00 pri43 systemd[1]: Timed out waiting for device dev-disk-by\x2did-scsi\x2d3500a0751277a985c\x2dpart2.device.
2020-10-01T20:30:47.885460+09:00 pri43 systemd[1]: Dependency failed for /boot/efi.
2020-10-01T20:30:47.885534+09:00 pri43 systemd[1]: boot-efi.mount: Job boot-efi.mount/start failed with result 'dependency'.
2020-10-01T20:30:47.885607+09:00 pri43 systemd[1]: dev-disk-by\x2did-scsi\x2d3500a0751277a985c\x2dpart2.device: Job dev-disk-by\x2did-scsi\x2d3500a0751277a985c\x2dpart2.device/start failed with result 'timeout'.
2020-10-01T20:30:47.885678+09:00 pri43 systemd[1]: dev-disk-by\x2did-scsi\x2d3500a0751277a985c\x2dpart3.device: Job dev-disk-by\x2did-scsi\x2d3500a0751277a985c\x2dpart3.device/start timed out.
2020-10-01T20:30:47.885751+09:00 pri43 systemd[1]: Timed out waiting for device dev-disk-by\x2did-scsi\x2d3500a0751277a985c\x2dpart3.device.
2020-10-01T20:30:47.885822+09:00 pri43 systemd[1]: Dependency failed for File System Check on /dev/disk/by-id/scsi-3500a0751277a985c-part3.
2020-10-01T20:30:47.885891+09:00 pri43 systemd[1]: Dependency failed for /boot.
2020-10-01T20:30:47.885962+09:00 pri43 systemd[1]: boot.mount: Job boot.mount/start failed with result 'dependency'.
2020-10-01T20:30:47.886030+09:00 pri43 systemd[1]: systemd-fsck@dev-disk-by\x2did-scsi\x2d3500a0751277a985c\x2dpart3.service: Job systemd-fsck@dev-disk-by\x2did-scsi\x2d3500a0751277a985c\x2dpart3.service/start failed with result 'dependency'.
2020-10-01T20:30:47.886100+09:00 pri43 systemd[1]: dev-disk-by\x2did-scsi\x2d3500a0751277a985c\x2dpart3.device: Job dev-disk-by\x2did-scsi\x2d3500a0751277a985c\x2dpart3.device/start failed with result 'timeout'.

This message occurs when booting or rebooting OS always.

Cause

In order to automatically mount devices when booting OS, OS searches for these devices using /etc/fstab. Default /etc/fstab configuration of RSA SecurID Hardware Appliance 230 maps "Device name" and "Mount point" using WWID(World Wide Identifier), which is unique identifier of device, but it sets wrong WWID. Therefore, the OS searches for incorrect devices but cannot find the them on RSA SecurID Hardware Appliance 230, OS fails to mount these devices when booting the OS. As a result, the appliance console and /var/log/messages show "Dependency failed" and "Timed out waiting for device".

Workaround

Correct device information in /etc/fstab.
 

Step 1. At first, check what devices were failed to mount to the appliance. Search for "Timed out waiting for device dev-disk-by" lines in /var/log/messages as follows:

2020-10-01T20:30:47.885374+09:00 pri43 systemd[1]: Timed out waiting for device dev-disk-by\x2did-scsi\x2d3500a0751277a985c\x2dpart2.device.
...
2020-10-01T20:30:47.885751+09:00 pri43 systemd[1]: Timed out waiting for device dev-disk-by\x2did-scsi\x2d3500a0751277a985c\x2dpart3.device.
...

As the above lines, you can find that "scsi\x2d3500a0751277a985c\x2dpart2" and "scsi\x2d3500a0751277a985c\x2dpart3" were failed.  "\x2d" is Regular expression. These can translate them as follows:

Before)

• scsi\x2d3500a0751277a985c\x2dpart2
• scsi\x2d3500a0751277a985c\x2dpart3

After)

• scsi-3500a0751277a985c-part2
• scsi-3500a0751277a985c-part3

This means that the appliance tried to mount "scsi-3500a0751277a985c-part2" and "scsi-3500a0751277a985c-part3" WWID devices but failed. Therefore, you need to correct these WWID in /etc/fstab.
 

Step 2. Login to the appliance, RSA SecurID Hardware Appliance 230, using ssh or appliance console.

Step 3. Switch user from rsaadmin to root user.

Step 4. Check correct WWID using the following command line:

# ls -l /dev/disk/by-id/ | grep "sda"
total 0
lrwxrwxrwx 1 root root 9 Nov 4 09:37 ata-HFS960G32FEH-BA10A_ES07N4164I0207G6V -> ../../sda
lrwxrwxrwx 1 root root 10 Nov 4 09:37 ata-HFS960G32FEH-BA10A_ES07N4164I0207G6V-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Nov 4 09:37 ata-HFS960G32FEH-BA10A_ES07N4164I0207G6V-part2 -> ../../sda2 // Note down this WWID
lrwxrwxrwx 1 root root 10 Nov 4 09:37 ata-HFS960G32FEH-BA10A_ES07N4164I0207G6V-part3 -> ../../sda3 // and Note down this WWID
lrwxrwxrwx 1 root root 10 Nov 4 09:37 ata-HFS960G32FEH-BA10A_ES07N4164I0207G6V-part4 -> ../../sda4
lrwxrwxrwx 1 root root 10 Nov 4 09:37 lvm-pv-uuid-ZYMNXJ-w8v5-MVZE-mURD-iunE-vK1i-CtvBjv -> ../../sda4
lrwxrwxrwx 1 root root 9 Nov 4 09:37 wwn-0x5ace42e02519da59 -> ../../sda
lrwxrwxrwx 1 root root 10 Nov 4 09:37 wwn-0x5ace42e02519da59-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Nov 4 09:37 wwn-0x5ace42e02519da59-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Nov 4 09:37 wwn-0x5ace42e02519da59-part3 -> ../../sda3
lrwxrwxrwx 1 root root 10 Nov 4 09:37 wwn-0x5ace42e02519da59-part4 -> ../../sda4

Note down "ata-xxxxxx-part2" and "ata-xxxxxx-part3" WWID. In this environment, "ata-HFS960G32FEH-BA10A_ES07N4164I0207G6V-part2" and "ata-HFS960G32FEH-BA10A_ES07N4164I0207G6V-part3" are correct WWID. These WWID can be different from your RSA SecurID Hardware Appliance 230 environment. So, you need to check WWIDs yourself on your RSA SecurID Hardware Appliance 230 environment.

Step 5. Modify from incorrect "part2" and "part3" lines of /etc/fstab to respective correct WWIDs noted down at step 4.

Before)

# cat /etc/fstab
/dev/systemVG/LVRoot / ext3 defaults 1 1
/dev/disk/by-id/scsi-35ace42e02519da59-part3 /boot ext3 defaults 1 2  // <-This is wrong WWID
/dev/disk/by-id/scsi-35ace42e02519da59-part2 /boot/efi vfat defaults 0 0 // <-This is also wrong WWID
/dev/systemVG/LVSwap swap swap defaults 0 0

After)

# cat /etc/fstab
/dev/systemVG/LVRoot / ext3 defaults 1 1
/dev/disk/by-id/ata-HFS960G32FEH-BA10A_ES07N4164I0207G6V-part3 /boot ext3 defaults 1 2 
/dev/disk/by-id/ata-HFS960G32FEH-BA10A_ES07N4164I0207G6V-part2 /boot/efi vfat defaults 0 0
/dev/systemVG/LVSwap swap swap defaults 0 0

Step 6. Reboot the appliance using the following command line:

# reboot -h now

After succeeded in booting the appliance, Check the appliance console will no longer shows "[DEPEND] Dependency failed for xxx" and "[ TIME ] Timed out waiting for device xxx" messages.
In addition, make sure that "/boot" and "/boot/efi" are mounted using "df -h" command line as follows:

# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 7.7G 0 7.7G 0% /dev
tmpfs 7.7G 4.0K 7.7G 1% /dev/shm
tmpfs 7.7G 8.7M 7.7G 1% /run
tmpfs 7.7G 0 7.7G 0% /sys/fs/cgroup
/dev/mapper/systemVG-LVRoot 876G 7.3G 824G 1% /
/dev/sda3 976M 96M 829M 11% /boot
/dev/sda2 200M 3.3M 197M 2% /boot/efi
tmpfs 1.6G 0 1.6G 0% /run/user/1000