PDA

View Full Version : Stuck at installing boot loader



underOATH777
10th October 2017, 03:27 AM
Complete newb to Linux. Already have win 10, tried the instructions in this video https://www.youtube.com/watch?v=9QzbX8o7pSY but it gets stuck and my caps button keeps blinking!

It's worthy of note that I had similar issues with previous Ubuntu installation, getting stuck at installing grub package!

I have this laptop here which comes with windows 10.

http://store.hp.com/CanadaStore/Merch/Product.aspx?id=1UG52UA&opt=ABL&sel=NTB

donatom
10th October 2017, 04:57 AM
Here is a good website for efi boot install:

https://ask.fedoraproject.org/en/question/82941/how-to-install-fedora-dual-boot-with-windows-10/

Do NOT create another efi boot partition. Fedora should install efi-boot to the same windows efi boot partition that is on your laptop.

Make sure you start up fedora live in eif-boot mode.

underOATH777
10th October 2017, 05:04 AM
Thanks for the reply. For someone with my current Linux knowledge, the website you linked looks too scary. I think I have a lot to learn about Linux having been a long time windows user.

But for the time being, if you give me detailed instructions on how to do what you suggested, I assume you saw the video so you know what I did, just tell me at which step "in the video" should I do what differently, I would really appreciate that.

Thanks a ton.

donatom
10th October 2017, 05:54 AM
My suggestion is -- especially since you are fairly new to fedora/red hat -- to not install fedora manually. Leave it on "automatic partitioning" (in other words, don't select "manual partitioning"). There is no reason to create another efi-partition. Allow Fedora to use /dev/sda2 or windows efi-partion for efi-grub. Fedora will create a swap partition and will install /root and other directories, including /home, on one partition and will use up the entire free space.

The most important thing to do is to make sure your bios is set to efi-boot mode so that the installer will start up in efi mode as well. This way it will install fedora efi-boot inside of the windows efi-boot partition.

After Fedora "creates" required partitions, you will be able to see how it is being set up. If you don't like the set-up just quit anaconda (the installation program) and nothing will be installed and no swap, etc. will be created.

I hope you have made more than 15 gigs available for the install. I would say 30 - 40 gigs is the bare minimum for a successful install. You should probably have double this space (80 gigs) since your fedora partition would soon fill up otherwise.

The video shows the user freeing up only 15 gigs in windows for the install. That will not work well at all.

Tquilha
10th October 2017, 04:39 PM
@ underOATH777: First thing: when you boot using the live distro, does everything work under Fedora?
Some laptops are kind of Windows-centric and will throw a bit of a tantrum if you try installing Linux in them. Boot any live distro, and try everything for a couple of hours, days, whatever you need.
If everything works OK in live mode, you should be OK to install, just do it like donatom said.
Welcome to the cuckoo's nest. :)

donatom
10th October 2017, 05:37 PM
If everything works OK in live mode, you should be OK to install

This is an excellent suggestion.

underOATH777
11th October 2017, 06:51 AM
Thanks guys, but with the automatic partitioning, I reach the same fatal end, "installing boat loader" freeze :(

I actually tried VM unfortunately it's slow. Now I really had it with this laptop. :( Can anyone rescue me from this situation?

donatom
11th October 2017, 04:20 PM
Thanks guys, but with the automatic partitioning, I reach the same fatal end, "installing boat loader" freeze

Strange since Linux generally works fine on HP machines.

Did you check the checksums of the live iso (compare output of "sha256sum /path/to/live/iso" to the checksum given by fedora for that iso)?

How much space have you freed up for the install? I would use a standard install, not LVM, especially if you are somewhat inexperienced (I don't know that you are trying to install using LVM, but generally anaconda defaults to an LVM install so you would need to change it to standard install)

Also have you tried to run the live iso on your laptop as Tquilha suggested to see how Fedora works without installing?

What live iso are you using for your install? I would download a live iso for fedora26-workstation (I generally use an xfce4 spin), check the checksum, burn it to a usb thumb drive with dd and then try the install again. It is possible that your live iso is corrupted.

lightman47
11th October 2017, 04:43 PM
FWIW - I've had bootloader installs take several minutes on a number of occasions - leading me to believe it was hung when it, in fact, wasn't. When it happened to me, I walked away for 5 minutes so it didn't drive me crazy.

- perhaps not in your case, but maybe -

donatom
11th October 2017, 04:58 PM
It is possible that your efi-boot partition is corrupted (this happened to me when I updated fedora on a dual-boot Windows 10/Fedora laptop. I kept reinstalling efi-boot to no avail. What finally solved it was to start up on a live iso and run:

fsck.vfat -a /dev/sda2

Change /dev/sda2 if necessary (wherever your efi-boot partition is)

This might work. In any case it will take but a few minutes.

underOATH777
11th October 2017, 10:18 PM
Strange since Linux generally works fine on HP machines.

Did you check the checksums of the live iso (compare output of "sha256sum /path/to/live/iso" to the checksum given by fedora for that iso)?

How much space have you freed up for the install? I would use a standard install, not LVM, especially if you are somewhat inexperienced (I don't know that you are trying to install using LVM, but generally anaconda defaults to an LVM install so you would need to change it to standard install)

Also have you tried to run the live iso on your laptop as Tquilha suggested to see how Fedora works without installing?

What live iso are you using for your install? I would download a live iso for fedora26-workstation (I generally use an xfce4 spin), check the checksum, burn it to a usb thumb drive with dd and then try the install again. It is possible that your live iso is corrupted.

I downloaded CentOS-7-x86_64-Everything-1708.iso and burnt to a usb using Rufus. I'm not sure if the ISO is corrupt, will have to figure how to verify checksums on windows, but given how I keep getting this same error in Ubuntu, Linuxmint, Centos, it probavbly has to do with my current system. Unfortunately, Centos live isn't offered when I boot fro mthe USB, I tried Ubuntu live before , it ran fine.

I'm very open to suggestions, instructions on new downloads, methods to burn to usb and installation options. Just be somewhat detailed and avoid terms that are too technical. :)



FWIW - I've had bootloader installs take several minutes on a number of occasions - leading me to believe it was hung when it, in fact, wasn't. When it happened to me, I walked away for 5 minutes so it didn't drive me crazy.

- perhaps not in your case, but maybe -

Unlikely, I had the same exact issue with Ubuntu before, I waited for like five hours. It just freezes, see this.

https://forums.techguy.org/threads/dual-booting-ubuntu-and-windows-10-freezes-at-grub2.1196616/

donatom
12th October 2017, 05:10 PM
I'm very open to suggestions, instructions on new downloads, methods to burn to usb and installation options.

The easiest and best way to copy an iso to a usb thumb drive is to use dd which is quite simple, but make sure you have the paths right or you could end up destroying your current install (i.e., Windows 10):


dd if=/path/to/image.iso of=/dev/sdX bs=8M status=progress oflag=direct

Have you run fsck.vfat on the efi-partition? If it is corrupt you won't be able to install grub2-efi.

underOATH777
12th October 2017, 06:16 PM
The easiest and best way to copy an iso to a usb thumb drive is to use dd which is quite simple, but make sure you have the paths right or you could end up destroying your current install (i.e., Windows 10):


dd if=/path/to/image.iso of=/dev/sdX bs=8M status=progress oflag=direct

Have you run fsck.vfat on the efi-partition? If it is corrupt you won't be able to install grub2-efi.

I only have windows 10 on the machine. Are you suggesting that I do all this linux commands from a live usb? Could you give me a suggestion to a dsoitro and version that you think is the most stable / would work best for my situation?

lsatenstein
12th October 2017, 09:38 PM
Hi Underoath777

I don't mind getting together with you to work on your installation problem. Until the weekend coming, I am out of the province. I will be back in Montreal Click on my name to write me a private message about phone number or other

donatom
12th October 2017, 10:07 PM
You could use a live iso (Ubuntu, Fedora, etc -- I prefer Fedora) to run the fsck.vfat on your efi partition. Do that and then try to install CentOS. If it still doesn't install, then I would recommend burning an install iso onto a dvd and then retry the install. You wouldn't be able to download and then burn an iso using a live system.

amiga
14th October 2017, 03:48 AM
A major error has been made below:


Correction for the command to fix file system corruption on the efi-boot partition:

sudo mkfs.vfat -F32 /dev/sda2


The command mkfs will of course reformat the partition erasing the Windows bootloader! Do not follow these instructions!

In post #10 donatom recommended the fsck command to fix file system corruption.


fsck.vfat -a /dev/sda2


I neglected to add -F32 which is, of course, referring to FAT 32 filesystems.

You also changed fsck file system check to mkfs which will reformat and erase all data on /dev/sda2.

The fsck utility doesn't require specifying F32 as the FAT-size as it will determine this itself.

underOATH777
18th October 2017, 03:40 PM
A major error has been made below:



The command mkfs will of course reformat the partition erasing the Windows bootloader! Do not follow these instructions!

In post #10 donatom recommended the fsck command to fix file system corruption.


fsck.vfat -a /dev/sda2



You also changed fsck file system check to mkfs which will reformat and erase all data on /dev/sda2.

The fsck utility doesn't require specifying F32 as the FAT-size as it will determine this itself.

Thank you. Can you please type the right commands that won't format / erase my disk?

amiga
18th October 2017, 07:13 PM
Thank you. Can you please type the right commands that won't format / erase my disk?

The correct command was the one originally given.


fsck.vfat -a /dev/sda2

There was nothing wrong with this command. It was the later post that changed this to the wrong dangerous command in trying to add a parameter that was not needed.

underOATH777
20th October 2017, 06:44 AM
The correct command was the one originally given.


fsck.vfat -a /dev/sda2

There was nothing wrong with this command. It was the later post that changed this to the wrong dangerous command in trying to add a parameter that was not needed.

OK just tried this from Ubuntu live, got this:
fsck.fat 3.0.28 (2015-05-16)
open: permission denied

Tried with sudo, works, but that's it? Ubuntu is supposed to install now? Let's see.....

underOATH777
20th October 2017, 09:22 PM
OK, I'm installing now, let's see how it goes. It just occurred to me though to bring this to your attention. When I try to boot from my usb, I can see in the boot manager menu an entry for possibly one of the previous failed Ubuntu installation attempts. I attached a screenshot.

Does it affect my installation? How to fix the boot manager menu to remove it?

underOATH777
30th October 2017, 06:08 PM
And the installation failed once more, too frustrated now beyond words can describe