Start job is running for hold until boot process finishes up 18.04
I just installed ubuntu-desktop 18.04 on a new machine (no OS was previously installed). When I restart after installation completes the boot process gets stuck with
Started hold until boot finishes up.
Pressing Ctrl+Alt+F2 or F1 does not do anything.
When I go into the recovery screen, the keyboard does not respond...
Any ideas how to deal with these issues?
Thanks!
boot 18.04
edited 1 hour ago
d a i s y
3,29582344
asked May 8 '18 at 14:34
id5hid5h
1613
add a comment |
I just installed ubuntu-desktop 18.04 on a new machine (no OS was previously installed). When I restart after installation completes the boot process gets stuck with
Started hold until boot finishes up.
Pressing Ctrl+Alt+F2 or F1 does not do anything.
When I go into the recovery screen, the keyboard does not respond...
Any ideas how to deal with these issues?
Thanks!
boot 18.04
edited 1 hour ago
d a i s y
3,29582344
asked May 8 '18 at 14:34
id5hid5h
1613
Did you found a solution for this ?
– Charles-Antoine Fournel
May 21 '18 at 16:20
Have you tried one of these solutions: askubuntu.com/questions/760825/… or If it is a bug and may now be fixed, try to update the systemsudo apt update && sudo apt upgrade
– d a i s y
18 hours ago
The fact that CTRL+ALT sequences do not work seem related to the fact that your keyboard also doesn't work in recovery mode, and seems like a hardware problem - try to replace your keyboard or connect it to a different port.
– Guss
18 hours ago
add a comment |
I just installed ubuntu-desktop 18.04 on a new machine (no OS was previously installed). When I restart after installation completes the boot process gets stuck with
Started hold until boot finishes up.
Pressing Ctrl+Alt+F2 or F1 does not do anything.
When I go into the recovery screen, the keyboard does not respond...
Any ideas how to deal with these issues?
Thanks!
boot 18.04
edited 1 hour ago
d a i s y
3,29582344
asked May 8 '18 at 14:34
id5hid5h
1613
I just installed ubuntu-desktop 18.04 on a new machine (no OS was previously installed). When I restart after installation completes the boot process gets stuck with
Started hold until boot finishes up.
Pressing Ctrl+Alt+F2 or F1 does not do anything.
When I go into the recovery screen, the keyboard does not respond...
Any ideas how to deal with these issues?
Thanks!
boot 18.04
boot 18.04
edited 1 hour ago
d a i s y
3,29582344
asked May 8 '18 at 14:34
id5hid5h
1613
edited 1 hour ago
d a i s y
3,29582344
asked May 8 '18 at 14:34
id5hid5h
1613
edited 1 hour ago
d a i s y
3,29582344
edited 1 hour ago
d a i s y
3,29582344
edited 1 hour ago
d a i s y
3,29582344
3,29582344
asked May 8 '18 at 14:34
id5hid5h
1613
asked May 8 '18 at 14:34
id5hid5h
1613
asked May 8 '18 at 14:34
id5hid5h
1613
1613
Did you found a solution for this ?
– Charles-Antoine Fournel
May 21 '18 at 16:20
Have you tried one of these solutions: askubuntu.com/questions/760825/… or If it is a bug and may now be fixed, try to update the systemsudo apt update && sudo apt upgrade
– d a i s y
18 hours ago
The fact that CTRL+ALT sequences do not work seem related to the fact that your keyboard also doesn't work in recovery mode, and seems like a hardware problem - try to replace your keyboard or connect it to a different port.
– Guss
18 hours ago
add a comment |
Did you found a solution for this ?
– Charles-Antoine Fournel
May 21 '18 at 16:20
Have you tried one of these solutions: askubuntu.com/questions/760825/… or If it is a bug and may now be fixed, try to update the systemsudo apt update && sudo apt upgrade
– d a i s y
18 hours ago
The fact that CTRL+ALT sequences do not work seem related to the fact that your keyboard also doesn't work in recovery mode, and seems like a hardware problem - try to replace your keyboard or connect it to a different port.
– Guss
18 hours ago
Did you found a solution for this ?
– Charles-Antoine Fournel
May 21 '18 at 16:20
Did you found a solution for this ?
– Charles-Antoine Fournel
May 21 '18 at 16:20
Have you tried one of these solutions: askubuntu.com/questions/760825/… or If it is a bug and may now be fixed, try to update the system
sudo apt update && sudo apt upgrade– d a i s y
18 hours ago
Have you tried one of these solutions: askubuntu.com/questions/760825/… or If it is a bug and may now be fixed, try to update the system
sudo apt update && sudo apt upgrade– d a i s y
18 hours ago
The fact that CTRL+ALT sequences do not work seem related to the fact that your keyboard also doesn't work in recovery mode, and seems like a hardware problem - try to replace your keyboard or connect it to a different port.
– Guss
18 hours ago
The fact that CTRL+ALT sequences do not work seem related to the fact that your keyboard also doesn't work in recovery mode, and seems like a hardware problem - try to replace your keyboard or connect it to a different port.
– Guss
18 hours ago
add a comment |
4 Answers
4
active
oldest
votes
On power up, can you press ESC or DEL or whatever key sequence gets you into the boot manager? I upgraded a LattePanda running lubuntu 16.04 to 18.04, and it was looping through some failure sequence. When I pressed ESC and entered the boot manager, I found that the first item in the boot sequence was an entry for Android. I don't have Android installed on this device, so I don't know how or why that entry was there. I selected the override to boot ubuntu, which worked fine. Once in the ubuntu O/S, I entered the following, based on info I found in another post:
sudo modprobe efivars
followed by:
efibootmgr
which told me that the Android entry was #5, so I then entered:
sudo efibootmgr -b 5 -B
to remove that entry from the boot sequence so that the next time I powered off and back on, it went to ubuntu.
Hope this helps.
edited Jun 8 '18 at 5:41
Eranda Peiris
671516
answered Jun 7 '18 at 20:09
Ed Trembicki-GuyEd Trembicki-Guy
12
add a comment |
This happens when you don't Unmount your external device and remove it . Use the above method press Ctrl+Alt+F2 orF1 enter Username and Password. Now Using terminal type
sudo modprobe efivars
and then followed by
efibootmgr
You will see the boot sequence order look for external device's now type
sudo efibootmgr -b no -B
Note no:denotes the external device's number.This worked for me.
edited Oct 3 '18 at 10:43
abu_bua
3,27981126
answered Oct 3 '18 at 10:19
Anurag Vishal RAnurag Vishal R
1
add a comment |
I had the same issue on boot after upgrading Kubuntu 16.04 to 18.04. I also saw error messages about lightdm failing to start. Here's what I did to fix the issue.
In the grub bootloader, edited the boot entry and removed the following variables from the linux boot command:
quiet splash $vt_handoff
Then press F10 to boot. It was now able to boot to a tty1 console login.
I first tried to install the latest nvidia drivers for my graphics card. This didn't help. I got the same error on reboot. (But keeping this here in case it was important https://linuxconfig.org/how-to-install-the-nvidia-drivers-on-ubuntu-18-04-bionic-beaver-linux )
Next I changed the display manager.
sudo dpkg-reconfigure lightdm
I changed the display manager to sddm (the only other option). Then I started sddm and the graphical interface started up.
sudo service sddm start
So it appears it was an issue with lightdm.
answered Jan 2 at 19:20
jdramerjdramer
1713
add a comment |
Had the same problem because the disks were full, I had to free up space
If you think this might be the issue you can select the advanced boot in GRUB menu and use the terminal option to remove some of the files then restart and try login again.
answered 19 hours ago
Haggui AyoubHaggui Ayoub
1
New contributor
Haggui Ayoub is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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%2faskubuntu.com%2fquestions%2f1033613%2fstart-job-is-running-for-hold-until-boot-process-finishes-up-18-04%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
On power up, can you press ESC or DEL or whatever key sequence gets you into the boot manager? I upgraded a LattePanda running lubuntu 16.04 to 18.04, and it was looping through some failure sequence. When I pressed ESC and entered the boot manager, I found that the first item in the boot sequence was an entry for Android. I don't have Android installed on this device, so I don't know how or why that entry was there. I selected the override to boot ubuntu, which worked fine. Once in the ubuntu O/S, I entered the following, based on info I found in another post:
sudo modprobe efivars
followed by:
efibootmgr
which told me that the Android entry was #5, so I then entered:
sudo efibootmgr -b 5 -B
to remove that entry from the boot sequence so that the next time I powered off and back on, it went to ubuntu.
Hope this helps.
edited Jun 8 '18 at 5:41
Eranda Peiris
671516
answered Jun 7 '18 at 20:09
Ed Trembicki-GuyEd Trembicki-Guy
12
add a comment |
On power up, can you press ESC or DEL or whatever key sequence gets you into the boot manager? I upgraded a LattePanda running lubuntu 16.04 to 18.04, and it was looping through some failure sequence. When I pressed ESC and entered the boot manager, I found that the first item in the boot sequence was an entry for Android. I don't have Android installed on this device, so I don't know how or why that entry was there. I selected the override to boot ubuntu, which worked fine. Once in the ubuntu O/S, I entered the following, based on info I found in another post:
sudo modprobe efivars
followed by:
efibootmgr
which told me that the Android entry was #5, so I then entered:
sudo efibootmgr -b 5 -B
to remove that entry from the boot sequence so that the next time I powered off and back on, it went to ubuntu.
Hope this helps.
edited Jun 8 '18 at 5:41
Eranda Peiris
671516
answered Jun 7 '18 at 20:09
Ed Trembicki-GuyEd Trembicki-Guy
12
add a comment |
On power up, can you press ESC or DEL or whatever key sequence gets you into the boot manager? I upgraded a LattePanda running lubuntu 16.04 to 18.04, and it was looping through some failure sequence. When I pressed ESC and entered the boot manager, I found that the first item in the boot sequence was an entry for Android. I don't have Android installed on this device, so I don't know how or why that entry was there. I selected the override to boot ubuntu, which worked fine. Once in the ubuntu O/S, I entered the following, based on info I found in another post:
sudo modprobe efivars
followed by:
efibootmgr
which told me that the Android entry was #5, so I then entered:
sudo efibootmgr -b 5 -B
to remove that entry from the boot sequence so that the next time I powered off and back on, it went to ubuntu.
Hope this helps.
edited Jun 8 '18 at 5:41
Eranda Peiris
671516
answered Jun 7 '18 at 20:09
Ed Trembicki-GuyEd Trembicki-Guy
12
On power up, can you press ESC or DEL or whatever key sequence gets you into the boot manager? I upgraded a LattePanda running lubuntu 16.04 to 18.04, and it was looping through some failure sequence. When I pressed ESC and entered the boot manager, I found that the first item in the boot sequence was an entry for Android. I don't have Android installed on this device, so I don't know how or why that entry was there. I selected the override to boot ubuntu, which worked fine. Once in the ubuntu O/S, I entered the following, based on info I found in another post:
sudo modprobe efivars
followed by:
efibootmgr
which told me that the Android entry was #5, so I then entered:
sudo efibootmgr -b 5 -B
to remove that entry from the boot sequence so that the next time I powered off and back on, it went to ubuntu.
Hope this helps.
edited Jun 8 '18 at 5:41
Eranda Peiris
671516
answered Jun 7 '18 at 20:09
Ed Trembicki-GuyEd Trembicki-Guy
12
edited Jun 8 '18 at 5:41
Eranda Peiris
671516
edited Jun 8 '18 at 5:41
Eranda Peiris
671516
edited Jun 8 '18 at 5:41
Eranda Peiris
671516
671516
answered Jun 7 '18 at 20:09
Ed Trembicki-GuyEd Trembicki-Guy
12
answered Jun 7 '18 at 20:09
Ed Trembicki-GuyEd Trembicki-Guy
12
answered Jun 7 '18 at 20:09
Ed Trembicki-GuyEd Trembicki-Guy
12
12
add a comment |
add a comment |
This happens when you don't Unmount your external device and remove it . Use the above method press Ctrl+Alt+F2 orF1 enter Username and Password. Now Using terminal type
sudo modprobe efivars
and then followed by
efibootmgr
You will see the boot sequence order look for external device's now type
sudo efibootmgr -b no -B
Note no:denotes the external device's number.This worked for me.
edited Oct 3 '18 at 10:43
abu_bua
3,27981126
answered Oct 3 '18 at 10:19
Anurag Vishal RAnurag Vishal R
1
add a comment |
This happens when you don't Unmount your external device and remove it . Use the above method press Ctrl+Alt+F2 orF1 enter Username and Password. Now Using terminal type
sudo modprobe efivars
and then followed by
efibootmgr
You will see the boot sequence order look for external device's now type
sudo efibootmgr -b no -B
Note no:denotes the external device's number.This worked for me.
edited Oct 3 '18 at 10:43
abu_bua
3,27981126
answered Oct 3 '18 at 10:19
Anurag Vishal RAnurag Vishal R
1
add a comment |
This happens when you don't Unmount your external device and remove it . Use the above method press Ctrl+Alt+F2 orF1 enter Username and Password. Now Using terminal type
sudo modprobe efivars
and then followed by
efibootmgr
You will see the boot sequence order look for external device's now type
sudo efibootmgr -b no -B
Note no:denotes the external device's number.This worked for me.
edited Oct 3 '18 at 10:43
abu_bua
3,27981126
answered Oct 3 '18 at 10:19
Anurag Vishal RAnurag Vishal R
1
This happens when you don't Unmount your external device and remove it . Use the above method press Ctrl+Alt+F2 orF1 enter Username and Password. Now Using terminal type
sudo modprobe efivars
and then followed by
efibootmgr
You will see the boot sequence order look for external device's now type
sudo efibootmgr -b no -B
Note no:denotes the external device's number.This worked for me.
edited Oct 3 '18 at 10:43
abu_bua
3,27981126
answered Oct 3 '18 at 10:19
Anurag Vishal RAnurag Vishal R
1
edited Oct 3 '18 at 10:43
abu_bua
3,27981126
edited Oct 3 '18 at 10:43
abu_bua
3,27981126
edited Oct 3 '18 at 10:43
abu_bua
3,27981126
3,27981126
answered Oct 3 '18 at 10:19
Anurag Vishal RAnurag Vishal R
1
answered Oct 3 '18 at 10:19
Anurag Vishal RAnurag Vishal R
1
answered Oct 3 '18 at 10:19
Anurag Vishal RAnurag Vishal R
1
1
add a comment |
add a comment |
I had the same issue on boot after upgrading Kubuntu 16.04 to 18.04. I also saw error messages about lightdm failing to start. Here's what I did to fix the issue.
In the grub bootloader, edited the boot entry and removed the following variables from the linux boot command:
quiet splash $vt_handoff
Then press F10 to boot. It was now able to boot to a tty1 console login.
I first tried to install the latest nvidia drivers for my graphics card. This didn't help. I got the same error on reboot. (But keeping this here in case it was important https://linuxconfig.org/how-to-install-the-nvidia-drivers-on-ubuntu-18-04-bionic-beaver-linux )
Next I changed the display manager.
sudo dpkg-reconfigure lightdm
I changed the display manager to sddm (the only other option). Then I started sddm and the graphical interface started up.
sudo service sddm start
So it appears it was an issue with lightdm.
answered Jan 2 at 19:20
jdramerjdramer
1713
add a comment |
I had the same issue on boot after upgrading Kubuntu 16.04 to 18.04. I also saw error messages about lightdm failing to start. Here's what I did to fix the issue.
In the grub bootloader, edited the boot entry and removed the following variables from the linux boot command:
quiet splash $vt_handoff
Then press F10 to boot. It was now able to boot to a tty1 console login.
I first tried to install the latest nvidia drivers for my graphics card. This didn't help. I got the same error on reboot. (But keeping this here in case it was important https://linuxconfig.org/how-to-install-the-nvidia-drivers-on-ubuntu-18-04-bionic-beaver-linux )
Next I changed the display manager.
sudo dpkg-reconfigure lightdm
I changed the display manager to sddm (the only other option). Then I started sddm and the graphical interface started up.
sudo service sddm start
So it appears it was an issue with lightdm.
answered Jan 2 at 19:20
jdramerjdramer
1713
add a comment |
I had the same issue on boot after upgrading Kubuntu 16.04 to 18.04. I also saw error messages about lightdm failing to start. Here's what I did to fix the issue.
In the grub bootloader, edited the boot entry and removed the following variables from the linux boot command:
quiet splash $vt_handoff
Then press F10 to boot. It was now able to boot to a tty1 console login.
I first tried to install the latest nvidia drivers for my graphics card. This didn't help. I got the same error on reboot. (But keeping this here in case it was important https://linuxconfig.org/how-to-install-the-nvidia-drivers-on-ubuntu-18-04-bionic-beaver-linux )
Next I changed the display manager.
sudo dpkg-reconfigure lightdm
I changed the display manager to sddm (the only other option). Then I started sddm and the graphical interface started up.
sudo service sddm start
So it appears it was an issue with lightdm.
answered Jan 2 at 19:20
jdramerjdramer
1713
I had the same issue on boot after upgrading Kubuntu 16.04 to 18.04. I also saw error messages about lightdm failing to start. Here's what I did to fix the issue.
In the grub bootloader, edited the boot entry and removed the following variables from the linux boot command:
quiet splash $vt_handoff
Then press F10 to boot. It was now able to boot to a tty1 console login.
I first tried to install the latest nvidia drivers for my graphics card. This didn't help. I got the same error on reboot. (But keeping this here in case it was important https://linuxconfig.org/how-to-install-the-nvidia-drivers-on-ubuntu-18-04-bionic-beaver-linux )
Next I changed the display manager.
sudo dpkg-reconfigure lightdm
I changed the display manager to sddm (the only other option). Then I started sddm and the graphical interface started up.
sudo service sddm start
So it appears it was an issue with lightdm.
answered Jan 2 at 19:20
jdramerjdramer
1713
answered Jan 2 at 19:20
jdramerjdramer
1713
answered Jan 2 at 19:20
jdramerjdramer
1713
answered Jan 2 at 19:20
jdramerjdramer
1713
1713
add a comment |
add a comment |
Had the same problem because the disks were full, I had to free up space
If you think this might be the issue you can select the advanced boot in GRUB menu and use the terminal option to remove some of the files then restart and try login again.
answered 19 hours ago
Haggui AyoubHaggui Ayoub
1
New contributor
Haggui Ayoub is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Had the same problem because the disks were full, I had to free up space
If you think this might be the issue you can select the advanced boot in GRUB menu and use the terminal option to remove some of the files then restart and try login again.
answered 19 hours ago
Haggui AyoubHaggui Ayoub
1
New contributor
Haggui Ayoub is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
Had the same problem because the disks were full, I had to free up space
If you think this might be the issue you can select the advanced boot in GRUB menu and use the terminal option to remove some of the files then restart and try login again.
answered 19 hours ago
Haggui AyoubHaggui Ayoub
1
New contributor
Haggui Ayoub is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Had the same problem because the disks were full, I had to free up space
If you think this might be the issue you can select the advanced boot in GRUB menu and use the terminal option to remove some of the files then restart and try login again.
answered 19 hours ago
Haggui AyoubHaggui Ayoub
1
New contributor
Haggui Ayoub is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 19 hours ago
Haggui AyoubHaggui Ayoub
1
New contributor
Haggui Ayoub is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 19 hours ago
Haggui AyoubHaggui Ayoub
1
answered 19 hours ago
Haggui AyoubHaggui Ayoub
1
1
New contributor
Haggui Ayoub is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Haggui Ayoub is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Haggui Ayoub is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1033613%2fstart-job-is-running-for-hold-until-boot-process-finishes-up-18-04%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
Did you found a solution for this ?
– Charles-Antoine Fournel
May 21 '18 at 16:20
Have you tried one of these solutions: askubuntu.com/questions/760825/… or If it is a bug and may now be fixed, try to update the system
sudo apt update && sudo apt upgrade– d a i s y
18 hours ago
The fact that CTRL+ALT sequences do not work seem related to the fact that your keyboard also doesn't work in recovery mode, and seems like a hardware problem - try to replace your keyboard or connect it to a different port.
– Guss
18 hours ago