Hello,
I am trying to boot the latest (8.11) NanoPi R5S image, and, well, failing: when powering on the R5S with the SD in place, nothing happens. Booting on a FriendlyElec image works, so it’s not a problem with the hardware.
I gave a look at the DietPi .img and while other images for the R5S have eight partitions, the first seven holding bootloader- and kernel -related code and data, the DietPi image only has one partition, the rootfs.
Is this single-partition scheme normal? Or could the DietPi R5S image have been built wrong?
Cheers,
Albert.
1 Like
Ah dammit my error, I didn’t remove the R5S from our build script where it was only for testing. I’ll recreate functioning images tomorrow night.
2 Likes
@MichaIng I could upload the version from end of October with enabled Wireguard support in meantime 
2 Likes
That would be great.
I think we need to implement an archive for at least the last image of every SBC. VPS drive space would be there.
@MichaIng I have uploaded the R5S image from my personal archive. The old one I renamed only, just to keep it and not going to delete straight away. I guess you would need to invalide the Cloudflare cache still. Otherwise it is not showing up
2 Likes
Cache cleared. The old image can be removed, same as Bookworm one. But I can do that on Sunday of course.
1 Like
Thank you both! I could re-download the image, check that it had all required partitions, and copy it onto the R5S eMMC (with an added line to have /var living on the NVMe stick), and it all works!
2 Likes
So, how is the possibility of transferring OS to the nvme going?
you could boot of an SD card and flash the img file directly to your eMMC or NVMe