@Stefan Hello again. Yes I pretty sure this is a known bug and one that has been quite difficult to reproduce but a few people have system configurations that seem to trigger it regularly. It seem to depend on how a system renames it’s devices from one boot to another and is essentially harmless but rather irritating and of course highly undesirable. But as it goes there is a pending pull request that I’m hoping should address the root cause of this but I can’t confirm this as I no longer have a system that previously reproduces this behaviour (but only occasionally) and nor do the other developers. We have an open GitHub issue:
on this bug which in turn links to the associated, in progress, pull request / code changes.
I have linked to this forum thread from within that issue so hopefully this thread should receive an update upon the suspected fix being merged and depending on what update channel your problematic machine is on you should receive what is hopefully a fix via the regular updates either sooner or later. In fact it would be really helpful if you could confirm any change in behaviour once this next code change is in place and released. Especially since it seem to be a fairly predictable event on your particular setup. So if possible don’t change anything as your system may potentially be one of the only proof of fixes we currently have as I am uncertain if prior reporters are still in contact. But don’t worry otherwise of course as hopefully other reporters are still in contact and can confirm any fix or otherwise when the time comes.
The main factor seems to be the drives arrangement and how they are re-named as the bug is triggered by a very particular re-arrangement.
Like the work around by the way.
There is another much older forum thread Pool not mounted on reboot but I believe that was when there were other bugs (since addressed) that could cause similar behaviour and I don’t think all reporters there were experiencing the same root cause.
Thanks for the report and hopefully this one should be fixed soon.
as your system may potentially be one of the only proof of fixes we currently have as I am uncertain if prior reporters are still in contact. But don’t worry otherwise of course as hopefully other reporters are still in contact and can confirm any fix or otherwise when the time comes.