Other External USB3 enclosure with an NTFS partition not visible when attached



Reaction score: 1
Messages: 79

It mounts in Windows and Linux on this same box. This is what dmesg reports when it is attached:

ugen7.2: <Generic External> at usbus7
umass1 on uhub6
umass1: <Generic External, class 0/0, rev 2.10/2.05, addr 2> on usbus7
umass1:  SCSI over Bulk-Only; quirks = 0x4000
umass1:10:1: Attached to scbus10
(probe0:umass-sim1:1:0:0): REPORT LUNS. CDB: a0 00 00 00 00 00 00 00 00 10 00 00
(probe0:umass-sim1:1:0:0): CAM status: SCSI Status Error
(probe0:umass-sim1:1:0:0): SCSI status: Check Condition
(probe0:umass-sim1:1:0:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command operation code)
(probe0:umass-sim1:1:0:0): Error 22, Unretryable error
da5 at umass-sim1 bus 1 scbus10 target 0 lun 0
da5: <Generic External 0205> Fixed Direct Access SPC-4 SCSI device
da5: Serial Number 353750545433585454202020
da5: 40.000MB/s transfers
da5: 152627MB (312581807 512 byte sectors)
da5: quirks=0x2<NO_6_BYTE>
Trying to mount it results in:

root@fb12hp:/dev# gpart list da5
Geom name: da5
modified: false
state: OK
fwheads: 255
fwsectors: 63
last: 312581806
first: 63
entries: 4
scheme: MBR
1. Name: da5s1
   Mediasize: 9437184000 (8.8G)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 1048576
   Mode: r0w0e0
   efimedia: HD(1,MBR,0x38654aae,0x800,0x1194000)
   rawtype: 7
   length: 9437184000
   offset: 1048576
   type: ntfs
   index: 1
   end: 18434047
   start: 2048
2. Name: da5s2
   Mediasize: 148494090240 (138G)
   Sectorsize: 512
   Stripesize: 0
   Stripeoffset: 2956984320
   Mode: r0w0e0
   efimedia: HD(2,MBR,0x38654aae,0x1582000,0x11497800)
   rawtype: 7
   length: 148494090240
   offset: 11546918912
   type: ntfs
   index: 2
   end: 312580095
   start: 22552576
1. Name: da5
   Mediasize: 160041885184 (149G)
   Sectorsize: 512
   Mode: r0w0e0

root@fb12hp:/dev# mount -t ntfs-3g /dev/da5s2 usb
mount: /dev/da5s2: Operation not supported by device

root@fb12hp:/mnt# mount -t ntfs-3g /dev/da5s1 usb
mount: /dev/da5s1: Operation not supported by device

Martin Paredes

Active Member

Reaction score: 25
Messages: 104

Is fuse loaded ? check with kldstat | grep fuse


mkdir /media/usb
/usr/local/bin/ntfs-3g /dev/da5s2 /media/usb


Aspiring Daemon

Reaction score: 15
Messages: 713

First, you need to install fusefs-ntfs by pkg and load it in loader.conf.
use dmesg to find the name of your external USB.
you can use gpart to show of partitioning of your USB.


Staff member

Reaction score: 7,763
Messages: 30,893

It can happen if the NTFS filesystem is dirty (at least the NTFS equivalent of a 'dirty' filesystem).



Reaction score: 1,181
Messages: 1,922

Correction: The native (Windows) implementation of NTFS is perfectly stable and good. Doesn't have many of the data safety features (that are for example available in ZFS), but it is a fine local file system. The problem lies with the reverse-engineered NTFS implementations that are found in OSes other than Windows, in particular in the ones that have to use fuse; those I would stay away from for data where reliability is important. Note that this observation is not specific to NTFS; quite a few other file system implementation that are based on things like reverse engineering should not be used in high-reliability production.



Reaction score: 1
Messages: 79

fuse loaded, ntfs installed, Linux and Win7/10 have no issues mounting the drive, holy wars skipped.