Description of problem: A fresh install of Fedora 19 on a Lenovo T440p works fine, and boots properly consistently. Version-Release number of selected component (if applicable): kernel-3.12.11-201.fc19 has no problems kernel-3.13.5-101.fc19 has this issue How reproducible: consistently, upon boot to 3.13.5 kernel Steps to Reproduce: 1. Install Fedora 19 2. Reboot several times, no issues 3. Upgrade manually to kernel-3.12.11 4. Reboot several times, no issues 5. Run default software update to upgrade to latest packages system-wide 6. Reboot once with new kernel-3.13.5 7. Observe that boot fails with error messages related to EXT4 filesystem corruption 8. Reboot back to 3.12.11 9. Observe same filesystem corruption errors upon boot Actual results: The root filesystem is corrupted just by booting with new kernel Expected results: Filesystem should not be corrupted Additional info: This seems to be a very similar issue to https://bbs.archlinux.org/viewtopic.php?id=177520 with a different kernel version (same major/minor though).
Can you attach a picture or the log showing the ext4 error messages?
I don't have the exact errors right now, it was some combination of "bad inode" type messages. I will try to create a sacrificial filesystem to test with on the same hardware. Would the initial errors be more helpful, or an fsck log after the corruption?
Created attachment 871666 [details] some EXT4-fs error messages during the failure and afterward I did find some syslog error messages related to the earlier errors. There are ellipses in the file to indicate other log messages between the FS error messages. All of the timestamped messages are from /var/log/messages on the host where the errors occurred.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs. Fedora 19 has now been rebased to 3.13.5-100.fc19. Please test this kernel update and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
This sounds like it's possibly a dup of bug #1067615
It may be the same issue regarding the NVidia drivers causing issues. The disk in my T440p is not SSD, as in #1067615, but is a magnetic disk so the workaround that is proposed in that other bug does not apply (I think). I am not able to attempt an install with the new kernel this week, but may be able to attempt next week.
Could maybe test by running w/ a generic video driver? *shrug* if it's video it's well out of my realm of expertise, I'm afraid.
After I saw the problem the first time and found that 'archlinux' comment above, I did attempt to add "nouveau" kernel module to blacklist. But at that point it may have been to late as the disk errors had already started.
Hi, after update my server with Fedora 19 , kernel update leads to kernel ata warning messages.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 19 kernel bugs. Fedora 19 has now been rebased to 3.14.4-100.fc19. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 20, and are still experiencing this issue, please change the version to Fedora 20. If you experience different issues, please open a new bug report for those.
On the same hardware and Acer Aspire 4930 with Nvidia motherboard ext4 also get corrupted, btrfs reports CRC error after disk reading. So this might be memory corruption.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.