| View previous topic :: View next topic |
| Author |
Message |
sicr0
Apprentice
Joined: 23 Mar 2022
Posts: 179
|
 Posted: Tue Dec 06, 2022 5:36 pm Post subject: [SOLVED] unable to boot |
 |
|
Last night I left my laptop updating, I forgot to leave it plugged so when I woke up I recharged it.
On boot I get presented with the message:
| Code: | /bin/sh: line 1: exec: set: not found
|
I booted from a Gentoo Live USB, ran emerge -auDN @world and rebooted, but the problem is still present.
The error message doesn't show which file has this error. How could I find it? Do you know how to fix this issue?
Last edited by sicr0 on Tue Dec 06, 2022 7:42 pm; edited 1 time in total |
|
| Back to top |
|
 |
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54315
Location: 56N 3W
|
| Posted: Tue Dec 06, 2022 5:51 pm Post subject: |
|
|
sicr0,
I've never seen this before but there is nothing like a challenge. :)
Explain your boot process and describe where it goes wrong.
The boot process may be
EFI loads grub
Grub loads the kernel and initrd.
There are kernel messages and eventually, a log in prompt.
Your own boot process may be nothing like that (mine isn't) that's just a very common one.
Once we know which step goes wrong, the problem space is much smaller.
We use that to look at file permissions and so on.
e.g. there is no point in looking at grub if the kernel starts. Grub has done its thing correctly by then.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
sicr0
Apprentice
Joined: 23 Mar 2022
Posts: 179
|
| Posted: Tue Dec 06, 2022 6:10 pm Post subject: |
|
|
Thanks Neddy!
GRUBs runs okay.
Kernel I THINK is running fine.
Then OpenRC begins with the log
| Code: | OpenRC 0.45.2 is starting up Gentoo Linux (x86_64)
* Mounting /proc ...
* Mounting /run ...
* /run/openrc: creating directory
* /run/lock: creating directory
* /run/lock: correcting owner
* Caching service dependencies ...
* Mounting /sys ...
* Remounting devtmpfs on /dev ...
* Mounting debug filesystem ...
* Mounting /dev/mqueue ...
* Mounting SELinux filesystem ...
* Mounting efivars filesystem ...
* Mounting /dev/pts ...
* Mounting /dev/shm ...
kmod-static-modules | * Creating list of required static device nodes for the current kernel ...
system-tmpfiles-setup-dev| * Create Static Devices Nodes in /dev ...
udev | * Starting udev
udev-trigger | * Generating a rule to create a /dev/root symlink ...
cgroups | * Mounting cgroup filesystem ...
udev-trigger | * Populating /dev with existing devices through uevents ...
termencoding | * Setting terminal encoding [UTF-8] ...
modules | * Loading module pkcs8_key_parser ...
modules | * Loading module vboxdrv ...
keymaps | * Setting keyboard mode [UTF-8] ...
keymaps | * Loading keyboard mapping [us] ...
modules | * Loading module vboxnetadp ...
|
After a few instants the screen goes dark and the aforementioned message appears on the screen.
The processes that I have selected are
| Code: | sicro@sicro ~ $ rc-update show
binfmt | boot
bluetooth | default
bootmisc | boot
cgroups | sysinit
dbus | default
dcron | default
devfs | sysinit
display-manager | default
dmesg | sysinit
elogind | boot
fsck | boot
hostname | boot
hwclock | boot
iwd | default
keymaps | boot
killprocs | shutdown
kmod-static-nodes | sysinit
local | default nonetwork
localmount | boot
loopback | boot
modules | boot
mount-ro | shutdown
mtab | boot
netmount | default
numlock | default
procfs | boot
root | boot
save-keymaps | boot
save-termencoding | boot
savecache | shutdown
seedrng | boot
swap | boot
sysctl | boot
sysfs | sysinit
systemd-tmpfiles-setup | boot
systemd-tmpfiles-setup-dev | sysinit
termencoding | boot
udev | sysinit
udev-trigger | sysinit
|
|
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54315
Location: 56N 3W
|
| Posted: Tue Dec 06, 2022 6:32 pm Post subject: |
|
|
sicr0,
That's very helpful.
Boot your live media, mount your real root filesystem at /mnt/gentoo, now edit /mnt/gentoo/etc/rc.conf
Find the bit that says
| Code: | # Set rc_interactive to "YES" and you'll be able to press the I key during
# boot so you can choose to start specific services. Set to "NO" to disable
# this feature. This feature is automatically disabled if rc_parallel is
# set to YES.
rc_interactive="YES" |
to make rc_interactive work.
Save the change and reboot your install.
Now you can press the 'I' key so that openrc asks you about starting services.
There is a message but you may miss it, so it may take several reboots
Start each service in turn. Which service fails?
If you reboot again and skip the failed service, does the next service start.
This 'next service' test is only useful if it does not require the skipped service.
e.g. sshd requires the network to be up.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
pietinger
Moderator
Joined: 17 Oct 2006
Posts: 4248
Location: Bavaria
|
| Posted: Tue Dec 06, 2022 6:33 pm Post subject: |
|
|
sicr0,
please edit /etc/rc.conf and enable this line:
| Code: | | #rc_interactive="YES" |
Then please reboot and check which runscript has this problem (it should be one from runlevel "boot" because sysinit has passed). |
|
| Back to top |
|
|
sicr0
Apprentice
Joined: 23 Mar 2022
Posts: 179
|
| Posted: Tue Dec 06, 2022 7:41 pm Post subject: |
|
|
| Thanks! I was able to solve it. It seems like I left a set keyword in the wild in the middle of /etc/greet.d/config.toml. The service that crashed was display-manager. |
|
| Back to top |
|
|
|
Other Things Gentoo
