While I understand what you're saying, in fact there is a bug report for just that case -- changing the scanning methodology, bug #59293 and related to that bug #48806, I'm trying to make the behaviour of dosfstools predictable.
At the moment, your bug could be interpreted as a fstab issue and a duplicate of the above two bugs, but I'm curious to know what the error was that scandisk found. What I'm trying to determine is if you've found another bug in dosfstools, or just unexpected behaviour we already know about. -- FAT drive scanned at boot, triples startup time https://launchpad.net/bugs/84617 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
