Boot Repair Cd

[Catrin Muzquiz]

AfrikaansArabic Breton ChineseSimpl. ChineseTrad. Croatian Czech Dutch English Estonian Finnish French Galician German Greek Hindi Hungarian Italian Japanese Korean Norwegian Polish Portuguese Romanian Russian Slovak Spanish Swedish Tagalog Telugu Turkish Ukrainian Vietnamese

USE BOOT-REPAIR:

Launch Boot-Repair, then click the "Recommended repair" button. When repair is finished, note the URL (paste.ubuntu.com/XXXXX) that appears on a paper, then reboot and check if you recovered access to your OSs. If the repair did not succeed, indicate the URL to boot....@gmail.com in order to get help.

Warning: the default settings of the Advanced Options are the ones used by the "Recommended Repair". Changing them may worsen your problem. Don't modify them before asking advice.

DISCLAIMER: Boot-Repair is distributed in the hope that it will be useful, but without any warranty. Please be aware that Boot-Repair writes logs&backups on disks, collects anonymous statistics about its use, and creates Pastebin containing basic system data such as partition labels, UUIDs and mount points.

PS: I am not trolling. I feel you should either learn to use a live cd + chroot to fix such problems. If you don't like that, there is supergrubdisk. In any case, you shouldn't be needing either too often unless you like to break your system on a regular basis.

@x33a @Jristz I don't have blank CD's at the moment. What I do have at the moment is an external USB SATA drive case that I can just plop drives into for repair, modifying, etc. Being able to easily install something like Boot-Repair would be very handy as opposed to getting up and having to skate or ride my bike 120 downtown-sized blocks to the nearest Walmart just to buy blank disks or a thumb drive. Plus all my Arch apps aren't in the Live CD.

Regarding your resistance to using the arch iso on removable media: I personally don't understand how anyone runs any distro without having rescue media at hand. Ask someone you know to pick you up a cheap usb stick whenever they're passing the shop, since you're too lazy to go there yourself.

I ended up finding my old Arch media so I updated all the media's packages after booting, mounted the hard drive with the broken system, then changed the root and cache directories in pacman.conf and re-installed and configured the needed packages. I got lucky.

I don't have Windows, but I have Pop!OS and turns out in upgrading the system it also vanished with my grub.

The Garuda partition is not showing at all on bios, (although it's shown in gparted, hallelujah) and I'm almost certain the Garuda Boot Repair can solve the problem

But I wasn't expecting so many options xD on this particular case, should I choose "Install on"

Yeah, Pop!OS do not have a grub so I think while upgrading, it didn't mind erasing Garuda's one. It didn't even try to recognize other OSs

That's why I installed it before Garuda but guess it didn't do much good on the long-term

And for the other "tutorial" I'll follow it along, but I'm at work today and I'll only be able to do so tomorrow. I'm really hoping that it works, I don't want to have to reinstall anything... that's for Windows users only xDD

Not sure if this will be any help? I had opposite problem with Solus couple days ago.

After fresh install there was no way to boot it as it wasn't even showing up in (F12) boot menu and BIOS.

I found this.

Mint update-grub was detecting it, but not adding to grub boot as Solus is not using grub.

In my case sudo efibootmgr -c -d /dev/sda -p 1 -l "\EFI\systemd\systemd-bootx64.efi" -L "Linux Boot Manager" created BIOS/boot entry and I was able to boot into it. I only had to change sda to nvme01p1

Like I said I don't know it it helps, but Pop!OS upgrade might only remove entry from BIOS/boot menu leaving files in EFI partition.

I really hope this either solve the problem or at least don't finally let me totally out of access from any OS because I just typed it as is.

Update: it didn't break anything, so it's good, but it didn't really do anything at all, so... not great yet. But good try, tho

People, you have no idea how much I am affraid of messing the stuff up xD

Well, in any case, I always have a bootable pendrive, so at least that's it

But most of all, thanks everyone, so much, for giving me so many ideas! One of them ought to work : 3

@sgs @filo @arco your help with the tutorial from petsam was all that I needed.

Indeed, the problem was that I was trying to install the grub on a device without EFI or any bios at all, as my EFI bios is in sda2, in the SSD.

I have a GPT formatted SSD Drive that I have moved from a rather new laptop to an older one that has an old BIOS. The Linux systems installed on it work fine (Kubuntu 22.04 and Mint 21), although I cannot install Windows (but that's another matter that doesn't concern us here).

With MBR drives it seemed very simple to me to use Boot Repair and fix frequent errors after installing or removing operating systems. But since a few years, with UEFI and GPT I usually end up with solutions that don't involve Boot Repair.

Then Boot Repair can be used for installing GRUB again for your Kubuntu. Alternatively you can boot from a Ubuntu/Kubuntu live/installation media and select the option to boot from the internal drive; then simply (re-)install GRUB for BIOS/Legacy/CSM mode:

The UEFI specification offers some freedom to vendors on how to implement an UEFI (and there even might be faulty UEFI implementations). So some UEFI specific stuff mentioned below may not work with your UEFI (it might be worth to check your motherboard vendors website for the latest UEFI version).

Before you start:

Your system may become completely unusable if you follow the guidelines below! Make sure you have a working and up to date backup of all your data.

Will help you to find the EFI system partition(s) available on your system. If you want to use a specific one (e.g. the one that was used in a once working boot scenario) and are not sure about which it is you can inspect each in order to determine which is the one you are looking for.

Check that GRUB2 is installed (that should be the case if there once was a working boot scenario). If no grub2-packages are listed GRUB2 needs to be installed (a working internet connection is needed for this!)

With secure-boot, your UEFI firmware comes with a certificate (public-key) for checking signatures. Usually, the public key is from Microsoft, though it could be from your computer vendor. The bare computer might come without a key, but that key is installed when the first software is installed.

It should be harmless to install secure-boot support. If you disable secure-boot in your BIOS, it should still work. The effect of disable secure-boot in the BIOS is that the digital signatures are not checked. But everything else should still work the same.

IMHO Secure boot is security theater. If a bad actor can modify the boot stack then they already own the machine. At best it is marginal protection but the protection is to brick the machine if things do not add up. At least you have to clean and reinstall the complete boot stack and all certificates.

This tells you the current boot order (0003,0005,0001,0000) and what each boot entry points to (e.g. 0003 will start openSUSE). So you can delete a specific entry or just rearrange the boot order using the command above.

Sorry! I definitely would like to do so. But in this forum there is now way to change an existing post that is more than few minutes old. One must read a thread to the very end to gather all its information.

Hello.

Very useful for me.

I just use it.

Concerning the use which I have just had, I have to make some remarks on the points which required a reflection from my part.

POST #1 - N9 : better to use insensitive pattern. In my case label was in small characters.

This point is more sophisticated and should be infirm or confirm by opensuse guru :The current system have a physical /boot partition which is different of the root file system partition.

or

Occasionally when updating my TW and Leap systems I see an error saying that there is no room to update the UEFI settings and executing efibootmgr -v shows no boot order set, this in my case is a f/w error on the mb.

When booting the USB stick in UEFI mode there is an option to boot from hard drive, if you select this and it works then go into yast and set up grub and in each case I have done that it has worked.May be worth a try initially before having to resort to a recovery boot up from USB.

not that i would recommend this....but i once new a guy who wrapped like a half of a roll of duct tape around the whole joint because the boot was torn....he said it worked until he could get money to fix it properly......

As mentioned, if there is still some grease inside the existing split boot, and you think not much dirt has gotten inside the bad boot, then maybe a split cv boot may work for a while. However, I wouldn't trust using one for an extended period of time. Once installed, I would keep a constant watch on the integrity of the split boot to see that it doesn't come apart.

Years back I installed a split boot on a VW. It didn't work well at all, but I think the size I used may have been incorrect. No matter how I installed the split boot, I could not get it to fit well. However, that was just my bad experience. Within a week, I took the car to a shop and had the boot replaced with a non split unit.

3a8082e126