Thanks for the clarification… While I understand eMMC in general is less reliable than SSD, my reasoning for wanted to install TrueNAS OS on it is because that’s where the Ugreen NAS OS is/was installed (UGOS). I’m kinda going by assumption that both OS’s would wear out the eMMC drive more or less the same, and Ugreen wouldn’t have put their OS there if it was an unreliable eMMC. But yea, an SSD would definitely be better - 100% agree.
Surely by the time the emmc has worn out it would have been many several years anyhow, perhaps by then you would have replaced the nas with a better one.
Doesn’t most of the work, happen in ram and maybe VMs/dockers can be stored and run from the nvme or ssds.
Most of these mini nas pcs come with emmc, I guess if it did wear out suddenly after 2-3 years you could then move over to an ssd or nvme and sacrifice ports/storage etc
asked dr google:
The estimated life of eMMC can also be influenced by the amount of data written to the device. For example, if a user writes 10 GB of data per day, the eMMC may last for several years depending on its capacity and the number of P/E cycles. In automotive applications, where eMMC is used for long-term reliability, the storage is designed to handle up to 10 years of use.6
In practical terms, eMMC can last for at least 10 years under normal usage conditions, but the exact lifespan depends on the specific device and how it is used.5 Some users have reported that lower-quality eMMC in budget devices may fail sooner, especially if they are subjected to heavy write operations.
level1techs and lawrence systems recently did a review on the beelink mini nas on youtube with emmc memory, both also suggested todays emmc has improved error control and reliability greatly over the last several years to the points its reliable.
Mentioned here
I had the same issue when trying to install TrueNAS 25.04 on a Beelink ME mini.
The fix I used was similar to the post above from Schuwi (from Apr 23) but slightly different. The changes I did relied on their work so thank you to them for their detailed post.
On the Beelink Me Mini as well as /dev/mmcblk0boot0 and /dev/mmcblk0boo1 there’s also a device /dev/mmcblk0rpmd which gets picked up by the get_partitions function in /lib/python3/dist-packages/truenas_installer/utils.py.
To fix the issue I followed the Workaround section iinb Schuwi’s post but for step 2 I edited line 46 in the file and changed it from
for partdir in filter(lambda x: x.is_dir() and x.name.startswith(device), dir_contents):
to
for partdir in filter(lambda x: x.is_dir() and x.name.startswith(device + 'p'), dir_contents):
and I skipped step 3.
The thinking behind this was that if the installer needed the devices for each partition and they would start with /dev/mmcblk0p. All other devices beginning with /dev/mmcblk0 could be ignored.
I also changed the value in the sleep function on line 61 from 1 second to 5. Just to make sure nothing timed out and that there was enough delay.
This worked nicely. You don’t need to delete the /dev/mmcblk0boot devices or worry about whether they’re readonly because the installer doesn’t pick them up. After several failures to get the installer to work this change fixed the problem and it installed right away.
6 Likes
Just registered here to say that this analysis seems to be correct and the workaround worked
2 Likes
It worked for me on a beelink me mini. Thanks a lot !
Also wanted to say that this worked for me on a beelink mini me, thanks for the workaround.
This worked for me on my Beelink Mini Me. Thank you. I’m going to refer a reddit thread over here for the same issue!
1 Like
Hello,
I have tried the echo-commands, I have tried the dd commands, but nothing helps. Tried both with Truenas 24.10 and 25.latest.
This is a Beelink mini.
Can someone help? I am not THAT strong with linux-commands and such…
Best,
Kurt
Norway
Hello,
I am still strugling, with the same beelink mini me and to install Truenas. Could I bother you to gather the instructions you did to make it work? Just dont ubderstand why I cant get my setup to install this.
Best,
Kurt
Norway
Same here with the G9, the shell solutions but they unfortunately have not helped
Hey Kurt. I only did what Buxton posted to do: edit the utils.py file and add in the + ‘p’ option on line 46. Don’t reboot, just type ‘exit’ after you edit the file in the shell (I used vi…no nano available) and then start the installer again. Hope this helps! I checked to see if you can edit that file directly from a windows/mac computer, but I can’t seem to get to it with plugging the thumbdrive into my computer. Maybe someone else can chime in on this. Thanks again @Buxton for the fix.
1 Like
Thanks man! First I have to get to edit the utils.py file…from installer-shell that is…feeling kinda newbie now… 
Hey Mark! Now it works! Thanks to you, Buxton and everyone else on this thread! 
Hello fellow kids.
Joining the chorus of people creating forum accounts.
buxton (via schuwi) got the install working for me on a beelink me mini.
Thanks for sharing the workaround 
I’m a nano guy (barely), so trying to edit the utils.py with vi is resulting in a handful of tab/indent/spacing error messages after I save and exit back to the installer. Any obvious tips/commands I should be using when doing the the line delete/add? Thanks!
sed -i '/for _try in range(tries):/a \ await asyncio.sleep(1)' /lib/python3/dist-packages/truenas_installer/utils.py
This one liner shoud add a wait, you only need to paste into shell, tested on odroid h3.
Do not remove any white space.
2 Likes
Tried all of these on 25.01 on G9 Nucbox
The second attempt just doing the normal install it worked, but then the OS wouldn’t load properly so assumed the USB image was corrupted. Reimaged the USB using different method (unetbootin, rufus, balenaetcha). None of which have triggered the normal install succesfully.
Tried all the work arounds here (except for modifying installation files), including others such as re-partitioning using Gparted, and using the 24.10 install ISO.
Wasted so much of time I don’t have trying to get this to work 
anyone got any more ideas?
Well, I solved it. I installed version 23.10 without fail, then updated it to 25.04 from the OS. Was up and running in 10 minutes. I suggest going this route, it’s much less fiddly.