How do you repair an “input/output error” in an NTFS partition?












35















I replaced a buggy Windows Vista installation with Ubuntu. All works fine except that the main HD where I had all my files are now inaccessible. Here is the error message I get:



Error mounting: mount exited with exit code 13: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
Failed to read NTFS $Bitmap: Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it's a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRAID/FakeRAID then first activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
for more details


Is it necessarily a hardware problem? If not, is there a way to repair the HD from Ubuntu?










share|improve this question





























    35















    I replaced a buggy Windows Vista installation with Ubuntu. All works fine except that the main HD where I had all my files are now inaccessible. Here is the error message I get:



    Error mounting: mount exited with exit code 13: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
    Failed to read NTFS $Bitmap: Input/output error
    NTFS is either inconsistent, or there is a hardware fault, or it's a
    SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
    then reboot into Windows twice. The usage of the /f parameter is very
    important! If the device is a SoftRAID/FakeRAID then first activate
    it and mount a different device under the /dev/mapper/ directory, (e.g.
    /dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
    for more details


    Is it necessarily a hardware problem? If not, is there a way to repair the HD from Ubuntu?










    share|improve this question



























      35












      35








      35


      18






      I replaced a buggy Windows Vista installation with Ubuntu. All works fine except that the main HD where I had all my files are now inaccessible. Here is the error message I get:



      Error mounting: mount exited with exit code 13: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
      Failed to read NTFS $Bitmap: Input/output error
      NTFS is either inconsistent, or there is a hardware fault, or it's a
      SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
      then reboot into Windows twice. The usage of the /f parameter is very
      important! If the device is a SoftRAID/FakeRAID then first activate
      it and mount a different device under the /dev/mapper/ directory, (e.g.
      /dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
      for more details


      Is it necessarily a hardware problem? If not, is there a way to repair the HD from Ubuntu?










      share|improve this question
















      I replaced a buggy Windows Vista installation with Ubuntu. All works fine except that the main HD where I had all my files are now inaccessible. Here is the error message I get:



      Error mounting: mount exited with exit code 13: ntfs_attr_pread_i: ntfs_pread failed: Input/output error
      Failed to read NTFS $Bitmap: Input/output error
      NTFS is either inconsistent, or there is a hardware fault, or it's a
      SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
      then reboot into Windows twice. The usage of the /f parameter is very
      important! If the device is a SoftRAID/FakeRAID then first activate
      it and mount a different device under the /dev/mapper/ directory, (e.g.
      /dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
      for more details


      Is it necessarily a hardware problem? If not, is there a way to repair the HD from Ubuntu?







      windows ntfs






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited May 15 '16 at 19:06









      muru

      1




      1










      asked Oct 31 '11 at 15:13









      CalixteCalixte

      1,11271930




      1,11271930






















          6 Answers
          6






          active

          oldest

          votes


















          24














          chkdsk /R is a pretty important command when things get hairy with NTFS. Unfortunately I don't know of a Linux tool that comes close to covering everything it does. In short, to run it, you're going to need some sort of Windows recovery disk.



          If you don't have one to hand, there's an ISO offered up in a thread on another set of support forums (see the first answer).



          There are tools like ntfsfix (part of the ntfsprogs package) that can do surface checks on NTFS disks but they don't tend to be able to fix the drives.






          share|improve this answer



















          • 3





            You could install VirtualBox and an XP on it. Prevent the drive mounting in fstab, (if USB mount: add the USB filter in VBox so that XP sees the "raw" USB drive), mount the drive on XP and run chkdsk on it.

            – Ring Ø
            Jan 6 '14 at 2:46











          • @ringø what if windows cannot mount it ? it shows that your new device wont work properly message, so how can i check it ?

            – Mostafa Hussein
            Aug 31 '16 at 1:03



















          46














          ntfsfix worked for me :



          sudo ntfsfix /dev/sdb1


          Provided in the ntfs-3g package.






          share|improve this answer





















          • 1





            after following askubuntu.com/a/364298/50885 follow above to get USB mount :)

            – CoDe
            Apr 3 '14 at 10:52



















          3














          NTFS is a closed source Microsoft file system, and you'll need Windows to repair it, by running chkdsk /f, as suggested.
          If the problem is hardware related, you'll have to replace the hdd.






          share|improve this answer
























          • Not necessary only Windows.

            – BVengerov
            Jan 13 '17 at 7:52



















          2














          i have encountered a similar situation once,then i kept the harddisk on windows,then a popup appeared asking to check the disk for errors.



          if didn't ask goto computer,right click on the drive and then click on properties,there would be a tab "tools"



          disk checking



          select "check now"



          this type of errors occur if you dont safely remove harddisks.






          share|improve this answer

































            2














            Background:



            So I was facing, more or less, the same issue. Around 12 files on the NTFS partition of my HD were inaccessible nor could they be deleted. Got to know about them through backintime's error logs. Fired up my Window 7 on vmware, accessed that folder containing the files through shared folder and copied them to a new folder. But for some reason I was not able to delete those files (0 bytes) from Windows 7 either. No surprise there, the OS did not have low-level access to those files.



            ntfsfix did not fix it, said nothing was wrong, and fsck said all's cool with the the device. I could not chkdsk /R because the files were shared through network drive. And I didn't have Window 7 installed on my physical machine.



            Solution (steps for vmplayer, but could easily be followed for virtualbox):




            1. Add a new HD to your vm (had to start vmplayer as root)

            2. When prompted for the disk type choose physical disk

            3. Choose the correct device (for this reason vmplayer was started as root)

            4. Select "Use individual partitions"

            5. Select the partition containing the buggy files

            6. Finish adding

            7. Start the vm


            For me Windows 7 detected the new partition and did a checkdisk on boot. It had a lot of (Index) cleaning to do. The buggy files were gone. And the problem solved.






            share|improve this answer
























            • I don't see an option to add a physical disk in VirtualBox. There must be a way but for whatever reason the Mac version I'm using isn't offering it to me.

              – Sridhar-Sarnobat
              Apr 8 '16 at 5:57



















            0














            I got this after newly fomratting an SD card as ntfs, all I had to do what umount it first.



            sudo umount -l /dev/sdx1


            then mount worked again






            share|improve this answer






















              protected by Community Jul 14 '12 at 14:05



              Thank you for your interest in this question.
              Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



              Would you like to answer one of these unanswered questions instead?














              6 Answers
              6






              active

              oldest

              votes








              6 Answers
              6






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              24














              chkdsk /R is a pretty important command when things get hairy with NTFS. Unfortunately I don't know of a Linux tool that comes close to covering everything it does. In short, to run it, you're going to need some sort of Windows recovery disk.



              If you don't have one to hand, there's an ISO offered up in a thread on another set of support forums (see the first answer).



              There are tools like ntfsfix (part of the ntfsprogs package) that can do surface checks on NTFS disks but they don't tend to be able to fix the drives.






              share|improve this answer



















              • 3





                You could install VirtualBox and an XP on it. Prevent the drive mounting in fstab, (if USB mount: add the USB filter in VBox so that XP sees the "raw" USB drive), mount the drive on XP and run chkdsk on it.

                – Ring Ø
                Jan 6 '14 at 2:46











              • @ringø what if windows cannot mount it ? it shows that your new device wont work properly message, so how can i check it ?

                – Mostafa Hussein
                Aug 31 '16 at 1:03
















              24














              chkdsk /R is a pretty important command when things get hairy with NTFS. Unfortunately I don't know of a Linux tool that comes close to covering everything it does. In short, to run it, you're going to need some sort of Windows recovery disk.



              If you don't have one to hand, there's an ISO offered up in a thread on another set of support forums (see the first answer).



              There are tools like ntfsfix (part of the ntfsprogs package) that can do surface checks on NTFS disks but they don't tend to be able to fix the drives.






              share|improve this answer



















              • 3





                You could install VirtualBox and an XP on it. Prevent the drive mounting in fstab, (if USB mount: add the USB filter in VBox so that XP sees the "raw" USB drive), mount the drive on XP and run chkdsk on it.

                – Ring Ø
                Jan 6 '14 at 2:46











              • @ringø what if windows cannot mount it ? it shows that your new device wont work properly message, so how can i check it ?

                – Mostafa Hussein
                Aug 31 '16 at 1:03














              24












              24








              24







              chkdsk /R is a pretty important command when things get hairy with NTFS. Unfortunately I don't know of a Linux tool that comes close to covering everything it does. In short, to run it, you're going to need some sort of Windows recovery disk.



              If you don't have one to hand, there's an ISO offered up in a thread on another set of support forums (see the first answer).



              There are tools like ntfsfix (part of the ntfsprogs package) that can do surface checks on NTFS disks but they don't tend to be able to fix the drives.






              share|improve this answer













              chkdsk /R is a pretty important command when things get hairy with NTFS. Unfortunately I don't know of a Linux tool that comes close to covering everything it does. In short, to run it, you're going to need some sort of Windows recovery disk.



              If you don't have one to hand, there's an ISO offered up in a thread on another set of support forums (see the first answer).



              There are tools like ntfsfix (part of the ntfsprogs package) that can do surface checks on NTFS disks but they don't tend to be able to fix the drives.







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Oct 31 '11 at 15:24









              OliOli

              221k86558762




              221k86558762








              • 3





                You could install VirtualBox and an XP on it. Prevent the drive mounting in fstab, (if USB mount: add the USB filter in VBox so that XP sees the "raw" USB drive), mount the drive on XP and run chkdsk on it.

                – Ring Ø
                Jan 6 '14 at 2:46











              • @ringø what if windows cannot mount it ? it shows that your new device wont work properly message, so how can i check it ?

                – Mostafa Hussein
                Aug 31 '16 at 1:03














              • 3





                You could install VirtualBox and an XP on it. Prevent the drive mounting in fstab, (if USB mount: add the USB filter in VBox so that XP sees the "raw" USB drive), mount the drive on XP and run chkdsk on it.

                – Ring Ø
                Jan 6 '14 at 2:46











              • @ringø what if windows cannot mount it ? it shows that your new device wont work properly message, so how can i check it ?

                – Mostafa Hussein
                Aug 31 '16 at 1:03








              3




              3





              You could install VirtualBox and an XP on it. Prevent the drive mounting in fstab, (if USB mount: add the USB filter in VBox so that XP sees the "raw" USB drive), mount the drive on XP and run chkdsk on it.

              – Ring Ø
              Jan 6 '14 at 2:46





              You could install VirtualBox and an XP on it. Prevent the drive mounting in fstab, (if USB mount: add the USB filter in VBox so that XP sees the "raw" USB drive), mount the drive on XP and run chkdsk on it.

              – Ring Ø
              Jan 6 '14 at 2:46













              @ringø what if windows cannot mount it ? it shows that your new device wont work properly message, so how can i check it ?

              – Mostafa Hussein
              Aug 31 '16 at 1:03





              @ringø what if windows cannot mount it ? it shows that your new device wont work properly message, so how can i check it ?

              – Mostafa Hussein
              Aug 31 '16 at 1:03













              46














              ntfsfix worked for me :



              sudo ntfsfix /dev/sdb1


              Provided in the ntfs-3g package.






              share|improve this answer





















              • 1





                after following askubuntu.com/a/364298/50885 follow above to get USB mount :)

                – CoDe
                Apr 3 '14 at 10:52
















              46














              ntfsfix worked for me :



              sudo ntfsfix /dev/sdb1


              Provided in the ntfs-3g package.






              share|improve this answer





















              • 1





                after following askubuntu.com/a/364298/50885 follow above to get USB mount :)

                – CoDe
                Apr 3 '14 at 10:52














              46












              46








              46







              ntfsfix worked for me :



              sudo ntfsfix /dev/sdb1


              Provided in the ntfs-3g package.






              share|improve this answer















              ntfsfix worked for me :



              sudo ntfsfix /dev/sdb1


              Provided in the ntfs-3g package.







              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Jan 11 '17 at 17:59









              jokerdino

              32.6k21119187




              32.6k21119187










              answered Jun 27 '12 at 21:32









              Marc MMarc M

              461142




              461142








              • 1





                after following askubuntu.com/a/364298/50885 follow above to get USB mount :)

                – CoDe
                Apr 3 '14 at 10:52














              • 1





                after following askubuntu.com/a/364298/50885 follow above to get USB mount :)

                – CoDe
                Apr 3 '14 at 10:52








              1




              1





              after following askubuntu.com/a/364298/50885 follow above to get USB mount :)

              – CoDe
              Apr 3 '14 at 10:52





              after following askubuntu.com/a/364298/50885 follow above to get USB mount :)

              – CoDe
              Apr 3 '14 at 10:52











              3














              NTFS is a closed source Microsoft file system, and you'll need Windows to repair it, by running chkdsk /f, as suggested.
              If the problem is hardware related, you'll have to replace the hdd.






              share|improve this answer
























              • Not necessary only Windows.

                – BVengerov
                Jan 13 '17 at 7:52
















              3














              NTFS is a closed source Microsoft file system, and you'll need Windows to repair it, by running chkdsk /f, as suggested.
              If the problem is hardware related, you'll have to replace the hdd.






              share|improve this answer
























              • Not necessary only Windows.

                – BVengerov
                Jan 13 '17 at 7:52














              3












              3








              3







              NTFS is a closed source Microsoft file system, and you'll need Windows to repair it, by running chkdsk /f, as suggested.
              If the problem is hardware related, you'll have to replace the hdd.






              share|improve this answer













              NTFS is a closed source Microsoft file system, and you'll need Windows to repair it, by running chkdsk /f, as suggested.
              If the problem is hardware related, you'll have to replace the hdd.







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Oct 31 '11 at 15:22









              mikewhatevermikewhatever

              23.6k76886




              23.6k76886













              • Not necessary only Windows.

                – BVengerov
                Jan 13 '17 at 7:52



















              • Not necessary only Windows.

                – BVengerov
                Jan 13 '17 at 7:52

















              Not necessary only Windows.

              – BVengerov
              Jan 13 '17 at 7:52





              Not necessary only Windows.

              – BVengerov
              Jan 13 '17 at 7:52











              2














              i have encountered a similar situation once,then i kept the harddisk on windows,then a popup appeared asking to check the disk for errors.



              if didn't ask goto computer,right click on the drive and then click on properties,there would be a tab "tools"



              disk checking



              select "check now"



              this type of errors occur if you dont safely remove harddisks.






              share|improve this answer






























                2














                i have encountered a similar situation once,then i kept the harddisk on windows,then a popup appeared asking to check the disk for errors.



                if didn't ask goto computer,right click on the drive and then click on properties,there would be a tab "tools"



                disk checking



                select "check now"



                this type of errors occur if you dont safely remove harddisks.






                share|improve this answer




























                  2












                  2








                  2







                  i have encountered a similar situation once,then i kept the harddisk on windows,then a popup appeared asking to check the disk for errors.



                  if didn't ask goto computer,right click on the drive and then click on properties,there would be a tab "tools"



                  disk checking



                  select "check now"



                  this type of errors occur if you dont safely remove harddisks.






                  share|improve this answer















                  i have encountered a similar situation once,then i kept the harddisk on windows,then a popup appeared asking to check the disk for errors.



                  if didn't ask goto computer,right click on the drive and then click on properties,there would be a tab "tools"



                  disk checking



                  select "check now"



                  this type of errors occur if you dont safely remove harddisks.







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Sep 7 '13 at 20:07









                  Braiam

                  51.6k20136220




                  51.6k20136220










                  answered Oct 31 '11 at 16:23









                  saiki4116saiki4116

                  4192522




                  4192522























                      2














                      Background:



                      So I was facing, more or less, the same issue. Around 12 files on the NTFS partition of my HD were inaccessible nor could they be deleted. Got to know about them through backintime's error logs. Fired up my Window 7 on vmware, accessed that folder containing the files through shared folder and copied them to a new folder. But for some reason I was not able to delete those files (0 bytes) from Windows 7 either. No surprise there, the OS did not have low-level access to those files.



                      ntfsfix did not fix it, said nothing was wrong, and fsck said all's cool with the the device. I could not chkdsk /R because the files were shared through network drive. And I didn't have Window 7 installed on my physical machine.



                      Solution (steps for vmplayer, but could easily be followed for virtualbox):




                      1. Add a new HD to your vm (had to start vmplayer as root)

                      2. When prompted for the disk type choose physical disk

                      3. Choose the correct device (for this reason vmplayer was started as root)

                      4. Select "Use individual partitions"

                      5. Select the partition containing the buggy files

                      6. Finish adding

                      7. Start the vm


                      For me Windows 7 detected the new partition and did a checkdisk on boot. It had a lot of (Index) cleaning to do. The buggy files were gone. And the problem solved.






                      share|improve this answer
























                      • I don't see an option to add a physical disk in VirtualBox. There must be a way but for whatever reason the Mac version I'm using isn't offering it to me.

                        – Sridhar-Sarnobat
                        Apr 8 '16 at 5:57
















                      2














                      Background:



                      So I was facing, more or less, the same issue. Around 12 files on the NTFS partition of my HD were inaccessible nor could they be deleted. Got to know about them through backintime's error logs. Fired up my Window 7 on vmware, accessed that folder containing the files through shared folder and copied them to a new folder. But for some reason I was not able to delete those files (0 bytes) from Windows 7 either. No surprise there, the OS did not have low-level access to those files.



                      ntfsfix did not fix it, said nothing was wrong, and fsck said all's cool with the the device. I could not chkdsk /R because the files were shared through network drive. And I didn't have Window 7 installed on my physical machine.



                      Solution (steps for vmplayer, but could easily be followed for virtualbox):




                      1. Add a new HD to your vm (had to start vmplayer as root)

                      2. When prompted for the disk type choose physical disk

                      3. Choose the correct device (for this reason vmplayer was started as root)

                      4. Select "Use individual partitions"

                      5. Select the partition containing the buggy files

                      6. Finish adding

                      7. Start the vm


                      For me Windows 7 detected the new partition and did a checkdisk on boot. It had a lot of (Index) cleaning to do. The buggy files were gone. And the problem solved.






                      share|improve this answer
























                      • I don't see an option to add a physical disk in VirtualBox. There must be a way but for whatever reason the Mac version I'm using isn't offering it to me.

                        – Sridhar-Sarnobat
                        Apr 8 '16 at 5:57














                      2












                      2








                      2







                      Background:



                      So I was facing, more or less, the same issue. Around 12 files on the NTFS partition of my HD were inaccessible nor could they be deleted. Got to know about them through backintime's error logs. Fired up my Window 7 on vmware, accessed that folder containing the files through shared folder and copied them to a new folder. But for some reason I was not able to delete those files (0 bytes) from Windows 7 either. No surprise there, the OS did not have low-level access to those files.



                      ntfsfix did not fix it, said nothing was wrong, and fsck said all's cool with the the device. I could not chkdsk /R because the files were shared through network drive. And I didn't have Window 7 installed on my physical machine.



                      Solution (steps for vmplayer, but could easily be followed for virtualbox):




                      1. Add a new HD to your vm (had to start vmplayer as root)

                      2. When prompted for the disk type choose physical disk

                      3. Choose the correct device (for this reason vmplayer was started as root)

                      4. Select "Use individual partitions"

                      5. Select the partition containing the buggy files

                      6. Finish adding

                      7. Start the vm


                      For me Windows 7 detected the new partition and did a checkdisk on boot. It had a lot of (Index) cleaning to do. The buggy files were gone. And the problem solved.






                      share|improve this answer













                      Background:



                      So I was facing, more or less, the same issue. Around 12 files on the NTFS partition of my HD were inaccessible nor could they be deleted. Got to know about them through backintime's error logs. Fired up my Window 7 on vmware, accessed that folder containing the files through shared folder and copied them to a new folder. But for some reason I was not able to delete those files (0 bytes) from Windows 7 either. No surprise there, the OS did not have low-level access to those files.



                      ntfsfix did not fix it, said nothing was wrong, and fsck said all's cool with the the device. I could not chkdsk /R because the files were shared through network drive. And I didn't have Window 7 installed on my physical machine.



                      Solution (steps for vmplayer, but could easily be followed for virtualbox):




                      1. Add a new HD to your vm (had to start vmplayer as root)

                      2. When prompted for the disk type choose physical disk

                      3. Choose the correct device (for this reason vmplayer was started as root)

                      4. Select "Use individual partitions"

                      5. Select the partition containing the buggy files

                      6. Finish adding

                      7. Start the vm


                      For me Windows 7 detected the new partition and did a checkdisk on boot. It had a lot of (Index) cleaning to do. The buggy files were gone. And the problem solved.







                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered Jun 6 '15 at 21:13









                      Bleeding FingersBleeding Fingers

                      4052724




                      4052724













                      • I don't see an option to add a physical disk in VirtualBox. There must be a way but for whatever reason the Mac version I'm using isn't offering it to me.

                        – Sridhar-Sarnobat
                        Apr 8 '16 at 5:57



















                      • I don't see an option to add a physical disk in VirtualBox. There must be a way but for whatever reason the Mac version I'm using isn't offering it to me.

                        – Sridhar-Sarnobat
                        Apr 8 '16 at 5:57

















                      I don't see an option to add a physical disk in VirtualBox. There must be a way but for whatever reason the Mac version I'm using isn't offering it to me.

                      – Sridhar-Sarnobat
                      Apr 8 '16 at 5:57





                      I don't see an option to add a physical disk in VirtualBox. There must be a way but for whatever reason the Mac version I'm using isn't offering it to me.

                      – Sridhar-Sarnobat
                      Apr 8 '16 at 5:57











                      0














                      I got this after newly fomratting an SD card as ntfs, all I had to do what umount it first.



                      sudo umount -l /dev/sdx1


                      then mount worked again






                      share|improve this answer




























                        0














                        I got this after newly fomratting an SD card as ntfs, all I had to do what umount it first.



                        sudo umount -l /dev/sdx1


                        then mount worked again






                        share|improve this answer


























                          0












                          0








                          0







                          I got this after newly fomratting an SD card as ntfs, all I had to do what umount it first.



                          sudo umount -l /dev/sdx1


                          then mount worked again






                          share|improve this answer













                          I got this after newly fomratting an SD card as ntfs, all I had to do what umount it first.



                          sudo umount -l /dev/sdx1


                          then mount worked again







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered 2 hours ago









                          teknopaulteknopaul

                          87669




                          87669

















                              protected by Community Jul 14 '12 at 14:05



                              Thank you for your interest in this question.
                              Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



                              Would you like to answer one of these unanswered questions instead?



                              Popular posts from this blog

                              GameSpot

                              connect to host localhost port 22: Connection refused

                              Getting a Wifi WPA2 wifi connection