View previous topic :: View next topic |
Author |
Message |
Tzuriel Apprentice
Joined: 01 Jun 2004 Posts: 260
|
Posted: Tue May 17, 2022 12:59 am Post subject: Sakaki EFI Install Guide: !!! It seems /run is not mounted. |
|
|
I'm installing a new machine and following this user wiki page:
User:Sakaki/Sakaki's EFI Install Guide/Building the Gentoo Base System Minus Kernel
I'm on the step: "Installing an Up-to-Date Portage Tree" and after having given the following command:
Code: | (chroot) livecd / # emain sync --auto
|
I get an error like so:
Code: | ...
Performing Global Updates
(Could take a couple of minutes if you have a lot of binary packages.)
!!! It seems run is not mounted. Process management may malfunction.
=== Sync completed for gentoo
Action: sync for repo: gentoo, returned code = 0
|
Update: /run actually exists, so not sure what's happening here.
Thoughts? |
|
Back to top |
|
|
szatox Advocate
Joined: 27 Aug 2013 Posts: 3477
|
Posted: Tue May 17, 2022 8:19 am Post subject: |
|
|
Quote: | Action: sync for repo: gentoo, returned code = 0 | So... it basically says there were no errors.
Is there any other problem?
Run is probably only mounted outside of chroot. But it's OK, it's just a tmpfs, putting those files on a disk instead doesn't change much. Keep going. |
|
Back to top |
|
|
Hu Administrator
Joined: 06 Mar 2007 Posts: 22915
|
Posted: Tue May 17, 2022 3:57 pm Post subject: |
|
|
Tzuriel wrote: | Update: /run actually exists, so not sure what's happening here. | The message says mounted, and that is what it is testing. The directory may exist, but it was not a mountpoint, so you get that diagnostic. |
|
Back to top |
|
|
fedeliallalinea Administrator
Joined: 08 Mar 2003 Posts: 31383 Location: here
|
Posted: Tue May 17, 2022 4:45 pm Post subject: |
|
|
Sakaki's EFI Install Guide is no longer maintained and may have dated content.
Moved from Installing Gentoo to Unsupported Software. _________________ Questions are guaranteed in life; Answers aren't. |
|
Back to top |
|
|
Tzuriel Apprentice
Joined: 01 Jun 2004 Posts: 260
|
Posted: Tue May 17, 2022 11:59 pm Post subject: |
|
|
Hu wrote: | Tzuriel wrote: | Update: /run actually exists, so not sure what's happening here. | The message says mounted, and that is what it is testing. The directory may exist, but it was not a mountpoint, so you get that diagnostic. |
It's on the root fs, but there's nothing to be mounted. |
|
Back to top |
|
|
Tzuriel Apprentice
Joined: 01 Jun 2004 Posts: 260
|
Posted: Wed May 18, 2022 12:00 am Post subject: |
|
|
Ok, hate to abandon this install as I don't see anything to replace it, but it's dated. Other stuff is breaking further down. |
|
Back to top |
|
|
Hu Administrator
Joined: 06 Mar 2007 Posts: 22915
|
Posted: Wed May 18, 2022 2:56 pm Post subject: |
|
|
The directory /run on the root filesystem is meant to be a mountpoint for a tmpfs used for early run activity. If it is not a mountpoint, then the writes go to the root fs, which is at best wasteful and at worst may cause problems. |
|
Back to top |
|
|
NeddySeagoon Administrator
Joined: 05 Jul 2003 Posts: 54663 Location: 56N 3W
|
Posted: Wed May 18, 2022 3:55 pm Post subject: |
|
|
Tzuriel,
Don't abandon the install.
Tell us what you did,
What happened
What you expected to happen.
I'm sure it will be fixable once we understand where you are and what the problem in.
During the chroot part of the install, /run being on permanent storage is not a real issue.
The will be some junk left there but not much.
Once you boot into your own system, /run will become a mount point and a tmpfs will be mounted there, hiding the junk on the permanent storage. _________________ Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
Back to top |
|
|
|