Last night, I updated Linux to 4.0.2. On the same night, weird things started happening, in the end, my system would not even boot properly (systemd stuck at starting the login service, other virtual terminals did not work either). I chrooted to my / using a live USB stick to get the logs. According to them, several shared libraries were missing or corrupted.

I fscked my ext4 partitions, there were some corrupted files and directories on my root. badblocks did not find anything.

I reinstalled the affected packages from the chroot and rebooted. After using my machine for some time, I noticed data loss on my /home. I went back to the live USB, and now fsck found corrupted directories on my /home partition. From the content I was able to salvage from them, all of them seemed "recent" (browser cache entries, nautilus thumbnails and a text file which I created during the last session).

After another reboot, there were some new problems, related to corrupted shared libraries again. I decided to get back to the live USB environment and reinstall all my packages just to make sure everything is ok. After this, I was able to use my machine without problems for several hours. Then I noticed a corrupted image on /home which I created during this session.

I don't think it's a hardware problem. I have two SSDs in RAID0 (mdadm). There is a Windows set up in dual-boot on the same drives, and there aren't any problems on the NTFS partitions. Also, the drives are only one and a half year old, with slightly above average usage, but far from anything extreme (just a normal development machine), so they should be nowhere near the end of their lifetimes.

I downgraded Linux to 4.0.1 to see if 4.0.2 caused the problems. As Linux 4.0.3 is already released, I checked the changelog for relevant entries. This one seems interesting.

My questions:

- Is anybody else affected by similar problems after updating to linux-4.0.2?

- Does the fix linked above in Linux 4.0.3 seem related to my problem?

- If it were a hardware problem, badblocks should have detected bad sectors, right?

EDIT:

This was the most likely reason: https://bugzilla.kernel.org/show_bug.cgi?id=98501

Last edited by zozi56 (2015-05-21 08:00:56)