Comment 2 for bug 1931077

Looking at the journal, I think the sequence of events is:

- SSD fails last Friday
- I log in today over ssh, start messing around
- I notice that collectd is not running (since Friday), try to `sudo systemctl start collectd`
- systemd tries to bring up collectd's dependency local-fs.target, which need /dev/sda1, which is the failed drive
- I figure _that_ out and start editing /etc/fstab to switch the /boot/efi device to the backup on /dev/sdb1
- in the background systemd gives up on local-fs.target and starts emergency.target, which shuts down all the services (including sshd, but not killing my ssh session) and brings up an emergency shell
- I finish editing /etc/fstab and do a `sudo mount /boot/efi; sudo systemctl daemon-reload; sudo systemctl start collectd`
- systemd notices that local-fs.target is all fine actually and stops the emergency shell
- systemd doesn't start all the services that it shut down minutes ago
- I exit my ssh session by mistake

and now we have the situation where the emergency shell is stopped but its startup message remains, confusing users. (And also no systemd services are running, except for collectd, which is not very useful for getting the system back online.)