"Reboot required" never goes away

Dripping6228 · 9 December 2022 11:46

Creating a bug report/issue

Required Information

DietPi version | G_DIETPI_VERSION_CORE=8 G_DIETPI_VERSION_SUB=11 G_DIETPI_VERSION_RC=2 G_GITBRANCH='master' G_GITOWNER='MichaIng' G_LIVE_PATCH_STATUS[0]='applied'
Distro version | bullseye
Kernel version | Linux DietPi 5.15.74-rockchip #22.08.6 SMP PREEMPT Tue Oct 18 06:40:37 UTC 2022 armv7l GNU/Linux
SBC model | ASUS Tinker Board (armv7l)
Power supply used | General usb socket
SD card used | ?

Additional Information (if applicable)

Booting from a SSD.

Steps to reproduce

DietPi boot message prompted me that there was updates available. After the update i get the message that i need to reboot. Done that several times but the message won’t go away.

grep: /proc/1/environ: Permission denied
 ─────────────────────────────────────────────────────
 DietPi v8.11.2 : Reboot required
 ─────────────────────────────────────────────────────
 - Device model : ASUS Tinker Board (armv7l)
 - CPU temp : N/A
 - LAN IP : 192.168.1.100 (eth0)
 - MOTD : Check out the DietPi v8.11 release notes:
          https://dietpi.com/docs/releases/v8_11/
 ─────────────────────────────────────────────────────

 DietPi Team     : https://github.com/MichaIng/DietPi#the-dietpi-project-team
 Image by        : DietPi Core Team (pre-image: from scratch)
 Patreon Legends : Camry2731, Chris Gelatt
 Website         : https://dietpi.com/ | https://twitter.com/DietPi_
 Contribute      : https://dietpi.com/contribute.html
 Web Hosting by  : https://myvirtualserver.com

 reboot          : A reboot is required to finalise a recent kernel upgrade

 dietpi-launcher : All the DietPi programs in one place
 dietpi-config   : Feature rich configuration tool for your device
 dietpi-software : Select optimised software for installation
 htop            : Resource monitor
 cpu             : Shows CPU information and stats

trendy · 9 December 2022 12:36

What is the output of mount; df -h ?

TahitianVibes · 9 December 2022 12:39

Hiii, @Dripping6228

Did you do the updates with DietPi-Update or you executed the commands yourself : apt update && apt upgrade ?
There is a file in path : /var/run/reboot-required maybe you can look at in this file …
I don’t know if DietPi is the same as other distributions …

Have a good day

Joulinar · 9 December 2022 12:56

I guess it is due to not fully complete kernel update.

You are using some special bootloader like Petiboot? Or are there diffent USB / eMMC / SD card connected?

Dripping6228 · 9 December 2022 13:08

sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=1014580k,nr_inodes=183706,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=205344k,mode=755)
/dev/sda on / type ext4 (rw,noatime,lazytime)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,size=4096k,nr_inodes=1024,mode=755)
cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noatime,lazytime,size=1026048k)
tmpfs on /var/log type tmpfs (rw,nosuid,nodev,noatime,lazytime,size=51200k)
Filesystem      Size  Used Avail Use% Mounted on
udev            991M     0  991M   0% /dev
tmpfs           201M  3.2M  198M   2% /run
/dev/sda        441G  3.5G  424G   1% /
tmpfs          1003M  1.3M 1002M   1% /dev/shm
tmpfs           5.0M     0  5.0M   0% /run/lock
tmpfs           4.0M     0  4.0M   0% /sys/fs/cgroup
tmpfs          1002M   32K 1002M   1% /tmp
tmpfs            50M  4.0K   50M   1% /var/log

Dripping6228 · 9 December 2022 13:10

gaaah, i wish i remembered. Having a bit to much projects going on the same time

ill check that out!

Dripping6228 · 9 December 2022 13:13

My tinkerboard does not come with a eMMC. So i found this guide where you “clone” the contens of the sd-card on to the ssd. Then generate a new UIID on the sd-card so the boot will occure on the ssd instead.

Dripping6228 · 9 December 2022 13:19

i don’t seem to have a /var/run/reboot-required/ dir

Joulinar · 9 December 2022 13:33

You have SD card as well as SSD connected same time?

Dripping6228 · 9 December 2022 17:23

yes, wont boot if i remove the sd-card

Joulinar · 9 December 2022 21:05

@MichaIng a couple of weeks ago we had a similar case where the kernel update was not correctly done due to a connected SD card were boot folder was present on SD card as well as SSD causing inconsistency.

@Dripping6228 can you share following

lsblk -o name,fstype,label,size,ro,type,mountpoint,partuuid,uuid

MichaIng · 9 December 2022 21:21

Does the ASUS Tinker Board support USB boot, i.e. is it possible to flash a fresh image to a USB drive and boot from it, without the SD card attached?

Otherwise, you’d need to mount the boot partition from the SD card, so that loaded and upgraded kernel do match.

Dripping6228 · 12 December 2022 12:52

NAME        FSTYPE LABEL   SIZE RO TYPE MOUNTPOINT PARTUUID                             UUID
sda         ext4         447.1G  0 disk /                                               19a04222-693b-42aa-95ab-5b17b389f0fd
mmcblk1                   28.9G  0 disk
└─mmcblk1p1 ext4          28.8G  0 part            4d0f29da-01                          42fbf56c-4a0b-4b65-8880-7dfb92295778

Dripping6228 · 12 December 2022 12:57

I don’t think so. They way i dit it was to clone the SD-card on to the SSD and then generate a new uuid for the SD-card.
It will not boot without the SD-card. But i’m pretty shure i’m booting using the SSD, but i’m not 100% certain tbh

Joulinar · 12 December 2022 19:31

Dripping6228:

NAME        FSTYPE LABEL   SIZE RO TYPE MOUNTPOINT PARTUUID                             UUID
sda         ext4         447.1G  0 disk /                                               19a04222-693b-42aa-95ab-5b17b389f0fd
mmcblk1                   28.9G  0 disk
└─mmcblk1p1 ext4          28.8G  0 part            4d0f29da-01                          42fbf56c-4a0b-4b65-8880-7dfb92295778

that was the entire output? nothing else?

My guess, during early boot, system is still using SD card partition mmcblk1p1 holding old kernel (/boot). However, this partition is not mounted at the end. That would explain why SD card is still needed.

can you share following

cat /etc/fstab

Dripping6228 · 13 December 2022 10:04

That was it

That sounds legit, thinking i could prob just flash the sd-card with the 8.11.2 and then generate a new UUID for it like i did when setting it up. Think that would work?

heres my outop for cat /etc/fstab

# You can use "dietpi-drive_manager" to setup mounts.
# NB: It overwrites and re-creates physical drive mount entries on use.
#----------------------------------------------------------------
# NETWORK
#----------------------------------------------------------------


#----------------------------------------------------------------
# TMPFS
#----------------------------------------------------------------
tmpfs /tmp tmpfs size=1002M,noatime,lazytime,nodev,nosuid,mode=1777
tmpfs /var/log tmpfs size=50M,noatime,lazytime,nodev,nosuid,mode=1777

#----------------------------------------------------------------
# MISC: ecryptfs, vboxsf, glusterfs, mergerfs, bind, Btrfs subvolume
#----------------------------------------------------------------


#----------------------------------------------------------------
# SWAP SPACE
#----------------------------------------------------------------


#----------------------------------------------------------------
# PHYSICAL DRIVES
#----------------------------------------------------------------
UUID=19a04222-693b-42aa-95ab-5b17b389f0fd / ext4 noatime,lazytime,rw 0 1

Joulinar · 13 December 2022 10:42

Maybe better to create an entry for the /boot folder to get mounted from SD card. This might avoid having 2 /boot folder.

Dripping6228 · 13 December 2022 12:44

Ok, this is above my knowledge. Do you mean that i have to add a entry in some kind of boot file on the sd-card that will point to the boot dir on the “system” boot dir (in this case the ssd) ?

Joulinar · 13 December 2022 12:54

following could be added to /etc/fstab file

UUID=42fbf56c-4a0b-4b65-8880-7dfb92295778 /boot ext4 noatime,lazytime,rw 0 2

Usually, the system should come up with a mounted /boot folder from SD card. If system is not booting, SSD would need to be connected to a different Linux box (could be a VM as well) to be able to revert the change.

Dripping6228 · 13 December 2022 13:13

Added the line to the last line as well as the second last line as below. but this results in this error message -bash: /boot/dietpi/func/dietpi-globals: No such file or directory [FAILED] DietPi-Login | Failed to load DietPi-Globals. Skipping DietPi login scripts... when doing a sudo reboot

# You can use "dietpi-drive_manager" to setup mounts.
# NB: It overwrites and re-creates physical drive mount entries on use.
#----------------------------------------------------------------
# NETWORK
#----------------------------------------------------------------


#----------------------------------------------------------------
# TMPFS
#----------------------------------------------------------------
tmpfs /tmp tmpfs size=1002M,noatime,lazytime,nodev,nosuid,mode=1777
tmpfs /var/log tmpfs size=50M,noatime,lazytime,nodev,nosuid,mode=1777

#----------------------------------------------------------------
# MISC: ecryptfs, vboxsf, glusterfs, mergerfs, bind, Btrfs subvolume
#----------------------------------------------------------------


#----------------------------------------------------------------
# SWAP SPACE
#----------------------------------------------------------------


#----------------------------------------------------------------
# PHYSICAL DRIVES
#----------------------------------------------------------------
UUID=42fbf56c-4a0b-4b65-8880-7dfb92295778 /boot ext4 noatime,lazytime,rw 0 2
UUID=19a04222-693b-42aa-95ab-5b17b389f0fd / ext4 noatime,lazytime,rw 0 1