From owner-freebsd-questions@freebsd.org Sun Apr 15 16:09:36 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2C7BDF9F011 for ; Sun, 15 Apr 2018 16:09:36 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B9DF06D1D5 for ; Sun, 15 Apr 2018 16:09:35 +0000 (UTC) (envelope-from luzar722@gmail.com) Received: by mail-it0-x22a.google.com with SMTP id b5-v6so8591091itj.1 for ; Sun, 15 Apr 2018 09:09:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-transfer-encoding; bh=VwrwyJ15IGVKMKXwcA1muhMSGO98lNVoi6ScP6fT9I8=; b=jdMswSPyjVR8tUuq+yMzyqg8kSn6D91MJGalzOsfT6TL6+fW70rTFus/R8EV47hNbE DIC+zpfosi5Q5sS1rcAQKIAYz6rW1TzvartNaQq7fb7rGA8cbDOqnHI5fBUuNBsVkVUm sR9uxWbahWMksoznj8OtKYLZRevUXuvtNYR2GX3E39ZQ1kY/2qPOqNTjg2y1n0FOjCHl G5e0BZyXe7MaC1SYf/W7tp5uUHdENl2KdrTZchI9l0OEZgqgBSvfofEK5bEgqmQ7IjRV VaVkmZwQ1VTQNVu6voFTw4ZYJPdzUQUMN2NwylaLFFmSiB+tLPaTubUYAb9mL8aM2l6B IsEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-transfer-encoding; bh=VwrwyJ15IGVKMKXwcA1muhMSGO98lNVoi6ScP6fT9I8=; b=Ha8by/mbxoA4/xjcVda+vykNQoieJ4B/q2VdRKBGTKuduwQxtJ8zBhDAAan7hkex9K EgxvKLz5YMTMV3P1Jak51tOY9KYM+HdfBotdHR7lNBtnxJx1PJzFFuMVfdsXRz2Zf1xm a/Qs71d1wI39t3ktqMd3ANQzjJsokBpEClmCB9pOtYOvzPWeKIwg8j9nBFHZOzq4uHzf hSzYzVixCGJrp4YVjJuFuWhgSSSAr5oXkQhNLrXwzffve9z6y0bh3aVw79FuMzHqT8UN 2fH86RejB2jElJs0CuwAJyJs5fmprUlbBJmqgb1hs/aG8RuZZRZxjyqHa6mUvt2m106D NRKA== X-Gm-Message-State: ALQs6tBqCMKPG9zmzNOaxTkox23DccbxdaWkdItO4CgEf3nnazv7iX2g n4aOIFEUo14F6MYsye3vIiyV1Q== X-Google-Smtp-Source: AIpwx4+B1LDk6+FXFgm7vzyz+jNWj03vL+/OOej2XLOEX+9WG1WMAmsl+kxKfDsg8WGMFHkE4rm7JA== X-Received: by 2002:a24:b60c:: with SMTP id g12-v6mr12746938itf.18.1523808575148; Sun, 15 Apr 2018 09:09:35 -0700 (PDT) Received: from [10.0.10.7] (cpe-65-25-48-31.neo.res.rr.com. [65.25.48.31]) by smtp.googlemail.com with ESMTPSA id w133-v6sm3858115itc.1.2018.04.15.09.09.26 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 15 Apr 2018 09:09:34 -0700 (PDT) Message-ID: <5AD3792B.70004@gmail.com> Date: Sun, 15 Apr 2018 12:09:15 -0400 From: Ernie Luzar User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Polytropon CC: "freebsd-questions@freebsd.org" Subject: Re: Help mounting USB NTFS HD References: <5AD35C67.9030208@gmail.com> <20180415171851.add2965a.freebsd@edvax.de> In-Reply-To: <20180415171851.add2965a.freebsd@edvax.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Apr 2018 16:09:36 -0000 Polytropon wrote: > 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: at usbus0 >> umass0 on uhub2 >> umass0: 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: 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 >> ses1 at umass-sim0 bus 0 scbus4 target 0 lun 1 >> ses1: 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. ;-) > > > If it was really a requirement to load fuse module you would think it would tell you to do so as message in the pkg install. But just to verify, I added it and rebooted. This changed nothing. Still got /root >ntfs-3g -o r /dev/da0s1 /mnt fuse: failed to open fuse device: No such file or directory