SUSE Support

Here When You Need Us

systemd[1]: Timed out waiting for device dev-mapper-hana_log\x2dhanalogTEST.device

This document (000020331) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 15
SUSE Linux Enterprise Server 12

Situation

Some systems with LVM, usually those with higher number of disks might fail booting
due to systemd time out such as:
  
May 21 09:49:59 sles_server systemd[1]: dev-mapper-hana_log\x2dhanalogTEST.device: Job dev-mapper-hana_log\x2dhanalogTEST.device/start timed out.
May 21 09:49:59 sles_server systemd[1]: Timed out waiting for device dev-mapper-hana_log\x2dhanalogTEST.device.
May 21 09:49:59 sles_server systemd[1]: Dependency failed for /hana/log/TEST.
May 21 09:49:59 sles_server systemd[1]: hana-log-TEST.mount: Job hana-log-TEST.mount/start failed with result 'dependency'.
May 21 09:49:59 sles_server systemd[1]: dev-mapper-hana_log\x2dhanalogTEST.device: Job dev-mapper-hana_log\x2dhanalogTEST.device/start failed with result 'timeout'.
May 21 09:49:59 sles_server systemd[1]: dev-mapper-hana_data\x2dhanadataTEST.device: Job dev-mapper-hana_data\x2dhanadataTEST.device/start timed out.
May 21 09:49:59 sles_server systemd[1]: Timed out waiting for device dev-mapper-hana_data\x2dhanadataTEST.device.
May 21 09:49:59 sles_server systemd[1]: Dependency failed for /hana/data/TEST.
May 21 09:49:59 sles_server systemd[1]: hana-data-TEST.mount: Job hana-data-TEST.mount/start failed with result 'dependency'.
May 21 09:49:59 sles_server systemd[1]: dev-mapper-hana_data\x2dhanadataTEST.device: Job dev-mapper-hana_data\x2dhanadataTEST.device/start failed with result 'timeout'.

Resolution

There are two ways to fix the timeout:
  1. add at least 600s timeout for the device in /etc/fstab
    An example entry might look like this:
    /dev/mapper/hana_inst-hanasharedTEST  /hana/shared/TEST  xfs  sunit=2048,swidth=28672,x-systemd.device-timeout=600  0  0
  2. change event_activation from 1 to 0 in /etc/lvm/lvm.conf
We recommend the second option as that will significantly improve the boot time.
 

Cause

This timeout is caused by lvm2 using too much time on iterating over /dev folder.
The default behavior with event_activation=1 in /etc/lvm/lvm.conf is event based activation mode.
While event_activation=0 is the direct activation mode.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:000020331
  • Creation Date: 13-Jul-2021
  • Modified Date:25-May-2023
    • SUSE Linux Enterprise Server

< Back to Support Search

For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com

tick icon

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community
tick icon

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.

Support FAQ
tick icon

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center