Ubuntu 18.04 LTS bootup issues

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
1
down vote

favorite












I've been running every flavour of Ubuntu since version 12.04 LTS, the latest was 17.10. However since Ubuntu 18.04 is now available I did a full clean install of the OS. However to my surprise after the OS fully installed and restarts it get stuck on the Ubuntu bootup screen 3rd dot. However if I run the OS in a live environment it loads up without any problems. The system I'm installing this on is a Dell OptiPlex 755 with 8GB ram, kindly assist.



While trying to find a fix for the above, i came across to the same issue:
Ubuntu 18.04 64-bit hangs during boot



Below I added some more details, maybe it can help find a resolution quicker :-)



enter image description here



fstab
system
lshw







share|improve this question






















  • Wow first time in Ask Ubuntu since 12.04 (judging from rep 1) +1 and welcome aboard!
    – WinEunuuchs2Unix
    May 13 at 18:31










  • I use the os mainly to browse, libre office, skype and TeamViewer why should i have any problems :P also when i had any problems in the past a simple google search managed to fix them :-) Thanks for the warm welcome.
    – FoxJr
    May 14 at 11:02










  • I suggest you temporarily disable the splash screen so you can see what's going on. After this you will see a ton of messages scrolling up during boot. The last one displayed can often be informative :) instructions here ubuntuincident.wordpress.com/2015/03/12/…
    – Organic Marble
    May 19 at 21:38














up vote
1
down vote

favorite












I've been running every flavour of Ubuntu since version 12.04 LTS, the latest was 17.10. However since Ubuntu 18.04 is now available I did a full clean install of the OS. However to my surprise after the OS fully installed and restarts it get stuck on the Ubuntu bootup screen 3rd dot. However if I run the OS in a live environment it loads up without any problems. The system I'm installing this on is a Dell OptiPlex 755 with 8GB ram, kindly assist.



While trying to find a fix for the above, i came across to the same issue:
Ubuntu 18.04 64-bit hangs during boot



Below I added some more details, maybe it can help find a resolution quicker :-)



enter image description here



fstab
system
lshw







share|improve this question






















  • Wow first time in Ask Ubuntu since 12.04 (judging from rep 1) +1 and welcome aboard!
    – WinEunuuchs2Unix
    May 13 at 18:31










  • I use the os mainly to browse, libre office, skype and TeamViewer why should i have any problems :P also when i had any problems in the past a simple google search managed to fix them :-) Thanks for the warm welcome.
    – FoxJr
    May 14 at 11:02










  • I suggest you temporarily disable the splash screen so you can see what's going on. After this you will see a ton of messages scrolling up during boot. The last one displayed can often be informative :) instructions here ubuntuincident.wordpress.com/2015/03/12/…
    – Organic Marble
    May 19 at 21:38












up vote
1
down vote

favorite









up vote
1
down vote

favorite











I've been running every flavour of Ubuntu since version 12.04 LTS, the latest was 17.10. However since Ubuntu 18.04 is now available I did a full clean install of the OS. However to my surprise after the OS fully installed and restarts it get stuck on the Ubuntu bootup screen 3rd dot. However if I run the OS in a live environment it loads up without any problems. The system I'm installing this on is a Dell OptiPlex 755 with 8GB ram, kindly assist.



While trying to find a fix for the above, i came across to the same issue:
Ubuntu 18.04 64-bit hangs during boot



Below I added some more details, maybe it can help find a resolution quicker :-)



enter image description here



fstab
system
lshw







share|improve this question














I've been running every flavour of Ubuntu since version 12.04 LTS, the latest was 17.10. However since Ubuntu 18.04 is now available I did a full clean install of the OS. However to my surprise after the OS fully installed and restarts it get stuck on the Ubuntu bootup screen 3rd dot. However if I run the OS in a live environment it loads up without any problems. The system I'm installing this on is a Dell OptiPlex 755 with 8GB ram, kindly assist.



While trying to find a fix for the above, i came across to the same issue:
Ubuntu 18.04 64-bit hangs during boot



Below I added some more details, maybe it can help find a resolution quicker :-)



enter image description here



fstab
system
lshw









share|improve this question













share|improve this question




share|improve this question








edited May 19 at 21:36

























asked May 13 at 16:36









FoxJr

62




62











  • Wow first time in Ask Ubuntu since 12.04 (judging from rep 1) +1 and welcome aboard!
    – WinEunuuchs2Unix
    May 13 at 18:31










  • I use the os mainly to browse, libre office, skype and TeamViewer why should i have any problems :P also when i had any problems in the past a simple google search managed to fix them :-) Thanks for the warm welcome.
    – FoxJr
    May 14 at 11:02










  • I suggest you temporarily disable the splash screen so you can see what's going on. After this you will see a ton of messages scrolling up during boot. The last one displayed can often be informative :) instructions here ubuntuincident.wordpress.com/2015/03/12/…
    – Organic Marble
    May 19 at 21:38
















  • Wow first time in Ask Ubuntu since 12.04 (judging from rep 1) +1 and welcome aboard!
    – WinEunuuchs2Unix
    May 13 at 18:31










  • I use the os mainly to browse, libre office, skype and TeamViewer why should i have any problems :P also when i had any problems in the past a simple google search managed to fix them :-) Thanks for the warm welcome.
    – FoxJr
    May 14 at 11:02










  • I suggest you temporarily disable the splash screen so you can see what's going on. After this you will see a ton of messages scrolling up during boot. The last one displayed can often be informative :) instructions here ubuntuincident.wordpress.com/2015/03/12/…
    – Organic Marble
    May 19 at 21:38















Wow first time in Ask Ubuntu since 12.04 (judging from rep 1) +1 and welcome aboard!
– WinEunuuchs2Unix
May 13 at 18:31




Wow first time in Ask Ubuntu since 12.04 (judging from rep 1) +1 and welcome aboard!
– WinEunuuchs2Unix
May 13 at 18:31












I use the os mainly to browse, libre office, skype and TeamViewer why should i have any problems :P also when i had any problems in the past a simple google search managed to fix them :-) Thanks for the warm welcome.
– FoxJr
May 14 at 11:02




I use the os mainly to browse, libre office, skype and TeamViewer why should i have any problems :P also when i had any problems in the past a simple google search managed to fix them :-) Thanks for the warm welcome.
– FoxJr
May 14 at 11:02












I suggest you temporarily disable the splash screen so you can see what's going on. After this you will see a ton of messages scrolling up during boot. The last one displayed can often be informative :) instructions here ubuntuincident.wordpress.com/2015/03/12/…
– Organic Marble
May 19 at 21:38




I suggest you temporarily disable the splash screen so you can see what's going on. After this you will see a ton of messages scrolling up during boot. The last one displayed can often be informative :) instructions here ubuntuincident.wordpress.com/2015/03/12/…
– Organic Marble
May 19 at 21:38










2 Answers
2






active

oldest

votes

















up vote
0
down vote













I had a similar problem on my mother's laptop. I'm guessing that you have a separate /home partition and want to use that with the clean install, right? If so, it's probably due to your user directory not having recognisable file permissions for the new system. If so, do this:



Clean install but instead of setting your new user as the original username, choose a (temporary) new one instead. This will allow you to boot into your desktop. Once you've done that, use the 'Users' app to create a new user with your original username and give it auto login. Then do:



cd /home
sudo chown -R youruser.youruser youruser


(swap youruser for the name you want) This will set your permissions properly. Now you can reboot into your proper user with all your settings, data etc.






share|improve this answer




















  • I will test this, however, I did a clean install with default settings meaning erase the previous installation and re-install from scratch, still, the issue persisted.
    – FoxJr
    May 14 at 11:04










  • HI Jim, tried suggested fix to no avail, any other ideas?
    – FoxJr
    May 19 at 19:28

















up vote
0
down vote













How about this: it could be to do with your display, so try setting nomodeset from the Grub screen. When you see Grub, press 'e' to edit the parameters, and add nomodeset to the Linux line. For example, if you see 'quiet splash' change it to 'quiet splash nomodeset' then Ctrl-X to continue booting. If this is successful it means you just have to update your video driver and once you've done that it will boot normally.






share|improve this answer




















  • I doubt its something like this, for the simple reason that when I boot using ubuntu live it works fine.
    – FoxJr
    May 27 at 17:58










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',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1035762%2fubuntu-18-04-lts-bootup-issues%23new-answer', 'question_page');

);

Post as a guest






























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes








up vote
0
down vote













I had a similar problem on my mother's laptop. I'm guessing that you have a separate /home partition and want to use that with the clean install, right? If so, it's probably due to your user directory not having recognisable file permissions for the new system. If so, do this:



Clean install but instead of setting your new user as the original username, choose a (temporary) new one instead. This will allow you to boot into your desktop. Once you've done that, use the 'Users' app to create a new user with your original username and give it auto login. Then do:



cd /home
sudo chown -R youruser.youruser youruser


(swap youruser for the name you want) This will set your permissions properly. Now you can reboot into your proper user with all your settings, data etc.






share|improve this answer




















  • I will test this, however, I did a clean install with default settings meaning erase the previous installation and re-install from scratch, still, the issue persisted.
    – FoxJr
    May 14 at 11:04










  • HI Jim, tried suggested fix to no avail, any other ideas?
    – FoxJr
    May 19 at 19:28














up vote
0
down vote













I had a similar problem on my mother's laptop. I'm guessing that you have a separate /home partition and want to use that with the clean install, right? If so, it's probably due to your user directory not having recognisable file permissions for the new system. If so, do this:



Clean install but instead of setting your new user as the original username, choose a (temporary) new one instead. This will allow you to boot into your desktop. Once you've done that, use the 'Users' app to create a new user with your original username and give it auto login. Then do:



cd /home
sudo chown -R youruser.youruser youruser


(swap youruser for the name you want) This will set your permissions properly. Now you can reboot into your proper user with all your settings, data etc.






share|improve this answer




















  • I will test this, however, I did a clean install with default settings meaning erase the previous installation and re-install from scratch, still, the issue persisted.
    – FoxJr
    May 14 at 11:04










  • HI Jim, tried suggested fix to no avail, any other ideas?
    – FoxJr
    May 19 at 19:28












up vote
0
down vote










up vote
0
down vote









I had a similar problem on my mother's laptop. I'm guessing that you have a separate /home partition and want to use that with the clean install, right? If so, it's probably due to your user directory not having recognisable file permissions for the new system. If so, do this:



Clean install but instead of setting your new user as the original username, choose a (temporary) new one instead. This will allow you to boot into your desktop. Once you've done that, use the 'Users' app to create a new user with your original username and give it auto login. Then do:



cd /home
sudo chown -R youruser.youruser youruser


(swap youruser for the name you want) This will set your permissions properly. Now you can reboot into your proper user with all your settings, data etc.






share|improve this answer












I had a similar problem on my mother's laptop. I'm guessing that you have a separate /home partition and want to use that with the clean install, right? If so, it's probably due to your user directory not having recognisable file permissions for the new system. If so, do this:



Clean install but instead of setting your new user as the original username, choose a (temporary) new one instead. This will allow you to boot into your desktop. Once you've done that, use the 'Users' app to create a new user with your original username and give it auto login. Then do:



cd /home
sudo chown -R youruser.youruser youruser


(swap youruser for the name you want) This will set your permissions properly. Now you can reboot into your proper user with all your settings, data etc.







share|improve this answer












share|improve this answer



share|improve this answer










answered May 13 at 17:07









JimDeadlock

1528




1528











  • I will test this, however, I did a clean install with default settings meaning erase the previous installation and re-install from scratch, still, the issue persisted.
    – FoxJr
    May 14 at 11:04










  • HI Jim, tried suggested fix to no avail, any other ideas?
    – FoxJr
    May 19 at 19:28
















  • I will test this, however, I did a clean install with default settings meaning erase the previous installation and re-install from scratch, still, the issue persisted.
    – FoxJr
    May 14 at 11:04










  • HI Jim, tried suggested fix to no avail, any other ideas?
    – FoxJr
    May 19 at 19:28















I will test this, however, I did a clean install with default settings meaning erase the previous installation and re-install from scratch, still, the issue persisted.
– FoxJr
May 14 at 11:04




I will test this, however, I did a clean install with default settings meaning erase the previous installation and re-install from scratch, still, the issue persisted.
– FoxJr
May 14 at 11:04












HI Jim, tried suggested fix to no avail, any other ideas?
– FoxJr
May 19 at 19:28




HI Jim, tried suggested fix to no avail, any other ideas?
– FoxJr
May 19 at 19:28












up vote
0
down vote













How about this: it could be to do with your display, so try setting nomodeset from the Grub screen. When you see Grub, press 'e' to edit the parameters, and add nomodeset to the Linux line. For example, if you see 'quiet splash' change it to 'quiet splash nomodeset' then Ctrl-X to continue booting. If this is successful it means you just have to update your video driver and once you've done that it will boot normally.






share|improve this answer




















  • I doubt its something like this, for the simple reason that when I boot using ubuntu live it works fine.
    – FoxJr
    May 27 at 17:58














up vote
0
down vote













How about this: it could be to do with your display, so try setting nomodeset from the Grub screen. When you see Grub, press 'e' to edit the parameters, and add nomodeset to the Linux line. For example, if you see 'quiet splash' change it to 'quiet splash nomodeset' then Ctrl-X to continue booting. If this is successful it means you just have to update your video driver and once you've done that it will boot normally.






share|improve this answer




















  • I doubt its something like this, for the simple reason that when I boot using ubuntu live it works fine.
    – FoxJr
    May 27 at 17:58












up vote
0
down vote










up vote
0
down vote









How about this: it could be to do with your display, so try setting nomodeset from the Grub screen. When you see Grub, press 'e' to edit the parameters, and add nomodeset to the Linux line. For example, if you see 'quiet splash' change it to 'quiet splash nomodeset' then Ctrl-X to continue booting. If this is successful it means you just have to update your video driver and once you've done that it will boot normally.






share|improve this answer












How about this: it could be to do with your display, so try setting nomodeset from the Grub screen. When you see Grub, press 'e' to edit the parameters, and add nomodeset to the Linux line. For example, if you see 'quiet splash' change it to 'quiet splash nomodeset' then Ctrl-X to continue booting. If this is successful it means you just have to update your video driver and once you've done that it will boot normally.







share|improve this answer












share|improve this answer



share|improve this answer










answered May 20 at 23:26









JimDeadlock

1528




1528











  • I doubt its something like this, for the simple reason that when I boot using ubuntu live it works fine.
    – FoxJr
    May 27 at 17:58
















  • I doubt its something like this, for the simple reason that when I boot using ubuntu live it works fine.
    – FoxJr
    May 27 at 17:58















I doubt its something like this, for the simple reason that when I boot using ubuntu live it works fine.
– FoxJr
May 27 at 17:58




I doubt its something like this, for the simple reason that when I boot using ubuntu live it works fine.
– FoxJr
May 27 at 17:58












 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1035762%2fubuntu-18-04-lts-bootup-issues%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

pylint3 and pip3 broken

Missing snmpget and snmpwalk

How to enroll fingerprints to Ubuntu 17.10 with VFS491