On Mon, 2020-05-25 at 07:49 -0500, Roger Heflin wrote:
His issue was he did the manual mount on /raid (already in fstab
with
a different device) and systemd immediately unmounted it. The mount
succeeds with no error, and the umount happens so fast you are left
confused about what is going on. It did at least note it in
messages so long as you can guess the stupid action it took. This
action of systemd is pretty badly designed, since it is overriding
what had to be someone/somethings explicit action (and even if this is
documented, documenting stupidity does not make it "right", it is
still wrong).
I *think* I've got it now. Re-creating the array made no difference
whatever, as it just left everything exactly the same apart from taking
many hours in useless resynching (why it does this is a mystery, as it
clearly knows the layout and should know that the array was already
synchronised). IOW even though I ran:
# mdadm --create /dev/md0 --level=1 --raid-devices=2 /dev/sd[de]
I still ended up with /dev/md127p1 as before, and /dev/md0 wa's not
created. However by putting that into /etc/fstab and running systemctl
daemon-reload', I can now mount the array correctly. It even survives a
system reboot.
Fingers crossed, it seems to be working now.
poc