G_DIETPI_VERSION_CORE=8
G_DIETPI_VERSION_SUB=21
G_DIETPI_VERSION_RC=1
G_GITBRANCH=‘master’
G_GITOWNER=‘MichaIng’
bookworm
Orange Pi 5 Plus (aarch64)
Linux KHG 5.10.160-legacy-rk35xx #1 SMP Mon Aug 28 01:21:24 UTC 2023 aarch64 GNU/Linux
5V 4A
Samsung EVO 32 GB
Creating a bug report/issue
Required Information
DietPi version | cat /boot/dietpi/.version
Distro version | echo $G_DISTRO_NAME $G_RASPBIAN
Kernel version | uname -a
Architecture | dpkg --print-architecture
SBC model | echo $G_HW_MODEL_NAME or (EG: RPi3)
Power supply used | (EG: 5V 1A RAVpower)
SD card used | (EG: SanDisk ultra)
60879d40-c57e-485b-8a15-8209f4040897
Additional Information (if applicable)
Software title | (EG: Nextcloud)
Was the software title installed freshly or updated/migrated?
Can this issue be replicated on a fresh installation of DietPi?
← If you sent a “dietpi-bugreport”, please paste the ID here →
Bug report ID | echo $G_HW_UUID
Steps to reproduce
…Seit einer Woche versuche ich dem Orange Pi 5 das booten von emmc beizubringen. Kein Erfolg. Dann habe ich Armbian installiert und dort wird im armbian-config Menü gefragt ob man über emmc booten will. Angeklickt und läuft.
Jetzt habe ich 2 Möglichkeiten: Stecke ich die Dietpi-SDCard ein,
startet dietpi os. Entferne ich sie, dann startet Armbian.
Ich möchte über emmc das Dietpi-OS starten. Gibt es da Hoffnung für mich?
kernelversion: Linux KHG 5.10.160-legacy-rk35xx #1 SMP Mon Aug 28 01:21:24 UTC 2023 aarch64 GNU/Linux
Nach meinem Verständnis müssten die Partitionen auf emmc erst einmal formatiert werden, bevor der Dietpi-Bootloader darauf geschrieben wird. Derzeit startet de Pi mit SD-Card mit Dietpi und ohne Karte mit Armbian.
Guys even if we have a couple of people who speak German, it would be appreciate if you could use English instead. We are an international community and the topic might be interesting for other as well
the contribution
“Moving a running DietPi system to a USB stick/disk or onboard eMMC”.
is probably the best guide for my problem.
It occurred to me that the shrinking process could also be automated:
If instead of fully expanding the partition right away, you expand the partition only when needed, then this point could be removed from the process.
An example: The partition is extended by 1GB during installation. In the future it is checked whether this limit is reached and 200MB before again extended by 1GB. Then one does not need to worry about this process any more.
Do you still have that problem, @Carl52? I have an OrangePi 5Plus that I can run of either the eMMC or an NVMe m.2 drive (and the latter is WAY preferable… roughly 10x faster).
IIRC (and I did this a couple of months ago), the trick was to make sure that the boot partition on the eMMC (or NVMe) is actually marked as active. At least back then that was missing in the instructions.
Thanks for the quick reply. The nas disk is already attached to the nvme. I don’t want to have the OS on it. Because I have no idea but much interest. Therefore emmc. Of which I have 2 (16 and 256GB). Could I partition the large emmc also with 128GB so I have not bought it for nothing?
I saw that you are working with the dietpie-imager - is my idea really not feasible?
from my point of view (half knowledge) i don’t see any sense in expanding the disk fully. Perhaps you could explain this to me briefly (this is just a request).
.
