> Why would it try for and NTFS file system on a Linux machine?

The way I understand it is that without a filesystem type,
mount will try all (disk-based) filesystem drivers that
you have currently loaded. And the ntfs driver generates
some debug output when it fails. So nothing to worry about.

It does make sense - sensibly enough the kernel has no other[1]
facility to work out what filesystem is really on a given
partition - it has to invoke the filesystem driver to find out.

regards

marc

[1] partition ids, etc may provide a clue but consider the case
of your magic new filesystem that you have just written a kernel
driver for...