Reverted BIOS to default, now don’t have GRUB?

I have a lenovo laptop with Windows 10. Some time later I installed Ubuntu on this laptop and could choose whether I wanted to use Windows or Ubuntu from GRUB. Today something strange happened, I turned on my PC as usual, but instead of GRUB menu I saw Lenovo Boot Manager with options Windows, Ubuntu and HDD, all of them sent me back to this Boot Manager.

I went to BIOS and set all settings to default. After that Lenovo finally loaded, but I don’t have GRUB, Window is just loaded like Ubuntu was’t installed at all.

How can I restore GRUB or at least delete it together with Ubuntu to reinstall them later?

Is there an alternative to mkusb to install Ubuntu on a portable SSD that works with both UEFI and BIOS boot methods?

I’ve successfully used mkusb to install a persistent Ubuntu 18.04.2 LTS system on a new Samsung T5 USB SSD. What is nice about mksusb is that it creates a bootable system that works on a wide variety of computer systems. However, I would like to have a portable ‘real’ Ubuntu installation vs. a live/persistent install that works with both UEFI and BIOS boot methods.

The process outlined here looked like it would do the trick, but in my case I’m just presented with the grub prompt when booting the drive. Note, that I interpreted the step:

Cut grub.cfg from sdx5/boot/grub and paste to sdx3/boot/grub, overwriting the existing grub.cfg file 

…to mean that I should move the new grub.cfg file from /dev/sdx5/boot/grub to /dev/sdx3/boot/grub, overwriting the grub.cfg file created by mkusb and deleting the grub configuration file created by the installation from the installation partition. Also, /dev/sdx3 was not mounted after the Ubuntu installation completed, I had to manually mount it (/dev/sdx5 was already mounted on /target).

Since mkusb without modifications works fine with the T5 SSD drive, I assume that there is something about the Ubuntu 18.04.2 LTS installation grub.cfg file that is causing an issue.

Is there an alternative approach that would work, or is there something inherently different with a portable SSD vs. a USB thumb drive that prevents creating a truly portable drive?

Ubuntu not booting after BIOS update boot-repair disk fail

complete Linux noob here.

I’ve been struggling with getting my Ubuntu boot up and running after a bios update.

After the update when booting windows i got the error message INACCESSIBLE_BOOT_DRIVE which somehow resolved it self through the windows recovery tools.

When booting Ubuntu I get dropping to shell message, along with error message telling me that the UUID of my boot doesn’t exist.

I just tried to use the boot-repair disk however it doesn’t show the recommended repair option for me hence I took a log http://paste.ubuntu.com/p/NCVjn5g9jp.

I read on a forum (cant find the link right now, I’ve read so many posts this week) that this might be related to the storage controller settings in BIOS. A user found a solution changing this setting to AHCI. Mine is set to RST right now although when trying to change it i’m prompted with a warning that it will delete all my data.

Any help would be very appreciated!

Lenovo G560 F1/F2/F12 won’t let me get into BIOS

Lenovo G560

I’ve replaced the HDD after it died to an SSD, it won’t let me boot from anything, not to mention it won’t let me get into BIOS. From all I found on google they suggested hitting F1/F2/F12/Delete (even tried the F keys with FN) nothing happens it goes into PXE, exits it and says no device.

I am clueless as to what to do with this laptop, it won’t boot to anything, although placing he dead HDD back in showed that it can’t “talk” to it and gave an error.

recover or reset BIOS setting

Alienware Aurora with Windows 10 preinstalled.

I was following https://github.com/rcasero/doc/wiki/Ubuntu-linux-on-Dell-XPS-15-(9560), trying to install Linux on my Desktop. After changing SATA Operation from “RAID On” to “AHCI”, I couldn’t load into Windows, only to get INACCESSIBLE_BOOT_DEVICE error:

enter image description here

And after rebooting, it fails to load BIOS setting. Now I couldn’t load Windows not edit BIOS setting.

Now how do I do to recover/reset BIOS setting?

I can use both Windows and OS X, and 1 USB drive.

Can’t enter BIOS after drive compression

So I decided to compress everything on my main drive which was a horrible idea.

enter image description here

Now I can’t enter my BIOS anymore. I tried:

  • Pressing keys on startup
  • Running shutdown /s /fw in cmd but I get this error Boot to firmware UI is not supported by this system's firmware.(1)
  • Unchecking the “Compress this drive to save space” checkbox (which took like 24 hours and most of my files still have that blue compressed icon on them, so maybe the decompression failed?)

Any idea what is wrong and how I can fix this so that I can enter my BIOS on startup? I could startup to my BIOS by pressing keys just fine, but after the compression I can’t enter my BIOS anymore. The compression is definitely the problem (I think)

Windows 10 Overrides boot settings in UEFI BIOS, requires Live CD fix to repair

I have been dual booting for years now and have problem I can’t seem to solve myself. As we all know Windows is an arrogant dick, and in my case whenever I chose to boot to it it will, automatically without asking me, alter my boot up settings in my BIOS and make itself de-facto king. Mildly annoying as all I had to do with enter setup, change the boot order and carry on.

Now however it is ALSO deleting the grub entry option in my BIOS, meaning I need to load a Live-USB and perform a boot repair (or what have you) to fix it. Long winded just to fix grub.

Now, several questions:

  1. How do I stop Windows 10 from doing this? (would fix all my problems)
  2. Else, since this never used to happen, is there a way of remaking the Grub boot option in my BIOS without a long winded string of commands to reinstall grub? (why is the grub option now not sticking around)
  3. Would I be better of not using EFI boot options if possible (all of my disks are less than 1TB) if that’s possible.

Using an AsRock Z77 Extreme 4 motherboard. Have 3 SSD’s laid out like this currently (in case my method is just wrong someone can correct me):

  1. Disk A is 240GB and used for Windows. I left 550MB free for another EFI partition and let Windows do it’s thing with the rest of the drive.
  2. Disk B is 120GB and used for root, and it has a ‘backup’ partition on there (not required by either OS on boot).
  3. Disk C can be ignored essentially, 1 partition, mounted to /home and used only by Linux.

    NAME FSTYPE SIZE MOUNTPOINT LABEL sda 238.5G
    ├─sda1 16M
    ├─sda2 ntfs 237.9G
    └─sda3 vfat 525M /boot/efi
    sdb 119.2G
    ├─sdb1 ext4 62G /media/root/Furnace Furnace └─sdb2 ext4 39.4G /
    sdc 477G
    └─sdc1 ext4 477G /home

What do now?

Can a virus destroy the BIOS of a modern computer?

In the late 1990s, a computer virus known as CIH began infecting some computers. Its payload, when triggered, overwrote system information and destroyed the computer’s BIOS, essentially bricking whatever computer it infected. Could a virus that affects modern operating systems (Like Windows 10) destroy the BIOS of a modern computer and essentially brick it the same way, or is it now impossible for a virus to gain access to a modern computer’s BIOS?