Boot-Repair hangs, possible alternative?
up vote
1
down vote
favorite
My overall goal is to dual boot Linux Mint and Windows 10. The motherboard is legacy bios only.
Firstly I installed Linux Mint then Windows 10 on a secondary partition.
Because I forgot to make a separate boot partition... I moved everything 1000MB to the right, and created a ext4 boot partition at the beginning of sda.
Running boot repair on a live Ubuntu USB with the options:
- Separate /boot partition: sda4 (the first partition on disk)
- GRUB Legacy (figured that was for legacy bios)
- Reinstall GRUB (default)
- Unhide boot menu: 10s (default)
Boot Repair hangs at Purge kernels then reinstall last kernel sda1 (ins). This may require several minuets...
I have let this running overnight, the process is still running. I have done a reboot and tried again, let the process run for 3 days. Nothing different.
Boot Info Summary: http://paste.ubuntu.com/17678629/
I have had gparted open at the same time, assuming that wouldn't have an affect.
boot grub-legacy
add a comment |
up vote
1
down vote
favorite
My overall goal is to dual boot Linux Mint and Windows 10. The motherboard is legacy bios only.
Firstly I installed Linux Mint then Windows 10 on a secondary partition.
Because I forgot to make a separate boot partition... I moved everything 1000MB to the right, and created a ext4 boot partition at the beginning of sda.
Running boot repair on a live Ubuntu USB with the options:
- Separate /boot partition: sda4 (the first partition on disk)
- GRUB Legacy (figured that was for legacy bios)
- Reinstall GRUB (default)
- Unhide boot menu: 10s (default)
Boot Repair hangs at Purge kernels then reinstall last kernel sda1 (ins). This may require several minuets...
I have let this running overnight, the process is still running. I have done a reboot and tried again, let the process run for 3 days. Nothing different.
Boot Info Summary: http://paste.ubuntu.com/17678629/
I have had gparted open at the same time, assuming that wouldn't have an affect.
boot grub-legacy
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
My overall goal is to dual boot Linux Mint and Windows 10. The motherboard is legacy bios only.
Firstly I installed Linux Mint then Windows 10 on a secondary partition.
Because I forgot to make a separate boot partition... I moved everything 1000MB to the right, and created a ext4 boot partition at the beginning of sda.
Running boot repair on a live Ubuntu USB with the options:
- Separate /boot partition: sda4 (the first partition on disk)
- GRUB Legacy (figured that was for legacy bios)
- Reinstall GRUB (default)
- Unhide boot menu: 10s (default)
Boot Repair hangs at Purge kernels then reinstall last kernel sda1 (ins). This may require several minuets...
I have let this running overnight, the process is still running. I have done a reboot and tried again, let the process run for 3 days. Nothing different.
Boot Info Summary: http://paste.ubuntu.com/17678629/
I have had gparted open at the same time, assuming that wouldn't have an affect.
boot grub-legacy
My overall goal is to dual boot Linux Mint and Windows 10. The motherboard is legacy bios only.
Firstly I installed Linux Mint then Windows 10 on a secondary partition.
Because I forgot to make a separate boot partition... I moved everything 1000MB to the right, and created a ext4 boot partition at the beginning of sda.
Running boot repair on a live Ubuntu USB with the options:
- Separate /boot partition: sda4 (the first partition on disk)
- GRUB Legacy (figured that was for legacy bios)
- Reinstall GRUB (default)
- Unhide boot menu: 10s (default)
Boot Repair hangs at Purge kernels then reinstall last kernel sda1 (ins). This may require several minuets...
I have let this running overnight, the process is still running. I have done a reboot and tried again, let the process run for 3 days. Nothing different.
Boot Info Summary: http://paste.ubuntu.com/17678629/
I have had gparted open at the same time, assuming that wouldn't have an affect.
boot grub-legacy
boot grub-legacy
edited Jun 28 '16 at 11:45
asked Jun 22 '16 at 6:17
Harry
64
64
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
0
down vote
I've had exactly the same issue today. Digging through boot-repair
tool logs I've found this error:
gui-actions-purge.sh: line 441: ${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic: bad substitution
The logs are stored in the varlogboot-savlogYYYY-MM-DD__HHhMMboot-repairXXboot-repair.log
file.
The package linux${$KERNELTOREINST}-generic
doesn't look like a valid package. It probably should be just linux-generic
.
So I've modified usrshareboot-savgui-actions-purge.sh
, replacing line 441
:
local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic"
with:
local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux-generic linux-headers-generic"
and restarted boot-repair
from taskbar menu.
It worked OK and fixed my boot issues, restoring grub on my cloned disk.
Quick how-to
- Boot
Boot-Repair
as usual, but close autostartedboot-repair
tool - Open terminal from taskbar menu
- Type
sudo su -
to get root shell - Type
leafpad &
- Text-editor will open. Open
usrshareboot-savgui-actions-purge.sh
file with it.
Find
local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic"
Replace with:
local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux-generic linux-headers-generic"
- Save file, close
Leafpad
- Leave root terminal open, you will need it later, as
boot-repair
will ask you to run some commands. - Run
boot-repair
from taskbar menu and follow it's instructions.
Made the change and still getting the same output. Searched for other peoples experiences and found this comment stating that you cannot use a legacy bios system. And the following comment suggests that I may need the live os in legacy?
– Harry
Jun 30 '16 at 7:50
@Harry Well, in my case it was legacy all the way down - it worked OK. Could you postboot-repair.log
? I've used TeamViewer to get it:wget https://download.teamviewer.com/download/teamviewer_i386.deb && apt-get install ./teamviewer_i386.deb && teamviewer
– beatcracker
Jun 30 '16 at 10:13
add a comment |
up vote
0
down vote
My general approach to these quagmires is image the disks involved, then just start fresh.
Not technically helpful I know, but my advice nonetheless.
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
I've had exactly the same issue today. Digging through boot-repair
tool logs I've found this error:
gui-actions-purge.sh: line 441: ${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic: bad substitution
The logs are stored in the varlogboot-savlogYYYY-MM-DD__HHhMMboot-repairXXboot-repair.log
file.
The package linux${$KERNELTOREINST}-generic
doesn't look like a valid package. It probably should be just linux-generic
.
So I've modified usrshareboot-savgui-actions-purge.sh
, replacing line 441
:
local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic"
with:
local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux-generic linux-headers-generic"
and restarted boot-repair
from taskbar menu.
It worked OK and fixed my boot issues, restoring grub on my cloned disk.
Quick how-to
- Boot
Boot-Repair
as usual, but close autostartedboot-repair
tool - Open terminal from taskbar menu
- Type
sudo su -
to get root shell - Type
leafpad &
- Text-editor will open. Open
usrshareboot-savgui-actions-purge.sh
file with it.
Find
local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic"
Replace with:
local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux-generic linux-headers-generic"
- Save file, close
Leafpad
- Leave root terminal open, you will need it later, as
boot-repair
will ask you to run some commands. - Run
boot-repair
from taskbar menu and follow it's instructions.
Made the change and still getting the same output. Searched for other peoples experiences and found this comment stating that you cannot use a legacy bios system. And the following comment suggests that I may need the live os in legacy?
– Harry
Jun 30 '16 at 7:50
@Harry Well, in my case it was legacy all the way down - it worked OK. Could you postboot-repair.log
? I've used TeamViewer to get it:wget https://download.teamviewer.com/download/teamviewer_i386.deb && apt-get install ./teamviewer_i386.deb && teamviewer
– beatcracker
Jun 30 '16 at 10:13
add a comment |
up vote
0
down vote
I've had exactly the same issue today. Digging through boot-repair
tool logs I've found this error:
gui-actions-purge.sh: line 441: ${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic: bad substitution
The logs are stored in the varlogboot-savlogYYYY-MM-DD__HHhMMboot-repairXXboot-repair.log
file.
The package linux${$KERNELTOREINST}-generic
doesn't look like a valid package. It probably should be just linux-generic
.
So I've modified usrshareboot-savgui-actions-purge.sh
, replacing line 441
:
local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic"
with:
local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux-generic linux-headers-generic"
and restarted boot-repair
from taskbar menu.
It worked OK and fixed my boot issues, restoring grub on my cloned disk.
Quick how-to
- Boot
Boot-Repair
as usual, but close autostartedboot-repair
tool - Open terminal from taskbar menu
- Type
sudo su -
to get root shell - Type
leafpad &
- Text-editor will open. Open
usrshareboot-savgui-actions-purge.sh
file with it.
Find
local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic"
Replace with:
local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux-generic linux-headers-generic"
- Save file, close
Leafpad
- Leave root terminal open, you will need it later, as
boot-repair
will ask you to run some commands. - Run
boot-repair
from taskbar menu and follow it's instructions.
Made the change and still getting the same output. Searched for other peoples experiences and found this comment stating that you cannot use a legacy bios system. And the following comment suggests that I may need the live os in legacy?
– Harry
Jun 30 '16 at 7:50
@Harry Well, in my case it was legacy all the way down - it worked OK. Could you postboot-repair.log
? I've used TeamViewer to get it:wget https://download.teamviewer.com/download/teamviewer_i386.deb && apt-get install ./teamviewer_i386.deb && teamviewer
– beatcracker
Jun 30 '16 at 10:13
add a comment |
up vote
0
down vote
up vote
0
down vote
I've had exactly the same issue today. Digging through boot-repair
tool logs I've found this error:
gui-actions-purge.sh: line 441: ${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic: bad substitution
The logs are stored in the varlogboot-savlogYYYY-MM-DD__HHhMMboot-repairXXboot-repair.log
file.
The package linux${$KERNELTOREINST}-generic
doesn't look like a valid package. It probably should be just linux-generic
.
So I've modified usrshareboot-savgui-actions-purge.sh
, replacing line 441
:
local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic"
with:
local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux-generic linux-headers-generic"
and restarted boot-repair
from taskbar menu.
It worked OK and fixed my boot issues, restoring grub on my cloned disk.
Quick how-to
- Boot
Boot-Repair
as usual, but close autostartedboot-repair
tool - Open terminal from taskbar menu
- Type
sudo su -
to get root shell - Type
leafpad &
- Text-editor will open. Open
usrshareboot-savgui-actions-purge.sh
file with it.
Find
local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic"
Replace with:
local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux-generic linux-headers-generic"
- Save file, close
Leafpad
- Leave root terminal open, you will need it later, as
boot-repair
will ask you to run some commands. - Run
boot-repair
from taskbar menu and follow it's instructions.
I've had exactly the same issue today. Digging through boot-repair
tool logs I've found this error:
gui-actions-purge.sh: line 441: ${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic: bad substitution
The logs are stored in the varlogboot-savlogYYYY-MM-DD__HHhMMboot-repairXXboot-repair.log
file.
The package linux${$KERNELTOREINST}-generic
doesn't look like a valid package. It probably should be just linux-generic
.
So I've modified usrshareboot-savgui-actions-purge.sh
, replacing line 441
:
local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic"
with:
local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux-generic linux-headers-generic"
and restarted boot-repair
from taskbar menu.
It worked OK and fixed my boot issues, restoring grub on my cloned disk.
Quick how-to
- Boot
Boot-Repair
as usual, but close autostartedboot-repair
tool - Open terminal from taskbar menu
- Type
sudo su -
to get root shell - Type
leafpad &
- Text-editor will open. Open
usrshareboot-savgui-actions-purge.sh
file with it.
Find
local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic"
Replace with:
local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux-generic linux-headers-generic"
- Save file, close
Leafpad
- Leave root terminal open, you will need it later, as
boot-repair
will ask you to run some commands. - Run
boot-repair
from taskbar menu and follow it's instructions.
answered Jun 29 '16 at 13:21
beatcracker
1012
1012
Made the change and still getting the same output. Searched for other peoples experiences and found this comment stating that you cannot use a legacy bios system. And the following comment suggests that I may need the live os in legacy?
– Harry
Jun 30 '16 at 7:50
@Harry Well, in my case it was legacy all the way down - it worked OK. Could you postboot-repair.log
? I've used TeamViewer to get it:wget https://download.teamviewer.com/download/teamviewer_i386.deb && apt-get install ./teamviewer_i386.deb && teamviewer
– beatcracker
Jun 30 '16 at 10:13
add a comment |
Made the change and still getting the same output. Searched for other peoples experiences and found this comment stating that you cannot use a legacy bios system. And the following comment suggests that I may need the live os in legacy?
– Harry
Jun 30 '16 at 7:50
@Harry Well, in my case it was legacy all the way down - it worked OK. Could you postboot-repair.log
? I've used TeamViewer to get it:wget https://download.teamviewer.com/download/teamviewer_i386.deb && apt-get install ./teamviewer_i386.deb && teamviewer
– beatcracker
Jun 30 '16 at 10:13
Made the change and still getting the same output. Searched for other peoples experiences and found this comment stating that you cannot use a legacy bios system. And the following comment suggests that I may need the live os in legacy?
– Harry
Jun 30 '16 at 7:50
Made the change and still getting the same output. Searched for other peoples experiences and found this comment stating that you cannot use a legacy bios system. And the following comment suggests that I may need the live os in legacy?
– Harry
Jun 30 '16 at 7:50
@Harry Well, in my case it was legacy all the way down - it worked OK. Could you post
boot-repair.log
? I've used TeamViewer to get it: wget https://download.teamviewer.com/download/teamviewer_i386.deb && apt-get install ./teamviewer_i386.deb && teamviewer
– beatcracker
Jun 30 '16 at 10:13
@Harry Well, in my case it was legacy all the way down - it worked OK. Could you post
boot-repair.log
? I've used TeamViewer to get it: wget https://download.teamviewer.com/download/teamviewer_i386.deb && apt-get install ./teamviewer_i386.deb && teamviewer
– beatcracker
Jun 30 '16 at 10:13
add a comment |
up vote
0
down vote
My general approach to these quagmires is image the disks involved, then just start fresh.
Not technically helpful I know, but my advice nonetheless.
add a comment |
up vote
0
down vote
My general approach to these quagmires is image the disks involved, then just start fresh.
Not technically helpful I know, but my advice nonetheless.
add a comment |
up vote
0
down vote
up vote
0
down vote
My general approach to these quagmires is image the disks involved, then just start fresh.
Not technically helpful I know, but my advice nonetheless.
My general approach to these quagmires is image the disks involved, then just start fresh.
Not technically helpful I know, but my advice nonetheless.
answered Jul 7 at 11:41
Luke Mlsna
1013
1013
add a comment |
add a comment |
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%2f291295%2fboot-repair-hangs-possible-alternative%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