Well, I’m wondering if you’re another victim of the ongoing issues reported mostly on the stable branch.
Check this out:
The issue with linux419 and systemd got resolved. The issue was an Aufs4 patch on our end, which got added by mistake 10 months ago. Due to changes in systemd to improve mounting of devices that patch from Aufs4 didn’t work anymore and created that issue.
Seems due to the incident we noticed that still some users use that old kernel, but we didn’t had any requests since ages to even provide install medias with that kernel series. The community reported it in our forums, but I had no time to rev…
Yep, the issue was that Aufs4 patch, which got added by mistake on 4.14.133-2 kernel. Thx to systemd we figured it out and it is now properly handled:
Will revert the changes made to systemd in unstable branch first. The proper fix will come with the next regular update.
opened 07:09PM - 14 Jun 21 UTC
closed 06:47PM - 15 Jun 21 UTC
pid1
not-our-bug
**systemd version the issue has been seen with**
> systemd 248.3-2
…
**Used distribution**
> Manjaro 21.0.7
**Linux kernel version used** (`uname -a`)
<!-- Make sure to enclose the pasted kernel version in `backticks`, so that
GitHub doesn't convert the `#` character typically included in it into a
reference to old GitHub issues. -->
> `4.19.194-1-MANJARO`
**CPU architecture issue was seen on**
> Ryzen 2 (x64)
**Expected behaviour you didn't see**
> Boot the system with 4.19 kernel
**Unexpected behaviour you saw**
> System compains about udev and haveged systemd services not able to run. Only a reboot of the system is possible. Note: 4.14 and other kernels boot fine.
**Steps to reproduce the problem**
> Get the latest [Manjaro 21.0.7 ISO](manjaro.org/download/), install it as Kernel 5.10 series boots with 248. Install the package **linux419** via `sudo mhwd-kernel -i linux419`. Try to boot the system with that 4.19 kernel.
**Additional program output to the terminal or log subsystem illustrating the issue**
<!-- Please paste relevant program terminal or journal output here, ideally
when generated in debug mode (try setting the SYSTEMD_LOG_LEVEL=debug
environment variable). For very long copy/pasted data consider using a
service like https://gist.github.com/. Where copy/paste is not possible
(for example early boot or late shutdown), a photo of the screen might do
too, but text is always much preferred. -->
```
Jun 14 20:40:33 development systemd[1]: systemd-udevd.service: Failed with result 'exit-code'.
Jun 14 20:40:33 development systemd[1]: Failed to start Rule-based Manager for Device Events and Files.
Jun 14 20:40:33 development systemd[1]: systemd-udevd.service: Scheduled restart job, restart counter is at 2.
Jun 14 20:40:33 development systemd[1]: Stopped Rule-based Manager for Device Events and Files.
Jun 14 20:40:33 development systemd[1]: Starting Rule-based Manager for Device Events and Files...
Jun 14 20:40:33 development systemd[392]: systemd-udevd.service: Failed to set up mount namespacing: /run/systemd/unit-root/proc/sys/kernel/hostname: Device or resource busy
Jun 14 20:40:33 development systemd[392]: systemd-udevd.service: Failed at step NAMESPACE spawning /usr/lib/systemd/systemd-udevd: Device or resource busy
Jun 14 20:40:33 development systemd[1]: systemd-udevd.service: Main process exited, code=exited, status=226/NAMESPACE
Jun 14 20:40:33 development systemd[1]: systemd-udevd.service: Failed with result 'exit-code'.
Jun 14 20:40:33 development systemd[1]: Failed to start Rule-based Manager for Device Events and Files.
Jun 14 20:40:33 development systemd[1]: systemd-udevd.service: Scheduled restart job, restart counter is at 3.
....
Jun 14 20:40:34 development systemd[1]: haveged.service: Scheduled restart job, restart counter is at 1.
Jun 14 20:40:34 development systemd[1]: Stopped Entropy Daemon based on the HAVEGE algorithm.
Jun 14 20:40:34 development systemd[1]: Started Entropy Daemon based on the HAVEGE algorithm.
Jun 14 20:40:34 development systemd[403]: haveged.service: Failed to set up mount namespacing: /run/systemd/unit-root/dev: Invalid argument
Jun 14 20:40:34 development systemd[403]: haveged.service: Failed at step NAMESPACE spawning /usr/bin/haveged: Invalid argument
Jun 14 20:40:34 development systemd[1]: haveged.service: Main process exited, code=exited, status=226/NAMESPACE
Jun 14 20:40:34 development systemd[1]: haveged.service: Failed with result 'exit-code'.
```
I guess you need to provide more information so you get proper assistance from somebody else within the community. (Have you ever seen this before, btw?)
