Other Mount ExFat using fusefs-exfat: failed to open fuse device: No such file or directory

zoujiaqing

Active Member

Reaction score: 6
Messages: 144

My USB storage device is 64GB ExFAT.

but using `gpart` command show NTFS?

Code:
[zoujiaqing@freebsd /home/zoujiaqing]$ sudo mount.exfat /dev/da0s1 /mnt
FUSE exfat 1.3.0
fuse: failed to open fuse device: No such file or directory
[zoujiaqing@freebsd /home/zoujiaqing]$ gpart show da0
=>       63  125829057  da0  MBR  (60G)
         63        385       - free -  (193K)
        448  125828672    1  ntfs  (60G)

How to mounting it?
 

ralphbsz

Son of Beastie

Reaction score: 2,030
Messages: 2,997

What file system is really used? Is it NTFS or FAT? Are you sure? How did you check?

Try "file /dev/da0s1", that might tell you what the file system of that partition really is.

And remember that the content of the partition table is a bit arbitrary. Even if a partition really contains data that is a file system of type X, I can set the partition type to anything I want.
 
OP
zoujiaqing

zoujiaqing

Active Member

Reaction score: 6
Messages: 144

What file system is really used? Is it NTFS or FAT? Are you sure? How did you check?

Try "file /dev/da0s1", that might tell you what the file system of that partition really is.

And remember that the content of the partition table is a bit arbitrary. Even if a partition really contains data that is a file system of type X, I can set the partition type to anything I want.
This device using macOS and WIndows to created partition.

Code:
[zoujiaqing@freebsd /usr/home/zoujiaqing]$ file /dev/da0s1 
/dev/da0s1: character special (0/173)
 
OP
zoujiaqing

zoujiaqing

Active Member

Reaction score: 6
Messages: 144

You have to kldload fuse first.
Thank you! but this question not resolve.
Code:
[zoujiaqing@freebsd /usr/home/zoujiaqing]$ sudo kldload fusefs
kldload: can't load fusefs: module already loaded or in kernel
[zoujiaqing@freebsd /usr/home/zoujiaqing]$ sudo mount /dev/da0s1 /mnt
mount: /dev/da0s1: No such file or directory
[zoujiaqing@freebsd /usr/home/zoujiaqing]$ gpart show da0
=>       63  125829057  da0  MBR  (60G)
         63        385       - free -  (193K)
        448  125828672    1  ntfs  (60G)

[zoujiaqing@freebsd ~]$ sudo ntfs-3g /dev/da0s1 /mnt
NTFS signature is missing.
Failed to mount '/dev/da0s1': Invalid argument
The device '/dev/da0s1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
 
OP
zoujiaqing

zoujiaqing

Active Member

Reaction score: 6
Messages: 144

This is Disk Manager on macOS:
USB-Flash-Device.png
 

aragats

Daemon

Reaction score: 656
Messages: 1,558

Just tested in FreeBSD 13.0 built on ~Feb 11, works with both GPT and MBR:
Code:
# gpart show md0
=>     34  2097085  md0  GPT  (1.0G)
       34    32734    1  ms-reserved  (16M)
    32768  2060288    2  ms-basic-data  (1.0G)
  2093056     4063       - free -  (2.0M)

# mount.exfat /dev/md0p2 /mnt/img/
FUSE exfat 1.3.0
# ll !$
ll /mnt/img/
total 164
drwxrwxrwx  1 root  wheel    32K 31 Dec  1969 .
drwxr-xr-x  7 root  wheel   512B 10 Feb 21:29 ..
drwxrwxrwx  1 root  wheel    32K 27 Feb 22:00 $RECYCLE.BIN
-rwxrwxrwx  1 root  wheel     6B 27 Feb 22:00 123.txt
drwxrwxrwx  1 root  wheel    32K 27 Feb 21:59 System Volume Information
drwxrwxrwx  1 root  wheel    32K 27 Feb 22:00 test
Code:
# gpart show md0
=>     1  204799  md0  MBR  (100M)
       1     127       - free -  (64K)
     128  198656    1  ntfs  (97M)
  198784    6016       - free -  (2.9M)

# mount.exfat /dev/md0s1 /mnt/img/
FUSE exfat 1.3.0
# ll !$
ll /mnt/img/
total 20
drwxrwxrwx  1 root  wheel   4.0K 31 Dec  1969 .
drwxr-xr-x  7 root  wheel   512B 10 Feb 21:29 ..
drwxrwxrwx  1 root  wheel   4.0K 27 Feb 22:10 $RECYCLE.BIN
-rwxrwxrwx  1 root  wheel     0B 27 Feb 22:11 qwerty.txt
drwxrwxrwx  1 root  wheel   4.0K 27 Feb 22:10 System Volume Information
drwxrwxrwx  1 root  wheel   4.0K 27 Feb 22:10 test-on-mbr
 

ralphbsz

Son of Beastie

Reaction score: 2,030
Messages: 2,997

Code:
[zoujiaqing@freebsd /usr/home/zoujiaqing]$ file /dev/da0s1
/dev/da0s1: character special (0/173)
Darn it! My fault, my instructions were incorrect. The idea was to use the "file" command to find out what type of file system is really on the device /dev/da0s1. What I forgot is that the file command by default will not read a device, only a file. To convince it to actually look inside the content of a device, you need the "-s" switch. I don't have any FAT file systems attached to my computer right now, so here is an example:
Code:
# file -s /dev/ada1p4
/dev/ada1p4: Unix Fast File system [v2] (little-endian) last mounted on /var, volume name lrvar, last written at Thu Jan  5 20:48:49 2017, clean flag 1, readonly flag 0, number of blocks 524288, number of data blocks 515975, number of cylinder groups 4, block size 32768, fragment size 4096, average file size 16384, average number of files in dir 64, pending blocks to free 0, pending inodes to free 0, system-wide uuid 0, minimum percentage of free blocks 8, TIME optimization
Honestly: If this is broken on a 13-current kernel, I will not be surprised. And personally, I have never liked FUSE, and I try to avoid it whenever possible. That's in spite of considering the father of fuse (Erez Zadok) to be a colleague and friend.

You also asked:
The device '/dev/da0s1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
No, the presence of a valid partition table tells us that the file system is not using the whole device, but only a partition. Given the screen shot from the Mac above, it is pretty certain that the file system on that partition is ExFAT and not NTFS. That's confirmed by the error message when you tried to mount it with NTFS, which clearly was able to access the device and not find the valid NTFS headers. The real problem is that for some reason the loading of the fusefs module is not working right for you. Could it be version skew between running kernel and module?

P.S. It's not /dev/sda and /dev/sda1, it's /dev/da0 and /dev/da0s1.
 

aragats

Daemon

Reaction score: 656
Messages: 1,558

Honestly: If this is broken on a 13-current kernel, I will not be surprised.
Here is how an exFat partition looks in 13-current:
Code:
# gpart show /dev/md0
=>     63  2097089  md0  MBR  (1.0G)
       63       65       - free -  (33K)
      128  2091008    1  ntfs  (1.0G)
  2091136     6016       - free -  (2.9M)

# file -s /dev/md0s1
/dev/md0s1: DOS/MBR boot sector
However, there is no problem with mounting it (as I showed above).
UFS and ext4 are recognized by file() correctly.
 

Mike G

New Member


Messages: 1

I had the same problem, but what I found worked was to kldload fusefs instead of kldload fuse.
 

SirDice

Administrator
Staff member
Administrator
Moderator

Reaction score: 10,991
Messages: 36,924

The module was renamed to fusefs for 12.1, and both fuse and fusefs loaded the fusefs(5) kernel module. With 13.0 the old fuse alias was removed.

Code:
It was	added to the
     base system in FreeBSD 10.0, and renamed to fusefs	for FreeBSD 12.1.
 
Top