I do agree with that, the problem is that this issue prevented system to boot. The only error was fsck.ntfs not found. Partition itself had no errors.
So in my humble opinion, the boot process shouldn't alert user about "serious errors" when there is NO error on partition but just a tool missing. Should it ? Regards, Le 16/10/2011 10:45, Jean-Pierre a écrit : >> Creating a symlink from ntfsfix to /sbin/fsck.ntfs make things working > again. > > Yes, but ntfsfix is not a file system checker, it fixes common errors > preventing the partition from mounting and triggers chkdsk next time the > partition will be used on Windows. > > It is a bad idea to give users the impression that they are in a safe > situation because they request their file system to be checked at boot > time, when there is no check at all. > > (When the traffic lights are out of order, it is better to force a > winking orange light than a green light) > -- Bertrand COTTENET Villa Ki Ou Le Avenue Brick Empire Albion Plage - Albion Ile Maurice Tel. Maurice : +230 940 2645 Tel. France : +33 skype : bertrand.cottenet -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/875237 Title: Mount ntfs partition at boot fails because no fsck.ntfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/875237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
