# Failed to set up mount namespacing: /run/systemd/unit-root/home: No such device

**URL:** <https://forum.endeavouros.com/t/failed-to-set-up-mount-namespacing-run-systemd-unit-root-home-no-such-device/36962>\
**Category:** EndeavourOS installation\
**Created:** [February 7, 2023, 8:43am UTC](https://forum.endeavouros.com/t/failed-to-set-up-mount-namespacing-run-systemd-unit-root-home-no-such-device/36962 "2023-02-07T08:43:58Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![richard](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/r/f0a364/32.png) [@richard](https://forum.endeavouros.com/u/richard)\
**Post date:** [February 7, 2023, 8:43am UTC](https://forum.endeavouros.com/t/failed-to-set-up-mount-namespacing-run-systemd-unit-root-home-no-such-device/36962/1 "2023-02-07T08:43:58Z")

</div>

Since the system updates applied the morning of 2 february 2023, I’m noticing a waterfall of startup problems, seemingly caused by NetworkManager (which, itself, restarts) but flakes out postgresql and uwsgi … postgresql needing manual restart which is a **PITA**.

What I notice in journalctl log file:

```auto
févr. 02 07:11:09 systemd[1]: Starting Network Manager...
févr. 02 07:12:39 systemd[1]: NetworkManager.service: start operation timed out. Terminating.
févr. 02 07:12:39 systemd[1]: NetworkManager.service: Failed with result 'timeout'.
févr. 02 07:12:39 systemd[1]: Failed to start Network Manager.
févr. 02 07:12:40 systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 1.
févr. 02 07:12:40 systemd[1]: Stopped Network Manager.
févr. 02 07:12:40 systemd[1]: Starting Network Manager...
févr. 02 07:12:50 systemd[622]: NetworkManager.service: Failed to set up mount namespacing: /run/systemd/unit-root/home: No such device
févr. 02 07:12:50 systemd[622]: NetworkManager.service: Failed at step NAMESPACE spawning /usr/bin/NetworkManager: No such device
févr. 02 07:12:50 systemd[1]: NetworkManager.service: Main process exited, code=exited, status=226/NAMESPACE
févr. 02 07:12:50 systemd[1]: NetworkManager.service: Failed with result 'exit-code'.
févr. 02 07:12:50 systemd[1]: Failed to start Network Manager.
févr. 02 07:12:50 systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 2.

```

currently at:

```auto
$ uname -a
Linux ... 6.1.9-arch1-2 #1 SMP PREEMPT_DYNAMIC Fri, 03 Feb 2023 18:49:53 +0000 x86_64 GNU/Linux
$ paclog-pkglist |grep -E "systemd|networkm"
lib32-systemd 252.5-1
networkmanager 1.40.12-1
networkmanager-openvpn 1.10.2-1
networkmanager-qt 5.102.0-1
systemd 252.5-1
systemd-libs 252.5-1
systemd-sysvcompat 252.5-1

```

Any ideas? for info, I do _not_ use systemd-homed, which is disabled.  
BTW - I don’t notice the supposed directory `/run/systemd/unit-root/home`, only the parent (which is empty)

```auto
$ sudo ls -lar /run/systemd/unit-root
total 0
drwxr-xr-x 21 root root 540 7 févr. 09:20 ..
drwx------ 2 root root 40 7 févr. 09:18 .

```

---

<div class="post-metadata">

**Author:** ![joekamprad](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/joekamprad/32/77608_2.png) [@joekamprad](https://forum.endeavouros.com/u/joekamprad)\
**Post date:** [February 7, 2023, 2:44pm UTC](https://forum.endeavouros.com/t/failed-to-set-up-mount-namespacing-run-systemd-unit-root-home-no-such-device/36962/2 "2023-02-07T14:44:22Z")

</div>

```auto
sudo /usr/bin/NetworkManager --no-daemon

```

could show better messages about what exactly is failing…

But never had such issue or saw this reported …

---

<div class="post-metadata">

**Author:** ![richard](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/r/f0a364/32.png) [@richard](https://forum.endeavouros.com/u/richard)\
**Post date:** [February 7, 2023, 3:03pm UTC](https://forum.endeavouros.com/t/failed-to-set-up-mount-namespacing-run-systemd-unit-root-home-no-such-device/36962/3 "2023-02-07T15:03:37Z")

</div>

This doesn’t show anything at all, but as I mentioned above, probably because NetworkManager restarts automatically a bit later.  
The turd is that postgresql doesn’t restart by itself, it needs a manual restart!

```auto
févr. 07 09:20:02 systemd[611]: postgresql.service: Failed to set up mount namespacing: /run/systemd/unit-root/home: No such device
févr. 07 09:20:02 systemd[611]: postgresql.service: Failed at step NAMESPACE spawning /usr/bin/postgresql-check-db-dir: No such device
févr. 07 09:20:02 systemd[1]: postgresql.service: Control process exited, code=exited, status=226/NAMESPACE
févr. 07 09:20:02 systemd[1]: postgresql.service: Failed with result 'exit-code'.
févr. 07 09:20:02 systemd[1]: Failed to start PostgreSQL database server.

```

---

<div class="post-metadata">

**Author:** ![richard](https://forum.endeavouros.com/letter_avatar_proxy/v4/letter/r/f0a364/32.png) [@richard](https://forum.endeavouros.com/u/richard)\
**Post date:** [February 9, 2023, 8:13am UTC](https://forum.endeavouros.com/t/failed-to-set-up-mount-namespacing-run-systemd-unit-root-home-no-such-device/36962/4 "2023-02-09T08:13:46Z")

</div>

Well, it seems it was related to the nfs mount for “/home” in /etc/fstab  
I restructured to use a bind mount from the root nfs mountpoint and put  
the following clause in nfsmounts.conf

```auto
# Would cause all mount to /export/home would be done in
# the background
[MountPoint "/export/home"]
background=True

```

Booting up to the graphical login screen takes a few moments longer, but it seems stable enough [at least for now].

---

<div class="post-metadata">

**Author:** ![system](https://forum.endeavouros.com/uploads/default/original/2X/9/9ea52f9fd5ef8e609e593c362d61a36295f48be8.png) [@system](https://forum.endeavouros.com/u/system)\
**Post date:** [February 11, 2023, 8:14am UTC](https://forum.endeavouros.com/t/failed-to-set-up-mount-namespacing-run-systemd-unit-root-home-no-such-device/36962/5 "2023-02-11T08:14:00Z")

</div>

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.