Menu

System Hangs On Shutdown After Automount

Help
prosef
2020-05-21
2020-07-08
  • prosef

    prosef - 2020-05-21

    On Kubuntu 20.04, Smb4k 3.04. Whenever I shutdown with mounts still present, the system hangs for 1m30sec, showing a message "A stop job is running for (the mount path)." It makes reboots considerably slower. Seems to be the same issue discussed here, from 8 years ago: https://bbs.archlinux.org/viewtopic.php?id=150661

    Is there any suggested way to avoid this, without having to manually dismount before & remount after each reboot?

     

    Last edit: prosef 2020-06-11
  • prosef

    prosef - 2020-06-11

    Would really very much appreciate any guidance as to how to resolve this - it makes each reboot agonizingly slow, especially due to connections to multiple shares.

     
  • Alexander Reinholdt

    Sorry for letting you wait so long.

    Please try the option 'Mounting' > 'Behavior' > 'Unmount all personal shares on exit'. This unmounts your mounted shares when the computer is shut down or you log off. Please let me know if that helps.

     
  • prosef

    prosef - 2020-06-11

    That solved it!! Thanks!

     
  • Alexander Reinholdt

    Good. :)

    If you do not want to remount the shares manually, you can also enable 'Mounting' >'Behavior' > 'Remount shares', if that is not already switched on.

     
  • prosef

    prosef - 2020-06-11

    Yup - that was my intention, I'd just temporarily disabled that because it made reboots take forever. But with both those options enabled, it works nicely :)

     
  • prosef

    prosef - 2020-06-11

    Actually, it turns out there's one more seemingly related issue (should I post this separately?)

    The majority of reboots, it works great. However, sometimes - at random - one of the shares fails to mount, and I get the notification "Mounting the share xxx on ip failed:mount error(2): No such file or directory." If I manually mount that share right after, it works fine. If I don't manually mount that share - if I just reboot again without doing anything - it works fine. It seems to be fail completely at random. Maybe one out of four reboots, for one of the two shares.

     
  • Alexander Reinholdt

    Thanks for reporting this. Since the mount helper cannot handle parallel mounts, they have to be done in series. Maybe the waiting time between the mounts is (still) too short. I can lengthen the waiting time and produce a package that you could test. (I also have Kubuntu 20.04 installed.)

     
  • prosef

    prosef - 2020-06-12

    Or perhaps there's no universal perfect delay (depends on network speed, device speed, computer speed, etc) - so a settable delay (option) could solve it? :)

     
  • prosef

    prosef - 2020-07-08

    Correction: I'm not sure why, but this seems to be happening more than originally reported. Maybe half the time I reboot, it shows an error and I still have to re-mount by hand. I don't suppose I can config this somehow anywhere via config - maybe even making the program overall delay until a bit after startup? I'd love to not have to dismiss the error and remote so frequently :)

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.