On Sun, 2020-05-24 at 18:07 -0500, Roger Heflin wrote:
Did you originally have /dev/md0p1 in fstab and you have edited
fstab
since you booted?
If so the great and amazing systemd will not be amused and will still
have a job for the old device, you will need to run systemctl
daemon-reload for it to read the fstab file as it is not smart enough
to do that itself.
That's ... illuminating ... I haven't come across this behaviour
before, but I now see that there is a warning to that effect in
/etc/fstab (which of course I've never noticed before now). It could
explain some of what's happened. I wonder why systemd doesn't notice
that the file has changed and reload accordingly.
poc