Package: linux-image-5.19.0-1-amd64
Package: linux-image-5.19.0-2-amd64

Version: 5.19.6-1
Version: 5.19.11-1

Since 5.19, the kernel shows this error screen on every boot:
Info: Fix the reported corruption.
Info: [/dev/sdb4] Disk Model: SanDisk SDSSDHII
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 233906176 (114212 MB)
Info: MKFS version
  "Linux version 4.3.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 
5.3.1 20160101 (Debian 5.3.1-5) ) #1 SMP Debian 4.3
.3-5 (2016-01-04)"
Info: FSCK version
  from "Linux version 4.3.0-1-amd64 (debian-ker...@lists.debian.org) (gcc 
version 5.3.1 20160121 (Debian 5.3.1-7) ) #1 SMP Debia
n 4.3.5-1 (2016-02-06)"
    to "Linux version 5.19.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-11 
(Debian 11.3.0-6) 11.3.0, GNU ld (GNU Binutils for
 Debian) 2.38.90.20220713) #1 SMP PREEMPT_DYNAMIC Debian 5.19.11-1 (2022-09-24)"
Info: superblock features = 0 : Info: superblock encrypt level = 0, salt = 00000000000000000000000000000000
Info: total FS sectors = 233906176 (114212 MB)
Info: CKPT version = 34a199
Info: checkpoint state = 45 :  crc compacted_summary unmount
Info: No error was reported
[    5.548001]

/dev/sdb4 is my root F2FS partition. The boot screen resembles the dump.f2fs screen in the live system. I already ran fsck.f2fs /dev/sdb4 -a and -f from a GRML64 Debian testing based system (with kernel 5.19.0-2) booted from an usb stick, but both reported no error (as does the kernel, see above). I am using a fully updated Debian testing system.

The bug is merely annoying, as the system boots normally, but it is annoying.

Reply via email to