[Fixed]VFat USB drive stuck in read only mode

Lel2000 · 2025-01-25 19:08:54

the drive is owned by my account, i made sure of that using chown
i tried using hdparm and modify the fstab file but no mater what it always tell me that the drive is in read only mode

i tried to use it on a windows computer and i can both read and write
i even tried it on a nintendo wii and it works fine

Last edited by Lel2000 (2025-02-20 17:23:27)

mpan · 2025-01-25 19:31:43

Hello.

There is some conflicting information and some things are missing.

What drive is it?
How can a FAT system by owned by your account, given FAT doesn’t contain ownership information?
What exactly did you chown? Provide the exact chown command you issued.
How is the drive read-only, if at the same time you were writing to it using chown?
How do you mount the filesystem?
The mention of fstab is a bit concerning: it shouldn’t even be in the picture. What exactly did you put in fstab?
What did you do with hdparm?

Lel2000 · 2025-01-25 20:09:46

dolphin says it is mounted on "/dev/sdd1"

i'm not sure myself but inspecting it with dolphin it says that my account is the owner of it

this it the comand that i used

chown -R "my user" /run/media/"my user"/"the usb drive"

and this to mount it

sudo mount /mnt/"the folder that i created"

and this is what i added in fstab

/dev/sdd1 /mnt/"the folder that i created" vfat user,r

this is the comand i used with hdparm but it gave me an error

sudo hdparm -r0 /run/media/"my user"/"the usb drive"

on another note, i formated another usb drive to fat and i can both read and write on it

V1del · 2025-01-25 20:18:32

if you create a folder in your root path and want the "user" option to do anything, you need to chown "the folder that you created" before mounting it there to your user.

As mentioned, chowning a VFAT drive has no effect, but since you're overwriting the defaults that udisks would handle on it's own by creating an fstab entry, you need to make sure it's mounted with the correct rights, also that "r" option in your fstab, does probably not help either. You want it to be rw. and you need to mount it with the mount command without sudo, fwiw for this to be in general more guaranteed the actual fstab option you're looking for is uid=/gid= where you add your user's primary uid and the gid you want the mounted drive to be occupied by.

Since all of this sounds kinda weird, what's your actual end goal here? Why is the default mount location of udisks /run/media/user a problem? Also what's the output of

mount

in [code][/code] tags?

Last edited by V1del (2025-01-25 20:24:22)

Lel2000 · 2025-01-25 21:30:59

i was trying to transfer files and create a folder directily from the usb drive

also after the first response i "reverted" the changes i did to the fstab file

anyway i'm gonna try to format the usb drive and see if it fixes it as soon as all the files get copied on my computer

seth · 2025-01-25 21:48:16

anyway i'm gonna try to format the usb drive and see if it fixes it as soon as all the files get copied on my computer

Spoiler: formatting the drive won't do anything about this.

Post the output of

mount

as V1del asked after mounting the "read only" key so we get a usable idea what you're doing there.

Lel2000 · 2025-01-25 21:58:28

output

WARNING: source write-protected, mounted read-only.

seth · 2025-01-25 22:01:45

That is most certainly not the complete output of "mount" (just that, not "mount foo bar" etc)

Lel2000 · 2025-01-25 22:10:08

here the full output, it just list the folder where i mounted it

mount: /run/media/"my user"/test: WARNING: source write-protected, mounted read-only.

Last edited by Lel2000 (2025-01-25 22:10:38)

V1del · 2025-01-25 22:57:07

it's not, just run mount without a path or anything, post the output of that.

mpan · 2025-01-26 01:00:10

Lel2000, it is very hard to help you. Put yourself in our perspective. Which is:

We know something weird is being done, but you don’t tell us what.
Apparently you tried to mitigate the problem. While reporting this, you only used single words: as if those were some standard methods everybody would recognize. They are not.
Those attempts seem to also be wrong, probably only making everything harder to untangle.
When explicitly asked to provide a particular output, you don’t.

I also asked you to tell us, what drive it is. The real reason behind the question is knowing only the kind of device we’re dealing with. But I’d much more prefer to make my own asessment of that, based on specific model.

Lel2000 · 2025-01-28 11:13:35

i never figured out what the problem was, but formatting the usb fixed the issue, i have now rw permission

seth · 2025-01-28 13:32:09

Neither did we as you avoided sharing any relevant details - chances are the FS was marked dirty for an unclean removal.

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Arch Linux

#1 2025-01-25 19:08:54

[Fixed]VFat USB drive stuck in read only mode

#2 2025-01-25 19:31:43

Re: [Fixed]VFat USB drive stuck in read only mode

#3 2025-01-25 20:09:46

Re: [Fixed]VFat USB drive stuck in read only mode

#4 2025-01-25 20:18:32

Re: [Fixed]VFat USB drive stuck in read only mode

#5 2025-01-25 21:30:59

Re: [Fixed]VFat USB drive stuck in read only mode

#6 2025-01-25 21:48:16

Re: [Fixed]VFat USB drive stuck in read only mode

#7 2025-01-25 21:58:28

Re: [Fixed]VFat USB drive stuck in read only mode

#8 2025-01-25 22:01:45

Re: [Fixed]VFat USB drive stuck in read only mode

#9 2025-01-25 22:10:08

Re: [Fixed]VFat USB drive stuck in read only mode

#10 2025-01-25 22:57:07

Re: [Fixed]VFat USB drive stuck in read only mode

#11 2025-01-26 01:00:10

Re: [Fixed]VFat USB drive stuck in read only mode

#12 2025-01-28 11:13:35

Re: [Fixed]VFat USB drive stuck in read only mode

#13 2025-01-28 13:32:09

Re: [Fixed]VFat USB drive stuck in read only mode

Board footer