[RPi5] How to install LibreELEC on NVMe SSD?

  • Hi.

    As i reconfigure stuff at home i bought a new case for the space to connect a poe/m2 hat in it (main reason was to try the poe part) and as i have a spare nvme i want to install libreelec onto it and remove the existing sd card.

    Problem, i do not have a m2 to usb adapter (or rather, i have a usb m2 enclosure with a nvme in it, but as i do not have spare thermal pads for it i only would try that as a last resort) to copy the image onto it for a fresh install, i did not found anything in the install guide of the wiki regarding that scenario (or overlooked it),.


    I tought of creating a install on the mentioned "external" m2, copy those files onto the nvme trough kodi, remove the sd card and hope that it boots & installs trough the hat nvme.

    Would that work?

    If not, what would be the easiest other way to achieve that without the use of a M2 to usb adapter?

  • Is this on a RPi5? If yes, just use it's netinstall feature.

    Make sure the bootloader EEPROM is up-to-date, power it up with keyboard , mouse and ethernet cable connected and press "shift" to start the installer / RPi Imager.

    so long,

    Hias

  • As i reconfigure stuff at home i bought a new case for the space to connect a poe/m2 hat in it (main reason was to try the poe part) and as i have a spare nvme i want to install libreelec onto it and remove the existing sd card.

    Hi, usually I like to have the "system" and "data" in two different device. And who had trouble with saving/restoring or even loosing huge amount of data after a "problematic" update/upgrade, would agee with me. I would let the OS (LE) in a good and fast SD card, and storing all of media files on that SSD. But this is only my point of view...

  • I run LE from an nvme drive on an RPi5 and it works fine. Just boot the RPi from SD card, write the LE image to the nvme drive using dd, then set the boot config changes needed, power off and remove the SD card, power on again.

  • Is this on a RPi5? If yes, just use it's netinstall feature.

    Make sure the bootloader EEPROM is up-to-date, power it up with keyboard , mouse and ethernet cable connected and press "shift" to start the installer / RPi Imager.

    so long,

    Hias


    I will look into that, might be that i need to use the external enclosure either way even if it do want to.

    Either the cable from m2 hat to pi5 board is not sitting correct (the build manual unfortunately does not state if the led only indictates power of the poe function, or a working m2 connection), or kodi does not like the file system which is used (used it for a few months as a read cache in a synology nas......back when 256GB gen3 drives cost me only 20€ to experiment for that)

    Hi, usually I like to have the "system" and "data" in two different device. And who had trouble with saving/restoring or even loosing huge amount of data after a "problematic" update/upgrade, would agee with me. I would let the OS (LE) in a good and fast SD card, and storing all of media files on that SSD. But this is only my point of view...

    I have all my stuff on a NAS, so apart from librelec/kodi itself there is not much on the sd either way

  • I have all my stuff on a NAS, so apart from librelec/kodi itself there is not much on the sd either way

    For LE installation in that case enough 1-2GB space... a 128GB or bigger SSD isn't a waste for this? The gain? 1-2 seconds of booting time? When comparing with the SSD, I talking about a good SD card like a Samsung EVO Plus or Kingston Canvas Go Plus. To repeat myself: But this is only my point of view...

  • For LE installation in that case enough 1-2GB space...

    That's very tight, my .kodi folder is about 2GB (thumbnails take quite a bit of space) and I don't have a large music/video library.

    Calculate at least 8-16GB of space for the storage partition, remember you also need quite a bit of scratch space - eg Widevine updates need to download and store large image files, kodi updates need space for database migrations (which results in separate, new database files) etc.

    No big deal with current SD cards which are 32GB and up.

    so long,

    Hias