LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software > Linux - Kernel
User Name
Password
Linux - Kernel This forum is for all discussion relating to the Linux kernel.

Notices


Reply
  Search this Thread
Old 03-04-2019, 04:54 PM   #1
RandomTroll
Senior Member
 
Registered: Mar 2010
Distribution: Slackware
Posts: 1,174

Rep: Reputation: 189Reputation: 189
Kernel 5.0 disk-errors on boot, can't boot up: is it just me?


I just built kernel 5.0. I had been running 4.20.13. I unpatched with the 4.20.13 patch then applied the 5.0 patch. It ran without complaint. When I try to boot into it, I get hard disk errors. I can still boot into 4.20.13. e2fsck run from a boot flash drive finds no errors. I had disk errors before; this may be a problem only I have. Has it worked for everyone else?

Later: I built the kernel from the 5.0 tarball, get the same result.

Quote:
EXT4-fs error in ext4_reserve_inode_write: Journal has aborted
EXT4-fs ext4_journal_check_start [whoops! forgot to write this down, but it fails]
then it mounts read-only.

Last edited by RandomTroll; 03-04-2019 at 10:56 PM.
 
Old 03-05-2019, 05:07 AM   #2
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 12,410

Rep: Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727
Quote:
Originally Posted by RandomTroll View Post
I just built kernel 5.0. I had been running 4.20.13. I unpatched with the 4.20.13 patch then applied the 5.0 patch. It ran without complaint. When I try to boot into it, I get hard disk errors. I can still boot into 4.20.13. e2fsck run from a boot flash drive finds no errors. I had disk errors before; this may be a problem only I have. Has it worked for everyone else?

Later: I built the kernel from the 5.0 tarball, get the same result.


then it mounts read-only.
I'm running 5.0 on 2 boxes running Slackware64-current without any hitch.
What patch did you apply?
 
Old 03-05-2019, 09:38 AM   #3
RandomTroll
Senior Member
 
Registered: Mar 2010
Distribution: Slackware
Posts: 1,174

Original Poster
Rep: Reputation: 189Reputation: 189
Quote:
Originally Posted by bathory View Post
What patch did you apply?
patch-5.0.xz I later downloaded the whole source then built from that, had the same result.
 
Old 03-05-2019, 03:32 PM   #4
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 12,410

Rep: Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727
Quote:
Originally Posted by RandomTroll View Post
patch-5.0.xz I later downloaded the whole source then built from that, had the same result.
Doh, I too downloaded the kernel source from here, and built it using the .config of the previous running kernel.
FYI, even the nvidia latest drivers (version 418.43) worked!
 
Old 03-05-2019, 05:45 PM   #5
RandomTroll
Senior Member
 
Registered: Mar 2010
Distribution: Slackware
Posts: 1,174

Original Poster
Rep: Reputation: 189Reputation: 189
I always get my kernel from kernel.org. I booted from a flash drive, turned off the journal, can boot, get
Quote:
EXT4-fs error (device sda1): ext4_find_entry:1439: inode #661755: comm udevd: reading directory lblock 0
but it seems to work otherwise. Do you use journals? I don't know how to interpret this error, why udevd is involved. How much do I miss by not-journaling? Why do I get this error in kernel 5.0 but not 4.20.13?
 
Old 03-06-2019, 02:01 AM   #6
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 12,410

Rep: Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727
Quote:
Originally Posted by RandomTroll View Post
I always get my kernel from kernel.org. I booted from a flash drive, turned off the journal, can boot, get but it seems to work otherwise. Do you use journals? I don't know how to interpret this error, why udevd is involved. How much do I miss by not-journaling? Why do I get this error in kernel 5.0 but not 4.20.13?
From what I've read this error affects SSD drives, which I don't have.
Other than that, I use the default journaling capabilities of EXT4 and the kernel is compiled with:
Code:
CONFIG_EXT4_FS=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
# CONFIG_EXT4_ENCRYPTION is not set
# CONFIG_EXT4_DEBUG is not set
 
Old 03-06-2019, 09:14 AM   #7
RandomTroll
Senior Member
 
Registered: Mar 2010
Distribution: Slackware
Posts: 1,174

Original Poster
Rep: Reputation: 189Reputation: 189
Quote:
Originally Posted by bathory View Post
From what I've read this error affects SSD drives, which I don't have.
Where have you read this? I don't have SSD drives.


Quote:
Originally Posted by bathory View Post
Other than that, I use the default journaling capabilities of EXT4 and the kernel is compiled with:
What does
Code:
 dumpe2fs /dev/sda1 | grep journal
return?
 
Old 03-06-2019, 12:05 PM   #8
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 12,410

Rep: Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727
Quote:
Originally Posted by RandomTroll View Post
Where have you read this? I don't have SSD drives.
Put the error you get in the search engine and the first hits were about SSD drives giving the same error.
Also what is strange is that these first hits were about ubuntu or debian distros


Quote:
What does
Code:
 dumpe2fs /dev/sda1 | grep journal
return?
Code:
dumpe2fs /dev/sda1 | grep -i journal
dumpe2fs 1.44.5 (15-Dec-2018)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file dir_nlink extra_isize
Journal inode:            8
Journal backup:           inode blocks
Journal features:         journal_incompat_revoke
Journal size:             128M
Journal length:           32768
Journal sequence:         0x00064a64
Journal start:            1
 
1 members found this post helpful.
Old 03-06-2019, 03:42 PM   #9
RandomTroll
Senior Member
 
Registered: Mar 2010
Distribution: Slackware
Posts: 1,174

Original Poster
Rep: Reputation: 189Reputation: 189
Quote:
Originally Posted by bathory View Post
Put the error you get in the search engine and the first hits were about SSD drives giving the same error.
Also what is strange is that these first hits were about ubuntu or debian distros
These are old messages about old kernels. Your disk has a journal, so it's not a general problem. The journal on my other volume has no problem. I seem to have some subtle defects with my hardware. I don't need a journal on the boot volume, so I'll let it ride. Thanks for your help.
 
Old 03-14-2019, 11:03 AM   #10
RandomTroll
Senior Member
 
Registered: Mar 2010
Distribution: Slackware
Posts: 1,174

Original Poster
Rep: Reputation: 189Reputation: 189
I try again every kernel update: no luck. I notice this error:
Quote:
ext4_dirty_inode:6087: IO Failure
I find this error from kernels in 2.6, relating to a bug when JBD_DEBUG isn't being used: the kernel didn't mark the inode as dirty. Could a similar error have recrudesced? I use JBD2_DEBUG. One would think this inode would get marked dirty, which would solve the problem. e2fsck finds no errors, so the inode can't have failed because the sector in which it resides is bad.
 
Old 03-14-2019, 01:38 PM   #11
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 12,410

Rep: Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727
Quote:
Originally Posted by RandomTroll View Post
I try again every kernel update: no luck. I notice this error: I find this error from kernels in 2.6, relating to a bug when JBD_DEBUG isn't being used: the kernel didn't mark the inode as dirty. Could a similar error have recrudesced? I use JBD2_DEBUG. One would think this inode would get marked dirty, which would solve the problem. e2fsck finds no errors, so the inode can't have failed because the sector in which it resides is bad.
Perhaps you should run a smartctl check on the disk, because getting different errors any time could mean a hardware problem
 
Old 03-14-2019, 01:59 PM   #12
RandomTroll
Senior Member
 
Registered: Mar 2010
Distribution: Slackware
Posts: 1,174

Original Poster
Rep: Reputation: 189Reputation: 189
Quote:
Originally Posted by bathory View Post
Perhaps you should run a smartctl check on the disk, because getting different errors any time could mean a hardware problem
I always get the same error. I finally installed 5.0.2 on my old disk and booted from it: it works, which points to my new disk having the problem. sigh.

Later: I bought a new disk because smartctl reported errors in the old one; it doesn't in the new one.

Last edited by RandomTroll; 03-14-2019 at 11:37 PM.
 
Old 03-15-2019, 01:59 AM   #13
bathory
LQ Guru
 
Registered: Jun 2004
Location: Piraeus
Distribution: Slackware
Posts: 12,410

Rep: Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727Reputation: 1727
Quote:
Originally Posted by RandomTroll View Post
I always get the same error. I finally installed 5.0.2 on my old disk and booted from it: it works, which points to my new disk having the problem. sigh.

Later: I bought a new disk because smartctl reported errors in the old one; it doesn't in the new one.
Could be a faulty cable, or (SATA) connector on the motherboard.
 
Old 03-15-2019, 11:55 AM   #14
RandomTroll
Senior Member
 
Registered: Mar 2010
Distribution: Slackware
Posts: 1,174

Original Poster
Rep: Reputation: 189Reputation: 189
Quote:
Originally Posted by bathory View Post
Could be a faulty cable, or (SATA) connector on the motherboard.
It's a laptop.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
repeatable disk read/write errors with no errors logged by kernel or SMART mxl2 Linux - Hardware 9 04-02-2011 09:27 AM
Errors, Errors, and more Errors (KDE 3.4.x GUI Errors) Dralnu Linux - Software 2 05-13-2006 08:30 AM
errors,errors,errors!!! randell6564 Mandriva 2 01-15-2006 02:29 AM
Grub errors...grub errors...grub errors smattmac Linux - Newbie 1 06-13-2005 02:07 PM
Help, no CLI at boot! Just a black screen, can still type though, just can't see text Slovak Slackware 12 11-17-2004 06:18 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Software > Linux - Kernel

All times are GMT -5. The time now is 11:34 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration