Le jeu. 1 août 2024 à 15:26, Michael <confabul...@kintzios.com> a écrit :
> On Thursday, 1 August 2024 13:38:33 BST Jacques Montier wrote: > > Le jeu. 1 août 2024 à 13:39, Michael <confabul...@kintzios.com> a écrit > : > > > On Thursday, 1 August 2024 11:24:29 BST Jacques Montier wrote: > > > > Le mer. 31 juil. 2024 à 18:46, Michael <confabul...@kintzios.com> a > > > > > > écrit : > > > > > Looks like a possibility, if this started when you ran an update of > > > > > the > > > > > desktop, or changed some cinnamon/gnome settings. Play around with > > > > > the > > > > > auto- > > > > > mount USB drive options, to see if it corrects itself. > > > > > > > > Thanks Michael, > > > > > > > > I did not understand why an usb stick was automounted and not WD usb > > > > > > drive. > > > > > > > I saw the one was fat32 formatted and WD ext4. > > > > So, i formatted fat32 another empty WD drive and it worked ! > > > > Last version of cinnamon could not automount ext4 drive ? That's > weird. > > > > > > > > Well, it's not so important and in can deal with it. > > > > > > > > Cheers, > > > > > > > > Jacques > > > > > > Unlike ext4, the FAT filesystem does not support Unix file permissions > so > > > accessing the fs via userspace is more restricted than FAT. However, I > > > would > > > expect a different error, like "wrong filesystem type ...". > > > > > > What do you get in your logs when your run: > > > > > > ~ $ udisksctl mount -b /dev/sdXx > > > > > > where Xx are the device and partition numbers? > > > > I get this : > > > > My external usb disk is labelled SAUVEGARDE. > > > > $ udisksctl mount -b /dev/sdf1 > > Mounted /dev/sdf1 at /run/media/jacques/SAUVEGARDE > > > > $ dmesg > > [ 1003.189856] usb 10-2: new SuperSpeed USB device number 5 using > xhci_hcd > > [ 1003.205671] usb 10-2: New USB device found, idVendor=1058, > > idProduct=2621, bcdDevice=10.34 > > [ 1003.205682] usb 10-2: New USB device strings: Mfr=1, Product=2, > > SerialNumber=3 > > [ 1003.205688] usb 10-2: Product: Elements 2621 > > [ 1003.205709] usb 10-2: Manufacturer: Western Digital > > [ 1003.205714] usb 10-2: SerialNumber: 575837324139315041324831 > > [ 1003.207086] usb-storage 10-2:1.0: USB Mass Storage device detected > > [ 1003.207196] scsi host15: usb-storage 10-2:1.0 > > [ 1004.268434] scsi 15:0:0:0: Direct-Access WD Elements 2621 > > 1034 PQ: 0 ANSI: 6 > > [ 1004.268645] sd 15:0:0:0: Attached scsi generic sg7 type 0 > > [ 1004.271067] sd 15:0:0:0: [sdf] Spinning up disk... > > [ 1005.291638] ....ready > > [ 1008.461012] sd 15:0:0:0: [sdf] 3906963456 512-byte logical blocks: > (2.00 > > TB/1.82 TiB) > > [ 1008.461494] sd 15:0:0:0: [sdf] Write Protect is off > > [ 1008.461502] sd 15:0:0:0: [sdf] Mode Sense: 47 00 10 08 > > [ 1008.462001] sd 15:0:0:0: [sdf] No Caching mode page found > > [ 1008.462009] sd 15:0:0:0: [sdf] Assuming drive cache: write through > > [ 1008.464128] sdf: sdf1 > > [ 1008.464219] sd 15:0:0:0: [sdf] Attached SCSI disk > > [ 1023.783260] EXT4-fs (sdf1): mounted filesystem > > e26e8fef-8c48-4ad3-8258-10cb8fb47f81 r/w with ordered data mode. Quota > > mode: none. > > The above shows user 'jacques' has no problem mounting the ext4 filesystem > on > WD Elements 2621, using udisksctl - this indicates there is no issue with > the > core userspace function. > > However, Gnome applications (e.g. Nemo) use GIO, which calls GVFS, which > then > calls udisksctl to do the mounting/unmounting - not sure if FUSE is also > brought into this mix as if the above stack of virtual fs libraries are > not > enough. > > In any case, since you have proven udisks works as it should, the problem > ought to lie within the Gnome related stack above that. > > > > Is it possible the owner/access rights of the ext4 fs has changed between > > > the time when it worked and now? > > > > Well, i really don't know... > > > > -- > >> Jacques > > > > Since udisks works, this is not related to a change in a fs access rights > > restriction issue. > > > So, everything seems ok. > > Thank you so much for helping me. Cheers, -- Jacques
