Hi there @mbx! I think we have seen a similar error before on certain configurations of network-mounted drivers:
Any chance this applies to your situation?