Comment # 30 on bug 1080485 from Martin Wilck

(In reply to Neil Rickert from comment #29)
> >(how long? how many messages)?
> 
> They go past so fast, that it is very hard to tell. 

So it's really a transient condition, and the problem is mainly the irritating
log messages, no real damage done. Might be solvable by adding a short sleep
somewhere (but I can't say where :-/ ).

> >Could you try to mask that service and see if the problem disappears?
> 
> How and when should I do that?

When the system is up, run "systemctl mask blk-availability.service".
You probably need to reboot after that.

But wait - first check whether that service is enabled at all ("systemctl
status blk-availability.service"). If it isn't, we have to find another
culprit.