"broken pipe" when updating MX 19.4 [Solved]

[br1anstorm]

Well, we seem to be only part-way there.

I followed those three steps, @Adrian, for both the initrd.img-4.19.0-9-amd64 and the initrd.img-4.19.0-10-amd64. Both have disappeared from the list showing in /boot, so they have been removed. The config, System.map and vmlinuz for both of them however remain.

I checked the usage and space in /boot, and sure enough, that had freed up about 120 MB.

Anyway, I then ran the "sudo dpkg --configure -a" command to finish the update - which as I understood it was to install 4.19.0-20 as well as other updates.

And initrd.img-4.19.0-20-amd64 is right there in /boot (as are the config, System.map and vmlinuz for this latest version of the kernel).

Okay, so I restarted, thinking the job was done. Checked which kernel was running. It's still 4.19.0-18.

Closed down, rebooted, looked through the advanced options in Grub. No sign of 4.19.0-20. The 'current' default is still 4.19.0-18. And - get this - the list of other options shows not only 4.19.0.17 (which I haven't touched) but still shows 4.19.0-9 and 4.19.0-10.

So I'm puzzled. If the update is now completed (and 4.19.0-20 is there in /boot) why isn't it now running when I reboot? And if i have indeed removed the initrd.img for 4.19.0-9 and 4.19.0-10, how come they are still listed as options in Grub?

Should I now delete (using the rm command) the config, System.map and vmlinuz that belong with those two older versions of the kernel, if they are now "leftovers"? Or could I now use the MX Cleanup tool to do so - or is something still borked?

And - separate question - when and how will 4.19.0-20 be brought into action?

Sorry that the questions are so basic. But I call it as I see it...

[Adrian]

I would use the MX Cleanup to remove the kernels you don't need (it would clear the stuff from the 4.19.0-9-amd64 that you removed manually)

Run "sudo update-grub" than take a look on MX Boot Options to see if you can select the correct kernel.

Basically the procedure worked, there's an issue with selecting the kernel to boot from "sudo update-grub" should take care of that and you can select the desired kernel with MX Boot Options.

I'm working to make MX Cleanup free up space and remove the kernel so you don't have to drop to CLI... but it's not yet ready.

[br1anstorm]

Closer.... but no cigar yet!

I have now got rid of 4.19.0-9 and 4.19.0-10. I also checked that 4.19.0-20 is definitely there in /boot.

I ran "sudo update-grub" and rebooted.

MX Boot Options told me I was still running the 4.19.0-18 version of the kernel. But the dropdown list in Boot Options gave me the option to select 4.19.0-20. I did so. A popup appeared saying Grub was being updated. Fine.

So I then rebooted again. And...... it is still running 4.19.0-18! The Grub menu advanced options list on startup shows 4.19.0-18 and 4.19.0-17 as options. No sign of 4.19.0.20 there.

But 4.19.0-20 is listed in Boot Options... and indeed also in the list of kernels in MX Cleanup (which confirms that 4.19.0-18 is running and offers the option to delete kernels 4.19.0-17 and 4.19.0-20).

So why - despite now apparently updating Grub twice - is it still not booting into the latest kernel, 4.19.0-20?

I did notice in Boot Options a tick-box saying "Enable saving last boot choice". It is blank (unticked). When I opted to select 4.19.0-20 and Grub got updated (as noted above), I did not tick that box. Should I have done so? Would that have made 4.19.0-20 the default choice?

Or do I now need to remove 4.19.0-20 (using MX Cleanup, or manually?) since it doesn't seem to want to play nicely, and then try reinstalling it from Synaptic? For obvious reasons I'm trying to keep things simple and not do major surgery on the system!

[dolphin_oracle]

Does some other Linux provide your grub menu?

[Huckleberry Finn]

Let me confuse you even more

( In your case it's "Debian 4.19" (to remove) instead of "Debian 5.10" )

[br1anstorm]

Ah, @dolphin_oracle you must be psychic, or extremely perceptive.

I did mention in an earlier post that this spare laptop is triple-boot. I set it up some time ago and I'm not sure I can now recall all the exact details of how I did so....

Basically I have Windows 10, Mint 19.3 and MXLinux 19.4 installed. But the booting arrangement is not the typical setup managed only by [one of the] Linux Grubs.

Windows 10 still boots as normal using its own MBR. I have EasyBCD installed in Windows, and that modifies the MBR to enable - or link onward to - the Linux distros. So at the Windows bootup splash screen I have the option to boot into Windows or into the Linux distros. If I choose the latter, it goes to Grub, where I then select either Mint or MX, or their advanced options (and of course the Grub also lists the Win10 as well).

I admit that I cannot now recall, or explain, exactly how Grub is configured or indeed whose Grub (Mint or MX) takes the lead, or has control. I seem to recall that - when I installed or added the two Linux distros, I put Grub into its own separate boot partition.

All I can say is that until this latest episode, I was able to update both Mint and MX entirely normally, each one separately. Each seems - until now - to have managed to take on board their respective kernel updates. I haven't been aware of what either of them have done "under the hood" to update either or both of their Grubs: it has just happened automatically and worked - until the situation arose as described in my OP.

In posting my original message, I did try to keep it simple by only setting out the details of the MXLinux installation/update situation. But the fact that the booting arrangement may well involve another grub, or some other linkages, is obviously a factor...

I hope this helps to explain the wider context. I imagine that you might find it easier to figure things out if I posted up some sort of "inxi" details. What exact command should I use to provide you with better, but technically precise, information about my setup?

[Huckleberry Finn]

Just boot Mint and open a terminal

Code: Select all

sudo update-grub

Reboot (into MX).

[br1anstorm]

Just boot Mint and open a terminal

Code: Select all

sudo update-grub

Reboot (into MX).

What's the expression in the movies ...? "Well I'll be doggoned!" (or something similar).

Complicated question, detailed explanation - and simple answer. Thankyou, to @dolphin_oracle for his detective work and for prompting me to explain things a bit more fully, to @Adrian for taking the trouble to walk me through some of the tidying-up of old kernel versions, and to @Huckleberry Finn for nailing the final step to solve the problem.

Clearly the Grub which manages the booting of both Mint and MXLinux in my set-up is the Mint Grub. By updating it I have now got the list and the choice of kernels for MXLinux sorted. MX is now running 4.19.0-20 , with 4.19.0-18 and 4.19.0-17 still available as options if needed.

So all is now well. Memo to self: it's probably a good idea to prune down the collection of old kernel versions (in both Mint and MX) after the periodic updates, just to avoid bumping into the problem of a lack of space again. MX Cleanup looks like a very useful tool.

So with renewed thanks, I'm marking this thread solved.

[Huckleberry Finn]

... and to @Huckleberry Finn for nailing the final step to solve the problem.

In fact, that, too was thanks to @dolphin_oracle : "good catch" :)

[br1anstorm]

... and to @Huckleberry Finn for nailing the final step to solve the problem.

In fact, that, too was thanks to @dolphin_oracle : "good catch" :)

And this @dolphin_oracle guy is the main man who drives, develops, maintains and promotes MXLinux! Huge kudos for that - and I'm deeply appreciative that experts such as him and the others who chipped in took the time and trouble to help a simple and not very knowledgeable user like me. Gives me a very warm feeling about MX and its community.