[opensuse-support] A Leap 15.1 machine with KDE automounts FAT32 usb drives read-only
Hi all, I just installed a fresh Leap 15.1 system with KDE and btrfs. Nothing special, I have done this on countless machines. This particular install has a wired issue: When I plug in in USB-drives (formatted with FAT32), KDE (through Dolphin) mounts them read-only (as I can see in the output of `mount`). Other Leap 15.1 systems mount the same sticks writeable without issues. If I mount the USB drives through a shell (as root) on the "broken" system, I can also write to them without an issue. Any idea what is going on here? Best regards, Sebastian -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org
On 20/04/2020 13.07, Sebastian M. Ernst wrote:
Hi all,
I just installed a fresh Leap 15.1 system with KDE and btrfs. Nothing special, I have done this on countless machines.
This particular install has a wired issue: When I plug in in USB-drives (formatted with FAT32), KDE (through Dolphin) mounts them read-only (as I can see in the output of `mount`). Other Leap 15.1 systems mount the same sticks writeable without issues. If I mount the USB drives through a shell (as root) on the "broken" system, I can also write to them without an issue.
Any idea what is going on here?
An USB stick may be mounted read only if the system thinks it is dirty. Ie, needs fsck. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Hi Carlos, thanks for the help. Multiple Leap 15.1 systems do different things for the *exact same USB sticks*. I.e. at least two machines with Leap 15.1 write onto those sticks just fine. Just ONE machine with a fresh install (with all updates) of Leap 15.1 does not want to write to the stick (unless I mount them with super user privileges from the CLI). Why would one system permanently think that all sticks are dirty while all other (identical) systems do not care? (Just tested. `fsck` does not make a difference.) Best regards, Sebastian Am 20.04.20 um 13:11 schrieb Carlos E. R.:
On 20/04/2020 13.07, Sebastian M. Ernst wrote:
Hi all,
I just installed a fresh Leap 15.1 system with KDE and btrfs. Nothing special, I have done this on countless machines.
This particular install has a wired issue: When I plug in in USB-drives (formatted with FAT32), KDE (through Dolphin) mounts them read-only (as I can see in the output of `mount`). Other Leap 15.1 systems mount the same sticks writeable without issues. If I mount the USB drives through a shell (as root) on the "broken" system, I can also write to them without an issue.
Any idea what is going on here?
An USB stick may be mounted read only if the system thinks it is dirty. Ie, needs fsck.
On 20/04/2020 13.55, Sebastian M. Ernst wrote:
Hi Carlos,
thanks for the help.
Multiple Leap 15.1 systems do different things for the *exact same USB sticks*. I.e. at least two machines with Leap 15.1 write onto those sticks just fine. Just ONE machine with a fresh install (with all updates) of Leap 15.1 does not want to write to the stick (unless I mount them with super user privileges from the CLI).
Why would one system permanently think that all sticks are dirty while all other (identical) systems do not care?
(Just tested. `fsck` does not make a difference.)
Does it say the stick is clean? By default, fsck does no repair. I say this because it happened to me recently on 15.1. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Hi Carlos,
(Just tested. `fsck` does not make a difference.)
Does it say the stick is clean? By default, fsck does no repair.
I say this because it happened to me recently on 15.1.
this is getting bizarre. One stick was not dirty but was still causing this issue. I found another one stick that was dirty (and also causing this issue). Repaired the dirty one, now both mount RW. I am not getting it ... Thanks for the help. Solved for now I guess. But why would some Leap 15.1 systems mount a dirty FAT32 FS in RW mode then in the first place? This is highly inconsistent ... Best regards, Sebastian
On 20/04/2020 14.12, Sebastian M. Ernst wrote:
Hi Carlos,
(Just tested. `fsck` does not make a difference.)
Does it say the stick is clean? By default, fsck does no repair.
I say this because it happened to me recently on 15.1.
this is getting bizarre. One stick was not dirty but was still causing this issue. I found another one stick that was dirty (and also causing this issue). Repaired the dirty one, now both mount RW. I am not getting it ...
Thanks for the help. Solved for now I guess.
But why would some Leap 15.1 systems mount a dirty FAT32 FS in RW mode then in the first place? This is highly inconsistent ...
Same desktop? I would look at the logs. Yes, it is curious. Last time I used "fsck -f -y /dev/whatever". But usually "fsck -a ..." -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
Hi Carlos,
But why would some Leap 15.1 systems mount a dirty FAT32 FS in RW mode then in the first place? This is highly inconsistent ...
Same desktop?
Three physical machines here, each with a Leap 15.1 install, each with KDE. One cares about the dirty state, two do not.
I would look at the logs. Yes, it is curious.
Just looked at ´journalctl -a | grep -i sdb` (i.e. my sticks) on all systems. Two are showing no errors. The system in question however does: Multiple entries of `invalid cluster chain` per mount, coming from `fat_get_cluster`, triggering an RO mount. The strange thing though is that the mounts from the command line do not exhibit those errors.
Last time I used "fsck -f -y /dev/whatever". But usually "fsck -a ..."
Just did `fsck.vfat /dev/sdb1` and went through all messages manually. Sebastian
participants (2)
-
Carlos E. R. -
Sebastian M. Ernst