Skip to main content ↑ ↓
Topic: Kernel 6.9 (?) - Nasty Bug (Read 378 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Kernel 6.9 (?) - Nasty Bug

I see the other reported this problem too:
https://bbs.archlinux.org/viewtopic.php?pid=2172691

Nobody knows what is going on. Your expertise would be helpful.

Issue:
Everytime system boots (after shutdown) filesystem reports errors to the kernel and it scans the drive for a long time.
In my case its probably scanning FAT and my /home (f2fs).

I tried scanning it from external live (6.8.x I believe) and once it helped, but later shudown and again...
Then I tried from debian 12x live and tried again to force fix. Shutdown, adn againg still reporting and scanning.

P.S.: There have been "badzillions" of update recently (kde, kernels, ....), so I cleaned the cache. It was booting no problem. So nothing in cache. Don't know about 6.6LTS guys downgraded to 6.8.9 and said it was OK, but one dude downgraded lower and the issue persisted. I'm not happy about something corrupting the data! I don't know what is causing it.

I remember that kernel 6.1 had issue with ext4, but here its not the case. I scanned both / (ext4) and /home (f2fs)

Noting helped:
1. GRUB_CMDLINE_LINUX="fsck.mode=force" fsck.repair="yes" (scans only "/" ext4) - did not help
2. fsck.f2fs -f /dev/sdaX
3. ext4:
a) e2fsck -f -p -c -v /dev/sdaY
b) e2fsck -f -v -E discard /dev/sdaY
c) e2fsck -f -v -E optimize_extents /dev/sdaY
d) e2fsck -f -v -D /dev/sdaY
4. e2fsck.fat blah blah

Full maintenance. Nothing helped. There's a NASTY BUG. SOMETHING IS CORRUPTING THE DRIVE, HENCE IT IS REPORTED TO THE KERNEL AND EACH BOOT IT SCANS. I"M AFFRAID OF DATA CORRUPTION.

Re: Kernel 6.9 (?) - I'm Hit Hard By This Nast Bug

Reply #1 –
Update:
I loaded kernel 6.6.x LTS and rebooted
1. First reboot = scanning
2. Second reboot = so far all went OK; let's hope it will continue to be OK.

The culprit might be nasty kernel (someone should be put in the "Hall of Shame" - putting something into the kernel that corrupts file systems/data? If I was Linus or Hartman, I would make sure this ***** would never "contribute" to anything!).

P.S.: I've bee through a lot of bugs and nastines, but this is by far the worst. I get it KDE is perpetual beta, maybe, maybe one time it slipped that 6.1 corrupted ext4 on Debian/Devuan and my clonezilla copies were corrupted, maybe its OK that clonezilla had a bug to not restore properly backup (late 2023...) even when you gave it expert --> checsums (...)  both ways (I always do it). Maybe its ok that openNTP does not work on Artix (Fedora's chrony works) and maybe its OK that there's no (proper) solution to run pa successor on Artix KDE, but kernel corrupting data? That is the worst I have ever seen.