Bsrgvty

How fast are we moving relative to the CMB?

Found a minor bug, affecting 1% of users. What should QA do?

Is there any problem with students seeing faculty naked in university gym?

What makes a character irredeemable?

Was Smaug sealed inside the Lonely Mountain?

In search of a pedagogically simple example of asymmetric encryption routine?

Why do we not always use the closed testing principle for multiple comparisons?

How Concerning Is This X-CU-modified: FAKECU Text Attack?

What’s the BrE for “shotgun wedding”?

As an interviewer, how to conduct interviews with candidates you already know will be rejected?

Where does the image of a data connector as a sharp metal spike originate from?

What does a textbook look like while you are writing it?

How dangerous are my worn rims?

Bothered by watching coworkers slacking off

Young adult short story book with one story where a woman finds a walrus suit and becomes a walrus

Substitution failure with `std::function` and previously deduced template parameter - why?

Is "weekend warrior" derogatory?

Is there any printer at Taiwan Taoyuan International Airport (TPE) that airline passengers can use?

TIKZ Macro to draw hundredth of a quare

The answer is the same (tricky puzzle!)

Did the Humans find out about Gaius Baltar's role in the sabotage of the fleet?

How to explain that the sums of numerators over sums of denominators isn't the same as the mean of ratios?

Can Fabled Passage generate two mana with Amulet of Vigor?

Is American Sign Language phonetic?

Computer doesn't boot, displays Read Error after splash screen

Ubuntu 14.04 is not booting normaly after a manual hard bootWindows 7 doesn't boot after Ubuntu installMacbook Air 4,2: “Boot error” with 12.04 live USBBlack Screen on Macbook Pro 6,2 After Installing 12.04LTS - Tried Everything AlreadyBlack Screen, blinking cursorBoot problem after installing Ubuntu 12.04.3 alongside Windows 8 - only get to grub promptubuntu 14.04 install doesn't boot but but displays read errorProblems with grub finding windows. Windows 7 / Ubuntu 14.04

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty
margin-bottom:0;

0

While rebooting my Linux box today, I get a:

Read Error after the splash screen

And it doesn't boot. I think I have 14.04, on a recently upgraded 32-proc 64Gb machine. I've gone into the BIOS, and have reordered the boot drives; doing that just leads to a blinking cursor. I have 4 HDs, only the first is boot drive. I don't think any other HD is loaded to function as a boot drive.

Occasionally, it comes up with grub rescue> but I don't see what to do. If I type ls, I get the list of hd's I expect and I can see some files doing ls (hd0,msdos)/ though the list seems incomplete.

boot grub2

share|improve this question

edited Apr 16 at 14:58

Philippe Delteil

1,11411 gold badge1111 silver badges2323 bronze badges

asked Apr 16 at 14:49

john Van Driejohn Van Drie

322 bronze badges

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Lets test the safest way first... boot to a Ubuntu Live DVD/USB. Start the Disks application, select your boot disk, go to the "hamburger" icon and select SMART Data & Tests, screenshot the Data and post it to imgur.com for me. Then run the SMART tests. See my answer for how to run fsck. Report back and we'll do further tests. Start comments to me with @heynnema or I may miss them.
  
  – heynnema
  Apr 16 at 15:01
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  That sounds like a disk error - can you boot from a live USB and execute fsck on the disks? Please refer to https://askubuntu.com/a/642789/283721
  
  – Charles Green
  Apr 16 at 15:02
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @CharlesGreen please see my partial answer for a more concise way to fsck.
  
  – heynnema
  Apr 16 at 15:06
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @heynnema - Thanks! I had found the other answer just a couple of days ago. I seem to have seen several questions that related to disk errors recently. Do you mind if I expand upon your answer a little to include checking other partitions, such as a separate /home partition?
  
  – Charles Green
  Apr 16 at 15:10
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @CharlesGreen help yourself :-) You may wish to edit the 17.10 fsck paragraph also.
  
  – heynnema
  Apr 16 at 15:39
  
  

  
  
  
  

 | 
show 5 more comments

0

While rebooting my Linux box today, I get a:

Read Error after the splash screen

And it doesn't boot. I think I have 14.04, on a recently upgraded 32-proc 64Gb machine. I've gone into the BIOS, and have reordered the boot drives; doing that just leads to a blinking cursor. I have 4 HDs, only the first is boot drive. I don't think any other HD is loaded to function as a boot drive.

Occasionally, it comes up with grub rescue> but I don't see what to do. If I type ls, I get the list of hd's I expect and I can see some files doing ls (hd0,msdos)/ though the list seems incomplete.

boot grub2

share|improve this question

edited Apr 16 at 14:58

Philippe Delteil

1,11411 gold badge1111 silver badges2323 bronze badges

asked Apr 16 at 14:49

john Van Driejohn Van Drie

322 bronze badges

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Lets test the safest way first... boot to a Ubuntu Live DVD/USB. Start the Disks application, select your boot disk, go to the "hamburger" icon and select SMART Data & Tests, screenshot the Data and post it to imgur.com for me. Then run the SMART tests. See my answer for how to run fsck. Report back and we'll do further tests. Start comments to me with @heynnema or I may miss them.
  
  – heynnema
  Apr 16 at 15:01
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  That sounds like a disk error - can you boot from a live USB and execute fsck on the disks? Please refer to https://askubuntu.com/a/642789/283721
  
  – Charles Green
  Apr 16 at 15:02
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @CharlesGreen please see my partial answer for a more concise way to fsck.
  
  – heynnema
  Apr 16 at 15:06
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @heynnema - Thanks! I had found the other answer just a couple of days ago. I seem to have seen several questions that related to disk errors recently. Do you mind if I expand upon your answer a little to include checking other partitions, such as a separate /home partition?
  
  – Charles Green
  Apr 16 at 15:10
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @CharlesGreen help yourself :-) You may wish to edit the 17.10 fsck paragraph also.
  
  – heynnema
  Apr 16 at 15:39
  
  

  
  
  
  

 | 
show 5 more comments

While rebooting my Linux box today, I get a:

Read Error after the splash screen

And it doesn't boot. I think I have 14.04, on a recently upgraded 32-proc 64Gb machine. I've gone into the BIOS, and have reordered the boot drives; doing that just leads to a blinking cursor. I have 4 HDs, only the first is boot drive. I don't think any other HD is loaded to function as a boot drive.

Occasionally, it comes up with grub rescue> but I don't see what to do. If I type ls, I get the list of hd's I expect and I can see some files doing ls (hd0,msdos)/ though the list seems incomplete.

boot grub2

share|improve this question

edited Apr 16 at 14:58

Philippe Delteil

1,11411 gold badge1111 silver badges2323 bronze badges

asked Apr 16 at 14:49

john Van Driejohn Van Drie

322 bronze badges

share|improve this question

edited Apr 16 at 14:58

Philippe Delteil

1,11411 gold badge1111 silver badges2323 bronze badges

asked Apr 16 at 14:49

john Van Driejohn Van Drie

322 bronze badges

share|improve this question

edited Apr 16 at 14:58

Philippe Delteil

1,11411 gold badge1111 silver badges2323 bronze badges

asked Apr 16 at 14:49

john Van Driejohn Van Drie

322 bronze badges

edited Apr 16 at 14:58

Philippe Delteil

1,11411 gold badge1111 silver badges2323 bronze badges

edited Apr 16 at 14:58

Philippe Delteil

1,11411 gold badge1111 silver badges2323 bronze badges

asked Apr 16 at 14:49

john Van Driejohn Van Drie

322 bronze badges

asked Apr 16 at 14:49

john Van Driejohn Van Drie

322 bronze badges

1 Answer
1

active

oldest

votes

1

Lets first check your file system for errors.

For 17.10 or older...

• 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
  
  
  • If you have your /home directories on a separate partition, run sudo fsck -f /home as well
  
  


• type reboot
  

For 18.04 or newer...

• boot to a Ubuntu Live DVD/USB


• open a terminal window


• type sudo fdisk -l
  


• identify the /dev/XXXX device name for your "Linux Filesystem"


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


• repeat the fsck command if there were errors
  
  
  • If you have separate partitions for your /home directory, repeat this using the appropriate /dev/xxxx
    
  
  


• type reboot
  

Update #1:

The HDD is getting ECC correctable read errors, and failing fsck.

Update #2:

Data is being recovered from the drive. The drive will be replaced with a SSD.

share|improve this answer

edited Apr 16 at 19:08

answered Apr 16 at 15:03

heynnemaheynnema

27k33 gold badges2828 silver badges7272 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I'm preparing a Ubuntu USB right now. In the past, I'd seen the GUI for the GRUB menu, but I'm not seeing that now. Instead I get a cmd line grub rescue> which doesn't appear to have disk-checking option. I'll let you know in 30 min or so how the Ubuntu USB works, I'm creating an 18.04-2 ISO
  
  – john Van Drie
  Apr 16 at 15:36
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @johnVanDrie Do the SMART stuff first, then the fsck.
  
  – heynnema
  Apr 16 at 15:41
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  The SMART data shows all HD's: overall assessment is OK. Would the simplest thing be to install Ubuntu from the USB to one of the other HD's, and boot from there. Worry about the bad disk later/
  
  – john Van Drie
  Apr 16 at 16:29
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @johnVanDrie No. Let finish troubleshooting first. Even though the SMART Data says OK, it may not be. That's why I want to look at it. Can you post the screenshot to imgur.com for me? Then do the fsck. Then we may look at syslog for more data.
  
  – heynnema
  Apr 16 at 16:36
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  OK - thanks so much. While I try to get this s-shot, I did notice I'd overlooked the boot drive. When trying to mount in the Disk Utility tool, I get the ff. error: error mounting /dev/sdf1 at /media/ubuntu.... wrong fs type, bad option, bad superblock on /dev/sdf1, misssing codepage or helper program, or other err (udisks-error-quark, 0). It now says SELF-TEST FAILED.
  
  – john Van Drie
  Apr 16 at 16:51
  
  

  
  
  
  

 | 
show 12 more comments

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/4.0/"u003ecc by-sa 4.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%2f1134391%2fcomputer-doesnt-boot-displays-read-error-after-splash-screen%23new-answer', 'question_page');

);

Post as a guest

Name

Email

Required, but never shown

1

Lets first check your file system for errors.

For 17.10 or older...

• 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
  
  
  • If you have your /home directories on a separate partition, run sudo fsck -f /home as well
  
  


• type reboot
  

For 18.04 or newer...

• boot to a Ubuntu Live DVD/USB


• open a terminal window


• type sudo fdisk -l
  


• identify the /dev/XXXX device name for your "Linux Filesystem"


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


• repeat the fsck command if there were errors
  
  
  • If you have separate partitions for your /home directory, repeat this using the appropriate /dev/xxxx
    
  
  


• type reboot
  

Update #1:

The HDD is getting ECC correctable read errors, and failing fsck.

Update #2:

Data is being recovered from the drive. The drive will be replaced with a SSD.

share|improve this answer

edited Apr 16 at 19:08

answered Apr 16 at 15:03

heynnemaheynnema

27k33 gold badges2828 silver badges7272 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I'm preparing a Ubuntu USB right now. In the past, I'd seen the GUI for the GRUB menu, but I'm not seeing that now. Instead I get a cmd line grub rescue> which doesn't appear to have disk-checking option. I'll let you know in 30 min or so how the Ubuntu USB works, I'm creating an 18.04-2 ISO
  
  – john Van Drie
  Apr 16 at 15:36
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @johnVanDrie Do the SMART stuff first, then the fsck.
  
  – heynnema
  Apr 16 at 15:41
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  The SMART data shows all HD's: overall assessment is OK. Would the simplest thing be to install Ubuntu from the USB to one of the other HD's, and boot from there. Worry about the bad disk later/
  
  – john Van Drie
  Apr 16 at 16:29
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @johnVanDrie No. Let finish troubleshooting first. Even though the SMART Data says OK, it may not be. That's why I want to look at it. Can you post the screenshot to imgur.com for me? Then do the fsck. Then we may look at syslog for more data.
  
  – heynnema
  Apr 16 at 16:36
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  OK - thanks so much. While I try to get this s-shot, I did notice I'd overlooked the boot drive. When trying to mount in the Disk Utility tool, I get the ff. error: error mounting /dev/sdf1 at /media/ubuntu.... wrong fs type, bad option, bad superblock on /dev/sdf1, misssing codepage or helper program, or other err (udisks-error-quark, 0). It now says SELF-TEST FAILED.
  
  – john Van Drie
  Apr 16 at 16:51
  
  

  
  
  
  

 | 
show 12 more comments

1

Lets first check your file system for errors.

For 17.10 or older...

• 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
  
  
  • If you have your /home directories on a separate partition, run sudo fsck -f /home as well
  
  


• type reboot
  

For 18.04 or newer...

• boot to a Ubuntu Live DVD/USB


• open a terminal window


• type sudo fdisk -l
  


• identify the /dev/XXXX device name for your "Linux Filesystem"


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


• repeat the fsck command if there were errors
  
  
  • If you have separate partitions for your /home directory, repeat this using the appropriate /dev/xxxx
    
  
  


• type reboot
  

Update #1:

The HDD is getting ECC correctable read errors, and failing fsck.

Update #2:

Data is being recovered from the drive. The drive will be replaced with a SSD.

share|improve this answer

edited Apr 16 at 19:08

answered Apr 16 at 15:03

heynnemaheynnema

27k33 gold badges2828 silver badges7272 bronze badges

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  I'm preparing a Ubuntu USB right now. In the past, I'd seen the GUI for the GRUB menu, but I'm not seeing that now. Instead I get a cmd line grub rescue> which doesn't appear to have disk-checking option. I'll let you know in 30 min or so how the Ubuntu USB works, I'm creating an 18.04-2 ISO
  
  – john Van Drie
  Apr 16 at 15:36
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @johnVanDrie Do the SMART stuff first, then the fsck.
  
  – heynnema
  Apr 16 at 15:41
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  The SMART data shows all HD's: overall assessment is OK. Would the simplest thing be to install Ubuntu from the USB to one of the other HD's, and boot from there. Worry about the bad disk later/
  
  – john Van Drie
  Apr 16 at 16:29
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @johnVanDrie No. Let finish troubleshooting first. Even though the SMART Data says OK, it may not be. That's why I want to look at it. Can you post the screenshot to imgur.com for me? Then do the fsck. Then we may look at syslog for more data.
  
  – heynnema
  Apr 16 at 16:36
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  OK - thanks so much. While I try to get this s-shot, I did notice I'd overlooked the boot drive. When trying to mount in the Disk Utility tool, I get the ff. error: error mounting /dev/sdf1 at /media/ubuntu.... wrong fs type, bad option, bad superblock on /dev/sdf1, misssing codepage or helper program, or other err (udisks-error-quark, 0). It now says SELF-TEST FAILED.
  
  – john Van Drie
  Apr 16 at 16:51
  
  

  
  
  
  

 | 
show 12 more comments

Lets first check your file system for errors.

For 17.10 or older...

• 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
  
  
  • If you have your /home directories on a separate partition, run sudo fsck -f /home as well
  
  


• type reboot
  

For 18.04 or newer...

• boot to a Ubuntu Live DVD/USB


• open a terminal window


• type sudo fdisk -l
  


• identify the /dev/XXXX device name for your "Linux Filesystem"


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


• repeat the fsck command if there were errors
  
  
  • If you have separate partitions for your /home directory, repeat this using the appropriate /dev/xxxx
    
  
  


• type reboot
  

Update #1:

The HDD is getting ECC correctable read errors, and failing fsck.

Update #2:

Data is being recovered from the drive. The drive will be replaced with a SSD.

share|improve this answer

edited Apr 16 at 19:08

answered Apr 16 at 15:03

heynnemaheynnema

27k33 gold badges2828 silver badges7272 bronze badges

share|improve this answer

edited Apr 16 at 19:08

answered Apr 16 at 15:03

heynnemaheynnema

27k33 gold badges2828 silver badges7272 bronze badges

answered Apr 16 at 15:03

heynnemaheynnema

27k33 gold badges2828 silver badges7272 bronze badges

answered Apr 16 at 15:03

heynnemaheynnema

27k33 gold badges2828 silver badges7272 bronze badges