Fix broken setup

[fgn-itsupport]

I've upgraded one of my older OS installs. After the upgrade the kernel didn't boot anymore. Trying to fix the config in grub, I've tried the command "mos kernel geninitramfs --all" Yet while trying to do the grub.cfg it complains about grub-mkconfig binary being missing.
So I tried to reinstall grub, but booting with a live system the luet repo doesn't seem to be properly configured when I try to do the reinstall. Is there some documentation about how to properly start and load the OS to repair it?
Like how to open the LUKS cryptdisk, mouting the proper mount points, etc.
Since MOS isn't exactly working like a gentoo system, it doesn't seem to be that easy to repair it.
Any help would be greatly appreciated.

[joostruis]

To repair I would try to boot live, chroot into the system and then rebuild initramfs.

The command that you should run for this is:

mocaccino-dracut --rebuild-all

"it complains about grub-mkconfig binary being missing."
That command should be available. Are you sure you did not run out of disk-space while upgrading the system?

I assume you understand what chrooting into a system means here but let me try to explain.

"Like how to open the LUKS cryptdisk, mouting the proper mount points, etc."

It’s still unclear whether you were operating inside your installed system or just from the live environment.
When booting a live system, you need to mount your install and chroot into it, otherwise commands won’t affect your system.
A minimal example (adjust device names to your setup):

# list disks and partitions
lsblk -f

# mount root (example)
mount /dev/sdXn /mnt

# if you have a separate /boot (optional)
mount /dev/sdXn /mnt/boot

# if you use encryption, unlock it first (example)
cryptsetup open /dev/sdXn cryptroot

# bind mounts
mount --bind /dev  /mnt/dev
mount --bind /proc /mnt/proc
mount --bind /sys  /mnt/sys

# chroot
chroot /mnt

/dev/sdXn is just a placeholder:

sdX = disk (e.g. sda, sdb, nvme0n1)
n = partition number (e.g. 1, 2)

You can use lsblk -f to identify:

your root filesystem (/)
boot partition (if separate)
encrypted volumes

After that you are working inside your installed system.
Then rebuild initramfs:

mocaccino-dracut --rebuild-all

[msdobrescu]

My chroot is like this (I use UEFI...):

# su
# mkdir /mnt/mychroot

# fdisk -l # Ascertain the partitioning scheme.
# mount /dev/sdaX /mnt/mychroot # ... find the partition

# mount --rbind /dev /mnt/mychroot/dev
# mount --make-rslave /mnt/mychroot/dev
# mount -t proc /proc /mnt/mychroot/proc
# mount --rbind /sys /mnt/mychroot/sys
# mount --make-rslave /mnt/mychroot/sys
# mount --rbind /tmp /mnt/mychroot/tmp
# chroot /mnt/mychroot /bin/bash
mocaccino / # source /etc/profile
mocaccino / # env-update
>>> Regenerating /etc/ld.so.cache...
mocaccino / # export PS1="(chroot) $PS1"
(chroot) mocaccino / #

[fgn-itsupport]

But that's exactly what I do as well. Still for some reason the lock folder is missing and the luet repo doesn't seem to be able to sync

[msdobrescu]

In such case, I have created it manually.
Did you use a live environment?

[fgn-itsupport]

Sure, I just used the latest ISO for that and used this as a recovery live system.

[msdobrescu]

Which one, exactly?

[joostruis]

"Thank you, the mocaccino-dracut command worked but it didn't rebuild the grub.cfg file."

Nobody claimed it would do that. I only explained the correct command for rebuilding your initramfs.

At this point I have no idea what happened to your system and you are also unclear about what happened.
To me it looks best that you reinstall the system. Good luck.

[fgn-itsupport]

I just need to get the grub-mkconfig implemented.
The only thing I can tell is, what I already told you.
I've updated the system and it broke after the restart

[joostruis]

No you do not "just need" to get grub-mkconfig working.

If the entire grub-mkconfig command is missing there really is a bigger problem. Most likely the system upgrade failed due disk issue or was interrupted due some other problem. (pulling the power cable in the middle of a system upgrade would do it)

[fgn-itsupport]

I've gotten the boot working again now, by coping the binaries from a working system to the broken one and executed the grub --all creation. That did the trick in terms of booting the OS from the disk. Yet I still get this error here: "Error on sync repository luet: open: no such file or directory"
Does anyone have an idea what could cause that? Cause the /var/luet directory does have the repo content.
A "luet repo list" does show all the repos. So something in there seems to have an issue. Question is, how do I figure out, what exactly?
My guess is, that one or more of the folders have the wrong permissions.

[msdobrescu]

I think so too.
Is there any /var/cache/luet?

[fgn-itsupport]

I think I fixed the permissions now, and the upgrade is working again. Yet for some reason the whole Window based packages are either gone or broken. I've tried to install the meta/gnome package and it got deployed, but it's missing the /var/lib/systemd/gdm... but it didn't got deployed. Would a reinstall of the gdm package specifically help. Any other ideas on how to fix that?

[fgn-itsupport]

Thank you for that hint.
Eventhough the "reclaim" didn't work I got it fixed somehow with luet oscheck --reinstall
Yet now I have another issue.
After restarting the system I got the message that there are new updates available. Trying to run the update I got another error message at the end proclaiming that there are package conflicts. Now I have to figure out what is in fact conflicting so I get the upgrade done without an error.

[msdobrescu]

I use a shell script from the community-repository, found in utils/system-tools, called loopup.sh.
This parses luet's output and iteratively finds the conflicts that happen due to the package upgrading order and reinstalls the dependencies in a loop until it finishes upgrading.
It won't work for conflicts due to duplicated files across the packages.

[fgn-itsupport]

Can I install a package to use that loopup.sh or do I have to download it from the repo manually?

[msdobrescu]

Either way.
luet install utils/system-tools

[fgn-itsupport]

Aside from that, what would be the approach to figure out which packages are conflicting? Cause I don't see anything which hints to any conflicts, like it does in Gentoo for example.

[fgn-itsupport]

Seems my WLAN isn't working on my gnome environment anymore, I just can't find the settings. Yet I don't find a package which could include that as well. How do I get it activated again?

[fgn-itsupport]

My Audio doesn't work either. What packages do I have to reinstall to get that stuff working again. WLAN, Audio, VPN, etc.