Comment # 34 on bug 1181970 from
(In reply to Walddys Emmanuel Dorrejo C���spedes from comment #33)
> i'm back.
> 
> Date of creating *.mount
> 
> lrwxrwxrwx  1 root root   9 Aug 25 11:44 tmp.mount -> /dev/null
> lrwxrwxrwx  1 root root   9 Aug 25 11:44 var-lib-machines.mount -> /dev/null
> lrwxrwxrwx  1 root root   9 Aug 25 11:44 var-lock.mount -> /dev/null
> lrwxrwxrwx  1 root root   9 Aug 25 11:44 var-run.mount -> /dev/null
> lrwxrwxrwx  1 root root   9 Aug 25 11:44 var.mount -> /dev/null
> 
> journal > https://pastebin.com/4h34yEcw

This log file starts with:

   -- Journal begins at Fri 2021-08-20 19:37:51 -05, ends at Wed 2021-08-25
   15:31:11 -05. -- [...]

That's not really helpfull since it shows logs emitted after the mount units
were masked.

Can you show the relevant parts of the journal instead (anything that happened
around Aug 25 11:44) ?

> var-mask > https://pastebin.com/TsxZYkzY

Nothing interesting here meaning probably that PID1 was requested to mask the
units.

> zypp-history > https://pastebin.com/GU6Q2QmT

This one shows that a `zypper dup` was (manually) issued less than 2 minutes
before:

   2021-08-25 11:42:43|command|root@venus|'zypper' 'dup'

A small set of packages was updated.

The last thing that happened right before the creation of the masks is the
recreation of the initrd which was triggered by the update of btrfsprogs
package:

   # 2021-08-25 11:43:37 Output of btrfsprogs-5.13.1-1.1.x86_64.rpm %posttrans
script:

Dunno, maybe try to recreate your initrd manually with `mkinitrd` and see if
it's the culprit ?

Or try to reinstall the packages that were updated with `zypper dup`.


You are receiving this mail because: