fsck can't find fsck.ntfs












33














On several machines that I've upgraded from Natty to Oneiric, I get an error every boot (one for every NTFS partition):



Serious errors were found while checking the disk drive for /windows/c.

Press I to ignore, S to skip mounting, or M for manual recovery


Following the suggestion in this answer, I ran fsck from the manual recovery shell. I got this output:



fsck from util-linux 2.19.1
fsck: fsck.ntfs: not found
fsck: Error 2 while executing fsck.ntfs for /dev/sda1


I can't find fsck.ntfs, and command-not-found doesn't help either. How can I make this error go away?



By the way, I've tried booting into Windows (XP) several times, thinking that Windows would repair the filesystems. But apparently Windows thinks the filesysystems are just fine. And it's odd that all NTFS filesystems are affected.



Also, I can work around this problem by dropping to a recovery shell and issuing mount -a, but for my coworkers' sakes I need unattended boot.










share|improve this question




















  • 1




    I can't find fsck.ntfs I think you should go with ntfsck or ntfsfix for ntfs partitions, AFAIK fsck is mainly used for ext partition.
    – sagarchalise
    Dec 8 '11 at 7:56
















33














On several machines that I've upgraded from Natty to Oneiric, I get an error every boot (one for every NTFS partition):



Serious errors were found while checking the disk drive for /windows/c.

Press I to ignore, S to skip mounting, or M for manual recovery


Following the suggestion in this answer, I ran fsck from the manual recovery shell. I got this output:



fsck from util-linux 2.19.1
fsck: fsck.ntfs: not found
fsck: Error 2 while executing fsck.ntfs for /dev/sda1


I can't find fsck.ntfs, and command-not-found doesn't help either. How can I make this error go away?



By the way, I've tried booting into Windows (XP) several times, thinking that Windows would repair the filesystems. But apparently Windows thinks the filesysystems are just fine. And it's odd that all NTFS filesystems are affected.



Also, I can work around this problem by dropping to a recovery shell and issuing mount -a, but for my coworkers' sakes I need unattended boot.










share|improve this question




















  • 1




    I can't find fsck.ntfs I think you should go with ntfsck or ntfsfix for ntfs partitions, AFAIK fsck is mainly used for ext partition.
    – sagarchalise
    Dec 8 '11 at 7:56














33












33








33


7





On several machines that I've upgraded from Natty to Oneiric, I get an error every boot (one for every NTFS partition):



Serious errors were found while checking the disk drive for /windows/c.

Press I to ignore, S to skip mounting, or M for manual recovery


Following the suggestion in this answer, I ran fsck from the manual recovery shell. I got this output:



fsck from util-linux 2.19.1
fsck: fsck.ntfs: not found
fsck: Error 2 while executing fsck.ntfs for /dev/sda1


I can't find fsck.ntfs, and command-not-found doesn't help either. How can I make this error go away?



By the way, I've tried booting into Windows (XP) several times, thinking that Windows would repair the filesystems. But apparently Windows thinks the filesysystems are just fine. And it's odd that all NTFS filesystems are affected.



Also, I can work around this problem by dropping to a recovery shell and issuing mount -a, but for my coworkers' sakes I need unattended boot.










share|improve this question















On several machines that I've upgraded from Natty to Oneiric, I get an error every boot (one for every NTFS partition):



Serious errors were found while checking the disk drive for /windows/c.

Press I to ignore, S to skip mounting, or M for manual recovery


Following the suggestion in this answer, I ran fsck from the manual recovery shell. I got this output:



fsck from util-linux 2.19.1
fsck: fsck.ntfs: not found
fsck: Error 2 while executing fsck.ntfs for /dev/sda1


I can't find fsck.ntfs, and command-not-found doesn't help either. How can I make this error go away?



By the way, I've tried booting into Windows (XP) several times, thinking that Windows would repair the filesystems. But apparently Windows thinks the filesysystems are just fine. And it's odd that all NTFS filesystems are affected.



Also, I can work around this problem by dropping to a recovery shell and issuing mount -a, but for my coworkers' sakes I need unattended boot.







ntfs fsck






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 13 '17 at 12:23









Community

1




1










asked Dec 8 '11 at 7:37









Scott Severance

10.3k73468




10.3k73468








  • 1




    I can't find fsck.ntfs I think you should go with ntfsck or ntfsfix for ntfs partitions, AFAIK fsck is mainly used for ext partition.
    – sagarchalise
    Dec 8 '11 at 7:56














  • 1




    I can't find fsck.ntfs I think you should go with ntfsck or ntfsfix for ntfs partitions, AFAIK fsck is mainly used for ext partition.
    – sagarchalise
    Dec 8 '11 at 7:56








1




1




I can't find fsck.ntfs I think you should go with ntfsck or ntfsfix for ntfs partitions, AFAIK fsck is mainly used for ext partition.
– sagarchalise
Dec 8 '11 at 7:56




I can't find fsck.ntfs I think you should go with ntfsck or ntfsfix for ntfs partitions, AFAIK fsck is mainly used for ext partition.
– sagarchalise
Dec 8 '11 at 7:56










9 Answers
9






active

oldest

votes


















36














fsck.ntfs is usually only a link to ntfsfix which is an utility from the package ntfsprogs that is already available with a standard installation of Ubuntu.



You can make a simbolic link between fsck.ntfs and ntfsfix to solve this permanently:



sudo ln -s /usr/bin/ntfsfix /sbin/fsck.ntfs
sudo ln -s /usr/bin/ntfsfix /sbin/fsck.ntfs-3g


Keep in mind that this utility came from a reverse engineering process and are not the best option to manage your filesystem, the NTFS filesystem does not belong to the GNU/linux world.






share|improve this answer

















  • 4




    Thanks. I set up the symlinks (which should have been made already) and the problem is solved. The only question that remains is: Why was the symlink missing in the first place? fsck apparently runs on boot. Therefore, it is a bug if it tries to check a filesystem that it can't handle. The partition was--and has been--perfectly fine. Apparently this was just a routine check that was failing.
    – Scott Severance
    Dec 8 '11 at 8:45






  • 1




    It is funny I trust a community reversed engineered tool a lot more than the official Microsoft tool which destroyed my perfectly working NTFS partitions before :)
    – AhHatem
    Jan 24 '13 at 14:37










  • Doesn't work to me. Ubuntu 12.04.3
    – zuba
    Dec 6 '13 at 14:08










  • You can count more on Linux-based tools to recover your Windows installation and data than the Windows-based tools. Also I experienced that Linux lets you do things such as putting question marks in your filenames; this is officially permitted by NTFS standards but here's the joke: the Windows driver doesn't support it! I would like to point at dedicated "Linux-based Rescue / Repair Live-CDs" (or USB) such as SystemRescueCD.
    – tiktak
    Jan 16 '14 at 0:35










  • The answer should be: askubuntu.com/a/292889/126984
    – wakeup
    Apr 8 '14 at 10:50



















20














I think it could be noted for some people that ntfsfix gets installed into /bin/ instead of /usr/bin. So



sudo ln -nsf /bin/ntfsfix /sbin/fsck.ntfs
sudo ln -nsf /bin/ntfsfix /sbin/fsck.ntfs-3g


If you have already created the symlink from /usr/bin/



sudo rm -f /sbin/fsck.ntfs
sudo rm -f /sbin/fsck.ntfs-3g


And then create the symlinks again.






share|improve this answer























  • upvoted because a) downvoter left no comment explaining downvote, which would be courteous at least, and b) just had to 'locate ntfsfix' to find mine at /bin/ntfsfix, so it seems relevant at least.
    – A. L. Flanagan
    Jun 22 '13 at 12:32










  • I would suggest adding this as a comment to Micro's answer, rather than as a standalone answer.
    – waldyrious
    Dec 3 '13 at 19:43










  • This is the correct answer for later versions of ubuntu like 13.04
    – wakeup
    Apr 8 '14 at 10:50










  • This worked for me in Ubuntu 14.04!
    – HarlemSquirrel
    Nov 17 '14 at 14:21



















5














If you have an NTFS partition automatically mounted at startup, the only reason could be you have manually or through some tool added it to /etc/fstab (not taking into account WUBI).



If the system tries to check the partition at startup it means that in the corresponding line in /etc/fstab there is a sixth field and its value is 1 or 2.



ntfsfix is not linked by default to fsck.ntfs, and it only provides limited check capabilities, as explained in the man page:




ntfsfix is a utility that fixes some common NTFS problems. ntfsfix is
NOT a Linux version of chkdsk. It only repairs some fundamental NTFS
inconsistencies, resets the NTFS journal file and schedules an NTFS
consistency check for the first boot into Windows.




The common solution is not to create the symlink, but to remove or set to 0 the sixth field in /etc/fstab.






share|improve this answer



















  • 2




    Actually, that's not exactly accurate. During installation, existing NTFS partitions get automatically added to fstab without any manual editing of fstab. So, they should get added in a sane way. I don't care whether they get checked or not. I just don't want unnecessary errors messages showing up at boot when in reality there is no error.
    – Scott Severance
    Dec 8 '11 at 21:57












  • Never seen this behavior in older Ubuntu releases, when I had ntfs partitions. I suppose is a new features, now that I do not use ntfs anymore. Btw, you did not say if there was the non-zero number in fstab.
    – enzotib
    Dec 8 '11 at 22:02












  • This might explain the problem: On the machine in question, there is indeed a nonzero number in fstab. On another machine, I formerly had this same problem, but it went away after I did a reinstall to solve a different issue. The new fstab has the sixth field set to zero. So, apparently the defaults changed between Natty and Oneiric and the upgrade didn't make any conversions.
    – Scott Severance
    Dec 8 '11 at 22:59






  • 1




    Me thinks that the "pass" argument is just in what order the partitions should be auto mounted, so this seems to be new in Oneiric. I just upgraded recently and I have had pass=3 set on my ntfs partitions, and I never had any problem until the first boot in oneiric. It got stuck on some stupid promt hidden among some irrelevant error messages. Not cool for a server to wait for a keypress during boot.
    – KarlP
    Dec 12 '11 at 21:04





















5














Micro's answer worked for me, however my 11.10 (upgraded from 11.04) did not have ntfsprogs. 'sudo apt-get install ntfsprogs' solved that, then the link suggestion worked fine.






share|improve this answer































    3














    The problem is a missing symbolic link, to either /usr/bin/ntfsfix or /bin/ntfsfix. You can make the needed link(s) with:



    sudo ln -s $(which ntfsfix) /sbin/fsck.ntfs
    sudo ln -s $(which ntfsfix) /sbin/fsck.ntfs-3





    share|improve this answer





















    • This worked for me on Ubuntu 14.04 LTS on April 13th, 2015
      – HarlemSquirrel
      Apr 13 '15 at 17:10



















    1














    I have the same problem after I accidentally installed ntfsprogs. I think there is bug in dependencies because after installation of ntfsprogs all NTFS drives started mounting read-only.



    When I turned back ntfs-3g, fsck.ntfs disappeared.



    SO:



    sudo apt-get install ntfsprogs
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    The following packages will be REMOVED:
    ntfs-3g
    The following NEW packages will be installed:
    ntfsprogs
    0 upgraded, 1 newly installed, 1 to remove and 0 not upgraded.


    BUT:



    apt-cache showpkg ntfs-3g
    Package: ntfs-3g
    Versions:
    1:2011.4.12AR.4-2ubuntu3 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_oneiric_main_binary-amd64_Packages) (/var/lib/dpkg/status)
    ...
    Provides:
    1:2011.4.12AR.4-2ubuntu3 - ntfsprogs


    I'm not sure what should be the right behavior there but be aware of it.






    share|improve this answer























    • I think so my usb is no useful furthermore please confirm :ntfsfix /dev/sdc1 Mounting volume... The disk contains an unclean file system (0, 0). FAILED Attempting to correct errors... Processing $MFT and $MFTMirr... Reading $MFT... OK Reading $MFTMirr... OK Comparing $MFTMirr to $MFT... OK Processing of $MFT and $MFTMirr completed successfully. Setting required flags on partition... OK Going to empty the journal ($LogFile)... OK Failed to sync device /dev/sdc1: Input/output error Checking the alternate boot sector... OK
      – Ashish Karpe
      Jan 22 at 7:07










    • NTFS volume version is 3.1. NTFS partition /dev/sdc1 was processed successfully. Failed to sync device /dev/sdc1: Input/output error Failed to unmount partition
      – Ashish Karpe
      Jan 22 at 7:08



















    0














    On ubuntu 14.04 package is not available as of Jan 2015




    1. sudo ln -s /bin/ntfsfix /sbin/fsck.ntfs

    2. sudo ln -s /bin/ntfsfix /sbin/fsck.ntfs-3g


    3. sudo apt-get install ntfsprogs



      Package ntfsprogs is not available, but is referred to by another package.
      This may mean that the package is missing, has been obsoleted, or
      is only available from another source
      E: Package 'ntfsprogs' has no installation candidate







    share|improve this answer































      0














      Try to force remapping of damaged sectors using this script:
      https://techoverflow.net/blog/2015/01/07/fixing-bad-blocks-on-hdds-using-fixhdd.py/



      mirror: https://github.com/unxed/fixhdd



      This script looks into system log for i/o errors every 5 seconds and writes zeroes to faulty sectors to force hdd controller to remap them.
      Usage sample:
      sudo fixhdd.py --loop /dev/sda






      share|improve this answer



















      • 1




        Welcome to Ask Ubuntu! Whilst this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference.
        – Kevin Bowen
        Jan 31 '17 at 16:47



















      -1














      $ man fsck



      fsck - check and repair a Linux filesystem




      To repair a broken NTFS system on GNU / Linux you could use ntfsfix which is part of ntfs-3g as following:



      $ ntfsfix /dev/sdc1





      share|improve this answer





















      • -1: This answer is unrelated to the question.
        – Scott Severance
        Mar 20 '16 at 2:54










      • @ScottSeverance /me being down voted for not ignoring the tools application as stated in their manual -- only in Ubuntu forums haha
        – sevaivanov
        Mar 21 '16 at 5:58










      • The question was about fsck.ntfs not being found at boot. Obviously, reporting the man page of irrelevant, since fsck wasn't being invoked manually. In addition, the situation wouldn't have arisen in the first place except for the fact that at one time fsck.ntfs did exist on a default Ubuntu install.
        – Scott Severance
        Mar 21 '16 at 11:39












      • @ScottSeverance Thanks for stating that your thread is outdated!
        – sevaivanov
        Mar 23 '16 at 20:33












      • It's quite possible that this question is outdated (though I can't be bothered to check so I can say for certain). However, that isn't the reason I down voted this answer. Even if it had been posted before my issue was solved, it doesn't even begin to address the question I asked. I asked about an error that appeared during boot and interrupted the boot process. The error indicated that the system was looking for fsck.ntfs, which didn't exist on the system. How exactly could an explanation of which tool is appropriate for fixing disk errors help me resolve my boot error?
        – Scott Severance
        Mar 23 '16 at 20:57











      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%2f86086%2ffsck-cant-find-fsck-ntfs%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      9 Answers
      9






      active

      oldest

      votes








      9 Answers
      9






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      36














      fsck.ntfs is usually only a link to ntfsfix which is an utility from the package ntfsprogs that is already available with a standard installation of Ubuntu.



      You can make a simbolic link between fsck.ntfs and ntfsfix to solve this permanently:



      sudo ln -s /usr/bin/ntfsfix /sbin/fsck.ntfs
      sudo ln -s /usr/bin/ntfsfix /sbin/fsck.ntfs-3g


      Keep in mind that this utility came from a reverse engineering process and are not the best option to manage your filesystem, the NTFS filesystem does not belong to the GNU/linux world.






      share|improve this answer

















      • 4




        Thanks. I set up the symlinks (which should have been made already) and the problem is solved. The only question that remains is: Why was the symlink missing in the first place? fsck apparently runs on boot. Therefore, it is a bug if it tries to check a filesystem that it can't handle. The partition was--and has been--perfectly fine. Apparently this was just a routine check that was failing.
        – Scott Severance
        Dec 8 '11 at 8:45






      • 1




        It is funny I trust a community reversed engineered tool a lot more than the official Microsoft tool which destroyed my perfectly working NTFS partitions before :)
        – AhHatem
        Jan 24 '13 at 14:37










      • Doesn't work to me. Ubuntu 12.04.3
        – zuba
        Dec 6 '13 at 14:08










      • You can count more on Linux-based tools to recover your Windows installation and data than the Windows-based tools. Also I experienced that Linux lets you do things such as putting question marks in your filenames; this is officially permitted by NTFS standards but here's the joke: the Windows driver doesn't support it! I would like to point at dedicated "Linux-based Rescue / Repair Live-CDs" (or USB) such as SystemRescueCD.
        – tiktak
        Jan 16 '14 at 0:35










      • The answer should be: askubuntu.com/a/292889/126984
        – wakeup
        Apr 8 '14 at 10:50
















      36














      fsck.ntfs is usually only a link to ntfsfix which is an utility from the package ntfsprogs that is already available with a standard installation of Ubuntu.



      You can make a simbolic link between fsck.ntfs and ntfsfix to solve this permanently:



      sudo ln -s /usr/bin/ntfsfix /sbin/fsck.ntfs
      sudo ln -s /usr/bin/ntfsfix /sbin/fsck.ntfs-3g


      Keep in mind that this utility came from a reverse engineering process and are not the best option to manage your filesystem, the NTFS filesystem does not belong to the GNU/linux world.






      share|improve this answer

















      • 4




        Thanks. I set up the symlinks (which should have been made already) and the problem is solved. The only question that remains is: Why was the symlink missing in the first place? fsck apparently runs on boot. Therefore, it is a bug if it tries to check a filesystem that it can't handle. The partition was--and has been--perfectly fine. Apparently this was just a routine check that was failing.
        – Scott Severance
        Dec 8 '11 at 8:45






      • 1




        It is funny I trust a community reversed engineered tool a lot more than the official Microsoft tool which destroyed my perfectly working NTFS partitions before :)
        – AhHatem
        Jan 24 '13 at 14:37










      • Doesn't work to me. Ubuntu 12.04.3
        – zuba
        Dec 6 '13 at 14:08










      • You can count more on Linux-based tools to recover your Windows installation and data than the Windows-based tools. Also I experienced that Linux lets you do things such as putting question marks in your filenames; this is officially permitted by NTFS standards but here's the joke: the Windows driver doesn't support it! I would like to point at dedicated "Linux-based Rescue / Repair Live-CDs" (or USB) such as SystemRescueCD.
        – tiktak
        Jan 16 '14 at 0:35










      • The answer should be: askubuntu.com/a/292889/126984
        – wakeup
        Apr 8 '14 at 10:50














      36












      36








      36






      fsck.ntfs is usually only a link to ntfsfix which is an utility from the package ntfsprogs that is already available with a standard installation of Ubuntu.



      You can make a simbolic link between fsck.ntfs and ntfsfix to solve this permanently:



      sudo ln -s /usr/bin/ntfsfix /sbin/fsck.ntfs
      sudo ln -s /usr/bin/ntfsfix /sbin/fsck.ntfs-3g


      Keep in mind that this utility came from a reverse engineering process and are not the best option to manage your filesystem, the NTFS filesystem does not belong to the GNU/linux world.






      share|improve this answer












      fsck.ntfs is usually only a link to ntfsfix which is an utility from the package ntfsprogs that is already available with a standard installation of Ubuntu.



      You can make a simbolic link between fsck.ntfs and ntfsfix to solve this permanently:



      sudo ln -s /usr/bin/ntfsfix /sbin/fsck.ntfs
      sudo ln -s /usr/bin/ntfsfix /sbin/fsck.ntfs-3g


      Keep in mind that this utility came from a reverse engineering process and are not the best option to manage your filesystem, the NTFS filesystem does not belong to the GNU/linux world.







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered Dec 8 '11 at 7:48









      Micro

      2,1021210




      2,1021210








      • 4




        Thanks. I set up the symlinks (which should have been made already) and the problem is solved. The only question that remains is: Why was the symlink missing in the first place? fsck apparently runs on boot. Therefore, it is a bug if it tries to check a filesystem that it can't handle. The partition was--and has been--perfectly fine. Apparently this was just a routine check that was failing.
        – Scott Severance
        Dec 8 '11 at 8:45






      • 1




        It is funny I trust a community reversed engineered tool a lot more than the official Microsoft tool which destroyed my perfectly working NTFS partitions before :)
        – AhHatem
        Jan 24 '13 at 14:37










      • Doesn't work to me. Ubuntu 12.04.3
        – zuba
        Dec 6 '13 at 14:08










      • You can count more on Linux-based tools to recover your Windows installation and data than the Windows-based tools. Also I experienced that Linux lets you do things such as putting question marks in your filenames; this is officially permitted by NTFS standards but here's the joke: the Windows driver doesn't support it! I would like to point at dedicated "Linux-based Rescue / Repair Live-CDs" (or USB) such as SystemRescueCD.
        – tiktak
        Jan 16 '14 at 0:35










      • The answer should be: askubuntu.com/a/292889/126984
        – wakeup
        Apr 8 '14 at 10:50














      • 4




        Thanks. I set up the symlinks (which should have been made already) and the problem is solved. The only question that remains is: Why was the symlink missing in the first place? fsck apparently runs on boot. Therefore, it is a bug if it tries to check a filesystem that it can't handle. The partition was--and has been--perfectly fine. Apparently this was just a routine check that was failing.
        – Scott Severance
        Dec 8 '11 at 8:45






      • 1




        It is funny I trust a community reversed engineered tool a lot more than the official Microsoft tool which destroyed my perfectly working NTFS partitions before :)
        – AhHatem
        Jan 24 '13 at 14:37










      • Doesn't work to me. Ubuntu 12.04.3
        – zuba
        Dec 6 '13 at 14:08










      • You can count more on Linux-based tools to recover your Windows installation and data than the Windows-based tools. Also I experienced that Linux lets you do things such as putting question marks in your filenames; this is officially permitted by NTFS standards but here's the joke: the Windows driver doesn't support it! I would like to point at dedicated "Linux-based Rescue / Repair Live-CDs" (or USB) such as SystemRescueCD.
        – tiktak
        Jan 16 '14 at 0:35










      • The answer should be: askubuntu.com/a/292889/126984
        – wakeup
        Apr 8 '14 at 10:50








      4




      4




      Thanks. I set up the symlinks (which should have been made already) and the problem is solved. The only question that remains is: Why was the symlink missing in the first place? fsck apparently runs on boot. Therefore, it is a bug if it tries to check a filesystem that it can't handle. The partition was--and has been--perfectly fine. Apparently this was just a routine check that was failing.
      – Scott Severance
      Dec 8 '11 at 8:45




      Thanks. I set up the symlinks (which should have been made already) and the problem is solved. The only question that remains is: Why was the symlink missing in the first place? fsck apparently runs on boot. Therefore, it is a bug if it tries to check a filesystem that it can't handle. The partition was--and has been--perfectly fine. Apparently this was just a routine check that was failing.
      – Scott Severance
      Dec 8 '11 at 8:45




      1




      1




      It is funny I trust a community reversed engineered tool a lot more than the official Microsoft tool which destroyed my perfectly working NTFS partitions before :)
      – AhHatem
      Jan 24 '13 at 14:37




      It is funny I trust a community reversed engineered tool a lot more than the official Microsoft tool which destroyed my perfectly working NTFS partitions before :)
      – AhHatem
      Jan 24 '13 at 14:37












      Doesn't work to me. Ubuntu 12.04.3
      – zuba
      Dec 6 '13 at 14:08




      Doesn't work to me. Ubuntu 12.04.3
      – zuba
      Dec 6 '13 at 14:08












      You can count more on Linux-based tools to recover your Windows installation and data than the Windows-based tools. Also I experienced that Linux lets you do things such as putting question marks in your filenames; this is officially permitted by NTFS standards but here's the joke: the Windows driver doesn't support it! I would like to point at dedicated "Linux-based Rescue / Repair Live-CDs" (or USB) such as SystemRescueCD.
      – tiktak
      Jan 16 '14 at 0:35




      You can count more on Linux-based tools to recover your Windows installation and data than the Windows-based tools. Also I experienced that Linux lets you do things such as putting question marks in your filenames; this is officially permitted by NTFS standards but here's the joke: the Windows driver doesn't support it! I would like to point at dedicated "Linux-based Rescue / Repair Live-CDs" (or USB) such as SystemRescueCD.
      – tiktak
      Jan 16 '14 at 0:35












      The answer should be: askubuntu.com/a/292889/126984
      – wakeup
      Apr 8 '14 at 10:50




      The answer should be: askubuntu.com/a/292889/126984
      – wakeup
      Apr 8 '14 at 10:50













      20














      I think it could be noted for some people that ntfsfix gets installed into /bin/ instead of /usr/bin. So



      sudo ln -nsf /bin/ntfsfix /sbin/fsck.ntfs
      sudo ln -nsf /bin/ntfsfix /sbin/fsck.ntfs-3g


      If you have already created the symlink from /usr/bin/



      sudo rm -f /sbin/fsck.ntfs
      sudo rm -f /sbin/fsck.ntfs-3g


      And then create the symlinks again.






      share|improve this answer























      • upvoted because a) downvoter left no comment explaining downvote, which would be courteous at least, and b) just had to 'locate ntfsfix' to find mine at /bin/ntfsfix, so it seems relevant at least.
        – A. L. Flanagan
        Jun 22 '13 at 12:32










      • I would suggest adding this as a comment to Micro's answer, rather than as a standalone answer.
        – waldyrious
        Dec 3 '13 at 19:43










      • This is the correct answer for later versions of ubuntu like 13.04
        – wakeup
        Apr 8 '14 at 10:50










      • This worked for me in Ubuntu 14.04!
        – HarlemSquirrel
        Nov 17 '14 at 14:21
















      20














      I think it could be noted for some people that ntfsfix gets installed into /bin/ instead of /usr/bin. So



      sudo ln -nsf /bin/ntfsfix /sbin/fsck.ntfs
      sudo ln -nsf /bin/ntfsfix /sbin/fsck.ntfs-3g


      If you have already created the symlink from /usr/bin/



      sudo rm -f /sbin/fsck.ntfs
      sudo rm -f /sbin/fsck.ntfs-3g


      And then create the symlinks again.






      share|improve this answer























      • upvoted because a) downvoter left no comment explaining downvote, which would be courteous at least, and b) just had to 'locate ntfsfix' to find mine at /bin/ntfsfix, so it seems relevant at least.
        – A. L. Flanagan
        Jun 22 '13 at 12:32










      • I would suggest adding this as a comment to Micro's answer, rather than as a standalone answer.
        – waldyrious
        Dec 3 '13 at 19:43










      • This is the correct answer for later versions of ubuntu like 13.04
        – wakeup
        Apr 8 '14 at 10:50










      • This worked for me in Ubuntu 14.04!
        – HarlemSquirrel
        Nov 17 '14 at 14:21














      20












      20








      20






      I think it could be noted for some people that ntfsfix gets installed into /bin/ instead of /usr/bin. So



      sudo ln -nsf /bin/ntfsfix /sbin/fsck.ntfs
      sudo ln -nsf /bin/ntfsfix /sbin/fsck.ntfs-3g


      If you have already created the symlink from /usr/bin/



      sudo rm -f /sbin/fsck.ntfs
      sudo rm -f /sbin/fsck.ntfs-3g


      And then create the symlinks again.






      share|improve this answer














      I think it could be noted for some people that ntfsfix gets installed into /bin/ instead of /usr/bin. So



      sudo ln -nsf /bin/ntfsfix /sbin/fsck.ntfs
      sudo ln -nsf /bin/ntfsfix /sbin/fsck.ntfs-3g


      If you have already created the symlink from /usr/bin/



      sudo rm -f /sbin/fsck.ntfs
      sudo rm -f /sbin/fsck.ntfs-3g


      And then create the symlinks again.







      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited Oct 2 '15 at 9:51









      evandrix

      11115




      11115










      answered May 9 '13 at 6:01









      Ruraj

      70278




      70278












      • upvoted because a) downvoter left no comment explaining downvote, which would be courteous at least, and b) just had to 'locate ntfsfix' to find mine at /bin/ntfsfix, so it seems relevant at least.
        – A. L. Flanagan
        Jun 22 '13 at 12:32










      • I would suggest adding this as a comment to Micro's answer, rather than as a standalone answer.
        – waldyrious
        Dec 3 '13 at 19:43










      • This is the correct answer for later versions of ubuntu like 13.04
        – wakeup
        Apr 8 '14 at 10:50










      • This worked for me in Ubuntu 14.04!
        – HarlemSquirrel
        Nov 17 '14 at 14:21


















      • upvoted because a) downvoter left no comment explaining downvote, which would be courteous at least, and b) just had to 'locate ntfsfix' to find mine at /bin/ntfsfix, so it seems relevant at least.
        – A. L. Flanagan
        Jun 22 '13 at 12:32










      • I would suggest adding this as a comment to Micro's answer, rather than as a standalone answer.
        – waldyrious
        Dec 3 '13 at 19:43










      • This is the correct answer for later versions of ubuntu like 13.04
        – wakeup
        Apr 8 '14 at 10:50










      • This worked for me in Ubuntu 14.04!
        – HarlemSquirrel
        Nov 17 '14 at 14:21
















      upvoted because a) downvoter left no comment explaining downvote, which would be courteous at least, and b) just had to 'locate ntfsfix' to find mine at /bin/ntfsfix, so it seems relevant at least.
      – A. L. Flanagan
      Jun 22 '13 at 12:32




      upvoted because a) downvoter left no comment explaining downvote, which would be courteous at least, and b) just had to 'locate ntfsfix' to find mine at /bin/ntfsfix, so it seems relevant at least.
      – A. L. Flanagan
      Jun 22 '13 at 12:32












      I would suggest adding this as a comment to Micro's answer, rather than as a standalone answer.
      – waldyrious
      Dec 3 '13 at 19:43




      I would suggest adding this as a comment to Micro's answer, rather than as a standalone answer.
      – waldyrious
      Dec 3 '13 at 19:43












      This is the correct answer for later versions of ubuntu like 13.04
      – wakeup
      Apr 8 '14 at 10:50




      This is the correct answer for later versions of ubuntu like 13.04
      – wakeup
      Apr 8 '14 at 10:50












      This worked for me in Ubuntu 14.04!
      – HarlemSquirrel
      Nov 17 '14 at 14:21




      This worked for me in Ubuntu 14.04!
      – HarlemSquirrel
      Nov 17 '14 at 14:21











      5














      If you have an NTFS partition automatically mounted at startup, the only reason could be you have manually or through some tool added it to /etc/fstab (not taking into account WUBI).



      If the system tries to check the partition at startup it means that in the corresponding line in /etc/fstab there is a sixth field and its value is 1 or 2.



      ntfsfix is not linked by default to fsck.ntfs, and it only provides limited check capabilities, as explained in the man page:




      ntfsfix is a utility that fixes some common NTFS problems. ntfsfix is
      NOT a Linux version of chkdsk. It only repairs some fundamental NTFS
      inconsistencies, resets the NTFS journal file and schedules an NTFS
      consistency check for the first boot into Windows.




      The common solution is not to create the symlink, but to remove or set to 0 the sixth field in /etc/fstab.






      share|improve this answer



















      • 2




        Actually, that's not exactly accurate. During installation, existing NTFS partitions get automatically added to fstab without any manual editing of fstab. So, they should get added in a sane way. I don't care whether they get checked or not. I just don't want unnecessary errors messages showing up at boot when in reality there is no error.
        – Scott Severance
        Dec 8 '11 at 21:57












      • Never seen this behavior in older Ubuntu releases, when I had ntfs partitions. I suppose is a new features, now that I do not use ntfs anymore. Btw, you did not say if there was the non-zero number in fstab.
        – enzotib
        Dec 8 '11 at 22:02












      • This might explain the problem: On the machine in question, there is indeed a nonzero number in fstab. On another machine, I formerly had this same problem, but it went away after I did a reinstall to solve a different issue. The new fstab has the sixth field set to zero. So, apparently the defaults changed between Natty and Oneiric and the upgrade didn't make any conversions.
        – Scott Severance
        Dec 8 '11 at 22:59






      • 1




        Me thinks that the "pass" argument is just in what order the partitions should be auto mounted, so this seems to be new in Oneiric. I just upgraded recently and I have had pass=3 set on my ntfs partitions, and I never had any problem until the first boot in oneiric. It got stuck on some stupid promt hidden among some irrelevant error messages. Not cool for a server to wait for a keypress during boot.
        – KarlP
        Dec 12 '11 at 21:04


















      5














      If you have an NTFS partition automatically mounted at startup, the only reason could be you have manually or through some tool added it to /etc/fstab (not taking into account WUBI).



      If the system tries to check the partition at startup it means that in the corresponding line in /etc/fstab there is a sixth field and its value is 1 or 2.



      ntfsfix is not linked by default to fsck.ntfs, and it only provides limited check capabilities, as explained in the man page:




      ntfsfix is a utility that fixes some common NTFS problems. ntfsfix is
      NOT a Linux version of chkdsk. It only repairs some fundamental NTFS
      inconsistencies, resets the NTFS journal file and schedules an NTFS
      consistency check for the first boot into Windows.




      The common solution is not to create the symlink, but to remove or set to 0 the sixth field in /etc/fstab.






      share|improve this answer



















      • 2




        Actually, that's not exactly accurate. During installation, existing NTFS partitions get automatically added to fstab without any manual editing of fstab. So, they should get added in a sane way. I don't care whether they get checked or not. I just don't want unnecessary errors messages showing up at boot when in reality there is no error.
        – Scott Severance
        Dec 8 '11 at 21:57












      • Never seen this behavior in older Ubuntu releases, when I had ntfs partitions. I suppose is a new features, now that I do not use ntfs anymore. Btw, you did not say if there was the non-zero number in fstab.
        – enzotib
        Dec 8 '11 at 22:02












      • This might explain the problem: On the machine in question, there is indeed a nonzero number in fstab. On another machine, I formerly had this same problem, but it went away after I did a reinstall to solve a different issue. The new fstab has the sixth field set to zero. So, apparently the defaults changed between Natty and Oneiric and the upgrade didn't make any conversions.
        – Scott Severance
        Dec 8 '11 at 22:59






      • 1




        Me thinks that the "pass" argument is just in what order the partitions should be auto mounted, so this seems to be new in Oneiric. I just upgraded recently and I have had pass=3 set on my ntfs partitions, and I never had any problem until the first boot in oneiric. It got stuck on some stupid promt hidden among some irrelevant error messages. Not cool for a server to wait for a keypress during boot.
        – KarlP
        Dec 12 '11 at 21:04
















      5












      5








      5






      If you have an NTFS partition automatically mounted at startup, the only reason could be you have manually or through some tool added it to /etc/fstab (not taking into account WUBI).



      If the system tries to check the partition at startup it means that in the corresponding line in /etc/fstab there is a sixth field and its value is 1 or 2.



      ntfsfix is not linked by default to fsck.ntfs, and it only provides limited check capabilities, as explained in the man page:




      ntfsfix is a utility that fixes some common NTFS problems. ntfsfix is
      NOT a Linux version of chkdsk. It only repairs some fundamental NTFS
      inconsistencies, resets the NTFS journal file and schedules an NTFS
      consistency check for the first boot into Windows.




      The common solution is not to create the symlink, but to remove or set to 0 the sixth field in /etc/fstab.






      share|improve this answer














      If you have an NTFS partition automatically mounted at startup, the only reason could be you have manually or through some tool added it to /etc/fstab (not taking into account WUBI).



      If the system tries to check the partition at startup it means that in the corresponding line in /etc/fstab there is a sixth field and its value is 1 or 2.



      ntfsfix is not linked by default to fsck.ntfs, and it only provides limited check capabilities, as explained in the man page:




      ntfsfix is a utility that fixes some common NTFS problems. ntfsfix is
      NOT a Linux version of chkdsk. It only repairs some fundamental NTFS
      inconsistencies, resets the NTFS journal file and schedules an NTFS
      consistency check for the first boot into Windows.




      The common solution is not to create the symlink, but to remove or set to 0 the sixth field in /etc/fstab.







      share|improve this answer














      share|improve this answer



      share|improve this answer








      edited Jan 26 '12 at 3:23









      Scott Severance

      10.3k73468




      10.3k73468










      answered Dec 8 '11 at 14:12









      enzotib

      62.5k6132154




      62.5k6132154








      • 2




        Actually, that's not exactly accurate. During installation, existing NTFS partitions get automatically added to fstab without any manual editing of fstab. So, they should get added in a sane way. I don't care whether they get checked or not. I just don't want unnecessary errors messages showing up at boot when in reality there is no error.
        – Scott Severance
        Dec 8 '11 at 21:57












      • Never seen this behavior in older Ubuntu releases, when I had ntfs partitions. I suppose is a new features, now that I do not use ntfs anymore. Btw, you did not say if there was the non-zero number in fstab.
        – enzotib
        Dec 8 '11 at 22:02












      • This might explain the problem: On the machine in question, there is indeed a nonzero number in fstab. On another machine, I formerly had this same problem, but it went away after I did a reinstall to solve a different issue. The new fstab has the sixth field set to zero. So, apparently the defaults changed between Natty and Oneiric and the upgrade didn't make any conversions.
        – Scott Severance
        Dec 8 '11 at 22:59






      • 1




        Me thinks that the "pass" argument is just in what order the partitions should be auto mounted, so this seems to be new in Oneiric. I just upgraded recently and I have had pass=3 set on my ntfs partitions, and I never had any problem until the first boot in oneiric. It got stuck on some stupid promt hidden among some irrelevant error messages. Not cool for a server to wait for a keypress during boot.
        – KarlP
        Dec 12 '11 at 21:04
















      • 2




        Actually, that's not exactly accurate. During installation, existing NTFS partitions get automatically added to fstab without any manual editing of fstab. So, they should get added in a sane way. I don't care whether they get checked or not. I just don't want unnecessary errors messages showing up at boot when in reality there is no error.
        – Scott Severance
        Dec 8 '11 at 21:57












      • Never seen this behavior in older Ubuntu releases, when I had ntfs partitions. I suppose is a new features, now that I do not use ntfs anymore. Btw, you did not say if there was the non-zero number in fstab.
        – enzotib
        Dec 8 '11 at 22:02












      • This might explain the problem: On the machine in question, there is indeed a nonzero number in fstab. On another machine, I formerly had this same problem, but it went away after I did a reinstall to solve a different issue. The new fstab has the sixth field set to zero. So, apparently the defaults changed between Natty and Oneiric and the upgrade didn't make any conversions.
        – Scott Severance
        Dec 8 '11 at 22:59






      • 1




        Me thinks that the "pass" argument is just in what order the partitions should be auto mounted, so this seems to be new in Oneiric. I just upgraded recently and I have had pass=3 set on my ntfs partitions, and I never had any problem until the first boot in oneiric. It got stuck on some stupid promt hidden among some irrelevant error messages. Not cool for a server to wait for a keypress during boot.
        – KarlP
        Dec 12 '11 at 21:04










      2




      2




      Actually, that's not exactly accurate. During installation, existing NTFS partitions get automatically added to fstab without any manual editing of fstab. So, they should get added in a sane way. I don't care whether they get checked or not. I just don't want unnecessary errors messages showing up at boot when in reality there is no error.
      – Scott Severance
      Dec 8 '11 at 21:57






      Actually, that's not exactly accurate. During installation, existing NTFS partitions get automatically added to fstab without any manual editing of fstab. So, they should get added in a sane way. I don't care whether they get checked or not. I just don't want unnecessary errors messages showing up at boot when in reality there is no error.
      – Scott Severance
      Dec 8 '11 at 21:57














      Never seen this behavior in older Ubuntu releases, when I had ntfs partitions. I suppose is a new features, now that I do not use ntfs anymore. Btw, you did not say if there was the non-zero number in fstab.
      – enzotib
      Dec 8 '11 at 22:02






      Never seen this behavior in older Ubuntu releases, when I had ntfs partitions. I suppose is a new features, now that I do not use ntfs anymore. Btw, you did not say if there was the non-zero number in fstab.
      – enzotib
      Dec 8 '11 at 22:02














      This might explain the problem: On the machine in question, there is indeed a nonzero number in fstab. On another machine, I formerly had this same problem, but it went away after I did a reinstall to solve a different issue. The new fstab has the sixth field set to zero. So, apparently the defaults changed between Natty and Oneiric and the upgrade didn't make any conversions.
      – Scott Severance
      Dec 8 '11 at 22:59




      This might explain the problem: On the machine in question, there is indeed a nonzero number in fstab. On another machine, I formerly had this same problem, but it went away after I did a reinstall to solve a different issue. The new fstab has the sixth field set to zero. So, apparently the defaults changed between Natty and Oneiric and the upgrade didn't make any conversions.
      – Scott Severance
      Dec 8 '11 at 22:59




      1




      1




      Me thinks that the "pass" argument is just in what order the partitions should be auto mounted, so this seems to be new in Oneiric. I just upgraded recently and I have had pass=3 set on my ntfs partitions, and I never had any problem until the first boot in oneiric. It got stuck on some stupid promt hidden among some irrelevant error messages. Not cool for a server to wait for a keypress during boot.
      – KarlP
      Dec 12 '11 at 21:04






      Me thinks that the "pass" argument is just in what order the partitions should be auto mounted, so this seems to be new in Oneiric. I just upgraded recently and I have had pass=3 set on my ntfs partitions, and I never had any problem until the first boot in oneiric. It got stuck on some stupid promt hidden among some irrelevant error messages. Not cool for a server to wait for a keypress during boot.
      – KarlP
      Dec 12 '11 at 21:04













      5














      Micro's answer worked for me, however my 11.10 (upgraded from 11.04) did not have ntfsprogs. 'sudo apt-get install ntfsprogs' solved that, then the link suggestion worked fine.






      share|improve this answer




























        5














        Micro's answer worked for me, however my 11.10 (upgraded from 11.04) did not have ntfsprogs. 'sudo apt-get install ntfsprogs' solved that, then the link suggestion worked fine.






        share|improve this answer


























          5












          5








          5






          Micro's answer worked for me, however my 11.10 (upgraded from 11.04) did not have ntfsprogs. 'sudo apt-get install ntfsprogs' solved that, then the link suggestion worked fine.






          share|improve this answer














          Micro's answer worked for me, however my 11.10 (upgraded from 11.04) did not have ntfsprogs. 'sudo apt-get install ntfsprogs' solved that, then the link suggestion worked fine.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Apr 13 '17 at 12:24









          Community

          1




          1










          answered Jan 25 '12 at 18:17









          RobDavenport

          37116




          37116























              3














              The problem is a missing symbolic link, to either /usr/bin/ntfsfix or /bin/ntfsfix. You can make the needed link(s) with:



              sudo ln -s $(which ntfsfix) /sbin/fsck.ntfs
              sudo ln -s $(which ntfsfix) /sbin/fsck.ntfs-3





              share|improve this answer





















              • This worked for me on Ubuntu 14.04 LTS on April 13th, 2015
                – HarlemSquirrel
                Apr 13 '15 at 17:10
















              3














              The problem is a missing symbolic link, to either /usr/bin/ntfsfix or /bin/ntfsfix. You can make the needed link(s) with:



              sudo ln -s $(which ntfsfix) /sbin/fsck.ntfs
              sudo ln -s $(which ntfsfix) /sbin/fsck.ntfs-3





              share|improve this answer





















              • This worked for me on Ubuntu 14.04 LTS on April 13th, 2015
                – HarlemSquirrel
                Apr 13 '15 at 17:10














              3












              3








              3






              The problem is a missing symbolic link, to either /usr/bin/ntfsfix or /bin/ntfsfix. You can make the needed link(s) with:



              sudo ln -s $(which ntfsfix) /sbin/fsck.ntfs
              sudo ln -s $(which ntfsfix) /sbin/fsck.ntfs-3





              share|improve this answer












              The problem is a missing symbolic link, to either /usr/bin/ntfsfix or /bin/ntfsfix. You can make the needed link(s) with:



              sudo ln -s $(which ntfsfix) /sbin/fsck.ntfs
              sudo ln -s $(which ntfsfix) /sbin/fsck.ntfs-3






              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Mar 16 '15 at 15:42









              Wes

              564




              564












              • This worked for me on Ubuntu 14.04 LTS on April 13th, 2015
                – HarlemSquirrel
                Apr 13 '15 at 17:10


















              • This worked for me on Ubuntu 14.04 LTS on April 13th, 2015
                – HarlemSquirrel
                Apr 13 '15 at 17:10
















              This worked for me on Ubuntu 14.04 LTS on April 13th, 2015
              – HarlemSquirrel
              Apr 13 '15 at 17:10




              This worked for me on Ubuntu 14.04 LTS on April 13th, 2015
              – HarlemSquirrel
              Apr 13 '15 at 17:10











              1














              I have the same problem after I accidentally installed ntfsprogs. I think there is bug in dependencies because after installation of ntfsprogs all NTFS drives started mounting read-only.



              When I turned back ntfs-3g, fsck.ntfs disappeared.



              SO:



              sudo apt-get install ntfsprogs
              Reading package lists... Done
              Building dependency tree
              Reading state information... Done
              The following packages will be REMOVED:
              ntfs-3g
              The following NEW packages will be installed:
              ntfsprogs
              0 upgraded, 1 newly installed, 1 to remove and 0 not upgraded.


              BUT:



              apt-cache showpkg ntfs-3g
              Package: ntfs-3g
              Versions:
              1:2011.4.12AR.4-2ubuntu3 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_oneiric_main_binary-amd64_Packages) (/var/lib/dpkg/status)
              ...
              Provides:
              1:2011.4.12AR.4-2ubuntu3 - ntfsprogs


              I'm not sure what should be the right behavior there but be aware of it.






              share|improve this answer























              • I think so my usb is no useful furthermore please confirm :ntfsfix /dev/sdc1 Mounting volume... The disk contains an unclean file system (0, 0). FAILED Attempting to correct errors... Processing $MFT and $MFTMirr... Reading $MFT... OK Reading $MFTMirr... OK Comparing $MFTMirr to $MFT... OK Processing of $MFT and $MFTMirr completed successfully. Setting required flags on partition... OK Going to empty the journal ($LogFile)... OK Failed to sync device /dev/sdc1: Input/output error Checking the alternate boot sector... OK
                – Ashish Karpe
                Jan 22 at 7:07










              • NTFS volume version is 3.1. NTFS partition /dev/sdc1 was processed successfully. Failed to sync device /dev/sdc1: Input/output error Failed to unmount partition
                – Ashish Karpe
                Jan 22 at 7:08
















              1














              I have the same problem after I accidentally installed ntfsprogs. I think there is bug in dependencies because after installation of ntfsprogs all NTFS drives started mounting read-only.



              When I turned back ntfs-3g, fsck.ntfs disappeared.



              SO:



              sudo apt-get install ntfsprogs
              Reading package lists... Done
              Building dependency tree
              Reading state information... Done
              The following packages will be REMOVED:
              ntfs-3g
              The following NEW packages will be installed:
              ntfsprogs
              0 upgraded, 1 newly installed, 1 to remove and 0 not upgraded.


              BUT:



              apt-cache showpkg ntfs-3g
              Package: ntfs-3g
              Versions:
              1:2011.4.12AR.4-2ubuntu3 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_oneiric_main_binary-amd64_Packages) (/var/lib/dpkg/status)
              ...
              Provides:
              1:2011.4.12AR.4-2ubuntu3 - ntfsprogs


              I'm not sure what should be the right behavior there but be aware of it.






              share|improve this answer























              • I think so my usb is no useful furthermore please confirm :ntfsfix /dev/sdc1 Mounting volume... The disk contains an unclean file system (0, 0). FAILED Attempting to correct errors... Processing $MFT and $MFTMirr... Reading $MFT... OK Reading $MFTMirr... OK Comparing $MFTMirr to $MFT... OK Processing of $MFT and $MFTMirr completed successfully. Setting required flags on partition... OK Going to empty the journal ($LogFile)... OK Failed to sync device /dev/sdc1: Input/output error Checking the alternate boot sector... OK
                – Ashish Karpe
                Jan 22 at 7:07










              • NTFS volume version is 3.1. NTFS partition /dev/sdc1 was processed successfully. Failed to sync device /dev/sdc1: Input/output error Failed to unmount partition
                – Ashish Karpe
                Jan 22 at 7:08














              1












              1








              1






              I have the same problem after I accidentally installed ntfsprogs. I think there is bug in dependencies because after installation of ntfsprogs all NTFS drives started mounting read-only.



              When I turned back ntfs-3g, fsck.ntfs disappeared.



              SO:



              sudo apt-get install ntfsprogs
              Reading package lists... Done
              Building dependency tree
              Reading state information... Done
              The following packages will be REMOVED:
              ntfs-3g
              The following NEW packages will be installed:
              ntfsprogs
              0 upgraded, 1 newly installed, 1 to remove and 0 not upgraded.


              BUT:



              apt-cache showpkg ntfs-3g
              Package: ntfs-3g
              Versions:
              1:2011.4.12AR.4-2ubuntu3 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_oneiric_main_binary-amd64_Packages) (/var/lib/dpkg/status)
              ...
              Provides:
              1:2011.4.12AR.4-2ubuntu3 - ntfsprogs


              I'm not sure what should be the right behavior there but be aware of it.






              share|improve this answer














              I have the same problem after I accidentally installed ntfsprogs. I think there is bug in dependencies because after installation of ntfsprogs all NTFS drives started mounting read-only.



              When I turned back ntfs-3g, fsck.ntfs disappeared.



              SO:



              sudo apt-get install ntfsprogs
              Reading package lists... Done
              Building dependency tree
              Reading state information... Done
              The following packages will be REMOVED:
              ntfs-3g
              The following NEW packages will be installed:
              ntfsprogs
              0 upgraded, 1 newly installed, 1 to remove and 0 not upgraded.


              BUT:



              apt-cache showpkg ntfs-3g
              Package: ntfs-3g
              Versions:
              1:2011.4.12AR.4-2ubuntu3 (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_oneiric_main_binary-amd64_Packages) (/var/lib/dpkg/status)
              ...
              Provides:
              1:2011.4.12AR.4-2ubuntu3 - ntfsprogs


              I'm not sure what should be the right behavior there but be aware of it.







              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Jan 15 '12 at 3:13









              Scott Severance

              10.3k73468




              10.3k73468










              answered Jan 14 '12 at 15:14









              Vlalex

              111




              111












              • I think so my usb is no useful furthermore please confirm :ntfsfix /dev/sdc1 Mounting volume... The disk contains an unclean file system (0, 0). FAILED Attempting to correct errors... Processing $MFT and $MFTMirr... Reading $MFT... OK Reading $MFTMirr... OK Comparing $MFTMirr to $MFT... OK Processing of $MFT and $MFTMirr completed successfully. Setting required flags on partition... OK Going to empty the journal ($LogFile)... OK Failed to sync device /dev/sdc1: Input/output error Checking the alternate boot sector... OK
                – Ashish Karpe
                Jan 22 at 7:07










              • NTFS volume version is 3.1. NTFS partition /dev/sdc1 was processed successfully. Failed to sync device /dev/sdc1: Input/output error Failed to unmount partition
                – Ashish Karpe
                Jan 22 at 7:08


















              • I think so my usb is no useful furthermore please confirm :ntfsfix /dev/sdc1 Mounting volume... The disk contains an unclean file system (0, 0). FAILED Attempting to correct errors... Processing $MFT and $MFTMirr... Reading $MFT... OK Reading $MFTMirr... OK Comparing $MFTMirr to $MFT... OK Processing of $MFT and $MFTMirr completed successfully. Setting required flags on partition... OK Going to empty the journal ($LogFile)... OK Failed to sync device /dev/sdc1: Input/output error Checking the alternate boot sector... OK
                – Ashish Karpe
                Jan 22 at 7:07










              • NTFS volume version is 3.1. NTFS partition /dev/sdc1 was processed successfully. Failed to sync device /dev/sdc1: Input/output error Failed to unmount partition
                – Ashish Karpe
                Jan 22 at 7:08
















              I think so my usb is no useful furthermore please confirm :ntfsfix /dev/sdc1 Mounting volume... The disk contains an unclean file system (0, 0). FAILED Attempting to correct errors... Processing $MFT and $MFTMirr... Reading $MFT... OK Reading $MFTMirr... OK Comparing $MFTMirr to $MFT... OK Processing of $MFT and $MFTMirr completed successfully. Setting required flags on partition... OK Going to empty the journal ($LogFile)... OK Failed to sync device /dev/sdc1: Input/output error Checking the alternate boot sector... OK
              – Ashish Karpe
              Jan 22 at 7:07




              I think so my usb is no useful furthermore please confirm :ntfsfix /dev/sdc1 Mounting volume... The disk contains an unclean file system (0, 0). FAILED Attempting to correct errors... Processing $MFT and $MFTMirr... Reading $MFT... OK Reading $MFTMirr... OK Comparing $MFTMirr to $MFT... OK Processing of $MFT and $MFTMirr completed successfully. Setting required flags on partition... OK Going to empty the journal ($LogFile)... OK Failed to sync device /dev/sdc1: Input/output error Checking the alternate boot sector... OK
              – Ashish Karpe
              Jan 22 at 7:07












              NTFS volume version is 3.1. NTFS partition /dev/sdc1 was processed successfully. Failed to sync device /dev/sdc1: Input/output error Failed to unmount partition
              – Ashish Karpe
              Jan 22 at 7:08




              NTFS volume version is 3.1. NTFS partition /dev/sdc1 was processed successfully. Failed to sync device /dev/sdc1: Input/output error Failed to unmount partition
              – Ashish Karpe
              Jan 22 at 7:08











              0














              On ubuntu 14.04 package is not available as of Jan 2015




              1. sudo ln -s /bin/ntfsfix /sbin/fsck.ntfs

              2. sudo ln -s /bin/ntfsfix /sbin/fsck.ntfs-3g


              3. sudo apt-get install ntfsprogs



                Package ntfsprogs is not available, but is referred to by another package.
                This may mean that the package is missing, has been obsoleted, or
                is only available from another source
                E: Package 'ntfsprogs' has no installation candidate







              share|improve this answer




























                0














                On ubuntu 14.04 package is not available as of Jan 2015




                1. sudo ln -s /bin/ntfsfix /sbin/fsck.ntfs

                2. sudo ln -s /bin/ntfsfix /sbin/fsck.ntfs-3g


                3. sudo apt-get install ntfsprogs



                  Package ntfsprogs is not available, but is referred to by another package.
                  This may mean that the package is missing, has been obsoleted, or
                  is only available from another source
                  E: Package 'ntfsprogs' has no installation candidate







                share|improve this answer


























                  0












                  0








                  0






                  On ubuntu 14.04 package is not available as of Jan 2015




                  1. sudo ln -s /bin/ntfsfix /sbin/fsck.ntfs

                  2. sudo ln -s /bin/ntfsfix /sbin/fsck.ntfs-3g


                  3. sudo apt-get install ntfsprogs



                    Package ntfsprogs is not available, but is referred to by another package.
                    This may mean that the package is missing, has been obsoleted, or
                    is only available from another source
                    E: Package 'ntfsprogs' has no installation candidate







                  share|improve this answer














                  On ubuntu 14.04 package is not available as of Jan 2015




                  1. sudo ln -s /bin/ntfsfix /sbin/fsck.ntfs

                  2. sudo ln -s /bin/ntfsfix /sbin/fsck.ntfs-3g


                  3. sudo apt-get install ntfsprogs



                    Package ntfsprogs is not available, but is referred to by another package.
                    This may mean that the package is missing, has been obsoleted, or
                    is only available from another source
                    E: Package 'ntfsprogs' has no installation candidate








                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Jan 14 '15 at 8:24









                  αғsнιη

                  24.2k2295156




                  24.2k2295156










                  answered Jan 13 '15 at 20:22









                  unixcreeper

                  12




                  12























                      0














                      Try to force remapping of damaged sectors using this script:
                      https://techoverflow.net/blog/2015/01/07/fixing-bad-blocks-on-hdds-using-fixhdd.py/



                      mirror: https://github.com/unxed/fixhdd



                      This script looks into system log for i/o errors every 5 seconds and writes zeroes to faulty sectors to force hdd controller to remap them.
                      Usage sample:
                      sudo fixhdd.py --loop /dev/sda






                      share|improve this answer



















                      • 1




                        Welcome to Ask Ubuntu! Whilst this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference.
                        – Kevin Bowen
                        Jan 31 '17 at 16:47
















                      0














                      Try to force remapping of damaged sectors using this script:
                      https://techoverflow.net/blog/2015/01/07/fixing-bad-blocks-on-hdds-using-fixhdd.py/



                      mirror: https://github.com/unxed/fixhdd



                      This script looks into system log for i/o errors every 5 seconds and writes zeroes to faulty sectors to force hdd controller to remap them.
                      Usage sample:
                      sudo fixhdd.py --loop /dev/sda






                      share|improve this answer



















                      • 1




                        Welcome to Ask Ubuntu! Whilst this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference.
                        – Kevin Bowen
                        Jan 31 '17 at 16:47














                      0












                      0








                      0






                      Try to force remapping of damaged sectors using this script:
                      https://techoverflow.net/blog/2015/01/07/fixing-bad-blocks-on-hdds-using-fixhdd.py/



                      mirror: https://github.com/unxed/fixhdd



                      This script looks into system log for i/o errors every 5 seconds and writes zeroes to faulty sectors to force hdd controller to remap them.
                      Usage sample:
                      sudo fixhdd.py --loop /dev/sda






                      share|improve this answer














                      Try to force remapping of damaged sectors using this script:
                      https://techoverflow.net/blog/2015/01/07/fixing-bad-blocks-on-hdds-using-fixhdd.py/



                      mirror: https://github.com/unxed/fixhdd



                      This script looks into system log for i/o errors every 5 seconds and writes zeroes to faulty sectors to force hdd controller to remap them.
                      Usage sample:
                      sudo fixhdd.py --loop /dev/sda







                      share|improve this answer














                      share|improve this answer



                      share|improve this answer








                      edited Feb 1 '17 at 10:39

























                      answered Jan 31 '17 at 16:28









                      user191894

                      11




                      11








                      • 1




                        Welcome to Ask Ubuntu! Whilst this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference.
                        – Kevin Bowen
                        Jan 31 '17 at 16:47














                      • 1




                        Welcome to Ask Ubuntu! Whilst this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference.
                        – Kevin Bowen
                        Jan 31 '17 at 16:47








                      1




                      1




                      Welcome to Ask Ubuntu! Whilst this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference.
                      – Kevin Bowen
                      Jan 31 '17 at 16:47




                      Welcome to Ask Ubuntu! Whilst this may theoretically answer the question, it would be preferable to include the essential parts of the answer here, and provide the link for reference.
                      – Kevin Bowen
                      Jan 31 '17 at 16:47











                      -1














                      $ man fsck



                      fsck - check and repair a Linux filesystem




                      To repair a broken NTFS system on GNU / Linux you could use ntfsfix which is part of ntfs-3g as following:



                      $ ntfsfix /dev/sdc1





                      share|improve this answer





















                      • -1: This answer is unrelated to the question.
                        – Scott Severance
                        Mar 20 '16 at 2:54










                      • @ScottSeverance /me being down voted for not ignoring the tools application as stated in their manual -- only in Ubuntu forums haha
                        – sevaivanov
                        Mar 21 '16 at 5:58










                      • The question was about fsck.ntfs not being found at boot. Obviously, reporting the man page of irrelevant, since fsck wasn't being invoked manually. In addition, the situation wouldn't have arisen in the first place except for the fact that at one time fsck.ntfs did exist on a default Ubuntu install.
                        – Scott Severance
                        Mar 21 '16 at 11:39












                      • @ScottSeverance Thanks for stating that your thread is outdated!
                        – sevaivanov
                        Mar 23 '16 at 20:33












                      • It's quite possible that this question is outdated (though I can't be bothered to check so I can say for certain). However, that isn't the reason I down voted this answer. Even if it had been posted before my issue was solved, it doesn't even begin to address the question I asked. I asked about an error that appeared during boot and interrupted the boot process. The error indicated that the system was looking for fsck.ntfs, which didn't exist on the system. How exactly could an explanation of which tool is appropriate for fixing disk errors help me resolve my boot error?
                        – Scott Severance
                        Mar 23 '16 at 20:57
















                      -1














                      $ man fsck



                      fsck - check and repair a Linux filesystem




                      To repair a broken NTFS system on GNU / Linux you could use ntfsfix which is part of ntfs-3g as following:



                      $ ntfsfix /dev/sdc1





                      share|improve this answer





















                      • -1: This answer is unrelated to the question.
                        – Scott Severance
                        Mar 20 '16 at 2:54










                      • @ScottSeverance /me being down voted for not ignoring the tools application as stated in their manual -- only in Ubuntu forums haha
                        – sevaivanov
                        Mar 21 '16 at 5:58










                      • The question was about fsck.ntfs not being found at boot. Obviously, reporting the man page of irrelevant, since fsck wasn't being invoked manually. In addition, the situation wouldn't have arisen in the first place except for the fact that at one time fsck.ntfs did exist on a default Ubuntu install.
                        – Scott Severance
                        Mar 21 '16 at 11:39












                      • @ScottSeverance Thanks for stating that your thread is outdated!
                        – sevaivanov
                        Mar 23 '16 at 20:33












                      • It's quite possible that this question is outdated (though I can't be bothered to check so I can say for certain). However, that isn't the reason I down voted this answer. Even if it had been posted before my issue was solved, it doesn't even begin to address the question I asked. I asked about an error that appeared during boot and interrupted the boot process. The error indicated that the system was looking for fsck.ntfs, which didn't exist on the system. How exactly could an explanation of which tool is appropriate for fixing disk errors help me resolve my boot error?
                        – Scott Severance
                        Mar 23 '16 at 20:57














                      -1












                      -1








                      -1






                      $ man fsck



                      fsck - check and repair a Linux filesystem




                      To repair a broken NTFS system on GNU / Linux you could use ntfsfix which is part of ntfs-3g as following:



                      $ ntfsfix /dev/sdc1





                      share|improve this answer












                      $ man fsck



                      fsck - check and repair a Linux filesystem




                      To repair a broken NTFS system on GNU / Linux you could use ntfsfix which is part of ntfs-3g as following:



                      $ ntfsfix /dev/sdc1






                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered Mar 19 '16 at 22:56









                      sevaivanov

                      1




                      1












                      • -1: This answer is unrelated to the question.
                        – Scott Severance
                        Mar 20 '16 at 2:54










                      • @ScottSeverance /me being down voted for not ignoring the tools application as stated in their manual -- only in Ubuntu forums haha
                        – sevaivanov
                        Mar 21 '16 at 5:58










                      • The question was about fsck.ntfs not being found at boot. Obviously, reporting the man page of irrelevant, since fsck wasn't being invoked manually. In addition, the situation wouldn't have arisen in the first place except for the fact that at one time fsck.ntfs did exist on a default Ubuntu install.
                        – Scott Severance
                        Mar 21 '16 at 11:39












                      • @ScottSeverance Thanks for stating that your thread is outdated!
                        – sevaivanov
                        Mar 23 '16 at 20:33












                      • It's quite possible that this question is outdated (though I can't be bothered to check so I can say for certain). However, that isn't the reason I down voted this answer. Even if it had been posted before my issue was solved, it doesn't even begin to address the question I asked. I asked about an error that appeared during boot and interrupted the boot process. The error indicated that the system was looking for fsck.ntfs, which didn't exist on the system. How exactly could an explanation of which tool is appropriate for fixing disk errors help me resolve my boot error?
                        – Scott Severance
                        Mar 23 '16 at 20:57


















                      • -1: This answer is unrelated to the question.
                        – Scott Severance
                        Mar 20 '16 at 2:54










                      • @ScottSeverance /me being down voted for not ignoring the tools application as stated in their manual -- only in Ubuntu forums haha
                        – sevaivanov
                        Mar 21 '16 at 5:58










                      • The question was about fsck.ntfs not being found at boot. Obviously, reporting the man page of irrelevant, since fsck wasn't being invoked manually. In addition, the situation wouldn't have arisen in the first place except for the fact that at one time fsck.ntfs did exist on a default Ubuntu install.
                        – Scott Severance
                        Mar 21 '16 at 11:39












                      • @ScottSeverance Thanks for stating that your thread is outdated!
                        – sevaivanov
                        Mar 23 '16 at 20:33












                      • It's quite possible that this question is outdated (though I can't be bothered to check so I can say for certain). However, that isn't the reason I down voted this answer. Even if it had been posted before my issue was solved, it doesn't even begin to address the question I asked. I asked about an error that appeared during boot and interrupted the boot process. The error indicated that the system was looking for fsck.ntfs, which didn't exist on the system. How exactly could an explanation of which tool is appropriate for fixing disk errors help me resolve my boot error?
                        – Scott Severance
                        Mar 23 '16 at 20:57
















                      -1: This answer is unrelated to the question.
                      – Scott Severance
                      Mar 20 '16 at 2:54




                      -1: This answer is unrelated to the question.
                      – Scott Severance
                      Mar 20 '16 at 2:54












                      @ScottSeverance /me being down voted for not ignoring the tools application as stated in their manual -- only in Ubuntu forums haha
                      – sevaivanov
                      Mar 21 '16 at 5:58




                      @ScottSeverance /me being down voted for not ignoring the tools application as stated in their manual -- only in Ubuntu forums haha
                      – sevaivanov
                      Mar 21 '16 at 5:58












                      The question was about fsck.ntfs not being found at boot. Obviously, reporting the man page of irrelevant, since fsck wasn't being invoked manually. In addition, the situation wouldn't have arisen in the first place except for the fact that at one time fsck.ntfs did exist on a default Ubuntu install.
                      – Scott Severance
                      Mar 21 '16 at 11:39






                      The question was about fsck.ntfs not being found at boot. Obviously, reporting the man page of irrelevant, since fsck wasn't being invoked manually. In addition, the situation wouldn't have arisen in the first place except for the fact that at one time fsck.ntfs did exist on a default Ubuntu install.
                      – Scott Severance
                      Mar 21 '16 at 11:39














                      @ScottSeverance Thanks for stating that your thread is outdated!
                      – sevaivanov
                      Mar 23 '16 at 20:33






                      @ScottSeverance Thanks for stating that your thread is outdated!
                      – sevaivanov
                      Mar 23 '16 at 20:33














                      It's quite possible that this question is outdated (though I can't be bothered to check so I can say for certain). However, that isn't the reason I down voted this answer. Even if it had been posted before my issue was solved, it doesn't even begin to address the question I asked. I asked about an error that appeared during boot and interrupted the boot process. The error indicated that the system was looking for fsck.ntfs, which didn't exist on the system. How exactly could an explanation of which tool is appropriate for fixing disk errors help me resolve my boot error?
                      – Scott Severance
                      Mar 23 '16 at 20:57




                      It's quite possible that this question is outdated (though I can't be bothered to check so I can say for certain). However, that isn't the reason I down voted this answer. Even if it had been posted before my issue was solved, it doesn't even begin to address the question I asked. I asked about an error that appeared during boot and interrupted the boot process. The error indicated that the system was looking for fsck.ntfs, which didn't exist on the system. How exactly could an explanation of which tool is appropriate for fixing disk errors help me resolve my boot error?
                      – Scott Severance
                      Mar 23 '16 at 20:57


















                      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.





                      Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                      Please pay close attention to the following guidance:


                      • 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%2f86086%2ffsck-cant-find-fsck-ntfs%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

                      數位音樂下載

                      When can things happen in Etherscan, such as the picture below?

                      格利澤436b