- Official Post
I've managed to get LE to boot from an eSata SSD with vpeter 7.95.3 K3.14.
I modified uEnv.txt on the SD card to point root=/dev/sda1 and disk=/dev/sda2.
However, I really want to use root=UUID=xxxx and disk=UUID=xxxx but the SD card and SSD have the same UUID.
Mercury:# blkid
/dev/sda1: SEC_TYPE="msdos" LABEL="LIBREELEC" UUID="42EE-5EC6" TYPE="vfat" PARTUUID="a22eb27c-01"
/dev/sda2: LABEL="Storage" UUID="e8c5ba0a-3f3c-41f4-988a-cd06f120819c" TYPE="ext4" PARTUUID="a22eb27c-02"
/dev/mmcblk0: PTUUID="a22eb27c" PTTYPE="dos"
/dev/mmcblk0p1: SEC_TYPE="msdos" LABEL="LIBREELEC" UUID="42EE-5EC6" TYPE="vfat" PARTUUID="a22eb27c-01"
/dev/mmcblk0p2: UUID="e8c5ba0a-3f3c-41f4-988a-cd06f120819c" TYPE="ext4" PARTUUID="a22eb27c-02"
/dev/loop0: TYPE="squashfs"
I assume this is normal because both were created from the same image.
It seems to boot happily with the eSata and a USB HDD attached but I want to make sure it doesn't try to use the HDD as the boot image - and fail!
So can I just use gparted and assign a new UUID to /dev/sdax
Also, what files do I really need on the SD card. Can I get away with just uEnv.txt, KERNEL and SYSTEM?