Sfdwhf

Do natural melee weapons (from racial traits) trigger Improved Divine Smite?

Should we avoid writing fiction about historical events without extensive research?

I've given my players a lot of magic items. Is it reasonable for me to give them harder encounters?

Questions of the type "What do you think other people would think?"

Gemara word for QED

Too soon for a plot twist?

Where do you go through passport control when transiting through another Schengen airport on your way out of the Schengen area?

Why do we call complex numbers “numbers” but we don’t consider 2 vectors numbers?

Create chunks from an array

How to make sure I'm assertive enough in contact with subordinates?

Does the US political system, in principle, allow for a no-party system?

Paper published similar to PhD thesis

Dukha vs legitimate need

Rationale to prefer local variables over instance variables?

Custom javascript not working

Why are special aircraft used for the carriers in the United States Navy?

Is every open circuit a capacitor?

Why do phishing e-mails use faked e-mail addresses instead of the real one?

“I had a flat in the centre of town, but I didn’t like living there, so …”

Changing the orders of the words

Computing the volume of a simplex-like object with constraints

Why is there an extra space when I type "ls" on the Desktop?

Was it really inappropriate to write a pull request for the company I interviewed with?

Ultrafilters as a double dual

Screen stuck at the Ubuntu logo

Ubuntu 17.04 doesn't bootUbuntu 12.04 reboots during startupUbuntu 12.04 wont start after manual restartUpgrading from 12.04 to 12.10 resulted in boot process sticking with “The disk drive for /dev/mapper/cryptswap1 is not ready or present”ubuntu shuts down for no reasonXubuntu 14.04: Empty desktop on bootUbuntu 14.04 boot hangs at logo after updatingLogin screen and recovery mode freeze in Ubuntu 16.04“watchdog: BUG: soft lockup CPU stuck” error and black screen on loginBluetooth won't work anymore (plug in dongle to use bluetooth)Ubuntu MATE - after update + removing outdated software, can’t get to login screen

0

1

I've using Ubuntu 17.10 for a few months. It has been working great until today. When I switch on my computer, the usual Ubuntu logo appears and I wait a few minutes but nothing happens. I've waited for half an hour and nothing happened. I restarted several times but the problem persists. I don't know what I'm supposed to do.

boot login 17.10

share|improve this question

asked Mar 30 '18 at 15:29

Ritchie SudarshanRitchie Sudarshan

112

bumped to the homepage by Community♦ 7 mins ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Can someone please answer. I really need to get my system working. All my work is saved in there. And it's due tomorrow.
  
  – Ritchie Sudarshan
  Mar 30 '18 at 15:53
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I don't know. I think it might be a 2gb graphic card.
  
  – Ritchie Sudarshan
  Mar 30 '18 at 16:05
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I can't. At least not right now. Do you think there might be some other problem?
  
  – Ritchie Sudarshan
  Mar 30 '18 at 16:11
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I really need to get this working right now
  
  – Ritchie Sudarshan
  Mar 30 '18 at 16:13
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Could it be anything else other than that? Is there anything I can do right now?
  
  – Ritchie Sudarshan
  Mar 30 '18 at 16:21
  

  
  
  
  

 | 
show 1 more comment

0

1

I've using Ubuntu 17.10 for a few months. It has been working great until today. When I switch on my computer, the usual Ubuntu logo appears and I wait a few minutes but nothing happens. I've waited for half an hour and nothing happened. I restarted several times but the problem persists. I don't know what I'm supposed to do.

boot login 17.10

share|improve this question

asked Mar 30 '18 at 15:29

Ritchie SudarshanRitchie Sudarshan

112

bumped to the homepage by Community♦ 7 mins ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Can someone please answer. I really need to get my system working. All my work is saved in there. And it's due tomorrow.
  
  – Ritchie Sudarshan
  Mar 30 '18 at 15:53
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I don't know. I think it might be a 2gb graphic card.
  
  – Ritchie Sudarshan
  Mar 30 '18 at 16:05
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I can't. At least not right now. Do you think there might be some other problem?
  
  – Ritchie Sudarshan
  Mar 30 '18 at 16:11
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I really need to get this working right now
  
  – Ritchie Sudarshan
  Mar 30 '18 at 16:13
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Could it be anything else other than that? Is there anything I can do right now?
  
  – Ritchie Sudarshan
  Mar 30 '18 at 16:21
  

  
  
  
  

 | 
show 1 more comment

I've using Ubuntu 17.10 for a few months. It has been working great until today. When I switch on my computer, the usual Ubuntu logo appears and I wait a few minutes but nothing happens. I've waited for half an hour and nothing happened. I restarted several times but the problem persists. I don't know what I'm supposed to do.

boot login 17.10

share|improve this question

asked Mar 30 '18 at 15:29

Ritchie SudarshanRitchie Sudarshan

112

share|improve this question

asked Mar 30 '18 at 15:29

Ritchie SudarshanRitchie Sudarshan

112

share|improve this question

asked Mar 30 '18 at 15:29

Ritchie SudarshanRitchie Sudarshan

112

asked Mar 30 '18 at 15:29

Ritchie SudarshanRitchie Sudarshan

112

asked Mar 30 '18 at 15:29

Ritchie SudarshanRitchie Sudarshan

112

1 Answer
1

active

oldest

votes

0

Check your file system for errors.

To check the file system on your Ubuntu partition...

• boot to the GRUB menu


• choose Advanced Options


• choose Recovery mode


• choose Root access


• at the # prompt, type sudo fsck -f /
  


• repeat the fsck command if there were errors


• type reboot
  

If for some reason you can't do the above...

• boot to a Ubuntu Live DVD/USB


• start gparted and determine which /dev/sdaX is your Ubuntu EXT4 partition


• quit gparted
  


• open a terminal window


• type sudo fsck -f /dev/sdaX # replacing X with the number you found earlier


• repeat the fsck command if there were errors


• type reboot
  

Update #1:

The fsck found and fixed errors on your file system, but the system continues to not boot fully. Other file corruption is possible. Booting to an older kernel works fine.

If you wish to continue to try troubleshooting the non-booting kernel, follow the procedure shown below, otherwise boot to the newest booting kernel, backup your files, and reinstall Ubuntu, then do Software Updates.

• use the first method from my original instructions and boot to the newest kernel (that doesn't fully boot), and get to the # prompt.


• type sudo pico /etc/default/grub and use the arrows keys to navigate to the line that contains "quiet splash" and delete the words quiet and splash so that you're left with "". Remember this line, as you'll need to reinsert those words back later, once the machine boots properly.


• 
  control-o # to save the edit


• 
  control-x # to exit the editor


• 
  sudo update-grub # to update grub


• 
  reboot # to reboot the computer

The machine still won't fully boot, but it'll show you on the screen where it's stopping, along with any error messages. Report back. Edit your original question with any important details, and then send me a comment that starts with @heynnema to alert me.

share|improve this answer

edited Mar 31 '18 at 17:39

answered Mar 31 '18 at 1:14

heynnemaheynnema

20.2k22258

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I tried the above procedure. I went into the recovery mode and did whatever you suggested. It showed some errors and I fixed them. But when I rebooted, the problem is still there. Apart from this, there has been some other development. When I chose "ubuntu, with linux 4.13.0-31-generic" it booted fine and I was able to use my system normally. What does that mean? Is it okay if I keep doing this? If no, then what is the solution?
  
  – Ritchie Sudarshan
  Mar 31 '18 at 6:46
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @RitchieSudarshan there may be some file corruption that fsck won't fix. If booting with "ubuntu, with linux 4.13.0-31-generic" is NOT the most current linux kernel that you have installed, then your last software update may have installed a bad newer kernel that's not booting. You'd have to risk deleting the 3-4 files related to the newer non-booting kernel and try to reapply the software update. If that doesn't work, you may have to backup your important files, wipe the disk, and reinstall Ubuntu. Did you install any dkms drivers on the newest kernel?
  
  – heynnema
  Mar 31 '18 at 13:15
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  I don't know what dkms drivers are. And "Ubuntu, with Linux 4.13.0-31-generic" is not the most recent kernal. But is it okay if I keep using it? If no, then I guess I'll have to reinstall Ubuntu.
  
  – Ritchie Sudarshan
  Mar 31 '18 at 17:11
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @RitchieSudarshan Follow my update in my answer and report back.
  
  – heynnema
  Mar 31 '18 at 17:44
  

  
  
  
  

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
});


}
});

draft saved

draft discarded

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

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1020614%2fscreen-stuck-at-the-ubuntu-logo%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

0

Check your file system for errors.

To check the file system on your Ubuntu partition...

• boot to the GRUB menu


• choose Advanced Options


• choose Recovery mode


• choose Root access


• at the # prompt, type sudo fsck -f /
  


• repeat the fsck command if there were errors


• type reboot
  

If for some reason you can't do the above...

• boot to a Ubuntu Live DVD/USB


• start gparted and determine which /dev/sdaX is your Ubuntu EXT4 partition


• quit gparted
  


• open a terminal window


• type sudo fsck -f /dev/sdaX # replacing X with the number you found earlier


• repeat the fsck command if there were errors


• type reboot
  

Update #1:

The fsck found and fixed errors on your file system, but the system continues to not boot fully. Other file corruption is possible. Booting to an older kernel works fine.

If you wish to continue to try troubleshooting the non-booting kernel, follow the procedure shown below, otherwise boot to the newest booting kernel, backup your files, and reinstall Ubuntu, then do Software Updates.

• use the first method from my original instructions and boot to the newest kernel (that doesn't fully boot), and get to the # prompt.


• type sudo pico /etc/default/grub and use the arrows keys to navigate to the line that contains "quiet splash" and delete the words quiet and splash so that you're left with "". Remember this line, as you'll need to reinsert those words back later, once the machine boots properly.


• 
  control-o # to save the edit


• 
  control-x # to exit the editor


• 
  sudo update-grub # to update grub


• 
  reboot # to reboot the computer

The machine still won't fully boot, but it'll show you on the screen where it's stopping, along with any error messages. Report back. Edit your original question with any important details, and then send me a comment that starts with @heynnema to alert me.

share|improve this answer

edited Mar 31 '18 at 17:39

answered Mar 31 '18 at 1:14

heynnemaheynnema

20.2k22258

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I tried the above procedure. I went into the recovery mode and did whatever you suggested. It showed some errors and I fixed them. But when I rebooted, the problem is still there. Apart from this, there has been some other development. When I chose "ubuntu, with linux 4.13.0-31-generic" it booted fine and I was able to use my system normally. What does that mean? Is it okay if I keep doing this? If no, then what is the solution?
  
  – Ritchie Sudarshan
  Mar 31 '18 at 6:46
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @RitchieSudarshan there may be some file corruption that fsck won't fix. If booting with "ubuntu, with linux 4.13.0-31-generic" is NOT the most current linux kernel that you have installed, then your last software update may have installed a bad newer kernel that's not booting. You'd have to risk deleting the 3-4 files related to the newer non-booting kernel and try to reapply the software update. If that doesn't work, you may have to backup your important files, wipe the disk, and reinstall Ubuntu. Did you install any dkms drivers on the newest kernel?
  
  – heynnema
  Mar 31 '18 at 13:15
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  I don't know what dkms drivers are. And "Ubuntu, with Linux 4.13.0-31-generic" is not the most recent kernal. But is it okay if I keep using it? If no, then I guess I'll have to reinstall Ubuntu.
  
  – Ritchie Sudarshan
  Mar 31 '18 at 17:11
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @RitchieSudarshan Follow my update in my answer and report back.
  
  – heynnema
  Mar 31 '18 at 17:44
  

  
  
  
  

add a comment | 

0

Check your file system for errors.

To check the file system on your Ubuntu partition...

• boot to the GRUB menu


• choose Advanced Options


• choose Recovery mode


• choose Root access


• at the # prompt, type sudo fsck -f /
  


• repeat the fsck command if there were errors


• type reboot
  

If for some reason you can't do the above...

• boot to a Ubuntu Live DVD/USB


• start gparted and determine which /dev/sdaX is your Ubuntu EXT4 partition


• quit gparted
  


• open a terminal window


• type sudo fsck -f /dev/sdaX # replacing X with the number you found earlier


• repeat the fsck command if there were errors


• type reboot
  

Update #1:

The fsck found and fixed errors on your file system, but the system continues to not boot fully. Other file corruption is possible. Booting to an older kernel works fine.

If you wish to continue to try troubleshooting the non-booting kernel, follow the procedure shown below, otherwise boot to the newest booting kernel, backup your files, and reinstall Ubuntu, then do Software Updates.

• use the first method from my original instructions and boot to the newest kernel (that doesn't fully boot), and get to the # prompt.


• type sudo pico /etc/default/grub and use the arrows keys to navigate to the line that contains "quiet splash" and delete the words quiet and splash so that you're left with "". Remember this line, as you'll need to reinsert those words back later, once the machine boots properly.


• 
  control-o # to save the edit


• 
  control-x # to exit the editor


• 
  sudo update-grub # to update grub


• 
  reboot # to reboot the computer

The machine still won't fully boot, but it'll show you on the screen where it's stopping, along with any error messages. Report back. Edit your original question with any important details, and then send me a comment that starts with @heynnema to alert me.

share|improve this answer

edited Mar 31 '18 at 17:39

answered Mar 31 '18 at 1:14

heynnemaheynnema

20.2k22258

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I tried the above procedure. I went into the recovery mode and did whatever you suggested. It showed some errors and I fixed them. But when I rebooted, the problem is still there. Apart from this, there has been some other development. When I chose "ubuntu, with linux 4.13.0-31-generic" it booted fine and I was able to use my system normally. What does that mean? Is it okay if I keep doing this? If no, then what is the solution?
  
  – Ritchie Sudarshan
  Mar 31 '18 at 6:46
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @RitchieSudarshan there may be some file corruption that fsck won't fix. If booting with "ubuntu, with linux 4.13.0-31-generic" is NOT the most current linux kernel that you have installed, then your last software update may have installed a bad newer kernel that's not booting. You'd have to risk deleting the 3-4 files related to the newer non-booting kernel and try to reapply the software update. If that doesn't work, you may have to backup your important files, wipe the disk, and reinstall Ubuntu. Did you install any dkms drivers on the newest kernel?
  
  – heynnema
  Mar 31 '18 at 13:15
  
  
  

  
  
  
  


• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  I don't know what dkms drivers are. And "Ubuntu, with Linux 4.13.0-31-generic" is not the most recent kernal. But is it okay if I keep using it? If no, then I guess I'll have to reinstall Ubuntu.
  
  – Ritchie Sudarshan
  Mar 31 '18 at 17:11
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @RitchieSudarshan Follow my update in my answer and report back.
  
  – heynnema
  Mar 31 '18 at 17:44
  

  
  
  
  

add a comment | 

Check your file system for errors.

To check the file system on your Ubuntu partition...

• boot to the GRUB menu


• choose Advanced Options


• choose Recovery mode


• choose Root access


• at the # prompt, type sudo fsck -f /
  


• repeat the fsck command if there were errors


• type reboot
  

If for some reason you can't do the above...

• boot to a Ubuntu Live DVD/USB


• start gparted and determine which /dev/sdaX is your Ubuntu EXT4 partition


• quit gparted
  


• open a terminal window


• type sudo fsck -f /dev/sdaX # replacing X with the number you found earlier


• repeat the fsck command if there were errors


• type reboot
  

Update #1:

The fsck found and fixed errors on your file system, but the system continues to not boot fully. Other file corruption is possible. Booting to an older kernel works fine.

If you wish to continue to try troubleshooting the non-booting kernel, follow the procedure shown below, otherwise boot to the newest booting kernel, backup your files, and reinstall Ubuntu, then do Software Updates.

• use the first method from my original instructions and boot to the newest kernel (that doesn't fully boot), and get to the # prompt.


• type sudo pico /etc/default/grub and use the arrows keys to navigate to the line that contains "quiet splash" and delete the words quiet and splash so that you're left with "". Remember this line, as you'll need to reinsert those words back later, once the machine boots properly.


• 
  control-o # to save the edit


• 
  control-x # to exit the editor


• 
  sudo update-grub # to update grub


• 
  reboot # to reboot the computer

The machine still won't fully boot, but it'll show you on the screen where it's stopping, along with any error messages. Report back. Edit your original question with any important details, and then send me a comment that starts with @heynnema to alert me.

share|improve this answer

edited Mar 31 '18 at 17:39

answered Mar 31 '18 at 1:14

heynnemaheynnema

20.2k22258

share|improve this answer

edited Mar 31 '18 at 17:39

answered Mar 31 '18 at 1:14

heynnemaheynnema

20.2k22258

answered Mar 31 '18 at 1:14

heynnemaheynnema

20.2k22258

answered Mar 31 '18 at 1:14

heynnemaheynnema

20.2k22258