Rootfs created with debootstrap and silent systemd boot

Kernels & Hardware, configuring network, installing services

Rootfs created with debootstrap and silent systemd boot

Postby vanfanel » 2018-09-28 15:50

Hi! I have created an aarch64 (arm64) rootfs using this guide:
https://www.debian.org/releases/stable/ ... 03.html.en

It's an aarch64 rootfs that was created on X86 hardware host.

It works fine, but it does not display the systemd boot messages. However, systemd shutdown messages ARE displayed!

The kernel commandline does NOT contain any message-supressing parameters like 'quiet', 'fastboot', 'loglevel=', etc. It does however contain 'console=tty1'.
The 2nd STAGE created some files on /dev.
This is what's on /dev before I boot the system:

Code: Select all

manuel@vader:~/src/aarch64$ ls /media/manuel/4449373a-546c-4754-947b-20baed181ed8/dev/ -l
total 8
lrwxrwxrwx 1 root root   13 sep 28 20:41 fd -> /proc/self/fd
crw-rw-rw- 1 root root 1, 7 sep 28 20:41 full
crw-rw-rw- 1 root root 1, 3 sep 28 20:41 null
crw-rw-rw- 1 root root 5, 2 sep 28 20:41 ptmx
drwxr-xr-x 2 root root 4096 sep 28 20:41 pts
crw-rw-rw- 1 root root 1, 8 sep 28 20:41 random
drwxr-xr-x 2 root root 4096 sep 28 20:41 shm
lrwxrwxrwx 1 root root   15 sep 28 20:41 stderr -> /proc/self/fd/2
lrwxrwxrwx 1 root root   15 sep 28 20:41 stdin -> /proc/self/fd/0
lrwxrwxrwx 1 root root   15 sep 28 20:41 stdout -> /proc/self/fd/1
crw-rw-rw- 1 root root 5, 0 sep 28 20:41 tty
crw-rw-rw- 1 root root 1, 9 sep 28 20:41 urandom
crw-rw-rw- 1 root root 1, 5 sep 28 20:41 zero




Note there are way fewer files there than those in a running system, because udev creates a lot of them.
In fact, it seems that tty1 is missing until I have already booted the system, so it's created by udev it seems! However, systemd could need /dev/tty1 before udev starts (remember I have 'console=tty1' on my kernel command line).
Could /dev/tty1 BEFORE udev starts what I am missing here?

On the tutorial, there's a step that fails for me. That's doing:

Code: Select all
MAKEDEV generic


which causes:

Code: Select all
/sbin/MAKEDEV: no support for generic on this arch


If I run 'MAKEDEV', without the 'generic' parameter, a lot of devices in /dev are created, and they are available even on the chrooted system (ie: they don't depend on udev to be created), but still systemd and the kernel are silent.

The fact that systemd is able to print shutdown messages but not startup messages seems to indicate I am missing something that should be present before boot (probably on /dev) and that systemd uses to print these messages on screen, but I don't know what. Any ideas?
vanfanel
 
Posts: 2
Joined: 2013-06-23 17:31

Re: Rootfs created with debootstrap and silent systemd boot

Postby L_V » 2018-09-29 08:35

Did you correctly specify ARCH variables ?
Substitute one of the following for ARCH in the debootstrap command: amd64, i386 , arm64
# /usr/sbin/debootstrap --arch ARCH stretch /mnt/debinst http://ftp.us.debian.org/debian

If the target architecture is different than the host, you should add the --foreign option.

f the target architecture is different from the host, you will need to first copy qemu-user-static to the new host:

# cp /usr/bin/qemu-ARCH-static /mnt/debinst/usr/bin
# LANG=C.UTF-8 chroot /mnt/debinst qemu-ARCH-static /bin/bash

WARNING with "ARCH" which is now different (see content of qemu-user-static )
=> aarch64 , x86_64 , i386
L_V
 
Posts: 799
Joined: 2007-03-19 09:04


Return to System configuration

Who is online

Users browsing this forum: No registered users and 8 guests

fashionable