You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we use the same IDs when generating disk images. This approach causes some problems, especially on ARM devices, when we have EVE installed on eMMC and we want to run a live image (for testing) from the SD Card. In this case, the partition on eMMC will be detected first than the partition in the SD Card (or USB stick) and will be considered as the rootfs.
How to reproduce
It applies to all EVE versions:
Install EVE-OS to some storage device (eMMC, NVMe) that is listed before SD Card or USB stick
Create a live image and try to boot from SD Card, USB stick
The partitions from the installed device (eMMC, NVMe) will be detected first and mounted instead of the partitions in the SD Card/USB Stick. This will confuse EVE and make it to reboot.
How to solve this issue?
We must implement dynamic UUID generation for disk partitions.
The text was updated successfully, but these errors were encountered:
Description
Currently we use the same IDs when generating disk images. This approach causes some problems, especially on ARM devices, when we have EVE installed on eMMC and we want to run a live image (for testing) from the SD Card. In this case, the partition on eMMC will be detected first than the partition in the SD Card (or USB stick) and will be considered as the rootfs.
How to reproduce
It applies to all EVE versions:
The partitions from the installed device (eMMC, NVMe) will be detected first and mounted instead of the partitions in the SD Card/USB Stick. This will confuse EVE and make it to reboot.
How to solve this issue?
We must implement dynamic UUID generation for disk partitions.
The text was updated successfully, but these errors were encountered: