VG doesn't get activated at boot time which are coming from scini block device

Solution Verified - Updated -

Environment

  • Red Hat Enterprise Linux 7
  • Red Hat Enterprise Linux 8
  • Red Hat Enterprise Linux 9
  • Dell ScaleIO block device.

Issue

  • VG doesn't get activated at boot time which is coming from scini block device.

Resolution

  • As ScaleIOor Scini devices are the intellectual property of Dell EMC, It is advised to reach out to a vendor.

Root Cause

  • There is race condition between lvm and ScaleIO devices (scini). The scini service which is required to create scini backed devices is starting in the later stage of the boot process while the lvm2-activation service starts earlier which causes lvm volumes to be left deactivated.

Diagnostic Steps

  • Underlying file system logs a timed out message at boot time in journal logs.
Jun 01 19:32:35 client.example.com systemd[1]: grid.mount: Job grid.mount/start failed with result 'dependency'.
Jun 01 19:32:35 client.example.com systemd[1]: dev-mapper-grid_vg\x2dgrid_lv.device: Job dev-mapper-grid_vg\x2dgrid_lv.device/start failed with result 'timeout'.
Jun 01 19:32:35 client.example.com systemd[1]: dev-mapper-oracle_vg\x2doracle_lv.device: Job dev-mapper-oracle_vg\x2doracle_lv.device/start timed out.
Jun 01 19:32:35 client.example.com systemd[1]: Timed out waiting for device dev-mapper-oracle_vg\x2doracle_lv.device.
  • Even lvscan command shows logical volume as inactive.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments