Member Avatar for Eduardo

Hello all,

I can't write in VFAT ou NTFS partition . I really can do it just as ROOT.

HELP.

SUSe 9x

Thanks in advance!!!
Eduardo :?:

  • 3 Contributors
  • 3 Replies
  • 200 Views
  • 1 Week Discussion Span
  • Latest Post Latest Post by Zachery

Dani AI

Generated

Short, practical update for the thread (adding to ’s discovery and the cautions from and ).

VFAT/FAT32: FAT family filesystems do not implement POSIX permissions — the kernel applies a single owner/group and permission mask at mount time, so “write only as root” almost always means the partition was mounted with root ownership or restrictive mask. Set the owner/group and the mask when mounting (or in /etc/fstab) so a normal user can write. See the VFAT mount-options reference for details. (docs.kernel.org)

NTFS: modern Linux has two common options. The historical, widely used userspace driver is ntfs-3g (recommended where packaged), which gives reliable read/write and user-mapping control; more recently a kernel driver called ntfs3 exists and provides native support with different behavior. For reliable write-access from a non-root account, install the distribution package that provides NTFS write support (ntfs-3g or the distro’s supported ntfs driver) and mount with uid=.../gid=... (or the driver-appropriate options). (wiki.debian.org)

Important safety note (why / were cautious): if Windows shut down via hibernation or Fast Startup the NTFS volume is left in an unsafe/“hibernated” state — mounting it read-write from Linux risks data loss. Always do a full Windows shutdown or disable Fast Startup before writing; if you can’t boot Windows, ntfsfix can sometimes clear the flag but is not a substitute for chkdsk and can be risky. (learn.microsoft.com)

Quick actionable checklist

  • Find your numeric UID/GID with id.
  • For a VFAT mount, pick uid=..., gid=... and an appropriate umask/fmask/dmask so files are owned by your user (example shown below).
  • For NTFS, install the distro ntfs package (often ntfs-3g) and mount with uid/gid or the driver’s permission options.
  • If a partition refuses read/write: check mount output and dmesg for messages, ensure Fast Startup/hibernation is off in Windows, and avoid forcing mounts unless you understand the risk.

Example (adjust UID/GID and device/point — do not paste these verbatim into a production fstab without testing):

id                # discover your UID/GID
sudo mount -t vfat -o uid=1000,gid=1000,umask=0002 /dev/sdXN /mnt/windows
sudo mount -t ntfs-3g -o uid=1000,gid=1000 /dev/sdYN /mnt/ntfs

This keeps ’s approach (mount-time masks) but adds: use uid/gid mapping for predictable ownership, prefer the supported NTFS driver on your distro, and never write to a hibernated Windows volume. (docs.kernel.org)

Recommended Answers

All 3 Replies

Member Avatar for Eduardo

Yes,

I think I already have the anwser!

I found it at

Just put in /etc/fstab, some thing like it:

/dev/hda1 /mnt/c vfat defaults,umask=0000 0 0

Where "umask=0000" will permit in octal format to all users to read, write and run.

or

/dev/hda1 /mnt/c vfat defaults,gid=610,umask=0707 0 0

If you want that only users from group 610 be able to read, and execute (not write):

use the table, below to reference the permissions:

M | R W X
-------------
0 | * * *
1 | * * -
2 | * - *
3 | * - -
4 | - * *
5 | - * -
6 | - - *
7 | - - -


Good luck !

Eduardo

Member Avatar for linux-tech

NTFS and Fat32 shouldn't be written to under the Linux FS anyways, as they're not exactly linux native FS systems. While it CAN be done (as you mentioned, root can do anything), it shouldn't be done, as that is THE quickest way to screw up a partition :)

Member Avatar for Zachery

FAT32 is safer to write into overall.. being a non advanced paritioning system, but I'd avoid messing with NTFS at all costs.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.