Solved Me thoughts that FreeBSD supported ntfs (RO) what up?

so far every way and some I did nt know, that I've tried and still cannot get ntfs partition to mount in fstab, or command line. fuse ntfs too is installed, rc.conf
Code:
autofs_enable="YES"
fuse_load="YES"
some of the comands tried
Code:
$ fstyp /dev/ada1p2
ntfs

.

$ sudo mount -a
mount: /dev/ada1p2: Operation not supported by device
userx@FreeBSD.edy:~
$ sudo mount /dev/ada1p2 -t ntfs-3g ro,uid=1000 /stores
usage: mount [-adflpruvw] [-F fstab] [-o options] [-t ufs | external_type]
       mount [-dfpruvw] special | node
       mount [-dfpruvw] [-o options] [-t ufs | external_type] special node
userx@FreeBSD.edy:~
$ sudo mount /dev/ada1p2 -t ntfs-3g -o uid=1000 /stores
usage: mount [-adflpruvw] [-F fstab] [-o options] [-t ufs | external_type]
       mount [-dfpruvw] special | node
       mount [-dfpruvw] [-o options] [-t ufs | external_type] special node
userx@FreeBSD.edy:~
$ sudo mount /dev/ada1p2 -t ntfs-3g  /stores
usage: mount [-adflpruvw] [-F fstab] [-o options] [-t ufs | external_type]
       mount [-dfpruvw] special | node
       mount [-dfpruvw] [-o options] [-t ufs | external_type] special node
userx@FreeBSD.edy:~
$ ls /stores
userx@FreeBSD.edy:~
$ sudo mount /dev/ada1p2 -t ntfs-3g -o ro  /stores
usage: mount [-adflpruvw] [-F fstab] [-o options] [-t ufs | external_type]
       mount [-dfpruvw] special | node
       mount [-dfpruvw] [-o options] [-t ufs | external_type] special node
userx@FreeBSD.edy:~
$ sudo mount /dev/ada1p2 -t ntfs -o ro  /stores
usage: mount [-adflpruvw] [-F fstab] [-o options] [-t ufs | external_type]
       mount [-dfpruvw] special | node
       mount [-dfpruvw] [-o options] [-t ufs | external_type] special node
userx@FreeBSD.edy:~
$ sudo mount -t nrtf-3g /dev/ada1p2 /stores
mount: /dev/ada1p2: Operation not supported by device
userx@FreeBSD.edy:~
$ sudo  nrtf-3g /dev/ada1p2 /stores
sudo: nrtf-3g: command not found
userx@FreeBSD.edy:~
$ sudo  ntfs-3g /dev/ada1p2 /stores
fuse: failed to open fuse device: No such file or directory
userx@FreeBSD.edy:~
$ sudo  mount ntfs-3g /dev/ada1p2 /stores
usage: mount [-adflpruvw] [-F fstab] [-o options] [-t ufs | external_type]
       mount [-dfpruvw] special | node
       mount [-dfpruvw] [-o options] [-t ufs | external_type] special node
userx@FreeBSD.edy:~
$ sudo  mount -t ntfs-3g /dev/ada1p2 /stores
mount: /dev/ada1p2: Operation not supported by device
userx@FreeBSD.edy:~
$


Code:
$ su

Password:

[root@FreeBSD /home/userx]# ntfs-3g /dev/ada1p2 /stores

fuse: failed to open fuse device: No such file or directory
 
In rc.conf:
Code:
kld_list="fusefs"

fstab:
Code:
/dev/ada1p2     /stores     ntfs   mountprog=/usr/local/bin/ntfs-3g    0   0
 
let me give that a shot, thanks, brb with results.
quick Q first, two can be used, and like this
Code:
kld_list="/boot/modules/i915kms.ko"
 kld_list="fusefs"
or
Code:
kld_list="vboot/modules/i915kms.ko,fusefs"
 
OK I can see this is not going to work in fstab???
Code:
kld_list     (str) A list of kernel    modules    to load    right after the    local
         disks are mounted.  Loading modules at    this point in the boot
         process is much faster    than doing it via /boot/loader.conf
         for those modules not necessary for mounting local disk.


Code:
$ kldstat
Id Refs Address                Size Name
 1   91 0xffffffff80200000  2448ef8 kernel
 2    1 0xffffffff82ffa000     494c linprocfs.ko
 3    4 0xffffffff82fff000     3178 linux_common.ko
 4    1 0xffffffff83003000     1eae linsysfs.ko
 5    1 0xffffffff83005000     88d8 tmpfs.ko
 6    1 0xffffffff8300e000   12b7f0 i915kms.ko
 7    1 0xffffffff8313a000    76370 drm.ko
 8    4 0xffffffff831b1000    10eb0 linuxkpi.ko
 9    3 0xffffffff831c2000    12f30 linuxkpi_gplv2.ko
10    2 0xffffffff831d5000      6d0 debugfs.ko
11    1 0xffffffff831d6000    15d20 if_iwm.ko
12    1 0xffffffff831ec000   12045f iwm7265fw.ko
13    1 0xffffffff8330d000     18a0 uhid.ko
14    1 0xffffffff8330f000     2928 ums.ko
15    1 0xffffffff83312000     1aa0 wmt.ko
16    1 0xffffffff83314000     4260 ng_ubt.ko
17    6 0xffffffff83319000     9e30 netgraph.ko
18    2 0xffffffff83323000     91b8 ng_hci.ko
19    3 0xffffffff8332d000      9c0 ng_bluetooth.ko
20    1 0xffffffff8332e000      970 pflog.ko
21    1 0xffffffff8332f000    32830 pf.ko
22    1 0xffffffff83362000    3df60 linux.ko
23    1 0xffffffff833a0000    35b20 linux64.ko
24    1 0xffffffff833d6000     cad0 ng_l2cap.ko
25    1 0xffffffff833e3000    1ba00 ng_btsocket.ko
26    1 0xffffffff833ff000     21c0 ng_socket.ko
27    1 0xffffffff83402000     47b0 autofs.ko
28    1 0xffffffff83407000      acf mac_ntpd.ko
29    1 0xffffffff83408000    18dc8 ext2fs.ko
 
They need to be space separated.


You may need to add the late keyword to the option field in order to have it mounted later on in the boot process.
I found this on it
this one
lead me to this one
which lead me to this one

added this suggested that Other OP in that post said fixed his issue.
Code:
sysrc kld_list+=fuse
rebooted, and seen loads of repeats of loding i915 -> fusefs lines going down the screen during boot up.

no fusefs loaded though
Code:
$ sudo kldstat
Id Refs Address                Size Name
 1   91 0xffffffff80200000  2448ef8 kernel
 2    1 0xffffffff82ffa000     494c linprocfs.ko
 3    4 0xffffffff82fff000     3178 linux_common.ko
 4    1 0xffffffff83003000     1eae linsysfs.ko
 5    1 0xffffffff83005000     88d8 tmpfs.ko
 6    1 0xffffffff8300e000   12b7f0 i915kms.ko
 7    1 0xffffffff8313a000    76370 drm.ko
 8    4 0xffffffff831b1000    10eb0 linuxkpi.ko
 9    3 0xffffffff831c2000    12f30 linuxkpi_gplv2.ko
10    2 0xffffffff831d5000      6d0 debugfs.ko
11    1 0xffffffff831d6000    15d20 if_iwm.ko
12    1 0xffffffff831ec000   12045f iwm7265fw.ko
13    1 0xffffffff8330d000     18a0 uhid.ko
14    1 0xffffffff8330f000     2928 ums.ko
15    1 0xffffffff83312000     1aa0 wmt.ko
16    1 0xffffffff83314000     4260 ng_ubt.ko
17    6 0xffffffff83319000     9e30 netgraph.ko
18    2 0xffffffff83323000     91b8 ng_hci.ko
19    3 0xffffffff8332d000      9c0 ng_bluetooth.ko
20    1 0xffffffff8332e000     cad0 ng_l2cap.ko
21    1 0xffffffff8333b000    1ba00 ng_btsocket.ko
22    1 0xffffffff83357000     21c0 ng_socket.ko
23    1 0xffffffff8335a000      970 pflog.ko
24    1 0xffffffff8335b000    32830 pf.ko
25    1 0xffffffff8338e000    3df60 linux.ko
26    1 0xffffffff833cc000    35b20 linux64.ko
27    1 0xffffffff83402000     47b0 autofs.ko
28    1 0xffffffff83407000      acf mac_ntpd.ko
29    1 0xffffffff83408000    18dc8 ext2fs.ko
so that being said,
Code:
kld_list="/boot/modules/i915kms.ko fusefs late"
#sysrc kld_list+=fuse
#kld_list="fusefs"
reboot....... brb
 
BIG NOPE. it loads fusefs, but fstab entry gets me repair mode, where i got to edit fstab and comment out mount for the ntfs partiton, then exit to continue booting.
 
No... The late option goes in the fstab

Code:
/dev/ada1p2     /stores     ntfs   mountprog=/usr/local/bin/ntfs-3g,late    0   0
it's be nice if people would stop assuming others just knew, where things go.

thanks let me try that now.
 
No... The late option goes in the fstab

Code:
/dev/ada1p2     /stores     ntfs   mountprog=/usr/local/bin/ntfs-3g,late    0   0
Nope that did not work either, nothing empty dir after booting.
what if I put it tow or three times like this?

Code:
/dev/ada1p2     /stores     ntfs   mountprog=/usr/local/bin/ntfs-3g,late ,late,late,late,late 0 0
make it wait wait wait wait .. :D j/k :D

kld_list (str) A list of kernel modules to load right after the local disks are mounted. after mounts are done then fusefs loads, so it looks like it is shooting the cow before putting the shell in the gun. fstab gets processed first then sys loads fusefs, so the line in fstab maybe correct because it does not stop boot and have me fix fstab, fusefs is not loaded untill after fstab is processed, so no mount ntfs partition, BUT ext2fs mounts Okay Dokay.. go figure... 🤪
 
what operates as if a rc.d/rc.local to call it to mount after fstab. if that is the order it boots.. Just a thought here...
 
Instead of kld_list="fusefs" try this in /boot/loader.conf:
Code:
fusefs_load="YES"

I was expecting kld_list to be processed quite soon in the boot process but apparently it loads later.

(Adding more than one late option in fstab is useless)
 
Instead of kld_list="fusefs" try this in /boot/loader.conf:
Code:
fusefs_load="YES"

I was expecting kld_list to be processed quite soon in the boot process but apparently it loads later.

(Adding more than one late option in fstab is useless)
I don't think that will work, but I'll give it a shot. brb
 
the big finale
SirDice bjs

in my rc.conf, just for this one thing,
Code:
autofs_enable="YES"
kld_list="/boot/modules/i915kms.ko fusefs"
in boot/loader.conf
Code:
$ cat /boot/loader.conf
security.bsd.allow_destructive_dtrace=0
autoboot_delay="5"
fuse_load="YES"
in fstab to mount ntfs
Code:
$ cat /etc/fstab
# Device    Mountpoint    FStype    Options    Dump    Pass#
/dev/ada1p8     /   ufs rw 1 1
/dev/ada1p9 none swap sw 0 0
/dev/ada0p2    /data            ext2fs  rw      1       2
/dev/ada1p2     /stores     ntfs   mountprog=/usr/local/bin/ntfs-3g,late,rw    0   0

#Linux binary support
linprocfs   /compat/linux/proc  linprocfs       rw      0       0
linsysfs    /compat/linux/sys   linsysfs        rw      0       0
tmpfs    /compat/linux/dev/shm  tmpfs   rw,mode=1777    0       0
and it is Read/Write? as I created a empty file, then opened it wrote into it, saved it, then opened it again and it was not harmed.

I thought NTFS was a r/w only on FreeBSD, but maybe not.
 
Remove both
Code:
kld_list="fusefs"
in /boot/loader.conf and /etc/rc.conf.

IIRC, the line in /boot/loader.conf should be:
Code:
fusefs_load="YES"
 
I thought NTFS was a r/w only on FreeBSD, but maybe not.
The old mount_ntfs that came with FreeBSD was read-only. But that was removed quite some time ago. The sysutils/fusefs-ntfs3g was always capable of writing (although I don't recommend enabling it).

Both fusefs_load and fuse_load should work, fuse.ko is a symlink to fusefs.ko:
Code:
# ll /boot/kernel/fuse*
lrwxr-xr-x  1 root  wheel       9 Nov 16 16:35 /boot/kernel/fuse.ko@ -> fusefs.ko
-r-xr-xr-x  1 root  wheel  169696 Nov 16 16:35 /boot/kernel/fusefs.ko*

But yes, use kld_list or loader.conf to load the module, not both.
 
Remove both
Code:
kld_list="fusefs"
in /boot/loader.conf and /etc/rc.conf.

IIRC, the line in /boot/loader.conf should be:
Code:
fusefs_load="YES"
what SirDice said above, they are symlinked for short hand, fuse .. so that is why it is working with fuse_load="YES" in my logical assumption.
Code:
userx@FreeBSD12.1.org:~
$ ll /boot/kernel/fuse*
lrwxr-xr-x  1 root  wheel     9B Oct 31 23:36 /boot/kernel/fuse.ko -> fusefs.ko
-r-xr-xr-x  2 root  wheel   165K Oct 31 23:36 /boot/kernel/fusefs.ko
 
The old mount_ntfs that came with FreeBSD was read-only. But that was removed quite some time ago. The sysutils/fusefs-ntfs3g was always capable of writing (although I don't recommend enabling it).

Both fusefs_load and fuse_load should work, fuse.ko is a symlink to fusefs.ko:
Code:
# ll /boot/kernel/fuse*
lrwxr-xr-x  1 root  wheel       9 Nov 16 16:35 /boot/kernel/fuse.ko@ -> fusefs.ko
-r-xr-xr-x  1 root  wheel  169696 Nov 16 16:35 /boot/kernel/fusefs.ko*

But yes, use kld_list or loader.conf to load the module, not both.
don't trust the system (coders), "was always capable of writing (although I don't recommend enabling it)."

so do you listen to , system of a down? :rolleyes:
 
The 'problem' is that ntfs-3g is a reverse-engineered implementation, so it's inherently dangerous. Microsoft could change some hidden details in the NTFS filesystem, which could result in ntfs-3g potentially destroying your filesystem. Always be careful with it.
 
The 'problem' is that ntfs-3g is a reverse-engineered implementation, so it's inherently dangerous. Microsoft could change some hidden details in the NTFS filesystem, which could result in ntfs-3g potentially destroying your filesystem. Always be careful with it.
Point taken, and I was going into it as a read only mind set on the git (get) go. time will tell if I go to writing anything to it.
 
Back
Top