MX Linux Forum

Thank you very much. So I suppose your answer is "yes". (designed to use also on running the very same system which is supposed to be repaired)
And from your another answers I deduce it is designed to use also on live systems, so repairing another system, than which it is running on.
I just wanted ...

Hi fehlix ,
sorry to bother you, please just give me clear yes/no, on this:
1. is this supposed to work - repair the actual running system - by not running this tool from the another, live system, but from the very same (emergency booted with the help of external tools) system which I want to ...

1. is this supposed to work - repair the actual running system - thus without chroot-ing?
(should be simpler, because no chroot is needed)

Don't think, that any MX tools are build or tested to be run within a chroot.
Even if you use Chroot-Rescue-Scann tool, which does provides some comfort to ...

That's not how troubleshooting works. Before anything is considered a bug, it has to be replicated. For this sort of thing, a VM will do. Meanwhile, I've spent a couple hundred hours understanding Grub, precisely so I wouldn't have to rely on inscrutable black box apps. Moreover, encryption is ...

...
And, no, MX Boot Repair didn't trash your /boot partition. Grub scripts don't do that. I'd even go so far as to say they can't.


But: Until I do repair, I was able to boot it, and immediately after, not.
How is that possible, if repair did not change anything?

edit: Encryption of root and ...

Hi Adrian ,
may I ask, if:
1. is this supposed to work - repair the actual running system - thus without chroot-ing?
(should be simpler, because no chroot is needed)
2. is MX-Boot repair adapted to all variants of install - LUKS+BTRS+root on @ subvolume?

Or was my attempt to use it in these cases ...

Hi pbear ,
I have set up rEFInd on Ventoy.
Interestingly, it cannot restore boot functionality on my crippled MX-23 setup.
It seems MX-Boot repair (when recent version finally unlocked LUKS), did something to break things even more.
rEFInd did boot from the boot partition, beyond the point I unlock ...

Hi MX-Linux developers,
I have discovered a bug in the installer. LUKS container from previous working installation reused, scanned for subvolumes, all three were marked to delete (i suppose that means delete&recreate).
minstall.log attached.

System:
Kernel: 6.1.0-10-amd64 [6.1.38-2] arch: x86_64 ...

I would like to start to promote MX-Linux, instead of Linux Mint, to family and friends.
Come now, Ubuntu's boot repair utility is so unreliable that all guru helpers I've seen say to use it only for generating a report in difficult cases.


Hi pbear ,
first warm thanks for your willingness to ...

I could first reinstall windows, which I will do anyway,
and only then install MX-23, to finally have the working MX-23.
(and then temporarily restore EFI partitions on another drives, to be able to boot older OSes).
edit: as I plan to delete old MX later, now I can use Boot Rescue Menus -> GRUB-EFI ...