On 2013-05-26 00:06, oldcpu wrote:
> Please, from where do you believe that is the appropriate mount command
> ? I have not tried a manual NTFS mount for some time, but last I recall
> such a command as you note is not correct. I do not believe the ‘mount’
> command will successfully guess/configure for an NTFS with no arguments.
> … or am I out of date ?

It does work, I’m trying right now. See, 3 methods:
Verification of the filesystem type:
> Telcontar:~ # file -s /dev/sde
> /dev/sde: x86 boot sector, Microsoft Windows XP MBR, Serial 0xc3072e18; partition 1: ID=0x7, active, starthead 1, startsector 2416, 31127184 sectors, code offset 0xc0
> Telcontar:~ # file -s /dev/sde1
> /dev/sde1: x86 boot sector, code offset 0x52, OEM-ID "NTFS ", sectors/cluster 8, reserved sectors 0, Media descriptor 0xf8, heads 255, hidden sectors 2416, dos < 4.0 BootSector (0x0)
> Telcontar:~ # fdisk -l /dev/sde
>
> Disk /dev/sde: 15.9 GB, 15938355200 bytes
> 256 heads, 40 sectors/track, 3040 cylinders, total 31129600 sectors
> Units = sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0xc3072e18
>
> Device Boot Start End Blocks Id System
> /dev/sde1 * 2416 31129599 15563592 7 HPFS/NTFS/exFAT
Testing mount directly:
> Telcontar:~ # md mnt
>
> TelTelcontar:~ # mount -v /dev/sde1 mnt
> mount: you didn't specify a filesystem type for /dev/sde1
> I will try type ntfs
> Telcontar:~ # ls mnt
> Curso de redes Documents
> Telcontar:~ #
> Telcontar:~ # mount | grep sde
> /dev/sde1 on /root/mnt type fuseblk (rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
> Telcontar:~ #
Despite the message, it mounted. Another method:
>
> Telcontar:~ # mount.ntfs -v /dev/sde1 mnt
> Telcontar:~ # mount | grep sde
> /dev/sde1 on /root/mnt type fuseblk (rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
> Telcontar:~ #
It mounted, actually using the same options (it even via fuse on all
methods)
> Telcontar:~ # umount mnt
> Telcontar:~ # mount.ntfs-3g -v /dev/sde1 mnt
> Telcontar:~ # mount | grep sde
> /dev/sde1 on /root/mnt type fuseblk (rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
> Telcontar:~ # umount mnt
> Telcontar:~ #
The second mount method would, time ago, have used the old ntfs, r/o,
driver, whereas the 3rd method would use ntfs-3g. The reason is this:
> Telcontar:~ # l /sbin/mount.ntfs*
> lrwxrwxrwx 1 root root 28 Sep 21 2010 /sbin/mount.ntfs -> /etc/alternatives/mount.ntfs*
> lrwxrwxrwx 1 root root 16 Feb 13 00:42 /sbin/mount.ntfs-3g -> /usr/bin/ntfs-3g*
> Telcontar:~ #
> Telcontar:~ # l /etc/alternatives/mount.ntfs
> lrwxrwxrwx 1 root root 19 Aug 12 2012 /etc/alternatives/mount.ntfs -> /sbin/mount.ntfs-3g*
> Telcontar:~ #
Why does it fail for the OP? Dunno.
However… it is known that if an NTFS filesystem is marked dirty, or
worse, if it is actually corrupted, it will not mount in Linux unless
you use an option to force it. In that case, it has to be mounted in
Windows and repaired there.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)