Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #235457 > unrolled thread

apt error not understood

Started byghe2001 <ghe2001@pm.me>
First post2021-05-22 18:10 +0200
Last post2021-05-22 20:50 +0200
Articles 5 — 4 participants

Back to article view | Back to linux.debian.user

Contents

  apt error not understood ghe2001 <ghe2001@pm.me> - 2021-05-22 18:10 +0200
    Re: apt error not understood Darac Marjal <mailinglist@darac.org.uk> - 2021-05-22 19:40 +0200
      Re: apt error not understood ghe2001 <ghe2001@protonmail.com> - 2021-05-22 21:50 +0200
    Re: apt error not understood Greg Wooledge <greg@wooledge.org> - 2021-05-22 20:30 +0200
      Re: apt error not understood ghe2001 <ghe2001@protonmail.com> - 2021-05-22 20:50 +0200

#235457 — apt error not understood

Fromghe2001 <ghe2001@pm.me>
Date2021-05-22 18:10 +0200
Subjectapt error not understood
Message-ID<ChCml-UQ-1@gated-at.bofh.it>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Buster everywhere, latest update.

I update/upgrade using apt on 3 different computers (SuperMicro desktop, Dell laptop, Raspberry Pi cute thing). Sample from a few minutes ago, on the desktop:

root@sbox:~# apt update
Hit:1 http://security.debian.org/debian-security buster/updates InRelease
Hit:2 http://deb.debian.org/debian buster InRelease
Get:3 http://deb.debian.org/debian buster-updates InRelease [51.9 kB]
Get:4 http://deb.debian.org/debian buster-backports InRelease [46.7 kB]
Fetched 98.6 kB in 2s (52.2 kB/s)
...
Error: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit -.mount is masked.
...
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.

And all seems to have worked -- when update says there are upgrades available, it asks if I want them, then downloads and installs properly, but the same error message is displayed.  I've been a Debian user for some 15 years, and I've never seen an error from dpkg, apt, apt-get, synaptic, or aptitude.  Until a few weeks ago.  On all my computers, except the 'Pi (also systemd).  I don't know what makes this happen or even what it means (a bent apt update?  a bent systemd update?).

Thoughts?  Howtos?

--
Glenn English


-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wsBzBAEBCAAGBQJgqSfUACEJEObKK1bRaqt3FiEExEbtoeXBeE9fruv35sor
VtFqq3dCbQf+OJ1Yykq72GKb5ElXOZqHbrM8HcjNDcmPfaUznzeROA/Zj7TE
sIJFxYIyQYGCOX5UCyx38Cwxdk5UzPU7c/HU+ZAIJDnVRLt14bpUBpHGkSMp
l3GgUeiRmTLgfw3yCrZH1Na34g7LkCrp7IrcDFJXIzMymgubJxzBYbycyxNx
OUB40tC2kdGlt3XiHOhSQg9KLaUqPuyHA8VZBP/22mn9TI4uWDJo4SWzgqe3
V9EqiWbHceMQRxBOU8P2rmsC5ZA3s6fLxCY5SllJF4DZz7lrJ9Az5/OO5krB
QOulZbOnY04lR2hyyviqSr+tTnIzzqZU91u3wzVssYTwXPNmUTE2rQ==
=+Itr
-----END PGP SIGNATURE-----

[toc] | [next] | [standalone]

#235458

FromDarac Marjal <mailinglist@darac.org.uk>
Date2021-05-22 19:40 +0200
Message-ID<ChDLs-1La-7@gated-at.bofh.it>
In reply to#235457

[Multipart message — attachments visible in raw view] — view raw

On 22/05/2021 16:48, ghe2001 wrote:
> Buster everywhere, latest update.
>
> I update/upgrade using apt on 3 different computers (SuperMicro
> desktop, Dell laptop, Raspberry Pi cute thing). Sample from a few
> minutes ago, on the desktop:
>
> root@sbox:~# apt update
> Hit:1 http://security.debian.org/debian-security buster/updates InRelease
> Hit:2 http://deb.debian.org/debian buster InRelease
> Get:3 http://deb.debian.org/debian buster-updates InRelease [51.9 kB]
> Get:4 http://deb.debian.org/debian buster-backports InRelease [46.7 kB]
> Fetched 98.6 kB in 2s (52.2 kB/s)
> ...
> Error: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit -.mount
> is masked.

*.mount files are systemd representations of mount points. Sometimes
they're autogenerated from /etc/fstab (that is, fstab is still a
first-class place to configure mount points), but they might also be in
the usual systemd locations such as /etc/systemd/system

Now you can't name the mount files exactly after the mount points
(mostly because / isn't valid in file names), so systemd uses an
escaping mechanism

$ systemd-escape --unescape - /

So, this is a mount file for the root directory.

Now, what does it mean that the unit is masked? Here, you need to look
at the man page for "systemctl", in the description for the "is-enabled"
subcommand. "Masked" means "Completely disabled, so that any start
operation on it fails". Masking may be done either by the system, or the
administrator, but it basically means that systemd won't be able to
mount your root directory (however, that's a moot point as userspace
never mounts the root directory; that's the kernel's job :)

In summary, I'd say it's a strange error, but harmless.


> ...
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> All packages are up to date.
>
> And all seems to have worked -- when update says there are upgrades
> available, it asks if I want them, then downloads and installs
> properly, but the same error message is displayed.  I've been a Debian
> user for some 15 years, and I've never seen an error from dpkg, apt,
> apt-get, synaptic, or aptitude.  Until a few weeks ago.  On all my
> computers, except the 'Pi (also systemd).  I don't know what makes
> this happen or even what it means (a bent apt update?  a bent systemd
> update?).
>
> Thoughts?  Howtos?
>
>

[toc] | [prev] | [next] | [standalone]

#235494

Fromghe2001 <ghe2001@protonmail.com>
Date2021-05-22 21:50 +0200
Message-ID<ChFNf-2Uf-3@gated-at.bofh.it>
In reply to#235458
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256






‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, May 22, 2021 11:29 AM, Darac Marjal <mailinglist@darac.org.uk> wrote:

> *.mount files are systemd representations of mount points. Sometimes they're autogenerated from /etc/fstab (that is, fstab is still a first-class place to configure mount points), but they might also be in the usual systemd locations such as /etc/systemd/system
>
> Now you can't name the mount files exactly after the mount points (mostly because / isn't valid in file names), so systemd uses an escaping mechanism
>
> $ systemd-escape --unescape -
> /
>
> So, this is a mount file for the root directory.
>
> Now, what does it mean that the unit is masked? Here, you need to look at the man page for "systemctl", in the description for the "is-enabled" subcommand. "Masked" means "Completely disabled, so that any start operation on it fails". Masking may be done either by the system, or the administrator, but it basically means that systemd won't be able to mount your root directory (however, that's a moot point as userspace never mounts the root directory; that's the kernel's job :)
>
> In summary, I'd say it's a strange error, but harmless.

Thanks, Darac.  Now I know it's systemd, not apt.

  On the desktop, 'systemctl list-devices' says, among other things:

● -.mount                                                                             masked active mounted   Root Mount              
● amandaDisk.mount                                                                    masked active mounted   /amandaDisk             
● blackHole.mount                                                                     masked active mounted   /blackHole              
● boot.mount                                                                          masked active mounted   /boot                   
  dev-hugepages.mount                                                                 loaded active mounted   Huge Pages File System  
  dev-mqueue.mount                                                                    loaded active mounted   POSIX Message Queue File
  proc-sys-fs-binfmt_misc.mount                                                       loaded active mounted   Arbitrary Executable File
● raid1Array.mount                                                                    masked active mounted   /raid1Array             

Why is systemd trying to mount /?  /'s already mounted or systemd couldn't run, not so? And doesn't that say / is mounted and active?  And completely disabled (masked)?  Isn't active/masked a contradiction?

All of those with the dots are in fstab.  / on the desktop is an nvme, if that makes any difference.  On the laptop it's a vanilla SATA. 

Desktop /boot is a thumb-drive because the elderly BIOS will boot USB and the Debian startup software knows how to read an nvme.

Sorry to not understand systemd and its buds very well at all.

--
Glenn English


-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wsBzBAEBCAAGBQJgqV5zACEJEJ/XhjGCrIwyFiEELKJzD0JScCVjQA2Xn9eG
MYKsjDJpyQf+J4q+UFK+//WiEi59f1YUFbndUz5ayjfMsj1uURj7/R59zxEw
qySvh/Lg51pUkAgTh7IvnCwtE2WUD37XcET1N8B3a1B1ldSw/qS+TVptu4MF
i2SFqt75K111z/nvBU/BqflkYAJATPJIK4pETHG1091rN+pb47mxJWLt4hCI
xvy6Bkjm6ppHqUj7toJKQ+jZPp1KPXDn+6VC5Nd+Uq1RUcrJ+dYh5hp8drVw
XDC3/Uvt6QXn4bxLgbhM2BHT6koBWvwkOGIfZmfvwZjIbcG1kjplDqtGLYXs
kpvJ4KtUF3bHdkojvX198UW3trJjpN8eAjxw3IQJGA3ZJWkW/33tmA==
=4Vl1
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#235459

FromGreg Wooledge <greg@wooledge.org>
Date2021-05-22 20:30 +0200
Message-ID<ChExQ-2g6-5@gated-at.bofh.it>
In reply to#235457
On Sat, May 22, 2021 at 03:48:38PM +0000, ghe2001 wrote:
> Error: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit -.mount is masked.

https://www.linuxquestions.org/questions/linux-software-2/error-gdbus-error-org-freedesktop-systemd1-unitmasked-unit-mount-is-masked-4175665031/

https://unix.stackexchange.com/questions/533933/systemd-cant-unmask-root-mount-mount

As well as several other google hits, most of which had no resolution.

[toc] | [prev] | [next] | [standalone]

#235460

Fromghe2001 <ghe2001@protonmail.com>
Date2021-05-22 20:50 +0200
Message-ID<ChERc-2mn-7@gated-at.bofh.it>
In reply to#235459
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Saturday, May 22, 2021 12:29 PM, Greg Wooledge <greg@wooledge.org> wrote:

> On Sat, May 22, 2021 at 03:48:38PM +0000, ghe2001 wrote:
>
> > Error: GDBus.Error:org.freedesktop.systemd1.UnitMasked: Unit -.mount is masked.
>
> https://www.linuxquestions.org/questions/linux-software-2/error-gdbus-error-org-freedesktop-systemd1-unitmasked-unit-mount-is-masked-4175665031/

Nope.  Gparted wasn't running anywhere.  Nor was much on the desktop, and nothing but the xfce4 desktop on the laptop (until I started up SSH and apt).

> https://unix.stackexchange.com/questions/533933/systemd-cant-unmask-root-mount-mount

StackExchange wouldn't let me in because I wouldn't agree to it's cookie policy.

> As well as several other google hits, most of which had no resolution.

Yeah, I did see those.

--
Glenn English


-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wsBzBAEBCAAGBQJgqVDJACEJEJ/XhjGCrIwyFiEELKJzD0JScCVjQA2Xn9eG
MYKsjDJC0ggAmytsOKX0VVcm2TJUNTykYE+C7lqKmIuPKyXx+xgxA+I4KtZO
qUhuUG6V5/Px12fbSLzqX8won0VvNl7R3J3BmwhqclYnrgK74v1XM21HLH3T
ZfdhJwPF0vCEMlgs1UE8mppB3MHWytW7nXXsPgWlvU2rW6fXfIy/vLyy693Q
GFfG711SYSgDrD1HEeNi2Npfyv1Lryc1pl1ysla6yDnnOR0rLRiTvDZLYpgU
bacMh3NJuutR7AT2UPlCvHCs6jsp61fKwf08Q+DxJNv8Pqgw3EirWzVc5gEw
R+iQaNoTs6dsuw9v7bwBWIXH6UT8kM/dnnKd40CWkmR8nlFvHjhVTw==
=793G
-----END PGP SIGNATURE-----

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web