Bootloader installation failed
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
I am trying to install Debian in ASUS P2440UA laptop. Previously I was using Windows 7 and Linux Mint in dual boot without any issue (for 6 months). But I decided to format whole hard drive and install only Debian. I have formatted the hard drive as GPT and tried to install Debian in UEFI mode. I used 256 MB EFI system partition, 60 GB root and 4 GB swap. Rest of the space is mounted as home. But at the end of installation process "failed to install grub bootloader on a hard drive".
Then I have followed this https://forums.kali.org/showthread.php?37091-GRUB-Boot-Loader-Not-installing-on-Hard-Drive but still didn't worked. It was an "input output error".
Then I have found this When wouldn't you want to install GRUB bootloader? saying that installing grub in a modern computer is not the best option.
In this case what is the best option for me? I am trying for four days.
Note that I havd an empty hard drive. I want to use gpt format for hard drive. I will use multi boot.
linux debian grub2 boot-loader
|
show 3 more comments
up vote
1
down vote
favorite
I am trying to install Debian in ASUS P2440UA laptop. Previously I was using Windows 7 and Linux Mint in dual boot without any issue (for 6 months). But I decided to format whole hard drive and install only Debian. I have formatted the hard drive as GPT and tried to install Debian in UEFI mode. I used 256 MB EFI system partition, 60 GB root and 4 GB swap. Rest of the space is mounted as home. But at the end of installation process "failed to install grub bootloader on a hard drive".
Then I have followed this https://forums.kali.org/showthread.php?37091-GRUB-Boot-Loader-Not-installing-on-Hard-Drive but still didn't worked. It was an "input output error".
Then I have found this When wouldn't you want to install GRUB bootloader? saying that installing grub in a modern computer is not the best option.
In this case what is the best option for me? I am trying for four days.
Note that I havd an empty hard drive. I want to use gpt format for hard drive. I will use multi boot.
linux debian grub2 boot-loader
"input output error" means you should replace your hdd (or the broken cables).
– Ipor Sircer
Nov 28 at 15:05
unix.stackexchange.com/questions/399626/…
– Rui F Ribeiro
Nov 28 at 15:06
Nothing is broken. Everything was working just fine. But I am having issue while trying to install only Deviation.
– Nafi Shahriyar
Nov 28 at 15:21
"input output error" or grub cannot 'talk' to the drive for some reason. Can you use BIOS mode not UEFI mode as a test?
– jc__
Nov 28 at 17:19
Yes I did. BIOS mode works
– Nafi Shahriyar
Nov 28 at 17:52
|
show 3 more comments
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I am trying to install Debian in ASUS P2440UA laptop. Previously I was using Windows 7 and Linux Mint in dual boot without any issue (for 6 months). But I decided to format whole hard drive and install only Debian. I have formatted the hard drive as GPT and tried to install Debian in UEFI mode. I used 256 MB EFI system partition, 60 GB root and 4 GB swap. Rest of the space is mounted as home. But at the end of installation process "failed to install grub bootloader on a hard drive".
Then I have followed this https://forums.kali.org/showthread.php?37091-GRUB-Boot-Loader-Not-installing-on-Hard-Drive but still didn't worked. It was an "input output error".
Then I have found this When wouldn't you want to install GRUB bootloader? saying that installing grub in a modern computer is not the best option.
In this case what is the best option for me? I am trying for four days.
Note that I havd an empty hard drive. I want to use gpt format for hard drive. I will use multi boot.
linux debian grub2 boot-loader
I am trying to install Debian in ASUS P2440UA laptop. Previously I was using Windows 7 and Linux Mint in dual boot without any issue (for 6 months). But I decided to format whole hard drive and install only Debian. I have formatted the hard drive as GPT and tried to install Debian in UEFI mode. I used 256 MB EFI system partition, 60 GB root and 4 GB swap. Rest of the space is mounted as home. But at the end of installation process "failed to install grub bootloader on a hard drive".
Then I have followed this https://forums.kali.org/showthread.php?37091-GRUB-Boot-Loader-Not-installing-on-Hard-Drive but still didn't worked. It was an "input output error".
Then I have found this When wouldn't you want to install GRUB bootloader? saying that installing grub in a modern computer is not the best option.
In this case what is the best option for me? I am trying for four days.
Note that I havd an empty hard drive. I want to use gpt format for hard drive. I will use multi boot.
linux debian grub2 boot-loader
linux debian grub2 boot-loader
asked Nov 28 at 14:59
Nafi Shahriyar
112
112
"input output error" means you should replace your hdd (or the broken cables).
– Ipor Sircer
Nov 28 at 15:05
unix.stackexchange.com/questions/399626/…
– Rui F Ribeiro
Nov 28 at 15:06
Nothing is broken. Everything was working just fine. But I am having issue while trying to install only Deviation.
– Nafi Shahriyar
Nov 28 at 15:21
"input output error" or grub cannot 'talk' to the drive for some reason. Can you use BIOS mode not UEFI mode as a test?
– jc__
Nov 28 at 17:19
Yes I did. BIOS mode works
– Nafi Shahriyar
Nov 28 at 17:52
|
show 3 more comments
"input output error" means you should replace your hdd (or the broken cables).
– Ipor Sircer
Nov 28 at 15:05
unix.stackexchange.com/questions/399626/…
– Rui F Ribeiro
Nov 28 at 15:06
Nothing is broken. Everything was working just fine. But I am having issue while trying to install only Deviation.
– Nafi Shahriyar
Nov 28 at 15:21
"input output error" or grub cannot 'talk' to the drive for some reason. Can you use BIOS mode not UEFI mode as a test?
– jc__
Nov 28 at 17:19
Yes I did. BIOS mode works
– Nafi Shahriyar
Nov 28 at 17:52
"input output error" means you should replace your hdd (or the broken cables).
– Ipor Sircer
Nov 28 at 15:05
"input output error" means you should replace your hdd (or the broken cables).
– Ipor Sircer
Nov 28 at 15:05
unix.stackexchange.com/questions/399626/…
– Rui F Ribeiro
Nov 28 at 15:06
unix.stackexchange.com/questions/399626/…
– Rui F Ribeiro
Nov 28 at 15:06
Nothing is broken. Everything was working just fine. But I am having issue while trying to install only Deviation.
– Nafi Shahriyar
Nov 28 at 15:21
Nothing is broken. Everything was working just fine. But I am having issue while trying to install only Deviation.
– Nafi Shahriyar
Nov 28 at 15:21
"input output error" or grub cannot 'talk' to the drive for some reason. Can you use BIOS mode not UEFI mode as a test?
– jc__
Nov 28 at 17:19
"input output error" or grub cannot 'talk' to the drive for some reason. Can you use BIOS mode not UEFI mode as a test?
– jc__
Nov 28 at 17:19
Yes I did. BIOS mode works
– Nafi Shahriyar
Nov 28 at 17:52
Yes I did. BIOS mode works
– Nafi Shahriyar
Nov 28 at 17:52
|
show 3 more comments
2 Answers
2
active
oldest
votes
up vote
0
down vote
My problem was poor implementation of UEFI by ASUS in my ASUS P2440UA laptop. While trying to find a solution I have found in many documents that UEFI standed is not strictly maintained by manufacturers. I have found a way to install Debina in UEFI mode but I can't consider it as a solution.
Solve
- Install Windows 7 in UEFI mode. But windows 7 won't boot and will get stuck at logo. To boot windows, I had to enable CSM support to boot windows 7. (Ignore sda4 and sda9)
- Then I have installed Debian as usual in UEFI mode.
- Then I have deleted sda4, boot Debian from live USB, moved sda8 (Debian root partison) to free space on right side.
- Then I have mounted sda2 (UEFI bootloader partison) and deletd a folder named Microsoft. It contained windows bootloader. After that
sudo update-grub
- Then I have also deletd sda1. Now everything is working as I wanted.
New contributor
add a comment |
up vote
0
down vote
From the info you provided, GRUB may not be the issue. It might be a poor implementation of UEFI by the computer manufacturer. Attempting to manually reinstall or fix GRUB would not help if this is the case.
Try installing rEFInd onto a USB drive and booting it (assuming your computer can boot from USB). Follow the instructions and links at http://www.rodsbooks.com/refind/ to download and install. I recommend using the USB image file. There's a good chance rEFInd will find your Debian installation and kernel image and present an option to boot it.
Afterward, if you want rEFInd as a permanent solution:
- log into Debian and get sudo/root access
- mount the rEFInd USB drive, open it, and cd into EFI/
- copy the "refind" folder and paste it to your system's /boot/efi/EFI directory (make sure your ESP is mounted at /boot/efi). This will prepare us to "install" rEFInd using EFI shell.
- Reboot computer and boot the rEFInd USB drive again
- Choose the EFI shell option
- Follow the instructions to install via EFI shell here: http://www.rodsbooks.com/refind/installing.html#efishell
This will update the nvram/computer's boot options with an entry pointing at Debian.
You may run into root access issues that need fixing first before you can install rEFInd on the main system. In my own experience, Debian's install process didn't enable root access despite me confirming otherwise. I'll leave this for some other time. As to why Windows and Mint worked before, if they were both on the same ESP, I'm guessing the UEFI detected Windows's presence and so was able to see other systems. If Windows was not present, it wouldn't have seen Mint (and therein lies the problem).
I had to do a lot of research for this because I'm assuming few people own hardware with poor UEFI firmware, so this issue is rarely reported and asked about. This is my two cents in order for me to give it more exposure. I hope I was able to help. I'm definitely not a Linux expert so feel free to correct anything I may have wrong. Anyway, good luck!
New contributor
You are correct. It was manufacturing issue. I have heard about it while trying to find a solve, but I didn't expect it from a reputable company like ASUS. I have also upgrade ASUS UEFI firmware. I have successfully installed Debian in UEFI mode but I canty consider it as a solution.
– Nafi Shahriyar
2 days ago
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
My problem was poor implementation of UEFI by ASUS in my ASUS P2440UA laptop. While trying to find a solution I have found in many documents that UEFI standed is not strictly maintained by manufacturers. I have found a way to install Debina in UEFI mode but I can't consider it as a solution.
Solve
- Install Windows 7 in UEFI mode. But windows 7 won't boot and will get stuck at logo. To boot windows, I had to enable CSM support to boot windows 7. (Ignore sda4 and sda9)
- Then I have installed Debian as usual in UEFI mode.
- Then I have deleted sda4, boot Debian from live USB, moved sda8 (Debian root partison) to free space on right side.
- Then I have mounted sda2 (UEFI bootloader partison) and deletd a folder named Microsoft. It contained windows bootloader. After that
sudo update-grub
- Then I have also deletd sda1. Now everything is working as I wanted.
New contributor
add a comment |
up vote
0
down vote
My problem was poor implementation of UEFI by ASUS in my ASUS P2440UA laptop. While trying to find a solution I have found in many documents that UEFI standed is not strictly maintained by manufacturers. I have found a way to install Debina in UEFI mode but I can't consider it as a solution.
Solve
- Install Windows 7 in UEFI mode. But windows 7 won't boot and will get stuck at logo. To boot windows, I had to enable CSM support to boot windows 7. (Ignore sda4 and sda9)
- Then I have installed Debian as usual in UEFI mode.
- Then I have deleted sda4, boot Debian from live USB, moved sda8 (Debian root partison) to free space on right side.
- Then I have mounted sda2 (UEFI bootloader partison) and deletd a folder named Microsoft. It contained windows bootloader. After that
sudo update-grub
- Then I have also deletd sda1. Now everything is working as I wanted.
New contributor
add a comment |
up vote
0
down vote
up vote
0
down vote
My problem was poor implementation of UEFI by ASUS in my ASUS P2440UA laptop. While trying to find a solution I have found in many documents that UEFI standed is not strictly maintained by manufacturers. I have found a way to install Debina in UEFI mode but I can't consider it as a solution.
Solve
- Install Windows 7 in UEFI mode. But windows 7 won't boot and will get stuck at logo. To boot windows, I had to enable CSM support to boot windows 7. (Ignore sda4 and sda9)
- Then I have installed Debian as usual in UEFI mode.
- Then I have deleted sda4, boot Debian from live USB, moved sda8 (Debian root partison) to free space on right side.
- Then I have mounted sda2 (UEFI bootloader partison) and deletd a folder named Microsoft. It contained windows bootloader. After that
sudo update-grub
- Then I have also deletd sda1. Now everything is working as I wanted.
New contributor
My problem was poor implementation of UEFI by ASUS in my ASUS P2440UA laptop. While trying to find a solution I have found in many documents that UEFI standed is not strictly maintained by manufacturers. I have found a way to install Debina in UEFI mode but I can't consider it as a solution.
Solve
- Install Windows 7 in UEFI mode. But windows 7 won't boot and will get stuck at logo. To boot windows, I had to enable CSM support to boot windows 7. (Ignore sda4 and sda9)
- Then I have installed Debian as usual in UEFI mode.
- Then I have deleted sda4, boot Debian from live USB, moved sda8 (Debian root partison) to free space on right side.
- Then I have mounted sda2 (UEFI bootloader partison) and deletd a folder named Microsoft. It contained windows bootloader. After that
sudo update-grub
- Then I have also deletd sda1. Now everything is working as I wanted.
New contributor
New contributor
answered yesterday
Nafi Shahriyar
112
112
New contributor
New contributor
add a comment |
add a comment |
up vote
0
down vote
From the info you provided, GRUB may not be the issue. It might be a poor implementation of UEFI by the computer manufacturer. Attempting to manually reinstall or fix GRUB would not help if this is the case.
Try installing rEFInd onto a USB drive and booting it (assuming your computer can boot from USB). Follow the instructions and links at http://www.rodsbooks.com/refind/ to download and install. I recommend using the USB image file. There's a good chance rEFInd will find your Debian installation and kernel image and present an option to boot it.
Afterward, if you want rEFInd as a permanent solution:
- log into Debian and get sudo/root access
- mount the rEFInd USB drive, open it, and cd into EFI/
- copy the "refind" folder and paste it to your system's /boot/efi/EFI directory (make sure your ESP is mounted at /boot/efi). This will prepare us to "install" rEFInd using EFI shell.
- Reboot computer and boot the rEFInd USB drive again
- Choose the EFI shell option
- Follow the instructions to install via EFI shell here: http://www.rodsbooks.com/refind/installing.html#efishell
This will update the nvram/computer's boot options with an entry pointing at Debian.
You may run into root access issues that need fixing first before you can install rEFInd on the main system. In my own experience, Debian's install process didn't enable root access despite me confirming otherwise. I'll leave this for some other time. As to why Windows and Mint worked before, if they were both on the same ESP, I'm guessing the UEFI detected Windows's presence and so was able to see other systems. If Windows was not present, it wouldn't have seen Mint (and therein lies the problem).
I had to do a lot of research for this because I'm assuming few people own hardware with poor UEFI firmware, so this issue is rarely reported and asked about. This is my two cents in order for me to give it more exposure. I hope I was able to help. I'm definitely not a Linux expert so feel free to correct anything I may have wrong. Anyway, good luck!
New contributor
You are correct. It was manufacturing issue. I have heard about it while trying to find a solve, but I didn't expect it from a reputable company like ASUS. I have also upgrade ASUS UEFI firmware. I have successfully installed Debian in UEFI mode but I canty consider it as a solution.
– Nafi Shahriyar
2 days ago
add a comment |
up vote
0
down vote
From the info you provided, GRUB may not be the issue. It might be a poor implementation of UEFI by the computer manufacturer. Attempting to manually reinstall or fix GRUB would not help if this is the case.
Try installing rEFInd onto a USB drive and booting it (assuming your computer can boot from USB). Follow the instructions and links at http://www.rodsbooks.com/refind/ to download and install. I recommend using the USB image file. There's a good chance rEFInd will find your Debian installation and kernel image and present an option to boot it.
Afterward, if you want rEFInd as a permanent solution:
- log into Debian and get sudo/root access
- mount the rEFInd USB drive, open it, and cd into EFI/
- copy the "refind" folder and paste it to your system's /boot/efi/EFI directory (make sure your ESP is mounted at /boot/efi). This will prepare us to "install" rEFInd using EFI shell.
- Reboot computer and boot the rEFInd USB drive again
- Choose the EFI shell option
- Follow the instructions to install via EFI shell here: http://www.rodsbooks.com/refind/installing.html#efishell
This will update the nvram/computer's boot options with an entry pointing at Debian.
You may run into root access issues that need fixing first before you can install rEFInd on the main system. In my own experience, Debian's install process didn't enable root access despite me confirming otherwise. I'll leave this for some other time. As to why Windows and Mint worked before, if they were both on the same ESP, I'm guessing the UEFI detected Windows's presence and so was able to see other systems. If Windows was not present, it wouldn't have seen Mint (and therein lies the problem).
I had to do a lot of research for this because I'm assuming few people own hardware with poor UEFI firmware, so this issue is rarely reported and asked about. This is my two cents in order for me to give it more exposure. I hope I was able to help. I'm definitely not a Linux expert so feel free to correct anything I may have wrong. Anyway, good luck!
New contributor
You are correct. It was manufacturing issue. I have heard about it while trying to find a solve, but I didn't expect it from a reputable company like ASUS. I have also upgrade ASUS UEFI firmware. I have successfully installed Debian in UEFI mode but I canty consider it as a solution.
– Nafi Shahriyar
2 days ago
add a comment |
up vote
0
down vote
up vote
0
down vote
From the info you provided, GRUB may not be the issue. It might be a poor implementation of UEFI by the computer manufacturer. Attempting to manually reinstall or fix GRUB would not help if this is the case.
Try installing rEFInd onto a USB drive and booting it (assuming your computer can boot from USB). Follow the instructions and links at http://www.rodsbooks.com/refind/ to download and install. I recommend using the USB image file. There's a good chance rEFInd will find your Debian installation and kernel image and present an option to boot it.
Afterward, if you want rEFInd as a permanent solution:
- log into Debian and get sudo/root access
- mount the rEFInd USB drive, open it, and cd into EFI/
- copy the "refind" folder and paste it to your system's /boot/efi/EFI directory (make sure your ESP is mounted at /boot/efi). This will prepare us to "install" rEFInd using EFI shell.
- Reboot computer and boot the rEFInd USB drive again
- Choose the EFI shell option
- Follow the instructions to install via EFI shell here: http://www.rodsbooks.com/refind/installing.html#efishell
This will update the nvram/computer's boot options with an entry pointing at Debian.
You may run into root access issues that need fixing first before you can install rEFInd on the main system. In my own experience, Debian's install process didn't enable root access despite me confirming otherwise. I'll leave this for some other time. As to why Windows and Mint worked before, if they were both on the same ESP, I'm guessing the UEFI detected Windows's presence and so was able to see other systems. If Windows was not present, it wouldn't have seen Mint (and therein lies the problem).
I had to do a lot of research for this because I'm assuming few people own hardware with poor UEFI firmware, so this issue is rarely reported and asked about. This is my two cents in order for me to give it more exposure. I hope I was able to help. I'm definitely not a Linux expert so feel free to correct anything I may have wrong. Anyway, good luck!
New contributor
From the info you provided, GRUB may not be the issue. It might be a poor implementation of UEFI by the computer manufacturer. Attempting to manually reinstall or fix GRUB would not help if this is the case.
Try installing rEFInd onto a USB drive and booting it (assuming your computer can boot from USB). Follow the instructions and links at http://www.rodsbooks.com/refind/ to download and install. I recommend using the USB image file. There's a good chance rEFInd will find your Debian installation and kernel image and present an option to boot it.
Afterward, if you want rEFInd as a permanent solution:
- log into Debian and get sudo/root access
- mount the rEFInd USB drive, open it, and cd into EFI/
- copy the "refind" folder and paste it to your system's /boot/efi/EFI directory (make sure your ESP is mounted at /boot/efi). This will prepare us to "install" rEFInd using EFI shell.
- Reboot computer and boot the rEFInd USB drive again
- Choose the EFI shell option
- Follow the instructions to install via EFI shell here: http://www.rodsbooks.com/refind/installing.html#efishell
This will update the nvram/computer's boot options with an entry pointing at Debian.
You may run into root access issues that need fixing first before you can install rEFInd on the main system. In my own experience, Debian's install process didn't enable root access despite me confirming otherwise. I'll leave this for some other time. As to why Windows and Mint worked before, if they were both on the same ESP, I'm guessing the UEFI detected Windows's presence and so was able to see other systems. If Windows was not present, it wouldn't have seen Mint (and therein lies the problem).
I had to do a lot of research for this because I'm assuming few people own hardware with poor UEFI firmware, so this issue is rarely reported and asked about. This is my two cents in order for me to give it more exposure. I hope I was able to help. I'm definitely not a Linux expert so feel free to correct anything I may have wrong. Anyway, good luck!
New contributor
edited 4 hours ago
New contributor
answered Dec 2 at 12:49
user3308815
11
11
New contributor
New contributor
You are correct. It was manufacturing issue. I have heard about it while trying to find a solve, but I didn't expect it from a reputable company like ASUS. I have also upgrade ASUS UEFI firmware. I have successfully installed Debian in UEFI mode but I canty consider it as a solution.
– Nafi Shahriyar
2 days ago
add a comment |
You are correct. It was manufacturing issue. I have heard about it while trying to find a solve, but I didn't expect it from a reputable company like ASUS. I have also upgrade ASUS UEFI firmware. I have successfully installed Debian in UEFI mode but I canty consider it as a solution.
– Nafi Shahriyar
2 days ago
You are correct. It was manufacturing issue. I have heard about it while trying to find a solve, but I didn't expect it from a reputable company like ASUS. I have also upgrade ASUS UEFI firmware. I have successfully installed Debian in UEFI mode but I canty consider it as a solution.
– Nafi Shahriyar
2 days ago
You are correct. It was manufacturing issue. I have heard about it while trying to find a solve, but I didn't expect it from a reputable company like ASUS. I have also upgrade ASUS UEFI firmware. I have successfully installed Debian in UEFI mode but I canty consider it as a solution.
– Nafi Shahriyar
2 days ago
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f484685%2fbootloader-installation-failed%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
"input output error" means you should replace your hdd (or the broken cables).
– Ipor Sircer
Nov 28 at 15:05
unix.stackexchange.com/questions/399626/…
– Rui F Ribeiro
Nov 28 at 15:06
Nothing is broken. Everything was working just fine. But I am having issue while trying to install only Deviation.
– Nafi Shahriyar
Nov 28 at 15:21
"input output error" or grub cannot 'talk' to the drive for some reason. Can you use BIOS mode not UEFI mode as a test?
– jc__
Nov 28 at 17:19
Yes I did. BIOS mode works
– Nafi Shahriyar
Nov 28 at 17:52