From nobody Wed Jan 10 23:42:22 2024 X-Original-To: freebsd-questions@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4T9PVG2FjDz56VBD for ; Wed, 10 Jan 2024 23:42:30 +0000 (UTC) (envelope-from freebsd@dreamchaser.org) Received: from ns.dreamchaser.org (ns.dreamchaser.org [66.109.141.57]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (P-256) client-digest SHA256) (Client CN "discoveriesinwood.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T9PVF5rchz49tW for ; Wed, 10 Jan 2024 23:42:29 +0000 (UTC) (envelope-from freebsd@dreamchaser.org) Authentication-Results: mx1.freebsd.org; none Received: from [192.168.151.122] (breakaway.dreamchaser.org [192.168.151.122]) by ns.dreamchaser.org (8.16.1/8.16.1) with ESMTP id 40ANgMdH012272; Wed, 10 Jan 2024 16:42:22 -0700 (MST) (envelope-from freebsd@dreamchaser.org) Message-ID: <1d60d68a-3569-4054-a460-41c5dd422a42@dreamchaser.org> Date: Wed, 10 Jan 2024 16:42:22 -0700 List-Id: User questions List-Archive: https://lists.freebsd.org/archives/freebsd-questions List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-questions@freebsd.org X-BeenThere: freebsd-questions@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Reply-To: freebsd@dreamchaser.org Subject: Re: Problem mounting new Sandisk 1TB USB drive Content-Language: en-US To: Polytropon Cc: Souji Thenria , FreeBSD Mailing List References: <746cd0fe-9de8-414b-8b5d-7030d423fa7f@dreamchaser.org> <85758e7a-f9bb-4568-a863-53c2439045ce@souji-thenria.net> <20240110233304.7a8b7f10.freebsd@edvax.de> From: Gary Aitken In-Reply-To: <20240110233304.7a8b7f10.freebsd@edvax.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: inspected by milter-greylist-4.6.4 (ns.dreamchaser.org [192.168.151.101]); Wed, 10 Jan 2024 16:42:23 -0700 (MST) for IP:'192.168.151.122' DOMAIN:'breakaway.dreamchaser.org' HELO:'[192.168.151.122]' FROM:'freebsd@dreamchaser.org' RCPT:'' X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.4 (ns.dreamchaser.org [192.168.151.101]); Wed, 10 Jan 2024 16:42:23 -0700 (MST) X-Rspamd-Queue-Id: 4T9PVF5rchz49tW X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:21947, ipnet:66.109.128.0/19, country:US] On 1/10/24 15:33, Polytropon wrote: > On Wed, 10 Jan 2024 13:03:28 -0700, Gary Aitken wrote: >> The stick has been plugged into an android phone since it was first >> tried on the fbsd and ubuntu systems, before I installed ntfs-3g. >> Mounting it on ubuntu, I see two suspect files, 'Install SanDisk Software.dmg' and 'Install SanDisk Software.exe', plus a pdf that >> says to run the appropriate file to get "valuable software..." >> I'm thinking / hoping neither of those got automagically run, since >> it's never been plugged into a microsoft or mac system. I've since >> renamed them away. > > This observation leads to the following assumption: > > The stick is actually pre-formatted with exFAT. > > Problem here: exFAT disguises itself as an NTFS partition, > but it does not have NTFS metadata and content, so ntfs-3g > cannot mount it, even though tools like gpart or fdisk > show a NTFS partition. > > So here is what you should check: > > 1. /boot/loader.conf contains: > > fuse_load="YES" /boot/loader.conf.local: # added and commented out amdtemp; no longer needed? #amdtemp="YES" verbose_loading="YES" # Enable FUSE functionality for exfat filesystem mounting fuse_enable="YES" fuse_load="YES" > 2. Mount device manually, read-only, perform checks, then > unmount again: > > # mount.exfat -o ro /dev/da0s1 /mnt/memstick > # df -f /mnt/memstick > # ls -R /mnt/memstick > # umount /mnt/memstick What was the intent of the df -f (-f => invalid option)? That seemed to work, although it was properly umounted on a ubuntu system; or at least I think so. It was automagically mounted when plugged in, not written to, and then sync ; umount. A series of mount.exfat / umount / mount.exfat on fbsd seemed to clear it up. > NB: mount.exfat does not have a manpage or help option. $ apropos exfat mount.exfat-fuse(8) - mount an exFAT file system >> However, something, I assume the android phone, automagically set >> up a bunch of directories, which are empty: Android, AudioBooks, >> DCIM, Pictures, Videos, etc. > > It wouldn't probably have been able to do this if the > stick was formatted with NTFS... thanks > Why don't you simply run newfs on the stick, with the > filesystem *you* _want_ to use? You can use UFS it you > want to, works perfectly well. ;-) I want to be able to read it from an android phone, and I was/am concerned reformatting may make it unreadable by the phone. It appears the problem was not having fusefs.ko loaded, but continuing trying ntfs-3g instead of retrying mount.exfat. So all is well, thanks, but one question not addressed: Given that FUSE_ENABLE="YES" is present in rc.conf, why is kldlist="fusefs" still needed? Thanks all, Gary