Help mounting USB NTFS HD
Polytropon
freebsd at edvax.de
Sun Apr 15 15:18:59 UTC 2018
On Sun, 15 Apr 2018 10:06:31 -0400, Ernie Luzar wrote:
> ******************* trying to mount usb ntfs HD ***************
>
> FreeBSD 11.1-RELEASE-p8
> pkg install fusefs-ntfs
>
> HD is 1tb usb external HD formated using win10 as ntfs.
> Works without problems on win10
> HD has small triangle circuit board USB adapter connected to the HD sata
> ports.
>
>
> Get these console messages after plugging into FreeBSD PC usb port.
>
> /root >ugen0.2: <Western Digital My Book 1140> at usbus0
> umass0 on uhub2
> umass0: <MSC Bulk-Only Transport> on usbus0
> umass0: SCSI over Bulk-Only; quirks = 0x8000
> umass0:4:0: Attached to scbus4
> da0 at umass-sim0 bus 0 scbus4 target 0 lun 0
> da0: <WD My Book 1140 1016> Fixed Direct Access SPC-4 SCSI device
> da0: Serial Number 5A3747523953484653
> da0: 400.000MB/s transfers
> da0: 953837MB (244182272 4096 byte sectors)
> da0: quirks=0x2<NO_6_BYTE>
> ses1 at umass-sim0 bus 0 scbus4 target 0 lun 1
> ses1: <WD SES Device 1016> Fixed Enclosure Services SPC-4 SCSI device
> ses1: Serial Number 5A3747523953484653
> ses1: 400.000MB/s transfers
> ses1: SCSI-3 ENC Device
Looks good so far.
> /root >ls /dev | grep da0
> da0
> da0s1
To be expected.
> /root >gpart show /dev/da0
> => 63 244182209 da0 MBR (931G)
> 63 1985 - free - (7.8M)
> 2048 244169887 1 ntfs (931G)
> 244171935 10337 - free - (40M)
>
> /root >ntfsinfo -m -v /dev/da0s1
> Volume Information
> Name of device: /dev/da0s1
> Device state: 11
> Volume Name: new 1tb
> Volume State: 91
> Volume Flags: 0x0000
> Volume Version: 3.1
> Sector Size: 4096
> Cluster Size: 4096
> Index Block Size: 4096
> Volume Size in Clusters: 244169886
> MFT Information
> MFT Record Size: 4096
> MFT Zone Multiplier: 0
> MFT Data Position: 24
> MFT Zone Start: 0
> MFT Zone End: 30521238
> MFT Zone Position: 3
> Current Position in First Data Zone: 30521238
> Current Position in Second Data Zone: 0
> Allocated clusters 256 (0.0%)
> LCN of Data Attribute for FILE_MFT: 3
> FILE_MFTMirr Size: 4
> LCN of Data Attribute for File_MFTMirr: 81389962
> Size of Attribute Definition Table: 2560
> Number of Attached Extent Inodes: 0
> FILE_Bitmap Information
> FILE_Bitmap MFT Record Number: 6
> State of FILE_Bitmap Inode: 80
> Length of Attribute List: 0
> Number of Attached Extent Inodes: 0
> FILE_Bitmap Data Attribute Information
> Decompressed Runlist: not done yet
> Base Inode: 6
> Attribute Types: not done yet
> Attribute Name Length: 0
> Attribute State: 3
> Attribute Allocated Size: 30523392
> Attribute Data Size: 30521240
> Attribute Initialized Size: 30521240
> Attribute Compressed Size: 0
> Compression Block Size: 0
> Compression Block Size Bits: 0
> Compression Block Clusters: 0
> Free Clusters: 244117193 (100.0%)
>
> Up to this point everything looks good. The win10 ntfs HD is recognized
> as ntfs.
Correct.
> But mounting it gives errors
>
> /root >ntfs-3g /dev/da0s1 /mnt
> fuse: failed to open fuse device: No such file or directory
>
> /root >mount -t ntfs-3g /dev/da0s1 /mnt
> mount: /dev/da0s1: Operation not supported by device
>
> /root >ntfsfix /dev/da0s1
> Mounting volume... OK
> Processing of $MFT and $MFTMirr completed successfully.
> Checking the alternate boot sector... FAILED
> Error: Failed to fix the alternate boot sector
>
> Question: Can ntfs-3g mount USB connected external HD?
Yes, it can. Examine the error message closely: "failed to open
fuse device". Do you have
fuse_enable="YES"
in /boot/loader.conf - or kldload'ed the corresponding module?
I think this is what's missing.
By the way, your first mount attempt should (for diagnostic
purposes) always be read-only:
# ntfs-3g -r /dev/da0s1 /mnt
For reading files, this is sufficient anyway. ;-)
--
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
More information about the freebsd-questions
mailing list