Meestor_X Posted December 12, 2024 Posted December 12, 2024 (edited) running 24.8.3, and Armbian-install's screen looks like this: Current root: UUID=117b851b-2be0-4bb7-8572-7edce1ef7375 SD card (/dev/mmcblk1) 1 Boot from SD - system on SATA, USB or NVMe 2 Boot from - system on 3 Boot from - system on SATA, USB or NVMe 5 Install/Update the bootloader on SD card (/dev/mmcblk1) I have a µSD card inserted and a 4gb eMMC, but it looks like the names of these devices are missing? Edited December 12, 2024 by Meestor_X 0 Quote
Igor Posted December 12, 2024 Posted December 12, 2024 32 minutes ago, Meestor_X said: running 24.8.3, and Armbian-install's screen looks like this By showing symptoms without logs people can only tell you that "something is wrong" Which you already know. 0 Quote
brentr Posted December 12, 2024 Posted December 12, 2024 I think I have seen this before, but wasn't sure whether it was a bug. On your system, what is the output of: # ls -l /dev/mmcblk* 0 Quote
Meestor_X Posted December 12, 2024 Author Posted December 12, 2024 1 hour ago, Igor said: By showing symptoms without logs people can only tell you that "something is wrong" Which you already know. Right you are! Is this the preferred method to send logs? 0 Quote
Meestor_X Posted December 12, 2024 Author Posted December 12, 2024 (edited) 1 hour ago, brentr said: What is the output of: ls -l /dev/mmcblk* # ls -l /dev/mmcblk* brw-rw---- 1 root disk 179, 0 Dec 12 00:46 /dev/mmcblk0 brw-rw---- 1 root disk 179, 1 Dec 12 00:46 /dev/mmcblk0p1 brw-rw---- 1 root disk 179, 32 Dec 12 00:46 /dev/mmcblk1 brw-rw---- 1 root disk 179, 33 Dec 12 00:46 /dev/mmcblk1p1 Edited December 12, 2024 by Meestor_X 0 Quote
Igor Posted December 13, 2024 Posted December 13, 2024 8 hours ago, Meestor_X said: Is this the preferred method to send logs? Yes, that is best way. First question is - is eMMC device recognized and it seems it is. So it would be handy to see everything, try updating to latest daily builds ... bug in armbian-install script is possible too. 0 Quote
Meestor_X Posted December 13, 2024 Author Posted December 13, 2024 9 hours ago, Igor said: Yes, that is best way Ok, I'm not sure that it's working? # armbianmonitor -u Collecting info and sending to paste.armbian.com, wait... /usr/bin/armbianmonitor: line 976: iostat: command not found <!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8"> <title>Error</title> </head> <body> <pre>Cannot POST /log</pre> </body> </html> Please post the URL in the forum where you've been asked for. 9 hours ago, Igor said: is eMMC device recognized and it seems it is. Yes, it's recognized and working as expected. The system runs off of the eMMC when there's no bootable image on the µSD card or no card inserted. 9 hours ago, Igor said: try updating to latest daily builds ... To do a fresh install of Armbian would take quite a while, I had tried a couple of days ago, but Armbian-install wasn't working so I went back to 24.8.3. However, I tried apt update/upgrade and ran into a new problem... 0 Quote
Meestor_X Posted December 16, 2024 Author Posted December 16, 2024 @Igor I got armbianmonitor working and sent the link it created in a PM to you. 0 Quote
Werner Posted December 17, 2024 Posted December 17, 2024 5 hours ago, Meestor_X said: armbianmonitor Try PASTE_SERVER_HOST=paste.armbian.de armbianmonitor -u I leave this here for others to find and use this workaround. 0 Quote
Igor Posted December 17, 2024 Posted December 17, 2024 13 hours ago, Meestor_X said: in a PM to you There is no need for privacy as logs don't carry any private information. And I didn't ask you to send me anything I advised you how you should present information to this community in order to meet minimum requirements. Who will look into this, I don't know. There is no warranty anyone will - support is "best effort". This is best we can do. Personally I am overloaded with problems for years, so I won't be resolving this problem. Not anytime soon. To have a picture on how much problems are thrown our / my way ... We will hire few people eventually to help us helping you around your endless problems faster. I have no better idea. As you can see, even our paste server is broken and need fixing ... 0 Quote
Meestor_X Posted December 17, 2024 Author Posted December 17, 2024 (edited) Copy that, @Igor. Just learning my way around here. 3 hours ago, Igor said: We will hire few people eventually to help us helping you around your endless problems faster Hopefully my donation will help a little! I appreciate you and your team. Armbian is a great gift to the SBC community. Edited December 17, 2024 by Meestor_X 1 Quote
Meestor_X Posted January 1 Author Posted January 1 (edited) Ok, I see the problem, but not the solution. In main() there is this code to find which mmcblk# device is the eMMC and which is the SD card. # find real mmcblk device numbered 0, 1, 2 for eMMC, SD for ret in $(find /dev -name 'mmcblk[0-2]' -and -type b) do if [ -b ${ret}boot0 ];then emmc_dev=$ret else sd_dev=$ret fi done The issue is that there's no "boot0" file at either device. I've no idea how to ACTUALLY determine which is which, except I know in my case the eMMC is ALWAYS mmcblk0 and the SD card is ALWAYS mmcblk1. I expect that's not always true, but for my purposes, I can do: emmc_dev='/dev/mmcblk0' sd_dev='/dev/mmcblk1' and the names populate correctly in the menu. Again, not a solution by any means, I've done some scouring on the 'net to see if there's any good way to determine the block name of the SD and eMMC, but I can't find anything. Edited January 1 by Meestor_X 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.