“Insmod normal” command returns "attempt to read or write outside of disk 'hd0' The 2019 Stack Overflow Developer Survey Results Are In“hd0 out of disk” / “hd0 write error” (still boots)Attempt to read or write outside of disk hd0 problemGrub: attempt to read or write outside of disk 'hd0'error:attempt to read or write outside 'hd0'Boot: error: attempt to read or write outside of disk 'hd0' after updatewrong start up diskubuntu 14.04 error “attempt to read outside of disk 'hd0'”Not able to grub rescue with error: attempt to read or write outside of disk 'hd0'Attempt to read or write outside of disk hd0Grub error “attempt to read or write outside of disk hd0”

Manuscript was "unsubmitted" because the manuscript was deposited in Arxiv Preprints

Is bread bad for ducks?

In microwave frequencies, do you use a circulator when you need a (near) perfect diode?

Why don't Unix/Linux systems traverse through directories until they find the required version of a linked library?

How to answer pointed "are you quitting" questioning when I don't want them to suspect

What tool would a Roman-age civilization have to grind silver and other metals into dust?

Is it possible for the two major parties in the UK to form a coalition with each other instead of a much smaller party?

If the Wish spell is used to duplicate the effect of Simulacrum, are existing duplicates destroyed?

Where to refill my bottle in India?

Does it makes sense to buy a new cycle to learn riding?

Is "plugging out" electronic devices an American expression?

Lethal sonic weapons

Does duplicating a spell with Wish count as casting that spell?

How can I create a character who can assume the widest possible range of creature sizes?

Is three citations per paragraph excessive for undergraduate research paper?

Pristine Bit Checking

What are the motivations for publishing new editions of an existing textbook, beyond new discoveries in a field?

Can distinct morphisms between curves induce the same morphism on singular cohomology?

How to make payment on the internet without leaving a money trail?

How are circuits which use complex ICs normally simulated?

Why is the maximum length of OpenWrt’s root password 8 characters?

How come people say “Would of”?

Is domain driven design an anti-SQL pattern?

What does "rabbited" mean/imply in this sentence?



“Insmod normal” command returns "attempt to read or write outside of disk 'hd0'



The 2019 Stack Overflow Developer Survey Results Are In“hd0 out of disk” / “hd0 write error” (still boots)Attempt to read or write outside of disk hd0 problemGrub: attempt to read or write outside of disk 'hd0'error:attempt to read or write outside 'hd0'Boot: error: attempt to read or write outside of disk 'hd0' after updatewrong start up diskubuntu 14.04 error “attempt to read outside of disk 'hd0'”Not able to grub rescue with error: attempt to read or write outside of disk 'hd0'Attempt to read or write outside of disk hd0Grub error “attempt to read or write outside of disk hd0”



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








0















I've got the issue shown below:



error: attempt to reader write outside of disk 'hd0'
Entering rescue mode...


It happened in the past, so I tried



grub rescue> ls
(hd0) (hd0,msdos1)
grub rescue> set prefix=(hd0,msdos1)/boot/grub
grub rescue> set root=(hd0,msdos1)
grub rescue> insmod normal
error: attempt to reader write outside of disk 'hd0'


Well, after enter "insmod normal" command, the next command would be "normal" and next would be "boot", but doesn't work fine at this time. I don't understanding what's happened because I've got the same problem in the past and I've used the same procedure and works fine.



Could you help me with this?










share|improve this question
















bumped to the homepage by Community 3 hours ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.





















    0















    I've got the issue shown below:



    error: attempt to reader write outside of disk 'hd0'
    Entering rescue mode...


    It happened in the past, so I tried



    grub rescue> ls
    (hd0) (hd0,msdos1)
    grub rescue> set prefix=(hd0,msdos1)/boot/grub
    grub rescue> set root=(hd0,msdos1)
    grub rescue> insmod normal
    error: attempt to reader write outside of disk 'hd0'


    Well, after enter "insmod normal" command, the next command would be "normal" and next would be "boot", but doesn't work fine at this time. I don't understanding what's happened because I've got the same problem in the past and I've used the same procedure and works fine.



    Could you help me with this?










    share|improve this question
















    bumped to the homepage by Community 3 hours ago


    This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

















      0












      0








      0


      1






      I've got the issue shown below:



      error: attempt to reader write outside of disk 'hd0'
      Entering rescue mode...


      It happened in the past, so I tried



      grub rescue> ls
      (hd0) (hd0,msdos1)
      grub rescue> set prefix=(hd0,msdos1)/boot/grub
      grub rescue> set root=(hd0,msdos1)
      grub rescue> insmod normal
      error: attempt to reader write outside of disk 'hd0'


      Well, after enter "insmod normal" command, the next command would be "normal" and next would be "boot", but doesn't work fine at this time. I don't understanding what's happened because I've got the same problem in the past and I've used the same procedure and works fine.



      Could you help me with this?










      share|improve this question
















      I've got the issue shown below:



      error: attempt to reader write outside of disk 'hd0'
      Entering rescue mode...


      It happened in the past, so I tried



      grub rescue> ls
      (hd0) (hd0,msdos1)
      grub rescue> set prefix=(hd0,msdos1)/boot/grub
      grub rescue> set root=(hd0,msdos1)
      grub rescue> insmod normal
      error: attempt to reader write outside of disk 'hd0'


      Well, after enter "insmod normal" command, the next command would be "normal" and next would be "boot", but doesn't work fine at this time. I don't understanding what's happened because I've got the same problem in the past and I've used the same procedure and works fine.



      Could you help me with this?







      boot grubrescue boot-repair boot-partition






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Sep 2 '17 at 3:53









      d a i s y

      3,41182444




      3,41182444










      asked Sep 1 '17 at 7:15









      Ronaldo OliveiraRonaldo Oliveira

      315




      315





      bumped to the homepage by Community 3 hours ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







      bumped to the homepage by Community 3 hours ago


      This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.






















          1 Answer
          1






          active

          oldest

          votes


















          0














          To check the file system on your Ubuntu partition...



          • boot to the GRUB menu

          • choose Advanced Options

          • choose Recovery mode

          • choose Root access

          • at the # prompt, type sudo fsck -f /

          • repeat the fsck command if there were errors

          • type reboot

          If for some reason you can't do the above...



          • boot to a Ubuntu Live DVD/USB

          • start gparted and determine which /dev/sdaX is your Ubuntu EXT4 partition

          • quit gparted

          • open a terminal window

          • type sudo fsck -f /dev/sdaX # replacing X with the number you found earlier

          • repeat the fsck command if there were errors

          • type reboot





          share|improve this answer























          • Thank for you contribuition @heynnema. As soon as possible I'll tried fixed as you recommended

            – Ronaldo Oliveira
            Sep 1 '17 at 19:57











          • Unfortunately it dosen't work. The 'grub rescue' does not have many options and the commands you showed above are not possible to execute. Many thanks for you support

            – Ronaldo Oliveira
            Sep 2 '17 at 0:12











          • @RonaldoOliveira You must have misread my instructions, because they have nothing to do with GRUB Rescue. Retry the first part of my answer, and if that doesn't work, then use the second method in my answer :-)

            – heynnema
            Sep 3 '17 at 0:48











          Your Answer








          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "89"
          ;
          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: 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%2faskubuntu.com%2fquestions%2f951844%2finsmod-normal-command-returns-attempt-to-read-or-write-outside-of-disk-hd0%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









          0














          To check the file system on your Ubuntu partition...



          • boot to the GRUB menu

          • choose Advanced Options

          • choose Recovery mode

          • choose Root access

          • at the # prompt, type sudo fsck -f /

          • repeat the fsck command if there were errors

          • type reboot

          If for some reason you can't do the above...



          • boot to a Ubuntu Live DVD/USB

          • start gparted and determine which /dev/sdaX is your Ubuntu EXT4 partition

          • quit gparted

          • open a terminal window

          • type sudo fsck -f /dev/sdaX # replacing X with the number you found earlier

          • repeat the fsck command if there were errors

          • type reboot





          share|improve this answer























          • Thank for you contribuition @heynnema. As soon as possible I'll tried fixed as you recommended

            – Ronaldo Oliveira
            Sep 1 '17 at 19:57











          • Unfortunately it dosen't work. The 'grub rescue' does not have many options and the commands you showed above are not possible to execute. Many thanks for you support

            – Ronaldo Oliveira
            Sep 2 '17 at 0:12











          • @RonaldoOliveira You must have misread my instructions, because they have nothing to do with GRUB Rescue. Retry the first part of my answer, and if that doesn't work, then use the second method in my answer :-)

            – heynnema
            Sep 3 '17 at 0:48















          0














          To check the file system on your Ubuntu partition...



          • boot to the GRUB menu

          • choose Advanced Options

          • choose Recovery mode

          • choose Root access

          • at the # prompt, type sudo fsck -f /

          • repeat the fsck command if there were errors

          • type reboot

          If for some reason you can't do the above...



          • boot to a Ubuntu Live DVD/USB

          • start gparted and determine which /dev/sdaX is your Ubuntu EXT4 partition

          • quit gparted

          • open a terminal window

          • type sudo fsck -f /dev/sdaX # replacing X with the number you found earlier

          • repeat the fsck command if there were errors

          • type reboot





          share|improve this answer























          • Thank for you contribuition @heynnema. As soon as possible I'll tried fixed as you recommended

            – Ronaldo Oliveira
            Sep 1 '17 at 19:57











          • Unfortunately it dosen't work. The 'grub rescue' does not have many options and the commands you showed above are not possible to execute. Many thanks for you support

            – Ronaldo Oliveira
            Sep 2 '17 at 0:12











          • @RonaldoOliveira You must have misread my instructions, because they have nothing to do with GRUB Rescue. Retry the first part of my answer, and if that doesn't work, then use the second method in my answer :-)

            – heynnema
            Sep 3 '17 at 0:48













          0












          0








          0







          To check the file system on your Ubuntu partition...



          • boot to the GRUB menu

          • choose Advanced Options

          • choose Recovery mode

          • choose Root access

          • at the # prompt, type sudo fsck -f /

          • repeat the fsck command if there were errors

          • type reboot

          If for some reason you can't do the above...



          • boot to a Ubuntu Live DVD/USB

          • start gparted and determine which /dev/sdaX is your Ubuntu EXT4 partition

          • quit gparted

          • open a terminal window

          • type sudo fsck -f /dev/sdaX # replacing X with the number you found earlier

          • repeat the fsck command if there were errors

          • type reboot





          share|improve this answer













          To check the file system on your Ubuntu partition...



          • boot to the GRUB menu

          • choose Advanced Options

          • choose Recovery mode

          • choose Root access

          • at the # prompt, type sudo fsck -f /

          • repeat the fsck command if there were errors

          • type reboot

          If for some reason you can't do the above...



          • boot to a Ubuntu Live DVD/USB

          • start gparted and determine which /dev/sdaX is your Ubuntu EXT4 partition

          • quit gparted

          • open a terminal window

          • type sudo fsck -f /dev/sdaX # replacing X with the number you found earlier

          • repeat the fsck command if there were errors

          • type reboot






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Sep 1 '17 at 13:51









          heynnemaheynnema

          21.4k32361




          21.4k32361












          • Thank for you contribuition @heynnema. As soon as possible I'll tried fixed as you recommended

            – Ronaldo Oliveira
            Sep 1 '17 at 19:57











          • Unfortunately it dosen't work. The 'grub rescue' does not have many options and the commands you showed above are not possible to execute. Many thanks for you support

            – Ronaldo Oliveira
            Sep 2 '17 at 0:12











          • @RonaldoOliveira You must have misread my instructions, because they have nothing to do with GRUB Rescue. Retry the first part of my answer, and if that doesn't work, then use the second method in my answer :-)

            – heynnema
            Sep 3 '17 at 0:48

















          • Thank for you contribuition @heynnema. As soon as possible I'll tried fixed as you recommended

            – Ronaldo Oliveira
            Sep 1 '17 at 19:57











          • Unfortunately it dosen't work. The 'grub rescue' does not have many options and the commands you showed above are not possible to execute. Many thanks for you support

            – Ronaldo Oliveira
            Sep 2 '17 at 0:12











          • @RonaldoOliveira You must have misread my instructions, because they have nothing to do with GRUB Rescue. Retry the first part of my answer, and if that doesn't work, then use the second method in my answer :-)

            – heynnema
            Sep 3 '17 at 0:48
















          Thank for you contribuition @heynnema. As soon as possible I'll tried fixed as you recommended

          – Ronaldo Oliveira
          Sep 1 '17 at 19:57





          Thank for you contribuition @heynnema. As soon as possible I'll tried fixed as you recommended

          – Ronaldo Oliveira
          Sep 1 '17 at 19:57













          Unfortunately it dosen't work. The 'grub rescue' does not have many options and the commands you showed above are not possible to execute. Many thanks for you support

          – Ronaldo Oliveira
          Sep 2 '17 at 0:12





          Unfortunately it dosen't work. The 'grub rescue' does not have many options and the commands you showed above are not possible to execute. Many thanks for you support

          – Ronaldo Oliveira
          Sep 2 '17 at 0:12













          @RonaldoOliveira You must have misread my instructions, because they have nothing to do with GRUB Rescue. Retry the first part of my answer, and if that doesn't work, then use the second method in my answer :-)

          – heynnema
          Sep 3 '17 at 0:48





          @RonaldoOliveira You must have misread my instructions, because they have nothing to do with GRUB Rescue. Retry the first part of my answer, and if that doesn't work, then use the second method in my answer :-)

          – heynnema
          Sep 3 '17 at 0:48

















          draft saved

          draft discarded
















































          Thanks for contributing an answer to Ask Ubuntu!


          • 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%2faskubuntu.com%2fquestions%2f951844%2finsmod-normal-command-returns-attempt-to-read-or-write-outside-of-disk-hd0%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

          Möglingen Índice Localización Historia Demografía Referencias Enlaces externos Menú de navegación48°53′18″N 9°07′45″E / 48.888333333333, 9.129166666666748°53′18″N 9°07′45″E / 48.888333333333, 9.1291666666667Sitio web oficial Mapa de Möglingen«Gemeinden in Deutschland nach Fläche, Bevölkerung und Postleitzahl am 30.09.2016»Möglingen

          Virtualbox - Configuration error: Querying “UUID” failed (VERR_CFGM_VALUE_NOT_FOUND)“VERR_SUPLIB_WORLD_WRITABLE” error when trying to installing OS in virtualboxVirtual Box Kernel errorFailed to open a seesion for the virtual machineFailed to open a session for the virtual machineUbuntu 14.04 LTS Virtualbox errorcan't use VM VirtualBoxusing virtualboxI can't run Linux-64 Bit on VirtualBoxUnable to insert the virtual optical disk (VBoxguestaddition) in virtual machine for ubuntu server in win 10VirtuaBox in Ubuntu 18.04 Issues with Win10.ISO Installation

          Torre de la Isleta Índice Véase también Referencias Bibliografía Enlaces externos Menú de navegación38°25′58″N 0°23′02″O / 38.43277778, -0.3838888938°25′58″N 0°23′02″O / 38.43277778, -0.38388889Torre de la Illeta de l’Horta o Torre Saleta. Base de datos de bienes inmuebles. Patrimonio Cultural. Secretaría de Estado de CulturaFicha BIC Torre de la Illeta de l’Horta. Dirección General de Patrimonio Cultural. Generalitat ValencianaLugares de interés. Ayuntamiento del CampelloTorre de la Isleta en CastillosNet.org