Date: Tue, 10 Aug 2010 21:13:39 +0300 From: =?ISO-8859-1?Q?Ott_K=F6stner?= <OttK@zzz.ee> To: freebsd-questions@freebsd.org Subject: Re: problem mounting USB drive Message-ID: <4C6196D3.1080505@zzz.ee> In-Reply-To: <AANLkTikoQF9f5GPv5kQ9_Tqt2TfZjFeXgyq2W9gh8Gqd@mail.gmail.com> References: <4C61710C.7000602@zzz.ee> <4C617A5F.1010909@antonioshome.net> <4C61803C.3050007@zzz.ee> <AANLkTi=o5rx5pHTjtm9BXTudCFOKrpWuOJ=h5Bf3QNiv@mail.gmail.com> <4C618A3E.2050703@zzz.ee> <AANLkTikoQF9f5GPv5kQ9_Tqt2TfZjFeXgyq2W9gh8Gqd@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Adam Vande More wrote:
> On Tue, Aug 10, 2010 at 12:19 PM, Ott Köstner <OttK@zzz.ee> wrote:
>
>
>> Adam Vande More wrote:
>>
>>
>>> On Tue, Aug 10, 2010 at 11:37 AM, Ott Köstner <OttK@zzz.ee> wrote:
>>>
>>>
>>> # ls -ld /mnt/BACKUP
>>>
>>> ls: /mnt/BACKUP: Argument list too long
>>>
>>> Some directories are not big at all. My question is, is is a FreeBSD
>>> problem here, or is there something wrong with the drive (or am I doing
>>> something wrong here)?
>>> For some reason my BSD does not want to eat that drive...
>>>
>>>
>
> Apparently that's a known bug kern/136873
>
> you can try sysutils/ntfsprogs to mount it.
>
>
>
Thank You again,
but even this does not seem to help in the first place.
1) Installed ntfsprogs-2.0.0_1 from ports. After that:
# ntfsmount /dev/da0s1 /mnt/
fuse: failed to open fuse device: No such file or directory
fuse_mount failed.
Unmounting /dev/da0s1 (WD Passport)
I can see the drive information:
# ntfsinfo -m /dev/da0s1
Volume Information
Name of device: /dev/da0s1
Device state: 3
Volume Name: WD Passport
Volume State: 1
Volume Version: 3.1
Sector Size: 512
Cluster Size: 16384
Volume Size in Clusters: 9768020
[...snip...]
2) After that...
# ntfsfix /dev/da0s1
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
NTFS volume version is 3.1.
NTFS partition /dev/da0s1 was processed successfully.
3) Trying to mount again:
# ntfsmount /dev/da0s1 /mnt/
Volume is scheduled for check.
Please boot into Windows TWICE, or use the 'force' option.
NOTE: If you had not scheduled check and last time accessed this volume
using ntfsmount and shutdown system properly, then init scripts in your
distribution are broken. Please report to your distribution developers
(NOT to us!) that init scripts kill ntfsmount or mount.ntfs-fuse during
shutdown instead of proper umount.
Mount failed.
4) UHH!!!
greetings,
Ott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C6196D3.1080505>