Hanging on reboot with black screen and blinking underscore












0















Everything works, but when I reboot via "systemctl reboot" or through GNOME, it will never actually reboot, but instead it gets stuck in a black screen with blinking underscore cursor, and I am forced to do a hard-reset.



These are the last entries in the journalctl -r:



Mar 14 23:07:29 Desktop systemd-journald[417]: Journal stopped
Mar 14 23:07:29 Desktop systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Mar 14 23:07:29 Desktop systemd-shutdown[1]: Syncing filesystems and block devices.
Mar 14 23:07:29 Desktop kernel: printk: systemd-shutdow: 50 output lines suppressed due to ratelimiting
Mar 14 23:07:29 Desktop systemd[1]: Shutting down.
Mar 14 23:07:29 Desktop systemd[1]: Reached target Reboot.
Mar 14 23:07:29 Desktop audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-reboot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 14 23:07:29 Desktop audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-reboot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 14 23:07:29 Desktop systemd[1]: Started Reboot.
Mar 14 23:07:29 Desktop systemd[1]: systemd-reboot.service: Succeeded.
Mar 14 23:07:29 Desktop systemd[1]: Reached target Final Step.
Mar 14 23:07:29 Desktop systemd[1]: Reached target Shutdown.
Mar 14 23:07:29 Desktop systemd[1]: Removed slice system-systemdx2dfsck.slice.


Any idea why this is happening?










share|improve this question



























    0















    Everything works, but when I reboot via "systemctl reboot" or through GNOME, it will never actually reboot, but instead it gets stuck in a black screen with blinking underscore cursor, and I am forced to do a hard-reset.



    These are the last entries in the journalctl -r:



    Mar 14 23:07:29 Desktop systemd-journald[417]: Journal stopped
    Mar 14 23:07:29 Desktop systemd-shutdown[1]: Sending SIGTERM to remaining processes...
    Mar 14 23:07:29 Desktop systemd-shutdown[1]: Syncing filesystems and block devices.
    Mar 14 23:07:29 Desktop kernel: printk: systemd-shutdow: 50 output lines suppressed due to ratelimiting
    Mar 14 23:07:29 Desktop systemd[1]: Shutting down.
    Mar 14 23:07:29 Desktop systemd[1]: Reached target Reboot.
    Mar 14 23:07:29 Desktop audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-reboot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
    Mar 14 23:07:29 Desktop audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-reboot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
    Mar 14 23:07:29 Desktop systemd[1]: Started Reboot.
    Mar 14 23:07:29 Desktop systemd[1]: systemd-reboot.service: Succeeded.
    Mar 14 23:07:29 Desktop systemd[1]: Reached target Final Step.
    Mar 14 23:07:29 Desktop systemd[1]: Reached target Shutdown.
    Mar 14 23:07:29 Desktop systemd[1]: Removed slice system-systemdx2dfsck.slice.


    Any idea why this is happening?










    share|improve this question

























      0












      0








      0








      Everything works, but when I reboot via "systemctl reboot" or through GNOME, it will never actually reboot, but instead it gets stuck in a black screen with blinking underscore cursor, and I am forced to do a hard-reset.



      These are the last entries in the journalctl -r:



      Mar 14 23:07:29 Desktop systemd-journald[417]: Journal stopped
      Mar 14 23:07:29 Desktop systemd-shutdown[1]: Sending SIGTERM to remaining processes...
      Mar 14 23:07:29 Desktop systemd-shutdown[1]: Syncing filesystems and block devices.
      Mar 14 23:07:29 Desktop kernel: printk: systemd-shutdow: 50 output lines suppressed due to ratelimiting
      Mar 14 23:07:29 Desktop systemd[1]: Shutting down.
      Mar 14 23:07:29 Desktop systemd[1]: Reached target Reboot.
      Mar 14 23:07:29 Desktop audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-reboot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
      Mar 14 23:07:29 Desktop audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-reboot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
      Mar 14 23:07:29 Desktop systemd[1]: Started Reboot.
      Mar 14 23:07:29 Desktop systemd[1]: systemd-reboot.service: Succeeded.
      Mar 14 23:07:29 Desktop systemd[1]: Reached target Final Step.
      Mar 14 23:07:29 Desktop systemd[1]: Reached target Shutdown.
      Mar 14 23:07:29 Desktop systemd[1]: Removed slice system-systemdx2dfsck.slice.


      Any idea why this is happening?










      share|improve this question














      Everything works, but when I reboot via "systemctl reboot" or through GNOME, it will never actually reboot, but instead it gets stuck in a black screen with blinking underscore cursor, and I am forced to do a hard-reset.



      These are the last entries in the journalctl -r:



      Mar 14 23:07:29 Desktop systemd-journald[417]: Journal stopped
      Mar 14 23:07:29 Desktop systemd-shutdown[1]: Sending SIGTERM to remaining processes...
      Mar 14 23:07:29 Desktop systemd-shutdown[1]: Syncing filesystems and block devices.
      Mar 14 23:07:29 Desktop kernel: printk: systemd-shutdow: 50 output lines suppressed due to ratelimiting
      Mar 14 23:07:29 Desktop systemd[1]: Shutting down.
      Mar 14 23:07:29 Desktop systemd[1]: Reached target Reboot.
      Mar 14 23:07:29 Desktop audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-reboot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
      Mar 14 23:07:29 Desktop audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-reboot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
      Mar 14 23:07:29 Desktop systemd[1]: Started Reboot.
      Mar 14 23:07:29 Desktop systemd[1]: systemd-reboot.service: Succeeded.
      Mar 14 23:07:29 Desktop systemd[1]: Reached target Final Step.
      Mar 14 23:07:29 Desktop systemd[1]: Reached target Shutdown.
      Mar 14 23:07:29 Desktop systemd[1]: Removed slice system-systemdx2dfsck.slice.


      Any idea why this is happening?







      arch-linux reboot






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 18 mins ago









      MuppetMuppet

      1011




      1011






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "106"
          };
          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',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          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%2funix.stackexchange.com%2fquestions%2f506395%2fhanging-on-reboot-with-black-screen-and-blinking-underscore%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • 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%2funix.stackexchange.com%2fquestions%2f506395%2fhanging-on-reboot-with-black-screen-and-blinking-underscore%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

          Loup dans la culture

          How to solve the problem of ntp “Unable to contact time server” from KDE?

          ASUS Zenbook UX433/UX333 — Configure Touchpad-embedded numpad on Linux