Re: blk-availability.service failure message

[Darac Marjal <mailinglist@darac.org.uk>]

On 02/11/17 18:18, Fjfj109 wrote:

Hi, on Debian Sid, how can I diagnose the following?

https://paste.debian.net/993924/

annadane@debian:~$ systemctl status blk-availability.service ● blk-availability.service - Availability of block devices Loaded: loaded (/lib/systemd/system/blk-availability.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2017-11-02 12:52:30 EDT; 1h 24min ago Main PID: 251 (code=exited, status=203/EXEC) Tasks: 0 (limit: 4915) CGroup: /system.slice/blk-availability.service Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

If you're wanting to diagnose the issue yourself, the simplest place to start would be to either look at the rotated log file, or just to run

$ systemctl restart blk-availability.service
$ journalctl -u blk-availability.service

If you're just wanting to get booting, run

# ln -s /bin/true /usr/bin/true

(which worked for me).

Attachment: signature.asc
Description: OpenPGP digital signature