[gentoo-user] chroot: on update I got "mount: /proc: mount failed: Unknown error 5005.,Unable to mark /proc slave: 32"

[gentoo-user] chroot: on update I got "mount: /proc: mount failed: Unknown error 5005.,Unable to mark /proc slave: 32"

[Vitaly Zdanevich]

[-- Attachment #1: Type: text/plain, Size: 16964 bytes --]

Hi, I did a chroot according to 
https://wiki.gentoo.org/index.php?title=Chroot

My script in the chroot folder:

```
mount --rbind /dev dev
mount --make-rslave dev
mount -t proc /proc proc
mount --rbind /sys sys
mount --make-rslave sys
mount --rbind /tmp tmp
mount --bind /run run

mount -o bind /var/db/repos/ var/db/repos/

chroot . /bin/bash

```

My /root/.bashrc of the new chroot:

```

. /etc/profile
export PS1="(chroot) $PS1"

```

Update command with full output (I never did an update on this chroot):

(chroot) thinkpad-t430 /etc/portage # emerge --ask --update --newuse 
--deep --with-bdeps=y @world

  * IMPORTANT: 15 news items need reading for repository 'gentoo'.
  * Use eselect news read to view new items.


These are the packages that would be merged, in order:

Calculating dependencies... done!
Dependency resolution took 5.08 s (backtrack: 0/20).

[ebuild   R    ] sys-apps/net-tools-2.10  USE="-ipv6*"
[ebuild     UD ] dev-db/sqlite-3.45.3 [3.46.0]
[ebuild   R    ] app-crypt/libb2-0.98.1-r3  USE="openmp*"
[ebuild   R    ] sys-devel/gettext-0.22.4  USE="openmp*"
[ebuild   R    ] sys-libs/pam-1.5.3-r1  USE="filecaps*"
[ebuild   R    ] net-misc/wget-1.24.5  USE="-ipv6*"
[ebuild  N     ] app-crypt/rhash-1.4.3  USE="nls ssl -debug -static-libs"
[ebuild  N     ] dev-libs/libuv-1.48.0  USE="-verify-sig"
[ebuild  N     ] app-arch/libarchive-3.7.4  USE="acl bzip2 e2fsprogs 
iconv lzma xattr zstd -blake2 -expat -lz4 -lzo -nettle -static-libs 
-test -verify-sig"
[ebuild     UD ] dev-python/trove-classifiers-2024.5.22 [2024.7.2]
[ebuild   R    ] net-misc/iputils-20240117  USE="filecaps*"
[ebuild  N     ] dev-libs/jsoncpp-1.9.5  USE="-doc -test"
[ebuild     UD ] dev-python/hatchling-1.24.2 [1.25.0]
[ebuild     UD ] dev-python/urllib3-2.2.1 [2.2.2]
[ebuild     UD ] dev-python/setuptools-70.0.0 [70.1.1-r1]
[ebuild   R    ] net-misc/dhcpcd-10.0.8  USE="-ipv6*"
[ebuild   R    ] app-portage/portage-utils-0.96.1  USE="openmp*"
[ebuild  N     ] dev-build/cmake-3.28.5  USE="ncurses -dap -doc -gui 
-qt6 -test -verify-sig"
[ebuild  N     ] net-libs/nghttp2-1.61.0  USE="-debug -hpack-tools 
-jemalloc -static-libs -systemd -test -utils -xml"
[ebuild     UD ] net-misc/curl-8.7.1-r4 [8.8.0-r1] USE="http2*"

Would you like to merge these packages? [Yes/No]

 >>> Verifying ebuild manifests

 >>> Running pre-merge checks for app-crypt/libb2-0.98.1-r3
mount: /proc: mount failed: Unknown error 5005.
Unable to mark /proc slave: 32
  * The ebuild phase 'pretend' has exited unexpectedly. This type of
  * behavior is known to be triggered by things such as failed variable
  * assignments (bug #190128) or bad substitution errors (bug #200313).
  * Normally, before exiting, bash should have displayed an error message
  * above. If bash did not produce an error message above, it's possible
  * that the ebuild has called `exit` when it should have called `die`
  * instead. This behavior may also be triggered by a corrupt bash binary or
  * a hardware problem such as memory or cpu malfunction. If the problem is
  * not reproducible or it appears to occur randomly, then it is likely to
  * be triggered by a hardware problem. If you suspect a hardware problem
  * then you should try some basic hardware diagnostics such as memtest.
  * Please do not report this as a bug unless it is consistently
  * reproducible and you are sure that your bash binary and hardware are
  * functioning properly.

 >>> Failed to emerge app-crypt/libb2-0.98.1-r3, Log file:

 >>> '/var/tmp/portage/app-crypt/libb2-0.98.1-r3/temp/build.log'

 >>> Running pre-merge checks for sys-devel/gettext-0.22.4
mount: /proc: mount failed: Unknown error 5005.
Unable to mark /proc slave: 32
  * The ebuild phase 'pretend' has exited unexpectedly. This type of
  * behavior is known to be triggered by things such as failed variable
  * assignments (bug #190128) or bad substitution errors (bug #200313).
  * Normally, before exiting, bash should have displayed an error message
  * above. If bash did not produce an error message above, it's possible
  * that the ebuild has called `exit` when it should have called `die`
  * instead. This behavior may also be triggered by a corrupt bash binary or
  * a hardware problem such as memory or cpu malfunction. If the problem is
  * not reproducible or it appears to occur randomly, then it is likely to
  * be triggered by a hardware problem. If you suspect a hardware problem
  * then you should try some basic hardware diagnostics such as memtest.
  * Please do not report this as a bug unless it is consistently
  * reproducible and you are sure that your bash binary and hardware are
  * functioning properly.
!!! When you file a bug report, please include the following information:
GENTOO_VM=  CLASSPATH="" JAVA_HOME="/etc/java-config-2/current-system-vm"
JAVACFLAGS="" COMPILER=""
and of course, the output of emerge --info =sys-devel/gettext-0.22.4

 >>> Failed to emerge sys-devel/gettext-0.22.4, Log file:

 >>> '/var/tmp/portage/sys-devel/gettext-0.22.4/temp/build.log'

  * Messages for package app-crypt/libb2-0.98.1-r3:

  * The ebuild phase 'pretend' has exited unexpectedly. This type of
  * behavior is known to be triggered by things such as failed variable
  * assignments (bug #190128) or bad substitution errors (bug #200313).
  * Normally, before exiting, bash should have displayed an error message
  * above. If bash did not produce an error message above, it's possible
  * that the ebuild has called `exit` when it should have called `die`
  * instead. This behavior may also be triggered by a corrupt bash binary or
  * a hardware problem such as memory or cpu malfunction. If the problem is
  * not reproducible or it appears to occur randomly, then it is likely to
  * be triggered by a hardware problem. If you suspect a hardware problem
  * then you should try some basic hardware diagnostics such as memtest.
  * Please do not report this as a bug unless it is consistently
  * reproducible and you are sure that your bash binary and hardware are
  * functioning properly.

  * Messages for package sys-devel/gettext-0.22.4:

  * The ebuild phase 'pretend' has exited unexpectedly. This type of
  * behavior is known to be triggered by things such as failed variable
  * assignments (bug #190128) or bad substitution errors (bug #200313).
  * Normally, before exiting, bash should have displayed an error message
  * above. If bash did not produce an error message above, it's possible
  * that the ebuild has called `exit` when it should have called `die`
  * instead. This behavior may also be triggered by a corrupt bash binary or
  * a hardware problem such as memory or cpu malfunction. If the problem is
  * not reproducible or it appears to occur randomly, then it is likely to
  * be triggered by a hardware problem. If you suspect a hardware problem
  * then you should try some basic hardware diagnostics such as memtest.
  * Please do not report this as a bug unless it is consistently
  * reproducible and you are sure that your bash binary and hardware are
  * functioning properly.
  *
  * The following 2 packages have failed to build, install, or execute
  * postinst:
  *
  *  (app-crypt/libb2-0.98.1-r3:0/0::gentoo, ebuild scheduled for 
merge), Log file:
  *   '/var/tmp/portage/app-crypt/libb2-0.98.1-r3/temp/build.log'
  *  (sys-devel/gettext-0.22.4:0/0::gentoo, ebuild scheduled for merge), 
Log file:
  *   '/var/tmp/portage/sys-devel/gettext-0.22.4/temp/build.log'
  *
[ERROR] Task was destroyed but it is pending!
task: <Task pending name='Task-775' coro=<ForkProcess._main() running at 
/usr/lib/python3.12/site-packages/portage/util/_async/ForkProcess.py:197> 
wait_for=<Future pending 
cb=[AsynchronousTask.async_wait.<locals>.<lambda>() at 
/usr/lib/python3.12/site-packages/_emerge/AsynchronousTask.py:49, 
Task.task_wakeup()]> cb=[SpawnProcess._main_exit()]>
[ERROR] Task was destroyed but it is pending!
task: <Task pending name='Task-774' coro=<PipeLogger._io_loop() running 
at 
/usr/lib/python3.12/site-packages/portage/util/_async/PipeLogger.py:97> 
wait_for=<Future pending cb=[Task.task_wakeup()]> 
cb=[PipeLogger._io_loop_done()]>
[ERROR] Task was destroyed but it is pending!
task: <Task pending name='Task-773' coro=<BuildLogger._main() running at 
/usr/lib/python3.12/site-packages/portage/util/_async/BuildLogger.py:134> 
wait_for=<Future pending 
cb=[AsynchronousTask.async_wait.<locals>.<lambda>() at 
/usr/lib/python3.12/site-packages/_emerge/AsynchronousTask.py:49, 
Task.task_wakeup()]> cb=[BuildLogger._main_exit()]>
[ERROR] Task was destroyed but it is pending!
task: <Task pending name='Task-772' coro=<PipeLogger._io_loop() running 
at 
/usr/lib/python3.12/site-packages/portage/util/_async/PipeLogger.py:97> 
wait_for=<Future pending cb=[Task.task_wakeup()]> 
cb=[PipeLogger._io_loop_done()]>





emerge --info of the host system:


Portage 3.0.65 (python 3.12.3-final-0, 
default/linux/amd64/17.1/no-multilib, gcc-13, glibc-2.39-r9, 
6.6.30-gentoo+ x86_64)
=================================================================
System uname: 
Linux-6.6.30-gentoo+-x86_64-Intel-R-_Core-TM-_i7-3840QM_CPU_@_2.80GHz-with-glibc2.39
KiB Mem:    16214828 total,   7489304 free
KiB Swap:   33554428 total,  33554428 free
Timestamp of repository gentoo: Thu, 11 Jul 2024 21:45:00 +0000
Head commit of repository gentoo: 0ce4619c4b3b4b2cc617696e4386425ea01f0c18
Head commit of repository amarlay: 2a4107e1466105f6f01d94a6a37bb4f858eca42c

Head commit of repository guru: 52a063e4a00023a13a2abb35c1529ffcb88039bf

Timestamp of repository palemoon: Fri, 21 Jun 2024 15:18:57 +0000
Head commit of repository palemoon: e06331010d4740d679502a26dfabdc2bb522770d

Head commit of repository unity-gentoo: 
2ee2fdb9534beed714dddb3351d1057de81781c2

sh bash 5.2_p26-r5
ld GNU ld (Gentoo 2.42 p3) 2.42.0
app-misc/pax-utils:        1.3.7::gentoo
app-shells/bash:           5.2_p26-r5::gentoo
dev-build/autoconf:        2.13-r8::gentoo, 2.71-r7::gentoo
dev-build/automake:        1.16.5-r2::gentoo
dev-build/cmake:           3.28.5::gentoo
dev-build/libtool:         2.4.7-r4::gentoo
dev-build/make:            4.4.1-r1::gentoo
dev-build/meson:           1.4.0-r1::gentoo
dev-java/java-config:      2.3.3-r1::gentoo
dev-lang/perl:             5.38.2-r3::gentoo
dev-lang/python:           3.9.19_p3::gentoo, 3.11.9-r1::gentoo, 
3.12.3-r1::gentoo
dev-lang/rust:             1.77.1::gentoo
sys-apps/baselayout:       2.15::gentoo
sys-apps/openrc:           0.54::gentoo
sys-apps/sandbox:          2.38::gentoo
sys-devel/binutils:        2.42-r1::gentoo
sys-devel/binutils-config: 5.5::gentoo
sys-devel/clang:           16.0.6::gentoo, 17.0.6::gentoo
sys-devel/gcc:             13.2.1_p20240210::gentoo
sys-devel/gcc-config:      2.11::gentoo
sys-devel/lld:             17.0.6::gentoo
sys-devel/llvm:            16.0.6::gentoo, 17.0.6::gentoo
sys-kernel/linux-headers:  6.6-r1::gentoo (virtual/os-headers)
sys-libs/glibc:            2.39-r9::gentoo
Repositories:

gentoo
     location: /var/db/repos/gentoo
     sync-type: rsync
     sync-uri: rsync://rsync2.ru.gentoo.org/gentoo-portage/
     priority: -1000
     volatile: False
     sync-rsync-verify-metamanifest: yes
     sync-rsync-extra-opts:
     sync-rsync-verify-jobs: 1
     sync-rsync-verify-max-age: 24

amarlay
     location: /var/db/repos/amarlay
     sync-type: git
     sync-uri: https://github.com/amarakon/amarlay
     masters: gentoo
     volatile: False

guru
     location: /var/db/repos/guru
     sync-type: git
     sync-uri: git@git.gentoo.org:repo/proj/guru.git
     masters: gentoo
     volatile: False

my
     location: /var/db/repos/my
     masters: gentoo
     volatile: False

palemoon
     location: /var/db/repos/palemoon
     sync-type: git
     sync-uri: https://github.com/gentoo-mirror/palemoon.git
     masters: gentoo
     volatile: False

unity-gentoo
     location: /var/db/repos/unity-gentoo
     sync-type: git
     sync-uri: https://github.com/shiznix/unity-gentoo
     masters: gentoo
     volatile: False

ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="@FREE @FREE ipw3945"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -march=native -pipe -frecord-gcc-switches"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/lib64/libreoffice/program/sofficerc 
/usr/share/config /usr/share/gnupg/qualified.txt"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/dconf /etc/env.d 
/etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release 
/etc/php/apache2-php8.2/ext-active/ /etc/php/cgi-php8.2/ext-active/ 
/etc/php/cli-php8.2/ext-active/ /etc/php/fpm-php8.2/ext-active/ 
/etc/php/phpdbg-php8.2/ext-active/ /etc/revdep-rebuild /etc/sandbox.d 
/etc/terminfo"
CXXFLAGS="-O2 -march=native -pipe -frecord-gcc-switches"
DISTDIR="/var/cache/distfiles"
ENV_UNSET="CARGO_HOME DBUS_SESSION_BUS_ADDRESS DISPLAY 
GDK_PIXBUF_MODULE_FILE GOBIN GOPATH PERL5LIB PERL5OPT PERLPREFIX 
PERL_CORE PERL_MB_OPT PERL_MM_OPT XAUTHORITY XDG_CACHE_HOME 
XDG_CONFIG_HOME XDG_DATA_HOME XDG_RUNTIME_DIR XDG_STATE_HOME"
FCFLAGS="-O2 -march=native -pipe -frecord-gcc-switches"
FEATURES="assume-digests binpkg-docompress binpkg-dostrip binpkg-logs 
buildpkg-live config-protect-if-modified distlocks ebuild-locks 
fixlafiles ipc-sandbox merge-sync merge-wait multilib-strict 
network-sandbox news parallel-fetch pid-sandbox pkgdir-index-trusted 
preserve-libs protect-owned qa-unresolved-soname-deps sandbox sfperms 
strict unknown-features-warn unmerge-logs unmerge-orphans userfetch 
userpriv usersandbox usersync xattr"
FFLAGS="-O2 -march=native -pipe -frecord-gcc-switches"
GENTOO_MIRRORS="http://mirror.yandex.ru/gentoo-distfiles/ 
http://gentoo-mirror.alexxy.name/"
LANG="C.UTF8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed -Wl,--defsym=__gentoo_check_ldflags__=0"
LEX="flex"
PKGDIR="/var/cache/binpkgs"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times 
--omit-dir-times --compress --force --whole-file --delete --stats 
--human-readable --timeout=180 --exclude=/distfiles --exclude=/local 
--exclude=/packages --exclude=/.git"
PORTAGE_TMPDIR="/var/tmp"
RUSTFLAGS="-C debuginfo=0 -C target-cpu=native -C opt-level=3"
SHELL="/bin/bash"
USE="X acl amd64 bluetooth bluray bzip2 chromecast cli crypt dbus dri 
dvd egl elogind eme-free exif ffmpeg flac fortran gdbm gdk-pixbuf 
graphite grub heif iconv jpeg libtirpc lto matroska mp3 ncurses nls ogg 
opengl openmp opus pam pcre pgo png pulseaudio rdp readline seccomp 
split-usr ssl svg svt-av1 test-rust tiff tkip unicode v4l vaapi vpx webp 
x264 x265 xattr xml zlib" ABI_X86="64" ADA_TARGET="gcc_12" 
APACHE2_MODULES="authn_core authz_core socache_shmcb unixd actions alias 
auth_basic authn_anon authn_dbm authn_file authz_dbm authz_groupfile 
authz_host authz_owner authz_user autoindex cache cgi cgid dav dav_fs 
dav_lock deflate dir env expires ext_filter file_cache filter headers 
include info log_config logio mime mime_magic negotiation rewrite 
setenvif speling status unique_id userdir usertrack vhost_alias" 
CALLIGRA_FEATURES="karbon sheets words" COLLECTD_PLUGINS="df interface 
irq load memory rrdtool swap syslog" CPU_FLAGS_X86="aes avx f16c mmx 
mmxext pclmul popcnt rdrand sse sse2 sse3 sse4_1 sse4_2 ssse3" 
ELIBC="glibc" GPSD_PROTOCOLS="ashtech aivdm earthmate evermore fv18 
garmin garmintxt gpsclock greis isync itrax mtk3301 ntrip navcom 
oceanserver oncore rtcm104v2 rtcm104v3 sirf skytraq superstar2 tsip 
tripmate tnt ublox" INPUT_DEVICES="libinput" KERNEL="linux" 
LCD_DEVICES="bayrad cfontz glk hd44780 lb216 lcdm001 mtxorb text" 
LLVM_TARGETS="x64" LUA_SINGLE_TARGET="lua5-1" LUA_TARGETS="lua5-1" 
OFFICE_IMPLEMENTATION="libreoffice" PHP_TARGETS="php8-2" 
POSTGRES_TARGETS="postgres15" PYTHON_SINGLE_TARGET="python3_12" 
PYTHON_TARGETS="python3_12" RUBY_TARGETS="ruby31 ruby32" 
VIDEO_CARDS="intel i965" XTABLES_ADDONS="quota2 psd pknock lscan length2 
ipv4options ipp2p iface geoip fuzzy condition tarpit sysrq proto logmark 
ipmark dhcpmac delude chaos account"
Unset:  ADDR2LINE, AR, ARFLAGS, AS, ASFLAGS, CC, CCLD, CONFIG_SHELL, 
CPP, CPPFLAGS, CTARGET, CXX, CXXFILT, ELFEDIT, EMERGE_DEFAULT_OPTS, 
EXTRA_ECONF, F77FLAGS, FC, GCOV, GPROF, INSTALL_MASK, LC_ALL, LD, 
LFLAGS, LIBTOOL, LINGUAS, MAKE, MAKEFLAGS, MAKEOPTS, NM, OBJCOPY, 
OBJDUMP, PORTAGE_BINHOST, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, 
PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PYTHONPATH, RANLIB, 
READELF, SIZE, STRINGS, STRIP, YACC, YFLAGS

Thanks for the help, I will update the Wiki after finding the root cause 
and a solution.

[-- Attachment #2: Type: text/html, Size: 21573 bytes --]

Re: [gentoo-user] chroot: on update I got "mount: /proc: mount failed: Unknown error 5005.,Unable to mark /proc slave: 32"

[Michael]

[-- Attachment #1: Type: text/plain, Size: 1527 bytes --]

Hi Vitaly,

On Wednesday, 17 July 2024 18:08:08 BST Vitaly Zdanevich wrote:
> Hi, I did a chroot according to
> https://wiki.gentoo.org/index.php?title=Chroot
> 
> My script in the chroot folder:
> 
> ```
> mount --rbind /dev dev
> mount --make-rslave dev
> mount -t proc /proc proc
> mount --rbind /sys sys
> mount --make-rslave sys
> mount --rbind /tmp tmp
> mount --bind /run run
> 
> mount -o bind /var/db/repos/ var/db/repos/
> 
> chroot . /bin/bash
> 
> ```
[snip ...]

The wiki and the Handbook, explain you need to have a mountpoint for the file 
system in which you are trying to chroot.

For example, the wiki page states:

mkdir /mnt/mychroot  <== this is the mountpoint
cd /mnt/mychroot

or if you are trying to chroot on an existing installation on some block 
device, e.g. say it is partition /dev/sdb3, you would run:

mkdir /mnt/mychroot
mount /dev/sdb3 /mnt/mychroot

Consequently, the mount commands after you mount the OS partition and before 
you chroot become:

cd /mnt/mychroot
mount --rbind /dev /mnt/mychroot/dev
mount --make-rslave /mnt/mychroot/dev
mount -t proc /proc /mnt/mychroot/proc
mount --rbind /sys /mnt/mychroot/sys
mount --make-rslave /mnt/mychroot/sys
mount --rbind /tmp /mnt/mychroot/tmp
rmount --bind /run /mnt/mychroot/run

After the above you can chroot into the mounted filesystem:

chroot /mnt/mychroot /bin/bash


The same approach is followed in the Handbook for a new installation:

https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/
Base#Mounting_the_necessary_filesystems

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: [gentoo-user] chroot: on update I got "mount: /proc: mount failed: Unknown error 5005.,Unable to mark /proc slave: 32"

[Waldo Lemmer]

[-- Attachment #1: Type: text/plain, Size: 850 bytes --]

On Wed, Jul 17, 2024, 19:09 Vitaly Zdanevich <zdanevich.vitaly@ya.ru> wrote:

> My script in the chroot folder:
>
> ```
> mount --rbind /dev dev
> mount --make-rslave dev
> mount -t proc /proc proc
> mount --rbind /sys sys
> mount --make-rslave sys
> mount --rbind /tmp tmp
> mount --bind /run run
>
> mount -o bind /var/db/repos/ var/db/repos/
>
> chroot . /bin/bash
>
> ```
>

The last line chroots into the current working directory, not the directory
where the script is located. Thus, it doesn't matter where your script is
located.

I would suggest adding the following line to the start of your script:

```
cd "$1"
```

Then you can pass the path to your mounted filesystem as a parameter:

```sh
# /mnt/gentoo/chroot.sh /mnt/gentoo/
```

You could also use `dirname "$0"` in your script to get the directory where
your script is located.

>

[-- Attachment #2: Type: text/html, Size: 1831 bytes --]