[Bug 896944] Re: NTFS partition scans clean in Windows, but I get 'Serious errors were found' at boot
Robert Roth
896944 at bugs.launchpad.net
Wed Jan 25 10:44:31 UTC 2012
*** This bug is a duplicate of bug 838091 ***
https://bugs.launchpad.net/bugs/838091
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug #838091, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.
** This bug has been marked a duplicate of bug 838091
should link fsck.ntfs -> ntfsfix/ntfsck
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ntfs-3g in Ubuntu.
https://bugs.launchpad.net/bugs/896944
Title:
NTFS partition scans clean in Windows, but I get 'Serious errors were
found' at boot
Status in “ntfs-3g” package in Ubuntu:
Incomplete
Bug description:
Most of this is copied from information contained in this thread:
http://ubuntuforums.org/showthread.php?t=1863787
I have a dual boot system (through grub)
I upgraded to Kubuntu 11.10 from 11.04. Before the upgrade, Kubuntu booted fine.
Now I get 'Serious errors were found while checking the disk for /NTFSFTW' on booting Kubuntu.
The partition is NTFS, and it scans completely clean under windows, plus I doubt the upgrade touched it, as there are no system files on there, so it is likely COMPLETELY fine, but the system CLAIMS it's faulty and halts startup.
I pressed ESC to see what was going on, and it seems the error happens because a call is being made to fsck.ntfs.
I get:
fsck.ntfs: not found.
Then I press 'I' for ignore, and continue using the system completely as normal (including the NTFS partition in question).
So it seems this error is coming up NOT because there's an error on the disk, but because some automatic boot procedure is trying to execute a command that doesn't exist!
If fsck can't do ntfs, don't try it, don't throw an error about it and don't halt boot!
Surely something can be done about this?
It happens EVERY Kubuntu boot, and scans clean under Windows EVERY
time.
This is an annoyance.
Has anyone got any suggestions for a workaround? - This doesn't seem to have been reported elsewhere.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: ntfs-3g 1:2011.4.12AR.4-2ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Uname: Linux 3.0.0-12-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Sun Nov 27 18:48:59 2011
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
ProcEnviron:
LANGUAGE=en_GB:en
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: ntfs-3g
UpgradeStatus: Upgraded to oneiric on 2011-10-14 (44 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/896944/+subscriptions
More information about the foundations-bugs
mailing list