Why my Fedora 26 is not unmounting /home?











up vote
2
down vote

favorite












I just upgraded to Fedora 26. Everything is working fine, except for a strange umounting problem at shutdown: /home and Temporary directory partitions are not being umounted. This is the boot message:



....
Jul 12 21:55:46 Orion systemd: Unmounting /home...
Jul 12 21:55:46 Orion systemd: tmp.mount: Mount process exited, code=exited status=32
Jul 12 21:55:46 Orion systemd: Failed unmounting Temporary Directory. <===== THIS
Jul 12 21:55:46 Orion systemd: home.mount: Mount process exited, code=exited status=32
Jul 12 21:55:46 Orion audit: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-disk-byx2duuid-786e5bbfx2d0527x2d4e71x2daf31x2d78cf5d8e3038 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 12 21:55:46 Orion systemd: Failed unmounting /home. <===== THIS
Jul 12 21:55:46 Orion systemd: Stopped File System Check on /dev/disk/by-uuid/786e5bbf-0527-4e71-af31-78cf5d8e3038. <===== THIS IS home
Jul 12 21:55:46 Orion systemd: Stopped target Swap.
....


I did a lsof /home before shutdown, and I get some pulseaudio activity and a autologin script in home. Neither ever gave any problem before. Temp stuff is irrelevant, but I am afraid that home may be unproperly umounted and eventually corrupted.



Clues?










share|improve this question


























    up vote
    2
    down vote

    favorite












    I just upgraded to Fedora 26. Everything is working fine, except for a strange umounting problem at shutdown: /home and Temporary directory partitions are not being umounted. This is the boot message:



    ....
    Jul 12 21:55:46 Orion systemd: Unmounting /home...
    Jul 12 21:55:46 Orion systemd: tmp.mount: Mount process exited, code=exited status=32
    Jul 12 21:55:46 Orion systemd: Failed unmounting Temporary Directory. <===== THIS
    Jul 12 21:55:46 Orion systemd: home.mount: Mount process exited, code=exited status=32
    Jul 12 21:55:46 Orion audit: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-disk-byx2duuid-786e5bbfx2d0527x2d4e71x2daf31x2d78cf5d8e3038 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
    Jul 12 21:55:46 Orion systemd: Failed unmounting /home. <===== THIS
    Jul 12 21:55:46 Orion systemd: Stopped File System Check on /dev/disk/by-uuid/786e5bbf-0527-4e71-af31-78cf5d8e3038. <===== THIS IS home
    Jul 12 21:55:46 Orion systemd: Stopped target Swap.
    ....


    I did a lsof /home before shutdown, and I get some pulseaudio activity and a autologin script in home. Neither ever gave any problem before. Temp stuff is irrelevant, but I am afraid that home may be unproperly umounted and eventually corrupted.



    Clues?










    share|improve this question
























      up vote
      2
      down vote

      favorite









      up vote
      2
      down vote

      favorite











      I just upgraded to Fedora 26. Everything is working fine, except for a strange umounting problem at shutdown: /home and Temporary directory partitions are not being umounted. This is the boot message:



      ....
      Jul 12 21:55:46 Orion systemd: Unmounting /home...
      Jul 12 21:55:46 Orion systemd: tmp.mount: Mount process exited, code=exited status=32
      Jul 12 21:55:46 Orion systemd: Failed unmounting Temporary Directory. <===== THIS
      Jul 12 21:55:46 Orion systemd: home.mount: Mount process exited, code=exited status=32
      Jul 12 21:55:46 Orion audit: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-disk-byx2duuid-786e5bbfx2d0527x2d4e71x2daf31x2d78cf5d8e3038 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
      Jul 12 21:55:46 Orion systemd: Failed unmounting /home. <===== THIS
      Jul 12 21:55:46 Orion systemd: Stopped File System Check on /dev/disk/by-uuid/786e5bbf-0527-4e71-af31-78cf5d8e3038. <===== THIS IS home
      Jul 12 21:55:46 Orion systemd: Stopped target Swap.
      ....


      I did a lsof /home before shutdown, and I get some pulseaudio activity and a autologin script in home. Neither ever gave any problem before. Temp stuff is irrelevant, but I am afraid that home may be unproperly umounted and eventually corrupted.



      Clues?










      share|improve this question













      I just upgraded to Fedora 26. Everything is working fine, except for a strange umounting problem at shutdown: /home and Temporary directory partitions are not being umounted. This is the boot message:



      ....
      Jul 12 21:55:46 Orion systemd: Unmounting /home...
      Jul 12 21:55:46 Orion systemd: tmp.mount: Mount process exited, code=exited status=32
      Jul 12 21:55:46 Orion systemd: Failed unmounting Temporary Directory. <===== THIS
      Jul 12 21:55:46 Orion systemd: home.mount: Mount process exited, code=exited status=32
      Jul 12 21:55:46 Orion audit: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-disk-byx2duuid-786e5bbfx2d0527x2d4e71x2daf31x2d78cf5d8e3038 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
      Jul 12 21:55:46 Orion systemd: Failed unmounting /home. <===== THIS
      Jul 12 21:55:46 Orion systemd: Stopped File System Check on /dev/disk/by-uuid/786e5bbf-0527-4e71-af31-78cf5d8e3038. <===== THIS IS home
      Jul 12 21:55:46 Orion systemd: Stopped target Swap.
      ....


      I did a lsof /home before shutdown, and I get some pulseaudio activity and a autologin script in home. Neither ever gave any problem before. Temp stuff is irrelevant, but I am afraid that home may be unproperly umounted and eventually corrupted.



      Clues?







      fedora shutdown umount






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jul 13 '17 at 1:28









      Luis A. Florit

      11617




      11617






















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          -1
          down vote













          I found that uninstalling plymouth (for fedora: dnf remove plymouth* && dracut --force) fixed a similar issue for me.
          I had the same error but also noticed that the first (visible) message was a failed to start plymouth.
          After that the system had trouble umounting tmp and home but also shutting down gdm and other services.
          It would take about 5 minutes to shutdown or reboot.



          Not sure why plymouth wouldn't start as I found no trace of this error in my logs.






          share|improve this answer





















          • My issues was with fedora 29 by the way..
            – Milo
            Dec 1 at 9:05











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "3"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1229348%2fwhy-my-fedora-26-is-not-unmounting-home%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          -1
          down vote













          I found that uninstalling plymouth (for fedora: dnf remove plymouth* && dracut --force) fixed a similar issue for me.
          I had the same error but also noticed that the first (visible) message was a failed to start plymouth.
          After that the system had trouble umounting tmp and home but also shutting down gdm and other services.
          It would take about 5 minutes to shutdown or reboot.



          Not sure why plymouth wouldn't start as I found no trace of this error in my logs.






          share|improve this answer





















          • My issues was with fedora 29 by the way..
            – Milo
            Dec 1 at 9:05















          up vote
          -1
          down vote













          I found that uninstalling plymouth (for fedora: dnf remove plymouth* && dracut --force) fixed a similar issue for me.
          I had the same error but also noticed that the first (visible) message was a failed to start plymouth.
          After that the system had trouble umounting tmp and home but also shutting down gdm and other services.
          It would take about 5 minutes to shutdown or reboot.



          Not sure why plymouth wouldn't start as I found no trace of this error in my logs.






          share|improve this answer





















          • My issues was with fedora 29 by the way..
            – Milo
            Dec 1 at 9:05













          up vote
          -1
          down vote










          up vote
          -1
          down vote









          I found that uninstalling plymouth (for fedora: dnf remove plymouth* && dracut --force) fixed a similar issue for me.
          I had the same error but also noticed that the first (visible) message was a failed to start plymouth.
          After that the system had trouble umounting tmp and home but also shutting down gdm and other services.
          It would take about 5 minutes to shutdown or reboot.



          Not sure why plymouth wouldn't start as I found no trace of this error in my logs.






          share|improve this answer












          I found that uninstalling plymouth (for fedora: dnf remove plymouth* && dracut --force) fixed a similar issue for me.
          I had the same error but also noticed that the first (visible) message was a failed to start plymouth.
          After that the system had trouble umounting tmp and home but also shutting down gdm and other services.
          It would take about 5 minutes to shutdown or reboot.



          Not sure why plymouth wouldn't start as I found no trace of this error in my logs.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Dec 1 at 9:04









          Milo

          12




          12












          • My issues was with fedora 29 by the way..
            – Milo
            Dec 1 at 9:05


















          • My issues was with fedora 29 by the way..
            – Milo
            Dec 1 at 9:05
















          My issues was with fedora 29 by the way..
          – Milo
          Dec 1 at 9:05




          My issues was with fedora 29 by the way..
          – Milo
          Dec 1 at 9:05


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Super User!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1229348%2fwhy-my-fedora-26-is-not-unmounting-home%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

          Alcedinidae

          RAC Tourist Trophy