[SOLVED] Install glibc on a broken system and profile update

[afdev]

logrusx,

[logrusx]

It looks like /boot is not mounted. Moreover, it's commented in fstab. I suspect your kernel is loaded from withing the boot partition, but before continuing, let's confirm that.

Mount /dev/md1 somewhere (perhaps /mnt/tmp or something liek that) and give me a list of files in it.

Also this looks like raid/lvm/md - things I'm not familiar with and I ask some of the more experienced users to join in helping resolve that.

Perhaps just removing the comment for the /boot line in fstab, mounting it and installing the new kernel and updating the grub config should work. I hope the separate boot partition is not because of some kind of disk encryption what not. I don't understand those.

Judging by the launch date of the CPU, this should still be a MBR/BIOS boot and that's why /boot is formatted with ext2 and is not an efi system partition. Someone confirm that please.

Best Regards,
Georgi

[afdev]

Hi logrusx,

it's correct, the boot partition is not mounted anymore, because I have moved the bootloader into the /boot directory (I was out of space in the boot partition).
I have commented the entry in the fstab file.

The disks are in Software Raid if I have understood correctly, the same configuration as in the staging server by luck.
I have found that I need only a flag while compiling the kernel (I have added MDADM="yes" in /etc/genkernel.conf) and a kernel command option in the bootloader entry "domdadm".
It worked in this way in the staging server without problems.

Maybe I was missing something while moving the boot partition... If the partition gets mounted, then I have only 2 kernels and a different grub configuration.
I was following this answer on askubuntu.com, because it doesn't involve anything Ubuntu-specific.

I was trying to reinstall grub into /dev/md3, but I am getting the following error:

[logrusx]

Someone with memory that goes longer back than mine should comment here. Back when I used BIOS/MBR boot I only used dual boot with Windows and don't even remember what had to be done to make a Linux volume bootable.

Do not follow outside resources to learn something new, only when you know enough to distinguish what's relevant and what would work.

I think you should follow 2.2 or 2.3 from GRUB page but I can't vouch for anything.

[afdev]

Hi logrusx,

thank you for the reply.
Yes, I know that the thread is long at this point and the main issue is solved now. I have continued here because it was part of the upgrade process to update the kernel too, but for this specific issue I could also open a new topic.

[afdev]

Thank you to all, who have helped me on this topic.
Many many thanks!!

I have updated the production server and switched to the new profile.
The only thing missing is the new kernel, for that I will open another issue in the relative section.

[logrusx]

You're very welcome!

You can now edit the first post and add SOLVED to the title.

Best Regards,
Georgi