Arch Linux

chosentorture

Member

Registered: 2014-10-31

Posts: 58

error message after booting arch - Fix the reported corruption

This error message started appearing some time ago after I edited my fstab and encrypted a partition. It pops up right after I boot arch.

Info: Fix the reported corruption.
Info: sector size = 512
Info: total sectors = 128966656 (in 512 bytes)
Info: MKFS version
  "Linux version 4.0.0-1-586 (debian-kernel@lists.debian.org) (gcc version 4.9.211)"
Info: FSCK version
  from "Linux version 4.1.4-1-ARCH (builduser@foutrelis) (gcc version 5.2.0 (GCC
    to "Linux version 4.1.4-1-ARCH (builduser@foutrelis) (gcc version 5.2.0 (GCC

Done.

The output of various relevant commands is as follows -

$ lsblk

NAME     MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda        8:0    0   1.8T  0 disk  
├─sda1     8:1    0   1.8T  0 part  
│ └─data 254:0    0   1.8T  0 crypt /run/media/archimedes/f88e84a7-5c4a-4fdc-804a-a2d3677adc98
├─sda2     8:2    0     9G  0 part  /var
├─sda3     8:3    0     1G  0 part  [SWAP]
└─sda4     8:4    0     2G  0 part  /home
sdb        8:16   0 111.8G  0 disk  
├─sdb1     8:17   0   300M  0 part  /boot
├─sdb2     8:18   0    50G  0 part  
└─sdb3     8:19   0  61.5G  0 part  /

$ cat /etc/fstab

# /dev/sdb3
UUID=c47e7364-c9a7-429f-b6af-c7f6461bd1d6	/         	f2fs      	rw,noatime,background_gc=on,active_logs=6	0 0

# /dev/sdb1
UUID=406C-5ECF      	/boot     	vfat      	rw,noatime,nodev,nosuid,noexec,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro	0 2

# /dev/sda2
UUID=b4538e0c-1ec1-4e41-af3d-7c86ff78836c	/var      	ext4      	rw,nodev,nosuid,relatime,data=ordered	0 2

# /dev/sda4
UUID=6ac2dade-124e-4fe0-b365-efc60ecc8583	/home     	ext4      	rw,relatime,data=ordered	0 2

# /dev/sda3
UUID=8bee1f67-bcf2-4dd3-955d-9c264bc08406	none      	swap      	defaults  	0 0

kernel parameters

options   "rw root=UUID=c47e7364-c9a7-429f-b6af-c7f6461bd1d6 quiet loglevel=3 udev.log-priority=3 initrd=/intel-ucode.img"

$ sudo fdisk -l

Disk /dev/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 2A448752-CEB5-4AF3-9F18-A265DFBDD39A

Device          Start        End    Sectors  Size Type
/dev/sda1        2048 3881863167 3881861120  1.8T Linux filesystem
/dev/sda2  3886057472 3904931839   18874368    9G Linux filesystem
/dev/sda3  3904931840 3907028991    2097152    1G Linux swap
/dev/sda4  3881863168 3886057471    4194304    2G Linux filesystem

Partition table entries are not in disk order.


Disk /dev/sdb: 111.8 GiB, 120034123776 bytes, 234441648 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 8FBD0484-D453-4645-81BE-E5BE9D461211

Device         Start       End   Sectors  Size Type
/dev/sdb1       2048    616447    614400  300M EFI System
/dev/sdb2     616448 105474047 104857600   50G Microsoft basic data
/dev/sdb3  105474048 234440703 128966656 61.5G Linux filesystem


Disk /dev/mapper/data: 1.8 TiB, 1987510796288 bytes, 3881857024 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

I figure that it's got something to do with /dev/sdb3 because it has the same number of sectors that the error message shows but I don't have any idea what's causing it. What have I done wrong?

smsware

Member

From: Szczecin, Poland

Registered: 2012-08-14

Posts: 149

Website

Re: error message after booting arch - Fix the reported corruption

I don't have an answer but I have the same situation and also the same filesystem: F2FS, so that's the reason probably. I figured it's not a warning but just an "information" so maybe it's just the way mkfs of f2fs works... or the filesystem itself is unstable or something. I will be going back to EXT4, can't feel the difference anyway.

h1arch

Member

Registered: 2023-12-03

Posts: 2

Re: error message after booting arch - Fix the reported corruption

For me this started with 5.19 kernel (under debian testing, https://bugs.debian.org/cgi-bin/bugrepo … g=1021927), but persists at least up to 6.5.10. I believe this is a kernel bug, the f2fs partition is healthy, running fsck.f2fs from a live system gives the same output as the boot fsck - without the "Info: Fix the reported corruption.", but ending with "Info: No error was reported". Seems the kernel detects a corruption that isn't there, the file system being error free and behaving stable. It has to do with the f2fs kernel module.

Btw: no need to change the file system, this output is only informativ and does not mean the file system is unstable.

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,720

Re: error message after booting arch - Fix the reported corruption

Note that you're replying to an 8 year old thread, very little of this will still be relevant today.

Please pay attention to the dates and don't necro-bump.

Closing.