From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 748A2159C9B for ; Thu, 1 Aug 2024 15:48:35 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8D01C2BC069; Thu, 1 Aug 2024 15:48:29 +0000 (UTC) Received: from mail-yw1-x1132.google.com (mail-yw1-x1132.google.com [IPv6:2607:f8b0:4864:20::1132]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 4139C2BC034 for ; Thu, 1 Aug 2024 15:48:29 +0000 (UTC) Received: by mail-yw1-x1132.google.com with SMTP id 00721157ae682-65fe1239f12so48465117b3.0 for ; Thu, 01 Aug 2024 08:48:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1722527308; x=1723132108; darn=lists.gentoo.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=nWYGo4/TfBJ4MM3fbPLHomZaM1jiod8L5z+ZsgSx7ns=; b=laJ+IyfZnz35vNQbg8wBNJ44mwgNcRAsrJIp1bv2Q4vqSgjiTpTQU/YRCDp5/MgQw8 GYUgK2iMO+kyBRJmF7DMSv29Nj6zCqQETCgbuYhhQZBwD3fvwUfsx/XXqOuUtSb6tGUY LNfL9BxrA4WDDkvFnXmgahBnLJQ4oM4TtgOEQHJkMkzsuxh0GeCDkQkS/gjDQc7cTuj0 fFywwTNG8ILylRo7tJ/h+vFRVR7gRA6DCpoz4lyCsJI7JhYKSUEF/rqMbkzs+XngjeD0 03s6+PaH1Y3+d8lSpbmGQeEvMVGMLRSjOnam50DS3h6FV4fTI4ifCm23Tp6nW8M8rB9w OBXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722527308; x=1723132108; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=nWYGo4/TfBJ4MM3fbPLHomZaM1jiod8L5z+ZsgSx7ns=; b=FOlDHvOWnQxUnjEb2JNE1slpBshO7IKRFRYRgDYf6Cw3QBr3p4Gd90wULIgsB9b1JL K1uxH4Sa11aXtJqQpFBqy5tiv5qtDkYDq7YQHemjqw9VBEQMtFrE56bSKgHArzOL61F0 XVwnwaX+3QpUFoZhKxZ5clIw74AKsXXNqLCSpHKzH0BACI+eO+INfmyxCBAU0hZTxLmv b22S82q2R8mlZRVR3qQl3wk0RE6WERbezTK7FC9ckTkueU5PVPdjyJn7RffB2ikca5G7 G9USp8p67AHYltBSzx/oHT0juyjbgFmQSgMRBWCWKYg+MWaYoY+QZIpjARXEXEgUnQHV SvJw== X-Gm-Message-State: AOJu0Yzjm71TbFuReAuVmV25UrXwCEym6AFFjbYF9HSQFeNMfxAziJe+ 3riogrYkzpuLiU8LyaUCmG0RzfgLgli87glvb8Yd9RwGgwOX33C6naWFZxlNtqEIcu8S/gO35ra U1YMxgc7iTRU9ZWFjXfH4xrXlPGiXRytn X-Google-Smtp-Source: AGHT+IELmd78ySps3AEiCRo0pc1yrH27YRjSXoB3g1Y0z/+dDN95rwnjYvWpgsdUdjpzHwNAPNxPbw1XUHPBwJfVkYo= X-Received: by 2002:a0d:c9c6:0:b0:627:de5d:cf36 with SMTP id 00721157ae682-689645923ebmr4917467b3.39.1722527307878; Thu, 01 Aug 2024 08:48:27 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: <3311609.44csPzL39Z@rogueboard> <1896244.tdWV9SEqCh@rogueboard> In-Reply-To: <1896244.tdWV9SEqCh@rogueboard> From: Jacques Montier Date: Thu, 1 Aug 2024 17:48:16 +0200 Message-ID: Subject: Re: [gentoo-user] auto-mounting external usb disk problem To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary="0000000000004d5a12061ea12440" X-Archives-Salt: d5eb061b-a05c-4110-bfe7-2e0506504043 X-Archives-Hash: b7f5111174f9f4a3ecada0d5ce69eb13 --0000000000004d5a12061ea12440 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Le jeu. 1 ao=C3=BBt 2024 =C3=A0 15:26, Michael a= =C3=A9crit : > On Thursday, 1 August 2024 13:38:33 BST Jacques Montier wrote: > > Le jeu. 1 ao=C3=BBt 2024 =C3=A0 13:39, Michael a =C3=A9crit > : > > > On Thursday, 1 August 2024 11:24:29 BST Jacques Montier wrote: > > > > Le mer. 31 juil. 2024 =C3=A0 18:46, Michael a > > > > > > =C3=A9crit : > > > > > Looks like a possibility, if this started when you ran an update = of > > > > > the > > > > > desktop, or changed some cinnamon/gnome settings. Play around wi= th > > > > > 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 us= b > > > > > > 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 permission= s > 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=3D1058, > > idProduct=3D2621, bcdDevice=3D10.34 > > [ 1003.205682] usb 10-2: New USB device strings: Mfr=3D1, Product=3D2, > > SerialNumber=3D3 > > [ 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 filesyste= m > 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 betwe= en > > > 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 righ= ts > > restriction issue. > > > So, everything seems ok. > > Thank you so much for helping me. Cheers, -- Jacques --0000000000004d5a12061ea12440 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable



Le=C2=A0jeu. 1 ao=C3=BBt 2= 024 =C3=A0=C2=A015:26, Michael <confabulate@kintzios.com> a =C3=A9crit=C2=A0:
On Thursday, 1 August 2024 13:38:3= 3 BST Jacques Montier wrote:
> Le jeu. 1 ao=C3=BBt 2024 =C3=A0 13:39, Michael <confabulate@kintzios.com>= a =C3=A9crit :
> > On Thursday, 1 August 2024 11:24:29 BST Jacques Montier wrote: > > > Le mer. 31 juil. 2024 =C3=A0 18:46, Michael <confabulate@kintzios.com<= /a>> a
> >
> > =C3=A9crit :
> > > > Looks like a possibility, if this started when you ran = an update of
> > > > the
> > > > desktop, or changed some cinnamon/gnome settings.=C2=A0= Play around with
> > > > the
> > > > auto-
> > > > mount USB drive options, to see if it corrects itself.<= br> > > >
> > > Thanks Michael,
> > >
> > > I did not understand why an usb stick was automounted and no= t 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 ? Th= at'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 permis= sions so
> > accessing the fs via userspace is more restricted than FAT.=C2=A0= However, I
> > would
> > expect a different error, like "wrong filesystem type ...&qu= ot;.
> >
> > 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=3D1058,
> idProduct=3D2621, bcdDevice=3D10.34
> [ 1003.205682] usb 10-2: New USB device strings: Mfr=3D1, Product=3D2,=
> SerialNumber=3D3
> [ 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<= br> > [ 1003.207196] scsi host15: usb-storage 10-2:1.0
> [ 1004.268434] scsi 15:0:0:0: Direct-Access=C2=A0 =C2=A0 =C2=A0WD=C2= =A0 =C2=A0 =C2=A0 =C2=A0Elements 2621
>=C2=A0 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<= br> > [ 1008.464128]=C2=A0 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 fil= esystem on
WD Elements 2621, using udisksctl - this indicates there is no issue with t= he
core userspace function.

However, Gnome applications (e.g. Nemo) use GIO, which calls GVFS, which th= en
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 <= br> ought to lie within the Gnome related stack above that.


> Is it possible the owner/access rights of the ext4 fs has changed betw= een
> > 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, e= verything seems ok.

Thank you so much for helping me.

--0000000000004d5a12061ea12440--