


pingtoo wrote:Sensei Art,
First, just to clear I don't have Odroid-M1S, so what I said here is speculation. it is just based on my experience with other SBC.
You cannot take Gentoo stage3 image as boot image. it does not contain any necessary binary for booting a ARM (or ARM64) board.
My guess is that at this stage you have lost the u-boot un eMMC, therefor you are not able to boot without external help.
From what I saw on ORDOID wiki it seems to me their design would allow you boot from SD card when eMMC fail, so if you download the a working OS on to SD card and boot from there you can begin recover(reflash) eMMC.
In order to better working on the problem you should connect board UART to PC so you can see booting messages.
NeddySeagoon wrote:Sensei Art,
I don't have Odroid either. SBCs typically have vendor specific boot mechanisms.
Propritary code that runs on the GPU, in the case of the Raspberry Pi.
Whatever loads u-boot on your Odroid-M1S.
The Gentoo ARM64 Minimal Installation CD expects be be supported by UEFI firmware. You don't have that, or you would not need the u-boot boot loader.
Its generally a bad idea to do things that you cannot easily undo.
You need to recover to where you can boot something, then use that something to install Gentoo, or alternatively, prepare a bootable SD card somewhere else an move it to the Odroid. The advantage with that approach is that the SD is easy to recover when it does not work as expected.
Its likely you will need the serial console to debug your Gentoo install too. Its always good to know that works before you need it in anger.


I am following this guide step by step: https://wiki.gentoo.org/wiki/Hardkernel_ODROID-M1SNeddySeagoon wrote:Sensei Art,
You need a working boot loader somewhere. The SD card has a higher priority in the boot order than the eMMC.
It follows that if you have a bootable SD, you can use it to recover the eMMC.
Its likely easier to prepare a bootable SD away from the Odroid-M1S than it is to fix the eMMC.
A bit like this.
I can't test that page.
I think this board does not support booting from NVMe, so you only need to partition eMMC.Sensei Art wrote:I am following this guide step by step: https://wiki.gentoo.org/wiki/Hardkernel_ODROID-M1S
I installed Ubuntu Server on microSD and now trying to figure out what to do next.
Looks like I should set partitions in NVMe SSD and eMMC.

Now I am working according this guide: https://distfiles.gentoo.org/releases/a ... 28Z.tar.xzpingtoo wrote:I think this board does not support booting from NVMe, so you only need to partition eMMC.Sensei Art wrote:I am following this guide step by step: https://wiki.gentoo.org/wiki/Hardkernel_ODROID-M1S
I installed Ubuntu Server on microSD and now trying to figure out what to do next.
Looks like I should set partitions in NVMe SSD and eMMC.
You can find partition table at Odroid Wiki Partition table page
is the link a mistake? The link point to a stage3 tarball. I like to point out Gentoo stage 3 is NOT a boot-able media. A simple flash of the image will not result a successful boot.Sensei Art wrote: Now I am working according this guide: https://distfiles.gentoo.org/releases/a ... 28Z.tar.xz
Which claims that it is possible to boot from NVMe SSD.
So may be you have already got you eMMC flashed with correct boot binary. and if you already tried with eMMC boot with success than please forgive me to butt in. Just ignore my stage 3 comment above.Sensei Art wrote:I am running a clone installation process both on eMMC and NVMe SSD.

Yes, it was a mistake. Here is the correct one: https://www.famera.cz/blog/computers/ge ... -luks.htmlpingtoo wrote:is the link a mistake? The link point to a stage3 tarball. I like to point out Gentoo stage 3 is NOT a boot-able media. A simple flash of the image will not result a successful boot.Sensei Art wrote: Now I am working according this guide: https://distfiles.gentoo.org/releases/a ... 28Z.tar.xz
Which claims that it is possible to boot from NVMe SSD.
It's okay buddy. Maybe you can help me with other issue that I am facing during the installation.pingtoo wrote:So may be you have already got you eMMC flashed with correct boot binary. and if you already tried with eMMC boot with success than please forgive me to butt in. Just ignore my stage 3 comment above.Sensei Art wrote:I am running a clone installation process both on eMMC and NVMe SSD.
Code: Select all
!!! Section 'gentoo' in repos.conf has location attribute set to nonexistent directory: '/var/db/repos/Gentoo's
!!! Invalid Repository Location (not a dir): '/var/db/repos/Gentoo's
>>>Regenerating/etc/ld.so.cache...

The error message lead me to think the content in repos.conf have some error. May be you can share the file so we can review if there is any mistake in it.Sensei Art wrote:I chrooted Gentoo as described in the link above. It entered me into server. Then I ran "env-update" and got the following output:Something went wrong and I am not sure how to react.Code: Select all
!!! Section 'gentoo' in repos.conf has location attribute set to nonexistent directory: '/var/db/repos/Gentoo's !!! Invalid Repository Location (not a dir): '/var/db/repos/Gentoo's >>>Regenerating/etc/ld.so.cache...

Sure, I already understood that it doesn't have any boot loader. I guess that I am going to configure the bootloader later.NeddySeagoon wrote:Sensei Art,
A stage3 is just a small corner of Gentoo user space.
There is no kernel and no bootloader. It cannot influence the possible bootable media. That has to be done before any boot loader can be loaded.
Is the boot loader that loads the kernel (which is not provided in the stage3)
Its perfectly possible to have root on NVMe even if NVMe is not bootable.
I am running the installation through Ubuntu Server on my Odroid-M1S and browse the forum with my tablet. It would be quite difficult to share files from the device.pingtoo wrote:The error message lead me to think the content in repos.conf have some error. May be you can share the file so we can review if there is any mistake in it.Sensei Art wrote:I chrooted Gentoo as described in the link above. It entered me into server. Then I ran "env-update" and got the following output:Something went wrong and I am not sure how to react.Code: Select all
!!! Section 'gentoo' in repos.conf has location attribute set to nonexistent directory: '/var/db/repos/Gentoo's !!! Invalid Repository Location (not a dir): '/var/db/repos/Gentoo's >>>Regenerating/etc/ld.so.cache...
Code: Select all
[DEFAULT]
main-repo = gentoo
[gentoo]
location = /var/db/repos/gentoo
sync-type = git
clone-depth = 1
sync-depth = 1
sync-uri = https://github.com/gentoo-mirror/gentoo
auto-sync = yes
sync-git-verify-commit-signature = true
#commit-hash = 35c0c279daace8053ac9cc0e58ecb96bfb777e17
#clone-date = 2021-04-11
Which command should I run to review the content of the file?pingtoo wrote:Sensei Art,
OK, so you need to review the content of repos.conf.
I will share mine as example, my repos.conf is a directory and in there is a file name gentoo.conf and the file content isSo as you can see the "location = /var/db/repos/gentoo" and your's may be different?Code: Select all
[DEFAULT] main-repo = gentoo [gentoo] location = /var/db/repos/gentoo sync-type = git clone-depth = 1 sync-depth = 1 sync-uri = https://github.com/gentoo-mirror/gentoo auto-sync = yes sync-git-verify-commit-signature = true #commit-hash = 35c0c279daace8053ac9cc0e58ecb96bfb777e17 #clone-date = 2021-04-11
I am surprised by your questionSensei Art wrote:Which command should I run to review the content of the file?pingtoo wrote:Sensei Art,
OK, so you need to review the content of repos.conf.
I will share mine as example, my repos.conf is a directory and in there is a file name gentoo.conf and the file content isSo as you can see the "location = /var/db/repos/gentoo" and your's may be different?Code: Select all
[DEFAULT] main-repo = gentoo [gentoo] location = /var/db/repos/gentoo sync-type = git clone-depth = 1 sync-depth = 1 sync-uri = https://github.com/gentoo-mirror/gentoo auto-sync = yes sync-git-verify-commit-signature = true #commit-hash = 35c0c279daace8053ac9cc0e58ecb96bfb777e17 #clone-date = 2021-04-11

Code: Select all
!!! Section 'gentoo' in repos.conf has location attribute set to nonexistent directory: '/var/db/repos/Gentoo's
!!! Invalid Repository Location (not a dir): '/var/db/repos/Gentoo's
>>>Regenerating/etc/ld.so.cache...Code: Select all
[DEFAULT]
main-repo = gentoo
[gentoo]
location = /var/db/repos/gentoo
sync-type = git
clone-depth = 1
sync-depth = 1
sync-uri = https://github.com/gentoo-mirror/gentoo
auto-sync = yes
sync-git-verify-commit-signature = true
#commit-hash = 35c0c279daace8053ac9cc0e58ecb96bfb777e17
#clone-date = 2021-04-11Code: Select all
cat repos.confCode: Select all
cat: repos.conf: No such file or directory Code: Select all
cat /etc/portage/repos.confCode: Select all
cat /etc/portage/repos.conf/gentoo.confIs this a direct copy from the error output, or did you transcribe it? The capitalization of Gentoo seems unexpected here, as does the trailing s after the single-quoted string.Sensei Art wrote:Code: Select all
!!! Section 'gentoo' in repos.conf has location attribute set to nonexistent directory: '/var/db/repos/Gentoo's !!! Invalid Repository Location (not a dir): '/var/db/repos/Gentoo's
Did you run that command in the correct directory? If you do not set a path, then the current working directory is implied. You do not indicate in what directory you ran the command.Sensei Art wrote:I ranThe output wasCode: Select all
cat repos.confPlease help me to pass this obstacle.Code: Select all
cat: repos.conf: No such file or directory
This is likely because the title is near the length limit, and your reply would exceed the limit. This is a well known issue with multiple forum threads discussing it. As a workaround, set the subject of your reply to be empty. I will merge these threads for you.Sensei Art wrote:By the way, I opened a new thread because I can't post on the previous one for some reason. I get error in posting.

I tried both of them and got an output that there is not such file or directory.pingtoo wrote:Sensei Art,
I am not 100% sure the current stage3 tarball structure. so please tryIf above code give you error, tryCode: Select all
cat /etc/portage/repos.confif both give you error we will need to see some directory structure in order to understand your current condition. However since you are not able to copy/paste command output, this will put us in to difficult condition. will you able to use a second computer connect to the board with serial cable?Code: Select all
cat /etc/portage/repos.conf/gentoo.conf

Thank you for merging the threads.Hu wrote:Is this a direct copy from the error output, or did you transcribe it? The capitalization of Gentoo seems unexpected here, as does the trailing s after the single-quoted string.Sensei Art wrote:Code: Select all
!!! Section 'gentoo' in repos.conf has location attribute set to nonexistent directory: '/var/db/repos/Gentoo's !!! Invalid Repository Location (not a dir): '/var/db/repos/Gentoo'sDid you run that command in the correct directory? If you do not set a path, then the current working directory is implied. You do not indicate in what directory you ran the command.Sensei Art wrote:I ranThe output wasCode: Select all
cat repos.confPlease help me to pass this obstacle.Code: Select all
cat: repos.conf: No such file or directoryThis is likely because the title is near the length limit, and your reply would exceed the limit. This is a well known issue with multiple forum threads discussing it. As a workaround, set the subject of your reply to be empty. I will merge these threads for you.Sensei Art wrote:By the way, I opened a new thread because I can't post on the previous one for some reason. I get error in posting.
I am not sure if there is another post from you after above post. But my browser given me error if I try to see next page, so I will use above post to continue this conversation.Sensei Art wrote:Thank you for merging the threads.Hu wrote:Is this a direct copy from the error output, or did you transcribe it? The capitalization of Gentoo seems unexpected here, as does the trailing s after the single-quoted string.Sensei Art wrote:Code: Select all
!!! Section 'gentoo' in repos.conf has location attribute set to nonexistent directory: '/var/db/repos/Gentoo's !!! Invalid Repository Location (not a dir): '/var/db/repos/Gentoo'sDid you run that command in the correct directory? If you do not set a path, then the current working directory is implied. You do not indicate in what directory you ran the command.Sensei Art wrote:I ranThe output wasCode: Select all
cat repos.confPlease help me to pass this obstacle.Code: Select all
cat: repos.conf: No such file or directoryThis is likely because the title is near the length limit, and your reply would exceed the limit. This is a well known issue with multiple forum threads discussing it. As a workaround, set the subject of your reply to be empty. I will merge these threads for you.Sensei Art wrote:By the way, I opened a new thread because I can't post on the previous one for some reason. I get error in posting.
It was a transcript. The Android's auto-correct probably messed it up.
I didn't know what is the correct directory. Today I tried to ran the command in the directories that @pingtoo suggested, but it didn't make any change. Please check it up: https://ibb.co/LCcNhQw

Same here. I get error if I try to see the next page. I guess it's happened after the threads were merged. There are not other posts anyway.pingtoo wrote:I am not sure if there is another post from you after above post. But my browser given me error if I try to see next page, so I will use above post to continue this conversation.
I understand. I will begin from scratch and follow the standard handbook.pingtoo wrote:It appear to me there are two issues, May be they are related or may be they are not.
1. the error about "Invalid Repository Location ...". I think it is due to the procedure you follow is a bit of misleading, the command "env-update" that cause this error was introduced too soon at this stage. I think the author of the procedure is either a very experienced Gentoo user or the article was written in early days Gentoo that have different directory structure or the etc-update command have different logic. Anyway I think you can possibly ignore this error OR proceed to next (get portage tree) first and come back to run etc-update and source /etc/profile.
2. The error about "No such file or directory" for reference to "repos.conf" is a bit of alarming. If the stage3 was decomposed correctly you should not get this error, the other possibility of getting this error is you executed in a wrong location (wrong current directory). Although I am not able to see how its possible but that is the only explain I can come up with.
I recommend you use Gentoo handbook's Configuring Portage as basis and review the link article you followed. The Gentoo handbook gave you verbose detail but better explained, whereas the link you follow give you quick step execution but lack of detail on why and howto handle when things works differently.

Code: Select all
blkid |grep -E '(nvme0n1p2|root_lv)'
/dev/nvme0n1p2: UUID="aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa" BLOCK_SIZE="1024" TYPE="ext2" PARTLABEL="primary" PARTUUID="aaaaaaaa-1111-1111-1111-111111111111"
/dev/mapper/vg_system-root_lv: UUID="bbbbbbbb-bbbb-bbbb-bbbb-bbbbbbbbbbbb" BLOCK_SIZE="512" TYPE="xfs"Code: Select all
blkid |grep -E '(nvme0n1p3|root_lv)'
/dev/nvme0n1p3: UUID="cccccccc-cccc-cccc-cccc-cccccccccccc" TYPE="crypto_LUKS" PARTLABEL="primary" PARTUUID="cccccccc-2222-2222-2222-222222222222"
/dev/mapper/vg_system-root_lv: UUID="bbbbbbbb-bbbb-bbbb-bbbb-bbbbbbbbbbbb" BLOCK_SIZE="512" TYPE="xfs"