Ubiquity generates bad fstab with NTFS partitions

Can you provide the full error message you get?

This is what i see at boot time (grabbed from TTY1):

fsck from util-linux-ng 2.1686d4e-7813-4b0f-8ab4-d0e5bf2551bf
fsck from util-linux-ng 2.16
fsck: fsck.ntfs: not found
fsck: Error 2 while executing fsck.ntfs for /dev/sdb1
/dev/sda2: clean, 332020/1835008 files, 3061327/7333672 blocks
 * Setting preliminary keymap...
 * Starting AppArmor profiles
 * Setting up console font and keymap...
 * Starting OpenBSD Secure Shell server sshd
 * Starting Kernel Oops catching service kerneloops
 * Not starting internet superserver: no services enabled
 * Starting Samba daemons

Thanks.

How have did you set up your system to mount the drive on boot?
If you added a line to the fstab file, please add this line to the bug report.
Thanks in advance.

This is the line:

# /media/storage was on /dev/sdb1 during installation
UUID=7260D4F760D4C2D1 /media/storage ntfs defaults,nls=utf8,umask=000,gid=46 0 1

As a workaround you can change the number 1 at the end of the line into a 0 so that i says
UUID=7260D4F760D4C2D1 /media/storage ntfs defaults,nls=utf8,umask=000,gid=46 0 0

the question would be now if util-linux should blacklist ntfs drives since there is no fsck program for them yet if drive checking is enabled for them. But the situation now is somehow the expected behaviour.

I have the same problem and I set up the ntfs partitions to be mounted in a /media subdirectory during install. So the easiest fix is changing the fstab entry ubiquity creates. Shall I open a new bug for this or can this one just be assigned to ubiquity?

I am running into the same problem with fsck.ntfs not found on boot, with a ntfs partition mounted at boot. A temporary fix, posted above was to change the last 1, to a 0. But that doesn't seam like a great fix, since there are days (very few mind you) that I do not need to transfer files to that partition.

@mniess: I agree with you, ubiquity should create the partition entry with a "0".

At least until the fsck.ntfs becomes available and installed by default in Ubuntu.

The missing fsck.ntfs message is just a warning, it's otherwise ignored and the filesystem will be mounted normally.

To suppress the warning, just fix your fstab

@scott: I agree with you. I filled this bug report as part of the new ubuntu boot experience.
That wrong line of fstab was not written by me but generated by ubiquity at install time. I suppose ubiquity developers should fix this little bug.

I'll change the installer to generate fstab lines with pass 0 rather than 1. This will still be an issue for upgraders, who will have to change /etc/fstab by hand; there's nothing much I can do about that, sorry.

I've added an update-manager task in case there's something that can be done there to smooth the upgrade process.

This bug was fixed in the package partman-basicfilesystems - 63ubuntu2

---------------
partman-basicfilesystems (63ubuntu2) karmic; urgency=low

  * Don't check NTFS at boot, since we have no fsck.ntfs right now
    (LP: #441242).

 -- Colin Watson <email address hidden> Tue, 06 Oct 2009 22:44:55 +0100

This bug was fixed in the package update-manager - 1:0.126

---------------
update-manager (1:0.126) karmic; urgency=low

  * DistUpgrade/DistUpgrade.cfg:
    - add gnome-app-install to the ForcedObsoletes
  * DistUpgrade/DistUpgrade.cfg.hardy:
    - add ability to upgrade from hardy to karmic (as asked for
      by Jonathan Riddell)
  * DistUpgrade/DistUpgradeQuirks.py:
    - add quirk handler to mark the dependencies of
      language-support-translations-* as manual on upgrade

      The language-support-translations- packages are removed in
      karmic and would otherwise be marked as auto-removable.
      (LP: #439296)
    - convert PASS value from 1 to 0 for ntfs entries in
      /etc/fstab (LP: #441242) and add tests for it
    - put 386 to generic transition code here and decouple from
      the kernel selection
    - inhibit gnome-screensaver once the upgrade started
      to avoid X crash (LP: #439594)
  * DistUpgrade/DistUpgradeCache.py:
    - workaround issues with kdesu when it drop the permission bits
      in a tmpdir (thanks to Jonathan Riddell)
    - fix base-installer kernel selection (LP: #441629)
    - fix log dir does not exist, create it (LP: #441959)
  * UpdateManager/backend/InstallBackendAptdaemon.py:
    - give up lock before running aptdaemon (LP: #445920)
  * po/
    - updated from launchpad (required as during a release upgrade
      we can't use langpacks)

 -- Michael Vogt <email address hidden> Thu, 08 Oct 2009 17:45:25 +0200

This occurs for me in Lucid.