what is the actual content of /boot with current configuration?
ls -la /boot
have i created another root in my boot? 
dietpi@DietPi:/boot$ ls -la
total 84
drwxr-xr-x 18 root root 4096 Nov 28 08:55 .
drwxr-xr-x 18 root root 4096 Nov 24 12:11 ..
lrwxrwxrwx 1 root root 7 Nov 24 11:54 bin -> usr/bin
drwxr-xr-x 4 root root 4096 Nov 28 08:22 boot
drwxr-xr-x 2 root root 4096 Nov 24 12:11 dev
drwxr-xr-x 59 root root 4096 Nov 28 08:45 etc
drwxr-xr-x 3 root root 4096 Nov 24 12:08 home
lrwxrwxrwx 1 root root 7 Nov 24 11:54 lib -> usr/lib
drwx------ 2 root root 16384 Nov 24 11:53 lost+found
drwxr-xr-x 2 root root 4096 Nov 24 12:08 media
drwxr-xr-x 6 root root 4096 Nov 24 12:11 mnt
drwxr-xr-x 2 root root 4096 Nov 24 11:54 opt
drwxr-xr-x 2 root root 4096 Sep 3 13:10 proc
drwx------ 3 root root 4096 Nov 28 08:56 root
drwxr-xr-x 2 root root 4096 Nov 24 12:11 run
lrwxrwxrwx 1 root root 8 Nov 24 11:54 sbin -> usr/sbin
drwxr-xr-x 2 root root 4096 Nov 24 11:54 srv
drwxr-xr-x 2 root root 4096 Sep 3 13:10 sys
drwxrwxrwt 2 root root 4096 Nov 24 12:11 tmp
drwxr-xr-x 11 root root 4096 Nov 24 11:54 usr
drwxr-xr-x 12 root root 4096 Nov 28 08:21 var
dietpi@DietPi:/boot$
ah my fault, was thinking that there is just the boot folder located on SD card, but it is the entire system, forget my idea of mounting the boot folder separately and remove the entry from /etc/fstab
1 Like
Mabey i could just remove the rest of the system from the sd-card and go with your sollution?
probably this will not work. Another option is to mound to SD card somewhere else and to copy manually content from SSD boot folder to SD card boot folder
Let’s check it
mkdir /mnt/boot
mount /dev/mmcblk0p1 /mnt/boot
ok hope that’s gonna work. If yes, we could verify the content of both folder
ls- la /boot
ls -la /mnt/boot
1 Like
Hey!! it worked!! thank u soo much for hangin in there!
dietpi@DietPi:~$ ls -la /boot/
total 28064
drwxr-xr-x 4 root root 4096 Dec 8 13:28 .
drwxr-xr-x 18 root root 4096 Nov 24 12:11 ..
-rw-r--r-- 1 root root 0 Dec 4 22:57 .next
-rw-r--r-- 1 root root 4780093 Nov 30 11:05 System.map-5.15.80-rockchip
-rw-r--r-- 1 root root 2713 Nov 24 12:00 boot.cmd
-rw-r--r-- 1 root root 2785 Nov 24 12:05 boot.scr
-rw-r--r-- 1 root root 188851 Nov 30 11:05 config-5.15.80-rockchip
drwxr-xr-x 4 root root 4096 Dec 8 14:14 dietpi
-rw-r--r-- 1 root root 18092 Nov 22 21:42 dietpi-LICENSE.txt
-rw-r--r-- 1 root root 15300 Nov 22 21:42 dietpi-README.md
-rw-r--r-- 1 root root 16292 Dec 8 13:28 dietpi.txt
-rw-r--r-- 1 root root 310 Nov 28 09:01 dietpiEnv.txt
lrwxrwxrwx 1 root root 20 Dec 4 22:57 dtb -> dtb-5.15.80-rockchip
drwxr-xr-x 3 root root 4096 Dec 4 22:57 dtb-5.15.80-rockchip
-rw-r--r-- 1 root root 7012421 Dec 4 22:57 initrd.img-5.15.80-rockchip
lrwxrwxrwx 1 root root 24 Dec 4 22:57 uInitrd -> uInitrd-5.15.80-rockchip
-rw-r--r-- 1 root root 7012485 Dec 4 22:57 uInitrd-5.15.80-rockchip
-rwxr-xr-x 1 root root 9645544 Nov 30 11:05 vmlinuz-5.15.80-rockchip
lrwxrwxrwx 1 root root 24 Dec 4 22:57 zImage -> vmlinuz-5.15.80-rockchip
dietpi@DietPi:~$
dietpi@DietPi:~$ ls -la /mnt/42fbf56c-4a0b-4b65-8880-7dfb92295778/boot/
total 28064
drwxr-xr-x 4 root root 4096 Dec 13 13:44 .
drwxr-xr-x 18 root root 4096 Dec 13 13:43 ..
-rw-r--r-- 1 root root 4780093 Dec 13 13:44 System.map-5.15.80-rockchip
-rw-r--r-- 1 root root 2713 Dec 13 13:44 boot.cmd
-rw-r--r-- 1 root root 2785 Dec 13 13:44 boot.scr
-rw-r--r-- 1 root root 188851 Dec 13 13:44 config-5.15.80-rockchip
drwxr-xr-x 4 root root 4096 Dec 13 13:44 dietpi
-rw-r--r-- 1 root root 18092 Dec 13 13:44 dietpi-LICENSE.txt
-rw-r--r-- 1 root root 15300 Dec 13 13:44 dietpi-README.md
-rw-r--r-- 1 root root 16292 Dec 13 13:44 dietpi.txt
-rw-r--r-- 1 root root 310 Dec 13 13:44 dietpiEnv.txt
lrwxrwxrwx 1 root root 20 Dec 13 13:44 dtb -> dtb-5.15.80-rockchip
drwxr-xr-x 3 root root 4096 Dec 13 13:44 dtb-5.15.80-rockchip
-rw-r--r-- 1 root root 7012421 Dec 13 13:44 initrd.img-5.15.80-rockchip
lrwxrwxrwx 1 root root 24 Dec 13 13:44 uInitrd -> uInitrd-5.15.80-rockchip
-rw-r--r-- 1 root root 7012485 Dec 13 13:44 uInitrd-5.15.80-rockchip
-rwxr-xr-x 1 root root 9645544 Dec 13 13:44 vmlinuz-5.15.80-rockchip
lrwxrwxrwx 1 root root 24 Dec 13 13:44 zImage -> vmlinuz-5.15.80-rockchip
dietpi@DietPi:~$
Did you copied stuff manually from SSD to SD card? And on a reboot the request to perform another reboot has been gone away?
Yes, i used the dietpi-drive-manager to mount the SD card. Then removed the contens of the SD card /boot dir. copied the contens of the SSD /boot to the now empty SD card /boot.
then after a system reboot the message was gone.
Ok thats supporting my theory, SD card boot folder is used on early boot process but not actively used on running system. Now as both folder are same and having a matching kernel, reboot message is gone.
1 Like
Did you solve it?
I’m with the exactly same problem. I did the same as you, following the same tutorial to flash the boot in SD Card and copy it to a SSD, generating a new uuid.
As you can see above, topic was solved. Anyway, as this is a 2 years old topic, better you create an one new one providing all relevant information about your system.