The history below show attempting to start ilm without the -D 1 and it hits a start limit. Then the -D 1 is added and it starts OK. Then the -D 1 is removed and it fails.
[root@node3 ~]# systemctl status seagate_ilm.service
● seagate_ilm.service - In Drive Mutex Locking Manager for Speedboat
Loaded: loaded (/etc/systemd/system/seagate_ilm.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) since Fri 2020-09-18 09:21:11 CDT; 458ms ago
Process: 10547 ExecStart=/usr/sbin/seagate_ilm -l 0 -L 7 -E 7 -S 7 (code=exited, status=0/SUCCESS)
Main PID: 10547 (code=exited, status=0/SUCCESS)
[root@node3 ~]# systemctl status seagate_ilm.service
● seagate_ilm.service - In Drive Mutex Locking Manager for Speedboat
Loaded: loaded (/etc/systemd/system/seagate_ilm.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) since Fri 2020-09-18 09:21:15 CDT; 555ms ago
Process: 10557 ExecStart=/usr/sbin/seagate_ilm -l 0 -L 7 -E 7 -S 7 (code=exited, status=0/SUCCESS)
Main PID: 10557 (code=exited, status=0/SUCCESS)
[root@node3 ~]# systemctl status seagate_ilm.service
● seagate_ilm.service - In Drive Mutex Locking Manager for Speedboat
Loaded: loaded (/etc/systemd/system/seagate_ilm.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Fri 2020-09-18 09:21:16 CDT; 1s ago
Process: 10557 ExecStart=/usr/sbin/seagate_ilm -l 0 -L 7 -E 7 -S 7 (code=exited, status=0/SUCCESS)
Main PID: 10557 (code=exited, status=0/SUCCESS)
Sep 18 09:21:16 node3 systemd[1]: seagate_ilm.service holdoff time over, scheduling restart.
Sep 18 09:21:16 node3 systemd[1]: Stopped In Drive Mutex Locking Manager for Speedboat.
Sep 18 09:21:16 node3 systemd[1]: start request repeated too quickly for seagate_ilm.service
Sep 18 09:21:16 node3 systemd[1]: Failed to start In Drive Mutex Locking Manager for Speedboat.
Sep 18 09:21:16 node3 systemd[1]: Unit seagate_ilm.service entered failed state.
Sep 18 09:21:16 node3 systemd[1]: seagate_ilm.service failed.
[root@node3 ~]# vim /etc/systemd/system/seagate_ilm.service
[root@node3 ~]# systemctl daemon-reload
[root@node3 ~]# systemctl stop seagate_ilm.service
[root@node3 ~]# systemctl start seagate_ilm.service
[root@node3 ~]# systemctl status seagate_ilm.service
● seagate_ilm.service - In Drive Mutex Locking Manager for Speedboat
Loaded: loaded (/etc/systemd/system/seagate_ilm.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2020-09-18 09:22:11 CDT; 2s ago
Main PID: 10596 (seagate_ilm)
Tasks: 4
Memory: 12.7M
CGroup: /system.slice/seagate_ilm.service
└─10596 /usr/sbin/seagate_ilm -D 1 -l 0 -L 7 -E 7 -S 7
Sep 18 09:22:11 node3 seagate_ilm[10596]: 2020-09-18 09:22:11 1469 [10596]: sg_path /dev/sg13
Sep 18 09:22:11 node3 seagate_ilm[10596]: 2020-09-18 09:22:11 1469 [10596]: SCSI dev ID: 906917b4-2d58-499a-8b5b...39a0f
Sep 18 09:22:11 node3 seagate_ilm[10596]: 2020-09-18 09:22:11 1469 [10596]: blk_path /dev/sdm
Sep 18 09:22:11 node3 seagate_ilm[10596]: 2020-09-18 09:22:11 1469 [10596]: sg_path /dev/sg12
Sep 18 09:22:11 node3 seagate_ilm[10596]: 2020-09-18 09:22:11 1469 [10596]: SCSI dev ID: 3816a4d7-1f56-4c46-a94f...cbed1
Sep 18 09:22:11 node3 seagate_ilm[10596]: 2020-09-18 09:22:11 1469 [10596]: blk_path /dev/sdl
Sep 18 09:22:11 node3 seagate_ilm[10596]: 2020-09-18 09:22:11 1469 [10596]: sg_path /dev/sg11
Sep 18 09:22:11 node3 seagate_ilm[10596]: 2020-09-18 09:22:11 1469 [10596]: SCSI dev ID: d1711b33-b05e-4612-a744...801c2
Sep 18 09:22:11 node3 seagate_ilm[10596]: 2020-09-18 09:22:11 1469 [10596]: blk_path /dev/sdk
Sep 18 09:22:11 node3 seagate_ilm[10596]: 2020-09-18 09:22:11 1469 [10596]: sg_path /dev/sg10
Hint: Some lines were ellipsized, use -l to show in full.
[root@node3 ~]# systemctl status seagate_ilm.service
● seagate_ilm.service - In Drive Mutex Locking Manager for Speedboat
Loaded: loaded (/etc/systemd/system/seagate_ilm.service; enabled; vendor preset: disabled)
Active: active (running) since Fri 2020-09-18 09:22:11 CDT; 14s ago
Main PID: 10596 (seagate_ilm)
Tasks: 4
Memory: 12.7M
CGroup: /system.slice/seagate_ilm.service
└─10596 /usr/sbin/seagate_ilm -D 1 -l 0 -L 7 -E 7 -S 7
Sep 18 09:22:11 node3 seagate_ilm[10596]: 2020-09-18 09:22:11 1469 [10596]: sg_path /dev/sg13
Sep 18 09:22:11 node3 seagate_ilm[10596]: 2020-09-18 09:22:11 1469 [10596]: SCSI dev ID: 906917b4-2d58-499a-8b5b...39a0f
Sep 18 09:22:11 node3 seagate_ilm[10596]: 2020-09-18 09:22:11 1469 [10596]: blk_path /dev/sdm
Sep 18 09:22:11 node3 seagate_ilm[10596]: 2020-09-18 09:22:11 1469 [10596]: sg_path /dev/sg12
Sep 18 09:22:11 node3 seagate_ilm[10596]: 2020-09-18 09:22:11 1469 [10596]: SCSI dev ID: 3816a4d7-1f56-4c46-a94f...cbed1
Sep 18 09:22:11 node3 seagate_ilm[10596]: 2020-09-18 09:22:11 1469 [10596]: blk_path /dev/sdl
Sep 18 09:22:11 node3 seagate_ilm[10596]: 2020-09-18 09:22:11 1469 [10596]: sg_path /dev/sg11
Sep 18 09:22:11 node3 seagate_ilm[10596]: 2020-09-18 09:22:11 1469 [10596]: SCSI dev ID: d1711b33-b05e-4612-a744...801c2
Sep 18 09:22:11 node3 seagate_ilm[10596]: 2020-09-18 09:22:11 1469 [10596]: blk_path /dev/sdk
Sep 18 09:22:11 node3 seagate_ilm[10596]: 2020-09-18 09:22:11 1469 [10596]: sg_path /dev/sg10
Hint: Some lines were ellipsized, use -l to show in full.
[root@node3 ~]# systemctl stop seagate_ilm.service
[root@node3 ~]# vim /etc/systemd/system/seagate_ilm.service
[root@node3 ~]# systemctl daemon-reload
[root@node3 ~]# systemctl start seagate_ilm.service
[root@node3 ~]# systemctl status seagate_ilm.service
● seagate_ilm.service - In Drive Mutex Locking Manager for Speedboat
Loaded: loaded (/etc/systemd/system/seagate_ilm.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) since Fri 2020-09-18 09:23:04 CDT; 767ms ago
Process: 10644 ExecStart=/usr/sbin/seagate_ilm -l 0 -L 7 -E 7 -S 7 (code=exited, status=0/SUCCESS)
Main PID: 10644 (code=exited, status=0/SUCCESS)
[root@node3 ~]# systemctl status seagate_ilm.service
● seagate_ilm.service - In Drive Mutex Locking Manager for Speedboat
Loaded: loaded (/etc/systemd/system/seagate_ilm.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) since Fri 2020-09-18 09:23:07 CDT; 384ms ago
Process: 10651 ExecStart=/usr/sbin/seagate_ilm -l 0 -L 7 -E 7 -S 7 (code=exited, status=0/SUCCESS)
Main PID: 10651 (code=exited, status=0/SUCCESS)
[root@node3 ~]# systemctl status seagate_ilm.service
● seagate_ilm.service - In Drive Mutex Locking Manager for Speedboat
Loaded: loaded (/etc/systemd/system/seagate_ilm.service; enabled; vendor preset: disabled)
Active: activating (auto-restart) since Fri 2020-09-18 09:23:08 CDT; 760ms ago
Process: 10655 ExecStart=/usr/sbin/seagate_ilm -l 0 -L 7 -E 7 -S 7 (code=exited, status=0/SUCCESS)
Main PID: 10655 (code=exited, status=0/SUCCESS)
[root@node3 ~]# systemctl status seagate_ilm.service
● seagate_ilm.service - In Drive Mutex Locking Manager for Speedboat
Loaded: loaded (/etc/systemd/system/seagate_ilm.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Fri 2020-09-18 09:23:09 CDT; 1s ago
Process: 10655 ExecStart=/usr/sbin/seagate_ilm -l 0 -L 7 -E 7 -S 7 (code=exited, status=0/SUCCESS)
Main PID: 10655 (code=exited, status=0/SUCCESS)
Sep 18 09:23:09 node3 systemd[1]: seagate_ilm.service holdoff time over, scheduling restart.
Sep 18 09:23:09 node3 systemd[1]: Stopped In Drive Mutex Locking Manager for Speedboat.
Sep 18 09:23:09 node3 systemd[1]: start request repeated too quickly for seagate_ilm.service
Sep 18 09:23:09 node3 systemd[1]: Failed to start In Drive Mutex Locking Manager for Speedboat.
Sep 18 09:23:09 node3 systemd[1]: Unit seagate_ilm.service entered failed state.
Sep 18 09:23:09 node3 systemd[1]: seagate_ilm.service failed.
The history below show attempting to start ilm without the -D 1 and it hits a start limit. Then the -D 1 is added and it starts OK. Then the -D 1 is removed and it fails.