From owner-freebsd-ports@FreeBSD.ORG  Fri Jan 16 18:32:12 2015
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 9AAC4B75
 for <freebsd-ports@freebsd.org>; Fri, 16 Jan 2015 18:32:12 +0000 (UTC)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21])
 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-1" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 2C1FFBB9
 for <freebsd-ports@freebsd.org>; Fri, 16 Jan 2015 18:32:12 +0000 (UTC)
Received: from walrus.pepperland ([81.217.76.60]) by mail.gmx.com (mrgmx102)
 with ESMTPSA (Nemesis) id 0MTMzb-1YMKi61ZKB-00SLuX; Fri, 16 Jan 2015 19:32:09
 +0100
Message-ID: <54B95927.8000800@gmx.net>
Date: Fri, 16 Jan 2015 19:32:07 +0100
From: Stefan Ehmann <shoesoft@gmx.net>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Thomas Mueller <mueller6724@bellsouth.net>, 
 freebsd-ports@freebsd.org
Subject: Re: Problems with fusefs-ntfs port
References: <131547.96781.bm@smtp118.sbc.mail.ne1.yahoo.com>
 <54B92EC5.1070903@gmx.net> <609982.64279.bm@smtp117.sbc.mail.ne1.yahoo.com>
In-Reply-To: <609982.64279.bm@smtp117.sbc.mail.ne1.yahoo.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:N2CSWDHDKiejli0JsBvDUah/uXdgMA0qT2aSaDX9+Hs8uLEN0yR
 e+KYWkDzeBEXP5Imp0pyDp0dBg6anR8awrUDeJOXJbEaDT8QxW0o+hIRv7Oe+U57EFaeTC+
 QiFjjzlKtTPdBrIkzgw7zYPfb7oDxdmEEpTGkdvG7h+bD+6Uh36JKXr7fcgwLIMjCmQYgWr
 rRlnQuY/dDGk4p0+keoqQ==
X-UI-Out-Filterresults: notjunk:1;
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports/>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Jan 2015 18:32:12 -0000

On 16.01.2015 19:17, Thomas Mueller wrote:
>> from Stefan Ehmann:
>
>> On 16.01.2015 06:38, Thomas Mueller wrote:
>>> I've been having trouble with fusefs-ntfs on a Seagate BackupPlus hard drive, 5 TB, external USB 3.0.
>
>>> It wouldn't mount with ntfs-3g, but I was apparently able to copy (ntfscat) the files one-by-one, very inelegant and quite unworkable for anything other than a small number of files in a simple directory structure.
>
>>> Trying to mount Seagate BackupPlus with ntfs-3g /dev/da0s1 /media/zip0
>
>>> fuse: failed to open fuse device: No such file or directory
>
>> Check dmesg. IIRC this message indicates a missing kernel module (not a
>> missing hard disk device).
>
> What module?  I built all modules with the kernel, and then why would ntfsls and ntfscat see the device file that ntfs-3g didn't?
>
> I checked /var/run/dmesg.boot, biggest thing I noticed was repeated attempts to find USB 3.0 device.

After you get the "No such file or directory" error type
# dmesg | tail
Hopefully this will reveal a more helpful error message.

I'm currently not using fuse. But I think something like
# kldload fuse
might fix this issue.