[Bug 238447] ntfs-3g-2017.3.23 external FUSE 29: fails mount: fuse: failed to open fuse device: No such file or directory

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238447

            Bug ID: 238447
           Summary: ntfs-3g-2017.3.23 external FUSE 29: fails mount: fuse:
                    failed to open fuse device: No such file or directory
           Product: Base System
           Version: 12.0-RELEASE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: misc
          Assignee: bugs at FreeBSD.org
          Reporter: jason.mours at verizon.net

Anyone else? I have work on a windows NTFS partition.

FREEBSD 12.0-RELEASE r341666

root at machine:~ # ntfs-3g -o ro /dev/ada2p1 /mnt/ada2
fuse: failed to open fuse device: No such file or directory

root at machine:~ # ntfs-3g -o ro /dev/ntfs/<volume> /mnt/ada2
fuse: failed to open fuse device: No such file or directory

root at machine:~ # mount -o ro -t ntfs /dev/ada2p1 /mnt/ada2
mount: /dev/ada2p1: Operation not supported by device

BSD touches the drive. Fails after *pause*.

FUSE-1.5.7 from binary pkg installed.

All installed packages are from pkg binary. No source ports yet. Install is
vanilla.


Seems simple, is it me?  I'm new to BSD, per se, is this something that Beastie
fixes on it's own? I feel him working in the solfeg. I leave the box alone,
mostly. 

The problem feels like command? Dunno, I never systemd...user>=. 

Not to pollute further, but I plan on reinstalling. Maybe re-striping..get it
TRUE RED. This over the course of the week. If hu-man start to hack at bits. I
would expect to be here again after.

-- 
You are receiving this mail because:
You are the assignee for the bug.