1 |
On Monday, 19 August 2019 07:41:20 BST Raffaele Belardi wrote: |
2 |
> Raffaele Belardi wrote: |
3 |
> > One thing I notice from the boot log is that the root FS requires |
4 |
> > recovery. My live CDs did not let me because they are too old so I'll |
5 |
> > try to find a more up to date live CD. |
6 |
> Looking better at the kernel log, for sda1 (the root partition) it says: |
7 |
> "Recovery complete" so I don't think a new live CD will help. I'm really |
8 |
> out of ideas. |
9 |
> |
10 |
> raffaele |
11 |
|
12 |
You have 3 drives attached while you're trying to boot. The kernel seems to |
13 |
come to a stop after /dev/sdc. It may need some driver for this device/fs. |
14 |
I'd start by unplugging any drives which do not contain the system you're |
15 |
trying to boot, then go through a step by step process of installing/setting |
16 |
up openrc, DM and boot loader. |
17 |
|
18 |
The DM is not necessary to boot your system, but while you chrooted into it |
19 |
you might as well install and set up sddm as a DM - there are others but be |
20 |
careful they do not try to bring in 2/3 of Gnome and its dependencies too. |
21 |
|
22 |
Re-install GRUB or whichever boot manager you use and make sure it points to |
23 |
the correct kernel. If you're on an UEFI system and you boot directly using |
24 |
the kernel EFI stub, re-run efibootmgr to specify the kernel UEFI will boot |
25 |
with, but first run fsck.vfat on the EFI partition just in case this fs was |
26 |
messed up too. |
27 |
|
28 |
Make sure you are using a kernel set up for openrc. |
29 |
|
30 |
In /etc/rc.conf set up a log file and temporarily enable logging. If any |
31 |
openrc scripts fail and can't boot, you will able to look at the logs when you |
32 |
chroot back into it - using less/cat/plain text editor. ;-) |
33 |
|
34 |
I hope the above should allow you to boot, or at least arrive at some |
35 |
meaningful failure message to resolve. |
36 |
-- |
37 |
Regards, |
38 |
|
39 |
Mick |