[arch-general] Udisks2: auto-mounts as read-only device/with wrong permissions
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I am currently having trouble mounting external devices with Gnome3. The corresponding Arch systems are up-to-date and free of old sysvinit components. Issue #1: Vfat-formated SD-cards are mounted as read-only into /run/media/$user/$device when they are plugged in. I am able to mount and write to them without trouble via console, e.g. with mout dev/sdxx /mnt. The corresponding dmesg output when pluging in and auto-mounting a card: \begin{code} [ 82.424085] usb 2-1.4: new high-speed USB device number 5 using ehci_hcd [ 82.577480] scsi7 : usb-storage 2-1.4:1.0 [ 82.577631] usbcore: registered new interface driver ums-realtek [ 83.580243] scsi 7:0:0:0: Direct-Access Generic- Multi-Card 1.00 PQ: 0 ANSI: 0 CCS [ 84.340304] sd 7:0:0:0: [sdc] 3862528 512-byte logical blocks: (1.97 GB/1.84 GiB) [ 84.341156] sd 7:0:0:0: [sdc] Write Protect is off [ 84.341162] sd 7:0:0:0: [sdc] Mode Sense: 03 00 00 00 [ 84.342015] sd 7:0:0:0: [sdc] No Caching mode page present [ 84.342023] sd 7:0:0:0: [sdc] Assuming drive cache: write through [ 84.345736] sd 7:0:0:0: [sdc] No Caching mode page present [ 84.345742] sd 7:0:0:0: [sdc] Assuming drive cache: write through [ 84.346998] sdc: sdc1 [ 84.349972] sd 7:0:0:0: [sdc] No Caching mode page present [ 84.349978] sd 7:0:0:0: [sdc] Assuming drive cache: write through [ 84.349982] sd 7:0:0:0: [sdc] Attached SCSI removable disk [ 85.036758] FAT-fs (sdc1): error, fat_get_cluster: invalid cluster chain (i_pos 0) [ 85.036765] FAT-fs (sdc1): Filesystem has been set read-only \end{code} The last 2 lines are not present when mounting the device via console (s. above). The interesting thing is that they are also mounted as writable, when using Gnome in fallback mode. Issue #2: Some (but obviously only some) USB sticks/external drives are auto-mounted as writable, but for root only. They can be mounted via console (mnt) without trouble, but it makes no difference if fallback mode is used or not or if ext4 or something else. As far as I understand everything right, Udisks2 performs mounting/unmounting tasks in Gnome right now, but I could not find any instructions how to configure it properly but postings articles about that most of the stuff in Udisks2 is hard-coded and the only way to change it is patching the source and re-compiling it. Does anyone in this list have similar issues and what can I do besides telling people I am supporting to use the console? It is also not possible to deactivate auto-mounting any more, at least not via gnome-session-properties, so a script wouldn't change the situation that much. Thanks, Jakob -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQIcBAEBAgAGBQJQ7CSrAAoJEOl7hkDId7YmB+EP/A7t3wcmJ1spTEU80a+FY1aX GsVFL1w+f3mpTR2F4ZLvWWcat9zUKSJ4YJhrktPGCG18hizznu58Gnvqf4FnnWzi jNun9DvyvbmWHHE3/JjZ43ZF3Z+kHpWiDW8u+12dG5m5igL4ibHHC8UI/uzVAtlS qEzPCiXETqR3sGYIoISg/BglZuGJSbCgnvVAHsHBaPH0+IryvPExItrXqgXrvzWz QtpaUOxEjWq858my3O/Zh4h/bR01UKqjXHYdFDISddJ/V5fq4rNZHhWkgJh9C66W HS84oXU/fg7gtSXjB9Q+yeokSU6aCiz9DFGMRzLU1xTw//f2+wFk+YrZrmhLJzxN 0VD7KkZtOgEj/kippJKObwz3iJw5/MGFnjD3Kxbwd+dtBAmez3Fwyaxi0wwSXt8v 2RNCnO33FJkT8a/QWdKb2DgzAPc+Y7dkFPf/Knd3Zz/zM21+H5xPwEdyD447Dsm0 amjF1lzJ0qjfvhD6g8YAo3a+CZ8+dYC7DqHo4GyXYiVwdz1yW/nB4ML7fOz8gXMS 3kT7OtnS87qP9Y1Kx1G/pKQpL0uDXANySLMXD/X4G9L3zEd2a6jRZ6cp4kdKPUj2 a7uHC+XRiQYhy4olGfnFOv2CymI0qoizYpktpPnh4JnLdMyX2t0VetrE5vZfwXBc sWI/cbBVjM4mN9Sk9D1E =yjpQ -----END PGP SIGNATURE-----
[ 85.036758] FAT-fs (sdc1): error, fat_get_cluster: invalid cluster chain (i_pos 0) [ 85.036765] FAT-fs (sdc1): Filesystem has been set read-only \end{code} The last 2 lines are not present when mounting the device via console (s. above). The interesting thing is that they are also mounted as writable, when using Gnome in fallback mode.
Jakob, Concerning the cluster chain problem, you can learn more about FAT at: http://en.wikipedia.org/wiki/File_Allocation_Table and possibly fix the error with: pacman -S dosfstools man dosfsck Greetings, Olivier ________________________________ CONFIDENTIALITY : This e-mail and any attachments are confidential and may be privileged. If you are not a named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose or store or copy the information in any medium.
[ 85.036758] FAT-fs (sdc1): error, fat_get_cluster: invalid cluster chain (i_pos 0) [ 85.036765] FAT-fs (sdc1): Filesystem has been set read-only \end{code} The last 2 lines are not present when mounting the device via console (s. above). The interesting thing is that they are also mounted as writable, when using Gnome in fallback mode.
Here is another interesting point concerning your observation in the difference of mount behavior: From fs/fat/misc.c in kernel source code: /* * fat_fs_error reports a file system problem that might indicate fa data * corruption/inconsistency. Depending on 'errors' mount option the * panic() is called, or error message is printed FAT and nothing is done, * or filesystem is remounted read-only (default behavior). * In case the file system is remounted read-only, it can be made writable * again by remounting it. */ ________________________________ CONFIDENTIALITY : This e-mail and any attachments are confidential and may be privileged. If you are not a named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose or store or copy the information in any medium.
participants (2)
-
Jakob Herrmann
-
LANGLOIS Olivier PIS -EXT