You are not logged in.

#1 2017-12-09 18:26:31

BacK|TracK
Member
Registered: 2017-12-09
Posts: 3

[Solved] NTFS-3G problem

Hi,

I have a problem with the NTFS file system permissions.

I had everything working fine, but I think after a windows update I ran out of permissions.
FluxBB bbcode test

I have NTFS-3G installed and I configured / etc / fstab.

/dev/sda1	/home/r0t3d/DATA	ntfs-3g	uid=r0t3d,gid=users,umask=0022,dmask=022,fmask=133	0	0

Could you help me?
Thank you

Last edited by BacK|TracK (2017-12-09 18:55:47)

Offline

#2 2017-12-09 18:31:17

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,466

Re: [Solved] NTFS-3G problem

1. You never told us what your actual problem was.
2. https://wiki.archlinux.org/index.php/Co … s_and_code
3. I have no idea what "after a windows update" means.

Offline

#3 2017-12-09 18:38:02

BacK|TracK
Member
Registered: 2017-12-09
Posts: 3

Re: [Solved] NTFS-3G problem

Scimmia wrote:

1. You never told us what your actual problem was.
2. https://wiki.archlinux.org/index.php/Co … s_and_code
3. I have no idea what "after a windows update" means.

The problem is, I do not have permissions to create or edit files on the ntfs disk.
And before the windows did the last upadate had full access to the disk.

Offline

#4 2017-12-09 18:42:16

Scimmia
Fellow
Registered: 2012-09-01
Posts: 11,466

Re: [Solved] NTFS-3G problem

So you actually updated *Windows* on a different partition and now it doesn't work? Did you actually shut down the system, and not use the hybrid shutdown Windows defaults to?

Post the actual permissions (from a CLI), as well as the output of `mount`.

Offline

#5 2017-12-09 18:55:22

BacK|TracK
Member
Registered: 2017-12-09
Posts: 3

Re: [Solved] NTFS-3G problem

Scimmia wrote:

So you actually updated *Windows* on a different partition and now it doesn't work? Did you actually shut down the system, and not use the hybrid shutdown Windows defaults to?

Post the actual permissions (from a CLI), as well as the output of `mount`.

Thank's for your time.
Yes my windows is on a different partition.

I already solved the problem, I had to boot to windows.
I think this happened because the partition got a flag that was not disassembled correctly, and it mounts read-only.


/solved

Last edited by BacK|TracK (2017-12-09 18:57:20)

Offline

Board footer

Powered by FluxBB