mount(2) system call failed: Structure needs cleaning












0















I cannot re-mount an AWS EBS drive to a Ubuntu instance. I'm not sure if this is a Ubuntu thing or Amazon Web Services. It's not a bootable drive.



sudo mount /dev/xvdf /data

mount(2) system call failed: Structure needs cleaning.


I originally mounted it following this: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-using-volumes.html



I rebooted, and the mount was missing.



I tried



sudo fsck.ext4 /dev/xvdf

/dev/xvdf: clean, 17665/1073741824 files, 233339937/4294967296 blocks

e2fsck also output the same.


I thought maybe the fstab was corrupted so I returned it to original state and then rebooted, but I still cannot mount the drive.



EDIT:



I ran the following, and it shows an error. The current block size is 4096 according to sudo stat -f /dev/xvde



sudo e2fsck -c /dev/xvde
badblocks: Value too large for defined data type invalid end block

(4294967296): must be 32-bit value
/dev/xvde: Updating bad block inode.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/xvde: ***** FILE SYSTEM WAS MODIFIED *****
/dev/xvde: 17666/1073741824 files (15.2% non-contiguous), 233339938/4294967296 blocks









share|improve this question









New contributor




Caleb Pitman is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

























    0















    I cannot re-mount an AWS EBS drive to a Ubuntu instance. I'm not sure if this is a Ubuntu thing or Amazon Web Services. It's not a bootable drive.



    sudo mount /dev/xvdf /data

    mount(2) system call failed: Structure needs cleaning.


    I originally mounted it following this: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-using-volumes.html



    I rebooted, and the mount was missing.



    I tried



    sudo fsck.ext4 /dev/xvdf

    /dev/xvdf: clean, 17665/1073741824 files, 233339937/4294967296 blocks

    e2fsck also output the same.


    I thought maybe the fstab was corrupted so I returned it to original state and then rebooted, but I still cannot mount the drive.



    EDIT:



    I ran the following, and it shows an error. The current block size is 4096 according to sudo stat -f /dev/xvde



    sudo e2fsck -c /dev/xvde
    badblocks: Value too large for defined data type invalid end block

    (4294967296): must be 32-bit value
    /dev/xvde: Updating bad block inode.
    Pass 1: Checking inodes, blocks, and sizes
    Pass 2: Checking directory structure
    Pass 3: Checking directory connectivity
    Pass 4: Checking reference counts
    Pass 5: Checking group summary information

    /dev/xvde: ***** FILE SYSTEM WAS MODIFIED *****
    /dev/xvde: 17666/1073741824 files (15.2% non-contiguous), 233339938/4294967296 blocks









    share|improve this question









    New contributor




    Caleb Pitman is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.























      0












      0








      0








      I cannot re-mount an AWS EBS drive to a Ubuntu instance. I'm not sure if this is a Ubuntu thing or Amazon Web Services. It's not a bootable drive.



      sudo mount /dev/xvdf /data

      mount(2) system call failed: Structure needs cleaning.


      I originally mounted it following this: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-using-volumes.html



      I rebooted, and the mount was missing.



      I tried



      sudo fsck.ext4 /dev/xvdf

      /dev/xvdf: clean, 17665/1073741824 files, 233339937/4294967296 blocks

      e2fsck also output the same.


      I thought maybe the fstab was corrupted so I returned it to original state and then rebooted, but I still cannot mount the drive.



      EDIT:



      I ran the following, and it shows an error. The current block size is 4096 according to sudo stat -f /dev/xvde



      sudo e2fsck -c /dev/xvde
      badblocks: Value too large for defined data type invalid end block

      (4294967296): must be 32-bit value
      /dev/xvde: Updating bad block inode.
      Pass 1: Checking inodes, blocks, and sizes
      Pass 2: Checking directory structure
      Pass 3: Checking directory connectivity
      Pass 4: Checking reference counts
      Pass 5: Checking group summary information

      /dev/xvde: ***** FILE SYSTEM WAS MODIFIED *****
      /dev/xvde: 17666/1073741824 files (15.2% non-contiguous), 233339938/4294967296 blocks









      share|improve this question









      New contributor




      Caleb Pitman is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.












      I cannot re-mount an AWS EBS drive to a Ubuntu instance. I'm not sure if this is a Ubuntu thing or Amazon Web Services. It's not a bootable drive.



      sudo mount /dev/xvdf /data

      mount(2) system call failed: Structure needs cleaning.


      I originally mounted it following this: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-using-volumes.html



      I rebooted, and the mount was missing.



      I tried



      sudo fsck.ext4 /dev/xvdf

      /dev/xvdf: clean, 17665/1073741824 files, 233339937/4294967296 blocks

      e2fsck also output the same.


      I thought maybe the fstab was corrupted so I returned it to original state and then rebooted, but I still cannot mount the drive.



      EDIT:



      I ran the following, and it shows an error. The current block size is 4096 according to sudo stat -f /dev/xvde



      sudo e2fsck -c /dev/xvde
      badblocks: Value too large for defined data type invalid end block

      (4294967296): must be 32-bit value
      /dev/xvde: Updating bad block inode.
      Pass 1: Checking inodes, blocks, and sizes
      Pass 2: Checking directory structure
      Pass 3: Checking directory connectivity
      Pass 4: Checking reference counts
      Pass 5: Checking group summary information

      /dev/xvde: ***** FILE SYSTEM WAS MODIFIED *****
      /dev/xvde: 17666/1073741824 files (15.2% non-contiguous), 233339938/4294967296 blocks






      mount hard-drive fstab aws






      share|improve this question









      New contributor




      Caleb Pitman is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      share|improve this question









      New contributor




      Caleb Pitman is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      share|improve this question




      share|improve this question








      edited 5 hours ago









      Jeff

      696319




      696319






      New contributor




      Caleb Pitman is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.









      asked 10 hours ago









      Caleb PitmanCaleb Pitman

      1012




      1012




      New contributor




      Caleb Pitman is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.





      New contributor





      Caleb Pitman is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






      Caleb Pitman is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.






















          0






          active

          oldest

          votes











          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
          });


          }
          });






          Caleb Pitman is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1117976%2fmount2-system-call-failed-structure-needs-cleaning%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








          Caleb Pitman is a new contributor. Be nice, and check out our Code of Conduct.










          draft saved

          draft discarded


















          Caleb Pitman is a new contributor. Be nice, and check out our Code of Conduct.













          Caleb Pitman is a new contributor. Be nice, and check out our Code of Conduct.












          Caleb Pitman is a new contributor. Be nice, and check out our Code of Conduct.
















          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%2f1117976%2fmount2-system-call-failed-structure-needs-cleaning%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

          Category:香港粉麵

          List *all* the tuples!

          Channel [V]