Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux? |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
04-05-2020, 01:49 PM
|
#1
|
LQ Newbie
Registered: Apr 2020
Posts: 2
Rep: 
|
failed boot in ubuntu - mce: [Hardware Error]
I'm using a Dell Inspiron 15 5567, with Ubuntu 16.04, kernel version 4.15.0-88-generic.
My Ubuntu installation is failing to boot. Upon restarting/powering on computer, the following errors show up:
Code:
[ 0.044000] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 6: ee0000000040110a
[ 0.044000] mce: [Hardware Error]:TSC 0 ADDR fef1ce80 MISC 43880014086
[ 0.044000] mce: [Hardware Error]: PROCESSOR 0:806e9 TIME 1586058968 SOCKET 0 APIC 0 microcode ca
[ 0.044000] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 7: ee0000000040110a
[ 0.044000] mce: [Hardware Error]:TSC 0 ADDR fef1ce80 MISC 7880014086
[ 0.044000] mce: [Hardware Error]: PROCESSOR 0:806e9 TIME 1586058968 SOCKET 0 APIC 0 microcode ca
[ 0.827289] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire
command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
[ 0.827359] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire
command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs fed40080 f80
[ 0.919117] Couldn't get size: 0x800000000000000e
/dev/sda7 contains a file system with errors, check forced.
Inodes that were part of a corrupted orphan linked list found
/dev/sda7: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
fsck exited with status code 4
The root filesystem on /dev/sda7 requires a manual fsck
BusyBox v1.27.2 (Ubuntu 1:1.27.2-ubuntu3.2) built-in shell (ash)
Enter 'help' for a list of built-in commands
I've tried updating the firmware BIOS on my Dell, no change. Before this issue happened the first time, the screen simply went dark from my Ubuntu desktop, and the system was unresponsive. The Windows 10 Home partition boots fine, although it does seem to run slow and hang up sometimes. Also I've noticed since having this computer that the fan tends to blow loudly a lot.
|
|
|
04-06-2020, 07:59 AM
|
#2
|
LQ Guru
Registered: Apr 2008
Distribution: Slackware, Ubuntu, PCLinux,
Posts: 11,386
|
What was the result when you followed the suggestion in the output to run fsck on /dev/sda7?
|
|
|
04-06-2020, 05:29 PM
|
#3
|
LQ Newbie
Registered: Apr 2020
Posts: 2
Original Poster
Rep: 
|
Quote:
Originally Posted by yancek
What was the result when you followed the suggestion in the output to run fsck on /dev/sda7?
|
I did eventually run fsck after googling about it, and answered "yes" to each error. After restarting the computer, my Ubuntu install was able to fully boot up. I don't know if this fully resolved all the issues that were being reported, but at least it works for now.
|
|
|
04-06-2020, 06:48 PM
|
#4
|
LQ Guru
Registered: Apr 2008
Distribution: Slackware, Ubuntu, PCLinux,
Posts: 11,386
|
If you have problems with the filesystem such as you reported and this happens on a regular basis it is one indication of a hardware problem with your drive.
|
|
|
04-09-2020, 07:15 AM
|
#5
|
LQ Guru
Registered: Jan 2006
Location: Ireland
Distribution: Slackware, Slarm64 & Android
Posts: 17,518
|
If you have an ext2/3/4 filesystem, there is tune2fs, which can schedule checks. I wouldn't advise messing much with other features. This gets it to do checks based on restarts. If you don't restart, but suspend you'd be better to do it by caendar, or cron, if you're into it.
|
|
|
All times are GMT -5. The time now is 09:07 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|