Date: Fri, 16 Jan 2015 19:32:07 +0100 From: Stefan Ehmann <shoesoft@gmx.net> To: Thomas Mueller <mueller6724@bellsouth.net>, freebsd-ports@freebsd.org Subject: Re: Problems with fusefs-ntfs port Message-ID: <54B95927.8000800@gmx.net> In-Reply-To: <609982.64279.bm@smtp117.sbc.mail.ne1.yahoo.com> References: <131547.96781.bm@smtp118.sbc.mail.ne1.yahoo.com> <54B92EC5.1070903@gmx.net> <609982.64279.bm@smtp117.sbc.mail.ne1.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54B95927.8000800>