Debian – Writing on NTFS drives (on Debian Wheezy)

debianntfs

I am currently setting up a personal server on Debian Wheezy. My machine is an ARM based architecture (Cubox).

The problem appear when I want to mount and use my NTFS external hard drives.
The mount point is correct, I can access files and folders, I can change owner but it is impossible to write files even as root.

I mount my drives with "mount -o options source destination"
The command mount gives rw option for this mounted drive.

Best Answer

You need "fuse" and "ntfs-3g" for this to work. From what I read cubox has this in the kernel so you can try:

mount -t ntfs-3g /dev/sdb1 /mnt/ntfs/

Change the paths to suit.

Related Solutions

Unable to mount NTFS partition from user account

The ntfs-3g binaries must be set uid root in order for user mounting to work. And you need permission to the block device & mount point.

sudo chmod 1755 /sbin/mount.ntfs-3g /usr/bin/ntfs-3g
sudo chmod 666 /dev/sda2
sudo chmod 777 /media/Windows

(Note: these are the Debian locations, they may differ for Suse, so you will want to check that they are actually in those locations.)

You also need to have ntfs-3g version 1.2506 or later.

See here for more info:

http://www.tuxera.com/community/ntfs-3g-faq/#useroption

Advanced NTFS partition file recovery techniques for damaged drives (IO errors)

A few notes from my experience:

(the cause) If you hear an unusual sound during hd access attempts, and problems don't occur at (more or less) just random disk locations, then the root cause is most probably on the disk surface (not the electronics) - unfortunately, that's the sad scenario. If it were "just" the electronics, you might have had a chance to recover most or even all of your data.
(bad sectors) If you haven't already, search the web for the disk manufacturer's bootable diagnostic/recovery tool, download it, boot, run a deep test and let it try to remap bad sectors - that's the best among free methods. Note that bad sectors have a tendency to grow - so even if you manage to catch one chunk of your file after some 2314'th read attempt, chances are that those attempts just made nearby bad sectors grow, effectively decreasing the chances of recovering other parts of the file.
(recovering NTFS) Nothing can fix an NTFS filesystem as well as MS Windows native tools. If the NTFS image is not mountable (also make sure that you were trying to mount the partition, not the entire disk!), you can try things like testdisk under Linux, but if those fail, Windows' chkdisk can help. If you have Windows installed under a virtual machine, you can convert the raw image obtained from ddrescue to a format supported by that virtual machine (such as VDI or VMDK), add it to the VM and boot Windows in command-line mode to fix the filesystem. If you use VirtualBox, the command to convert such image is VBoxManage convertfromraw <filename> <outputfile> optionally with --format VDI|VMDK|VHD to obtain the specified output format.

Best Answer

Related Solutions

Unable to mount NTFS partition from user account

Advanced NTFS partition file recovery techniques for damaged drives (IO errors)

Related Question