On Wed, 2021-06-16 at 20:18 +0800, Ed Greshko wrote: > On 16/06/2021 19:35, Patrick O'Callaghan wrote: > > So two questions: > > > > 1) Is there an obvious error with the drive itself? > > If you've not seen errors when you're using the drive, then probably > not. > I haven't seen any errors, so it's probably a feature rather than a bug with this drive. > > 2) Is there a way to prevent the system boot from freezing while it > > waits for the drive to come online? > > How about trying to turn it into user unit/service? It would require > a login. But may not delay that process. There's no indication it has anything to do with my existing unit(s) such as dock-watch or raid.[auto]mount, neither of which are logged in the journal extract I posted, so I don't think converting any of that into a user unit or service would make any difference. Just to be sure, my next step will be to completely disable those units and reboot again, but I'm 99% sure that is still going to show the 30- second delay. poc _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure