[Bug 838091] Re: should not try to fsck ntfs volumes on boot

[Launchpad Bug Tracker]

This bug was fixed in the package mountall - 2.36

---------------
mountall (2.36) precise; urgency=low

  * If no specific fsck.* checker is found for a given filesystem type
    (except for a short list where we know that checkers really should be
    present), skip checking that filesystem rather than emitting scary error
    messages (LP: #838091).  This duplicates some logic from 'fsck -A', but
    that seems reasonable given mountall's purpose.
 -- Colin Watson <cjwatson at ubuntu.com>   Thu, 12 Apr 2012 18:58:16 +0100

** Changed in: mountall (Ubuntu Precise)
       Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mountall in Ubuntu.
https://bugs.launchpad.net/bugs/838091

Title:
  should not try to fsck ntfs volumes on boot

Status in “mountall” package in Ubuntu:
  Fix Released
Status in “mountall” source package in Oneiric:
  Confirmed
Status in “mountall” source package in Precise:
  Fix Released

Bug description:
  == Regression details ==
  Discovered in version: 11.10
  Last known good version: 11.04

  I've got a dualboot laptop, and the installer has created fstab
  entries for the NTFS partitions. But now oneiric is complaining that
  it can't mount them, and prompts me on boot what to do about it.
  Skipping or ignoring the error makes the boot complete, and boot.log
  reveals that it fails due to fsck.ntfs being missing.

  So, ntfs-3g should symlink fsck.ntfs to ntfsfix or ntfsck, though the
  latter fails to check my partitions, so maybe ntfsfix would be better.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/838091/+subscriptions