REISUB cause hard disk IO error

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












I just installed Ubuntu 17.10 , when I restarted by using Alt + SysRq + R +E+I+S+U+B, Ubuntu fails to boot, it show;
Unexpected inconsistency and tells me to manually run fsck on /dev/sda2 the / of Ubuntu. Then it shows me busybox console where I run fsck. Why does it happen? How can I fix it?







share|improve this question
























    up vote
    1
    down vote

    favorite












    I just installed Ubuntu 17.10 , when I restarted by using Alt + SysRq + R +E+I+S+U+B, Ubuntu fails to boot, it show;
    Unexpected inconsistency and tells me to manually run fsck on /dev/sda2 the / of Ubuntu. Then it shows me busybox console where I run fsck. Why does it happen? How can I fix it?







    share|improve this question






















      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      I just installed Ubuntu 17.10 , when I restarted by using Alt + SysRq + R +E+I+S+U+B, Ubuntu fails to boot, it show;
      Unexpected inconsistency and tells me to manually run fsck on /dev/sda2 the / of Ubuntu. Then it shows me busybox console where I run fsck. Why does it happen? How can I fix it?







      share|improve this question












      I just installed Ubuntu 17.10 , when I restarted by using Alt + SysRq + R +E+I+S+U+B, Ubuntu fails to boot, it show;
      Unexpected inconsistency and tells me to manually run fsck on /dev/sda2 the / of Ubuntu. Then it shows me busybox console where I run fsck. Why does it happen? How can I fix it?









      share|improve this question











      share|improve this question




      share|improve this question










      asked Oct 21 '17 at 6:46









      drake01

      82




      82




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          2
          down vote



          accepted










          Your title may not be clear, I think that actually your hard disk is not having any I/O errors, instead the problem is that you have an inconsistent Filesystem because Ubuntu didn't shutdown properly.



          Maybe you typed very fast the REISUB sequence? What about pressing REISUB more slowly? Mmm, Have already run fsck and rebooted? Is it still failing to boot?






          share|improve this answer




















          • It booted when I ran fsck, but when I rebooted again it showed the same messages.(Even rebooting normally)
            – drake01
            Oct 21 '17 at 9:24










          • +1 for REISUB slowly. VERY slowly. These actions are far from instantaneous (depending on what the machine is doing, of course...). Allowing processes to terminate gracefully and syncing data to drives should be given time.
            – frostschutz
            Oct 21 '17 at 20:47











          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',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          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%2f399484%2freisub-cause-hard-disk-io-error%23new-answer', 'question_page');

          );

          Post as a guest






























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          2
          down vote



          accepted










          Your title may not be clear, I think that actually your hard disk is not having any I/O errors, instead the problem is that you have an inconsistent Filesystem because Ubuntu didn't shutdown properly.



          Maybe you typed very fast the REISUB sequence? What about pressing REISUB more slowly? Mmm, Have already run fsck and rebooted? Is it still failing to boot?






          share|improve this answer




















          • It booted when I ran fsck, but when I rebooted again it showed the same messages.(Even rebooting normally)
            – drake01
            Oct 21 '17 at 9:24










          • +1 for REISUB slowly. VERY slowly. These actions are far from instantaneous (depending on what the machine is doing, of course...). Allowing processes to terminate gracefully and syncing data to drives should be given time.
            – frostschutz
            Oct 21 '17 at 20:47















          up vote
          2
          down vote



          accepted










          Your title may not be clear, I think that actually your hard disk is not having any I/O errors, instead the problem is that you have an inconsistent Filesystem because Ubuntu didn't shutdown properly.



          Maybe you typed very fast the REISUB sequence? What about pressing REISUB more slowly? Mmm, Have already run fsck and rebooted? Is it still failing to boot?






          share|improve this answer




















          • It booted when I ran fsck, but when I rebooted again it showed the same messages.(Even rebooting normally)
            – drake01
            Oct 21 '17 at 9:24










          • +1 for REISUB slowly. VERY slowly. These actions are far from instantaneous (depending on what the machine is doing, of course...). Allowing processes to terminate gracefully and syncing data to drives should be given time.
            – frostschutz
            Oct 21 '17 at 20:47













          up vote
          2
          down vote



          accepted







          up vote
          2
          down vote



          accepted






          Your title may not be clear, I think that actually your hard disk is not having any I/O errors, instead the problem is that you have an inconsistent Filesystem because Ubuntu didn't shutdown properly.



          Maybe you typed very fast the REISUB sequence? What about pressing REISUB more slowly? Mmm, Have already run fsck and rebooted? Is it still failing to boot?






          share|improve this answer












          Your title may not be clear, I think that actually your hard disk is not having any I/O errors, instead the problem is that you have an inconsistent Filesystem because Ubuntu didn't shutdown properly.



          Maybe you typed very fast the REISUB sequence? What about pressing REISUB more slowly? Mmm, Have already run fsck and rebooted? Is it still failing to boot?







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Oct 21 '17 at 8:28









          princessgentoo

          362




          362











          • It booted when I ran fsck, but when I rebooted again it showed the same messages.(Even rebooting normally)
            – drake01
            Oct 21 '17 at 9:24










          • +1 for REISUB slowly. VERY slowly. These actions are far from instantaneous (depending on what the machine is doing, of course...). Allowing processes to terminate gracefully and syncing data to drives should be given time.
            – frostschutz
            Oct 21 '17 at 20:47

















          • It booted when I ran fsck, but when I rebooted again it showed the same messages.(Even rebooting normally)
            – drake01
            Oct 21 '17 at 9:24










          • +1 for REISUB slowly. VERY slowly. These actions are far from instantaneous (depending on what the machine is doing, of course...). Allowing processes to terminate gracefully and syncing data to drives should be given time.
            – frostschutz
            Oct 21 '17 at 20:47
















          It booted when I ran fsck, but when I rebooted again it showed the same messages.(Even rebooting normally)
          – drake01
          Oct 21 '17 at 9:24




          It booted when I ran fsck, but when I rebooted again it showed the same messages.(Even rebooting normally)
          – drake01
          Oct 21 '17 at 9:24












          +1 for REISUB slowly. VERY slowly. These actions are far from instantaneous (depending on what the machine is doing, of course...). Allowing processes to terminate gracefully and syncing data to drives should be given time.
          – frostschutz
          Oct 21 '17 at 20:47





          +1 for REISUB slowly. VERY slowly. These actions are far from instantaneous (depending on what the machine is doing, of course...). Allowing processes to terminate gracefully and syncing data to drives should be given time.
          – frostschutz
          Oct 21 '17 at 20:47


















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f399484%2freisub-cause-hard-disk-io-error%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          How to check contact read email or not when send email to Individual?

          Bahrain

          Postfix configuration issue with fips on centos 7; mailgun relay