<html><head></head><body>Thank God All-Mighty I remembered having Parabola installed in my portable hard driver, everything I had to do in GRUB command line was:<br>
<br>
grub> configfile (usb1,msdos3)/boot/grub/grub.cfg <br>
<br>
And now I had a rescue device to fix this mess on my laptop :)<br>
<br>
I don't think this will work for people that isn't using UUID to identify their partitions in a Parabola installation, people should be aware.<br><br><div class="gmail_quote">El 19 de noviembre de 2016 15:34:42 GMT-06:00, Moritz Klammler <moritz@klammler.eu> escribió:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">The same happened to me and (apparently) many others. I'm somewhat<br />disappointed that the Arch project still didn't add an item on the NEWS<br />page for this even though it was suggested in their forums. Maybe the<br />Parabola website can add a notice on its own?<br /><br />The problem is that the order in which libreadline is updated and the<br />new kernel image is built is broken. If you manually run<br /><br /> # mkinitcpio -p ${KERNEL}<br /><br />after<br /><br /> # pacman -Syu<br /><br />has completed (with an incorrect exit code claiming success when it<br />actually failed to create a bootable kernel image), everything will be<br />fine.<br /><br />If you have already powered off the system, booting a live-system,<br />mounting your hard drive, chroot()ing into it and running `mkinitcpio`<br />from there also fixes the issue.<br /><br />I'm sorry to hear that you cannot boot a live-system either. I'm afraid<br />that you probably won't be
able to fix your system without doing that.<br />I cannot diagnose what might be the problem that your Grub refuses to<br />boot a live-system and I'm also not an expert on this so I'm sorry for<br />somehow giving you a non-answer. I'm posting this anyway in the hope<br />that it might help others from running into this (avoidable) situation<br />in the first place. I can assure you that I have already successfully<br />bootet live systems from Libreboot's GRUB, though, so hopefully a more<br />experienced person will be able to diagnose your problem so you can fix<br />your system, too.<br /><br /><br /><br />Jorge Araya Navarro <elcorreo@deshackra.com> writes:<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> Yeah, I discovered this after an upgrade done to my system, today I<br /> was in the recovery shell and issuing 'lvm vgscan' throw this:<br /><br /> lvm: error while loading shared
libraries: <a href="http://libreadline.so">libreadline.so</a>.6: cannot open shared object file: No such file or directory<br /><br /> The worst thing is that I can't boot a live cd, Libreboot's GRUB keeps sending<br /> me back to the menu or the command line without throwing errors of any kind. I<br /> don't have any other computer here or know someone running GNU to give me a<br /> hand and fix my laptop.<br /><br /> Any suggestions? I'm desperate.<br /></blockquote></pre></blockquote></div><br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>