Re: Problem mounting new Sandisk 1TB USB drive

On 10/01/2024 20:03, Gary Aitken wrote:
> On 1/10/24 11:01, Souji Thenria wrote:
>>> # mount -t ntfs-3g /dev/da0s1 /mnt/memstick
>>> mount: /dev/da0s1: Invalid fstype: Invalid argument
>>> # ntfs-3g /dev/da0s1 /mnt/memstick
>>> 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?
>>> # ntfs-3g /dev/da0 /mnt/memstick
>>> NTFS signature is missing.
>>> Failed to mount '/dev/da0': Invalid argument
>>> The device '/dev/da0' 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?
>>>
>>> -o debug shows nothing additional
>>
>>
>> Can you try to mount the drive using:
>> 'ntfs-3g /dev/da0s1 /mnt/memstick'
>>
>> If I remember correctly, using the mount command with ntfs-3g did not
>> work for me in the past while using the command directly worked...
>
> Thanks; already tried that, same results (2nd command given above)
>
> 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.
>
> However, something, I assume the android phone, automagically set
> up a bunch of directories, which are empty: Android, AudioBooks,
> DCIM, Pictures, Videos, etc.
>
> Doesn't seem like any of that should have affected the formatting,
> Although at some point after I can get it to mount I'd like to
> know how to prevent the auto directory setup from happening.
>
> Gary

I suspect you don't have the FUSE driver compiled into the kernel (if 
this is even possible).

Try "kldload fusefs" and then try ntfs-g3 again.

Regards, Frank.