1 |
On Monday, 19 August 2019 13:24:05 BST Raffaele Belardi wrote: |
2 |
> Mick wrote: |
3 |
> > On Monday, 19 August 2019 07:41:20 BST Raffaele Belardi wrote: |
4 |
> > |
5 |
> > You have 3 drives attached while you're trying to boot. The kernel seems |
6 |
> > to come to a stop after /dev/sdc. It may need some driver for this |
7 |
> > device/fs. I'd start by unplugging any drives which do not contain the |
8 |
> > system you're trying to boot, then go through a step by step process of |
9 |
> > installing/setting up openrc, DM and boot loader. |
10 |
> |
11 |
> sdc is an external USB drive, I'll try to unplug that. |
12 |
> |
13 |
> > The DM is not necessary to boot your system, but while you chrooted into |
14 |
> > it |
15 |
> > you might as well install and set up sddm as a DM - there are others but |
16 |
> > be |
17 |
> > careful they do not try to bring in 2/3 of Gnome and its dependencies too. |
18 |
> |
19 |
> I'll do but first I want to see a working terminal, too much stuff to debug |
20 |
> otherwise. |
21 |
> > Re-install GRUB or whichever boot manager you use and make sure it points |
22 |
> > to the correct kernel. If you're on an UEFI system and you boot directly |
23 |
> > using the kernel EFI stub, re-run efibootmgr to specify the kernel UEFI |
24 |
> > will boot with, but first run fsck.vfat on the EFI partition just in case |
25 |
> > this fs was messed up too. |
26 |
> |
27 |
> It's grub2, non-UEFI. I don't normally reinstall it when I update the |
28 |
> kernel, I only run grub-mkconfig. I did the same this time. |
29 |
> |
30 |
> > Make sure you are using a kernel set up for openrc. |
31 |
> |
32 |
> Good catch, although I'm not sure where to find that info in the available |
33 |
> kernel log. I'll look better, I need to stop it from scrolling. |
34 |
|
35 |
It may be possible to hit CTRL-s to pause the scrolling, then CTRL-q to resume |
36 |
it. |
37 |
|
38 |
> > In /etc/rc.conf set up a log file and temporarily enable logging. If any |
39 |
> > openrc scripts fail and can't boot, you will able to look at the logs when |
40 |
> > you chroot back into it - using less/cat/plain text editor. ;-) |
41 |
> |
42 |
> Good idea. |
43 |
> |
44 |
> > I hope the above should allow you to boot, or at least arrive at some |
45 |
> > meaningful failure message to resolve. |
46 |
> |
47 |
> One of the last things printed in the kernel log is "random: crng init |
48 |
> done". The random service is part (possibly the last service) of the boot |
49 |
> runlevel which is entered after the sysinit runlevel. So apparently a lot |
50 |
> of openrc stuff has already started successfully. Instead, nothing from the |
51 |
> default runlevel is output. I'll re-check those services. |
52 |
> |
53 |
> raffaele |
54 |
|
55 |
|
56 |
-- |
57 |
Regards, |
58 |
Peter. |