You are not logged in.

Pages: 1

#1 2024-11-30 18:22:45

Strangiato
Member
Registered: 2020-01-10
Posts: 406

Arch runs fsck before almost every boot

Hello

My Arch is fully updated. Arch runs fsck before almost every boot.
dmesg log prints these errors:

[sáb nov 30 15:05:24 2024] EXT4-fs error (device sda1): ext4_ext_check_inode:524: inode #2770363: comm ThreadPoolForeg: pblk 0 bad header/extent: invalid extent entries - magic f30a, entries 1, max 4(4), depth 0(0)
[sáb nov 30 15:05:24 2024] EXT4-fs error (device sda1): ext4_ext_check_inode:524: inode #2770363: comm ThreadPoolForeg: pblk 0 bad header/extent: invalid extent entries - magic f30a, entries 1, max 4(4), depth 0(0)
[sáb nov 30 15:05:24 2024] EXT4-fs error (device sda1): ext4_ext_check_inode:524: inode #2770363: comm ThreadPoolForeg: pblk 0 bad header/extent: invalid extent entries - magic f30a, entries 1, max 4(4), depth 0(0)
[sáb nov 30 15:05:24 2024] EXT4-fs error (device sda1): ext4_ext_check_inode:524: inode #2770363: comm ThreadPoolForeg: pblk 0 bad header/extent: invalid extent entries - magic f30a, entries 1, max 4(4), depth 0(0)
[sáb nov 30 15:05:24 2024] EXT4-fs error (device sda1): ext4_ext_check_inode:524: inode #2770363: comm ThreadPoolForeg: pblk 0 bad header/extent: invalid extent entries - magic f30a, entries 1, max 4(4), depth 0(0)
[sáb nov 30 15:05:24 2024] EXT4-fs error (device sda1): ext4_ext_check_inode:524: inode #2770363: comm ThreadPoolForeg: pblk 0 bad header/extent: invalid extent entries - magic f30a, entries 1, max 4(4), depth 0(0)
[sáb nov 30 15:05:24 2024] EXT4-fs error (device sda1): ext4_ext_check_inode:524: inode #2770363: comm ThreadPoolForeg: pblk 0 bad header/extent: invalid extent entries - magic f30a, entries 1, max 4(4), depth 0(0)
[sáb nov 30 15:07:13 2024] EXT4-fs error (device sda1): ext4_ext_check_inode:524: inode #2770363: comm ThreadPoolForeg: pblk 0 bad header/extent: invalid extent entries - magic f30a, entries 1, max 4(4), depth 0(0)
[sáb nov 30 15:07:13 2024] EXT4-fs error (device sda1): ext4_ext_check_inode:524: inode #2770363: comm ThreadPoolForeg: pblk 0 bad header/extent: invalid extent entries - magic f30a, entries 1, max 4(4), depth 0(0)

I use the default kernel:

$ uname -a
Linux Arch-PC 6.12.1-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 22 Nov 2024 16:04:27 +0000 x86_64 GNU/Linux

Any idea on what is the problem, and how to fix it?

Thanks for reading.

Last edited by Strangiato (2024-11-30 18:23:03)

Offline

#2 2024-11-30 20:28:42

seth
Member
Registered: 2012-09-03
Posts: 58,964

Re: Arch runs fsck before almost every boot

Unclean shutdown, the FS doesn't get synced or closed.
If you're not habitually shutting down the system by pressing the power button until it turns off, please post your complete system journal for the previous to such boot, eg. 

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

if the current boot had this.

(If you *are* habitually shutting down the system by pressing the power button until it turns off, stop doing that)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#3 2024-11-30 20:38:34

Strangiato
Member
Registered: 2020-01-10
Posts: 406

Re: Arch runs fsck before almost every boot

LOL
I only use the power button when there is no alternative and thus I'm forced to do it.
I have just noticed that the errors appear in the kernel log immediately after opening my internet browser (Vivaldi).

The requested log:
http://0x0.st/XRD_.txt

Edit:
Well, even opening the /home/myuser/.config/vivaldi folder with my file manager produces an "EXT4-fs error..." message in the kernel log, and then Arch runs fsck in the next boot. What a bizarre thing.

Last edited by Strangiato (2024-11-30 20:56:37)

Offline

#4 2024-11-30 21:17:38

seth
Member
Registered: 2012-09-03
Posts: 58,964

Re: Arch runs fsck before almost every boot

Did you repartition the disk?
Is the filesystem bigger than the partition?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#5 2024-11-30 21:21:50

Strangiato
Member
Registered: 2020-01-10
Posts: 406

Re: Arch runs fsck before almost every boot

My ssd has 3 partitions.

$ sudo fdisk -l /dev/sda
Disk /dev/sda: 953,87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: Asgard AS1TS3-S7
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: dos
Disk identifier: 0xb72af171

Device     Boot      Start        End   Sectors   Size Id Type
/dev/sda1             2048  734005247 734003200   350G 83 Linux
/dev/sda2  *     734005248 1048578047 314572800   150G  7 HPFS/NTFS/exFAT
/dev/sda3       1048578048 2000409263 951831216 453,9G 83 Linux

Offline

#6 Yesterday 07:00:20

seth
Member
Registered: 2012-09-03
Posts: 58,964

Re: Arch runs fsck before almost every boot

That doesn't really answer the question, though. Add

df -h

Also manually running fsck on the device (must not be mounted, so in doubt has to happen when booting a live system or, I guess, sda3) would complain about that.

Ceterum censeo: 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#7 Yesterday 10:57:07

Strangiato
Member
Registered: 2020-01-10
Posts: 406

Re: Arch runs fsck before almost every boot

$ df -H
Filesystem      Size  Used Avail Use% Mounted on
dev              17G     0   17G   0% /dev
run              17G  1,8M   17G   1% /run
/dev/sda1       370G  306G   47G  87% /
tmpfs            17G  178M   17G   2% /dev/shm
tmpfs            17G  222M   17G   2% /tmp
tmpfs           1,1M     0  1,1M   0% /run/credentials/systemd-journald.service
tmpfs           1,1M     0  1,1M   0% /run/credentials/systemd-udev-load-credentials.service
tmpfs           1,1M     0  1,1M   0% /run/credentials/systemd-tmpfiles-setup-dev-early.service
tmpfs           1,1M     0  1,1M   0% /run/credentials/systemd-tmpfiles-setup-dev.service
tmpfs           1,1M     0  1,1M   0% /run/credentials/systemd-sysctl.service
tmpfs           1,1M     0  1,1M   0% /run/credentials/systemd-vconsole-setup.service
/dev/sdc2       2,0T  2,0T  8,8G 100% /mnt/2TB
/dev/sdb3       984G  968G   17G  99% /mnt/WD
/dev/loop0      132k  132k     0 100% /var/lib/snapd/snap/bare/5
/dev/loop1      112M  112M     0 100% /var/lib/snapd/snap/core/16202
/dev/loop2       59M   59M     0 100% /var/lib/snapd/snap/core18/2796
/dev/loop3      110M  110M     0 100% /var/lib/snapd/snap/core/17200
/dev/loop5       59M   59M     0 100% /var/lib/snapd/snap/core18/2829
/dev/loop4       67M   67M     0 100% /var/lib/snapd/snap/core20/2015
/dev/loop7       68M   68M     0 100% /var/lib/snapd/snap/core20/2318
/dev/loop6       86M   86M     0 100% /var/lib/snapd/snap/gtk-common-themes/1534
/dev/loop8       97M   97M     0 100% /var/lib/snapd/snap/gtk-common-themes/1535
/dev/loop9      274M  274M     0 100% /var/lib/snapd/snap/kde-frameworks-5-core18/32
/dev/loop10     304M  304M     0 100% /var/lib/snapd/snap/kde-frameworks-5-core18/35
/dev/sda3       479G  474G  5,4G  99% /mnt/DADOS
tmpfs           1,1M     0  1,1M   0% /run/credentials/systemd-tmpfiles-setup.service
/dev/sda2       162G  156G  6,0G  97% /mnt/WIN10
tmpfs           3,4G  136k  3,4G   1% /run/user/1003
/dev/sde1        31G   25G  6,6G  79% /media/Ventoy

Fast boot is already disabled on my Windows 10.

Someone gave me this command in Vivaldi forum:

sudo debugfs -R 'ncheck 2770363' /dev/sda1

The output:

$ sudo debugfs -R 'ncheck 2770363' /dev/sda1
[sudo] password for stalker: 
debugfs 1.47.1 (20-May-2024)
Inode   Pathname
2770363 /home/stalker/.config/vivaldi/Default/DIPS-journal

I got errors when trying to handle DIPS-journal:

stalker@Arch-PC:~$ ls /home/stalker/.config/vivaldi/Default/DIPS*
ls: cannot access '/home/stalker/.config/vivaldi/Default/DIPS-journal': Structure needs cleaning
/home/stalker/.config/vivaldi/Default/DIPS
stalker@Arch-PC:~$ cp /home/stalker/.config/vivaldi/Default/DIPS-journal /tmp
cp: cannot stat '/home/stalker/.config/vivaldi/Default/DIPS-journal': Structure needs cleaning

SpinRite software found no failure after testing my SSD for more than 6 hours:
https://i.imgur.com/4kIew5w.jpeg

Hard Disk Sentinel and HD Tune ran on Windows 10 also found no errors.

I have just ran fsck manually:

$ sudo fsck -pfv /dev/sda1
fsck from util-linux 2.39.3
ARCH: Inode 655927 extent tree (at level 1) could be narrower.  IGNORED.
ARCH: Inode 2770363, i_size is 17592186044416, should be 17592186044416.  FIXED.
ARCH: Inode 6309990 extent tree (at level 1) could be narrower.  IGNORED.
ARCH: Inode 6312174 extent tree (at level 1) could be narrower.  IGNORED.
ARCH: Inode 6312183 extent tree (at level 1) could be narrower.  IGNORED.
ARCH: Inode 6312187 extent tree (at level 1) could be narrower.  IGNORED.
ARCH: Inode 6312189 extent tree (at level 1) could be narrower.  IGNORED.
ARCH: Inode 6312194 extent tree (at level 1) could be narrower.  IGNORED.
ARCH: Inode 6312198 extent tree (at level 1) could be narrower.  IGNORED.

     2011221 inodes used (8.77%, out of 22937600)
       18150 non-contiguous files (0.9%)
        1638 non-contiguous directories (0.1%)
             # of inodes with ind/dind/tind blocks: 0/0/0
             Extent depth histogram: 1720443/5610/8
    76197307 blocks used (83.05%, out of 91750400)
           0 bad blocks
          10 large files

     1501583 regular files
      182172 directories
           0 character device files
           0 block device files
           0 fifos
       70520 links
      327427 symbolic links (285122 fast symbolic links)
          30 sockets
------------
     2081732 files

However, after rebooting and opening Vivaldi, dmesg reported ext4 errors again:

[dom dez  1 07:48:29 2024] EXT4-fs error (device sda1): ext4_ext_check_inode:524: inode #2770363: comm ThreadPoolForeg: pblk 0 bad header/extent: invalid extent entries - magic f30a, entries 1, max 4(4), depth 0(0)
[dom dez  1 07:48:29 2024] EXT4-fs error (device sda1): ext4_ext_check_inode:524: inode #2770363: comm ThreadPoolForeg: pblk 0 bad header/extent: invalid extent entries - magic f30a, entries 1, max 4(4), depth 0(0)
[dom dez  1 07:48:29 2024] EXT4-fs error (device sda1): ext4_ext_check_inode:524: inode #2770363: comm ThreadPoolForeg: pblk 0 bad header/extent: invalid extent entries - magic f30a, entries 1, max 4(4), depth 0(0)
[dom dez  1 07:48:29 2024] EXT4-fs error (device sda1): ext4_ext_check_inode:524: inode #2770363: comm ThreadPoolForeg: pblk 0 bad header/extent: invalid extent entries - magic f30a, entries 1, max 4(4), depth 0(0)
[dom dez  1 07:48:29 2024] EXT4-fs error (device sda1): ext4_ext_check_inode:524: inode #2770363: comm ThreadPoolForeg: pblk 0 bad header/extent: invalid extent entries - magic f30a, entries 1, max 4(4), depth 0(0)
[dom dez  1 07:48:29 2024] EXT4-fs error (device sda1): ext4_ext_check_inode:524: inode #2770363: comm ThreadPoolForeg: pblk 0 bad header/extent: invalid extent entries - magic f30a, entries 1, max 4(4), depth 0(0)
[dom dez  1 07:48:29 2024] EXT4-fs error (device sda1): ext4_ext_check_inode:524: inode #2770363: comm ThreadPoolForeg: pblk 0 bad header/extent: invalid extent entries - magic f30a, entries 1, max 4(4), depth 0(0)
[dom dez  1 07:48:29 2024] EXT4-fs error (device sda1): ext4_ext_check_inode:524: inode #2770363: comm ThreadPoolForeg: pblk 0 bad header/extent: invalid extent entries - magic f30a, entries 1, max 4(4), depth 0(0)
[dom dez  1 07:48:29 2024] EXT4-fs error (device sda1): ext4_ext_check_inode:524: inode #2770363: comm ThreadPoolForeg: pblk 0 bad header/extent: invalid extent entries - magic f30a, entries 1, max 4(4), depth 0(0)
[dom dez  1 07:48:29 2024] EXT4-fs error (device sda1): ext4_ext_check_inode:524: inode #2770363: comm ThreadPoolForeg: pblk 0 bad header/extent: invalid extent entries - magic f30a, entries 1, max 4(4), depth 0(0)

Offline

#8 Yesterday 11:58:16

seth
Member
Registered: 2012-09-03
Posts: 58,964

Re: Arch runs fsck before almost every boot

Size is ok, ftr. 350G ./. 370G is probably just the 2^10/10^3 factor.

So

ARCH: Inode 2770363, i_size is 17592186044416, should be 17592186044416.  FIXED.

is

[dom dez  1 07:48:29 2024] EXT4-fs error (device sda1): ext4_ext_check_inode:524: inode #2770363: comm ThreadPoolForeg: pblk 0 bad header/extent: invalid extent entries - magic f30a, entries 1, max 4(4), depth 0(0)

Begging the question: if that was fixed, why is it acting up again? Also it's always the exact same inode.
=> https://wiki.archlinux.org/title/SMART - "smartctl -a /dev/sda"
https://wiki.archlinux.org/title/Identi … _bad_block
https://wiki.archlinux.org/title/Badblo … stem_check

But take this one at a time, don't rush through the various steps and let's first see the smart data.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#9 Yesterday 12:00:02

Strangiato
Member
Registered: 2020-01-10
Posts: 406

Re: Arch runs fsck before almost every boot

smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.1-arch1-1] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     Asgard AS1TS3-S7
Serial Number:    202209291131
LU WWN Device Id: 5 000000 00000281a
Firmware Version: SN09553
User Capacity:    1.024.209.543.168 bytes [1,02 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
TRIM Command:     Available, deterministic, zeroed
Device is:        Not in smartctl database 7.3/5528
ATA Version is:   ACS-4 (minor revision not indicated)
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sun Dec  1 08:59:14 2024 -03
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x02) Offline data collection activity
                                        was completed without error.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever 
                                        been run.
Total time to complete Offline 
data collection:                (   33) seconds.
Offline data collection
capabilities:                    (0x7b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine 
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        (   2) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x0031) SCT Status supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 20
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0013   100   100   050    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       4119
 12 Power_Cycle_Count       0x0012   100   100   000    Old_age   Always       -       473
167 Unknown_Attribute       0x0022   100   100   000    Old_age   Always       -       0
168 Unknown_Attribute       0x0012   100   100   000    Old_age   Always       -       0
169 Unknown_Attribute       0x0013   100   100   010    Pre-fail  Always       -       0
171 Unknown_Attribute       0x0032   000   000   000    Old_age   Always       -       0
172 Unknown_Attribute       0x0032   000   000   000    Old_age   Always       -       0
173 Unknown_Attribute       0x0012   200   200   000    Old_age   Always       -       68735139989
174 Unknown_Attribute       0x0022   100   100   000    Old_age   Always       -       20
175 Program_Fail_Count_Chip 0x0022   100   100   010    Old_age   Always       -       0
180 Unused_Rsvd_Blk_Cnt_Tot 0x0033   100   100   000    Pre-fail  Always       -       510
187 Reported_Uncorrect      0x0032   100   000   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0012   100   100   000    Old_age   Always       -       82
194 Temperature_Celsius     0x0022   032   032   000    Old_age   Always       -       32 (Min/Max 22/35)
206 Unknown_SSD_Attribute   0x0032   200   200   000    Old_age   Always       -       16
207 Unknown_SSD_Attribute   0x0032   200   200   000    Old_age   Always       -       239
208 Unknown_SSD_Attribute   0x0032   200   200   000    Old_age   Always       -       149
209 Unknown_SSD_Attribute   0x0032   200   200   000    Old_age   Always       -       1
210 Unknown_Attribute       0x0032   200   200   000    Old_age   Always       -       2878
211 Unknown_Attribute       0x0032   200   200   000    Old_age   Always       -       2516
231 Unknown_SSD_Attribute   0x0023   091   091   005    Pre-fail  Always       -       9
241 Total_LBAs_Written      0x0032   100   100   000    Old_age   Always       -       14704
242 Total_LBAs_Read         0x0032   100   100   000    Old_age   Always       -       14548
243 Unknown_Attribute       0x0032   050   050   000    Old_age   Always       -       4294311925
245 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       41

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

The above only provides legacy SMART information - try 'smartctl -x' for more

Offline

#10 Yesterday 12:10:10

seth
Member
Registered: 2012-09-03
Posts: 58,964

Re: Arch runs fsck before almost every boot

There're a bunch of "unkonwn" parameters that *might* be concerning (but we don't know what they actually indicate…)
=> Run a long test, you can do that in the background while the system is operating and check in once in a while.
When it's done, re-check the smart data (post it, there might either have been an error or movement in one or some of the "unknown" attributes)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#11 Yesterday 12:20:56

Strangiato
Member
Registered: 2020-01-10
Posts: 406

Re: Arch runs fsck before almost every boot

"Long" test only takes 2 minutes, according to smartctl.

Output after the "long" test:

$ sudo smartctl -a /dev/sda
smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.1-arch1-1] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     Asgard AS1TS3-S7
Serial Number:    202209291131
LU WWN Device Id: 5 000000 00000281a
Firmware Version: SN09553
User Capacity:    1.024.209.543.168 bytes [1,02 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
TRIM Command:     Available, deterministic, zeroed
Device is:        Not in smartctl database 7.3/5528
ATA Version is:   ACS-4 (minor revision not indicated)
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Sun Dec  1 09:18:58 2024 -03
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x02) Offline data collection activity
                                        was completed without error.
                                        Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0) The previous self-test routine completed
                                        without error or no self-test has ever 
                                        been run.
Total time to complete Offline 
data collection:                (   33) seconds.
Offline data collection
capabilities:                    (0x7b) SMART execute Offline immediate.
                                        Auto Offline data collection on/off support.
                                        Suspend Offline collection upon new
                                        command.
                                        Offline surface scan supported.
                                        Self-test supported.
                                        Conveyance Self-test supported.
                                        Selective Self-test supported.
SMART capabilities:            (0x0003) Saves SMART data before entering
                                        power-saving mode.
                                        Supports SMART auto save timer.
Error logging capability:        (0x01) Error logging supported.
                                        General Purpose Logging supported.
Short self-test routine 
recommended polling time:        (   2) minutes.
Extended self-test routine
recommended polling time:        (   2) minutes.
Conveyance self-test routine
recommended polling time:        (   2) minutes.
SCT capabilities:              (0x0031) SCT Status supported.
                                        SCT Feature Control supported.
                                        SCT Data Table supported.

SMART Attributes Data Structure revision number: 20
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0013   100   100   050    Pre-fail  Always       -       0
  9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       4120
 12 Power_Cycle_Count       0x0012   100   100   000    Old_age   Always       -       473
167 Unknown_Attribute       0x0022   100   100   000    Old_age   Always       -       0
168 Unknown_Attribute       0x0012   100   100   000    Old_age   Always       -       0
169 Unknown_Attribute       0x0013   100   100   010    Pre-fail  Always       -       0
171 Unknown_Attribute       0x0032   000   000   000    Old_age   Always       -       0
172 Unknown_Attribute       0x0032   000   000   000    Old_age   Always       -       0
173 Unknown_Attribute       0x0012   200   200   000    Old_age   Always       -       68735139989
174 Unknown_Attribute       0x0022   100   100   000    Old_age   Always       -       20
175 Program_Fail_Count_Chip 0x0022   100   100   010    Old_age   Always       -       0
180 Unused_Rsvd_Blk_Cnt_Tot 0x0033   100   100   000    Pre-fail  Always       -       510
187 Reported_Uncorrect      0x0032   100   000   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0012   100   100   000    Old_age   Always       -       82
194 Temperature_Celsius     0x0022   034   034   000    Old_age   Always       -       34 (Min/Max 22/35)
206 Unknown_SSD_Attribute   0x0032   200   200   000    Old_age   Always       -       16
207 Unknown_SSD_Attribute   0x0032   200   200   000    Old_age   Always       -       239
208 Unknown_SSD_Attribute   0x0032   200   200   000    Old_age   Always       -       149
209 Unknown_SSD_Attribute   0x0032   200   200   000    Old_age   Always       -       1
210 Unknown_Attribute       0x0032   200   200   000    Old_age   Always       -       2880
211 Unknown_Attribute       0x0032   200   200   000    Old_age   Always       -       2517
231 Unknown_SSD_Attribute   0x0023   091   091   005    Pre-fail  Always       -       9
241 Total_LBAs_Written      0x0032   100   100   000    Old_age   Always       -       14704
242 Total_LBAs_Read         0x0032   100   100   000    Old_age   Always       -       14549
243 Unknown_Attribute       0x0032   050   050   000    Old_age   Always       -       4294311925
245 Unknown_Attribute       0x0032   100   100   000    Old_age   Always       -       43

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error       00%      4120         -

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

The above only provides legacy SMART information - try 'smartctl -x' for more

Offline

#12 Yesterday 12:33:22

seth
Member
Registered: 2012-09-03
Posts: 58,964

Re: Arch runs fsck before almost every boot

Only change is in

  9 Power_On_Hours          0x0012   100   100   000    Old_age   Always       -       4120
210 Unknown_Attribute       0x0032   200   200   000    Old_age   Always       -       2880
211 Unknown_Attribute       0x0032   200   200   000    Old_age   Always       -       2517

which is probably all uptime related.

Look for the affected block(s)

filefrag -v /home/stalker/.config/vivaldi/Default/DIPS-journal

and then try to rewrite it w/ hdparm, https://wiki.archlinux.org/title/Identi … _bad_block

Sanity check:

du -h /home/stalker/.config/vivaldi/Default/DIPS-journal

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#13 Yesterday 12:46:54

Strangiato
Member
Registered: 2020-01-10
Posts: 406

Re: Arch runs fsck before almost every boot

The affected block is not reported (I have renamed "vivaldi" folder to "vivaldi.old2"):

$ filefrag -v /home/stalker/.config/vivaldi.old2/Default/DIPS-journal
open: Structure needs cleaning

Edit:
Weird output of "DIPS-journal" in "ls -l":

$ ls -l /home/stalker/.config/vivaldi.old2/Default/
ls: cannot access '/home/stalker/.config/vivaldi.old2/Default/DIPS-journal': Structure needs cleaning
total 112712
drwx--S---+   4 stalker adm     4096 jul 17 12:51  AdBlockRules
-rw-------    1 stalker adm    16825 dez  1 08:02  AdBlockState
-rw-------    1 stalker adm    16825 dez  1 08:02  AdBlockState.bak
-rw-------    1 stalker adm    53248 jul 17 12:51 'Affiliation Database'
-rw-------    1 stalker adm        0 jul 17 12:51 'Affiliation Database-journal'
drwx--S---+   2 stalker adm     4096 dez  1 08:02  AutofillStrikeDatabase
drwx--S---+   3 stalker adm     4096 dez  1 08:02  blob_storage
-rw-------    1 stalker adm  4857758 dez  1 08:21  Bookmarks
-rw-------    1 stalker adm  4792025 dez  1 08:02  Bookmarks.bak
drwx--S---+   2 stalker adm     4096 dez  1 08:02  BudgetDatabase
-rw-------    1 stalker adm    49152 nov 11 20:44  Calendar
-rw-------    1 stalker adm        0 nov 11 20:44  Calendar-journal
drwx--S---+   2 stalker adm     4096 out 24 07:53  chrome_cart_db
drwx--S---+   2 stalker adm     4096 dez  1 08:02  ClientCertificates
drwx--S---+   2 stalker adm     4096 dez  1 08:02  commerce_subscription_db
-rw-------    1 stalker adm    32768 jul 17 12:51  Contacts
-rw-------    1 stalker adm        0 jul 17 12:51  Contacts-journal
-rw-------    1 stalker adm  3080192 dez  1 08:22  Cookies
-rw-------    1 stalker adm        0 dez  1 08:22  Cookies-journal
drwx--S---+   2 stalker adm     4096 out 24 07:53  coupon_db
drwx--S---+   2 stalker adm     4096 jul 17 12:51  DawnGraphiteCache
drwx--S---+   2 stalker adm     4096 jul 17 12:51  DawnWebGPUCache
-rw-------    1 stalker adm   360448 nov 24 17:32  DIPS
-??????????   ? ?       ?          ?            ?  DIPS-journal
drwx--S---+   2 stalker adm     4096 dez  1 08:02  discounts_db
drwx--S---+   6 stalker adm     4096 nov 24 15:47 'DNR Extension Rules'
-rw-------    1 stalker adm    20480 out 26 17:53 'Extension Cookies'
-rw-------    1 stalker adm        0 out 26 17:53 'Extension Cookies-journal'
drwx--S---+   2 stalker adm     4096 nov 28 20:06 'Extension Rules'
drwx--S---+  17 stalker adm     4096 nov 28 20:06  Extensions
drwx--S---+   2 stalker adm     4096 nov 28 20:06 'Extension Scripts'
drwx--S---+   3 stalker adm     4096 dez  1 08:02 'Extension State'
-rw-------    1 stalker adm 46563328 dez  1 08:21  Favicons
-rw-------    1 stalker adm        0 dez  1 08:21  Favicons-journal
drwx--S---+   4 stalker adm     4096 jul 17 12:51 'Feature Engagement Tracker'
drwx--S---+   3 stalker adm     4096 jul 17 13:01  feedv2
drwx--S---+   5 stalker adm     4096 nov 30 18:02 'File System'
drwx--S---+   3 stalker adm     4096 nov 11 15:22 'GCM Store'
drwx--S---+   2 stalker adm     4096 jul 17 12:51  GPUCache
-rw-------    1 stalker adm    16384 jul 17 12:51  heavy_ad_intervention_opt_out.db
-rw-------    1 stalker adm        0 jul 17 12:51  heavy_ad_intervention_opt_out.db-journal
-rw-------    1 stalker adm 45285376 dez  1 08:22  History
-rw-------    1 stalker adm        0 dez  1 08:22  History-journal
drwx--S---+  18 stalker adm    12288 dez  1 07:17  IndexedDB
-rw-------    1 stalker adm   106496 out 26 18:04  InterestGroups
drwx--S---+   3 stalker adm     4096 jul 17 12:51 'Local App Settings'
drwx--S---+  14 stalker adm     4096 nov 24 15:47 'Local Extension Settings'
drwx--S---+   3 stalker adm     4096 jul 17 12:51 'Local Storage'
-rw-------    1 stalker adm        0 jul 17 12:51  LOCK
-rw-------    1 stalker adm        0 dez  1 08:02  LOG
-rw-------    1 stalker adm    40960 nov 15 09:52 'Login Data'
-rw-------    1 stalker adm    40960 nov 19 17:27 'Login Data For Account'
-rw-------    1 stalker adm        0 nov 19 17:27 'Login Data For Account-journal'
-rw-------    1 stalker adm        0 nov 15 09:52 'Login Data-journal'
-rw-------    1 stalker adm        0 dez  1 07:48  LOG.old
-rw-------    1 stalker adm    28672 jul 17 12:51  MailSearchDB
-rw-------    1 stalker adm        0 jul 17 12:51  MailSearchDB-journal
drwx--S---+   3 stalker adm     4096 jul 17 13:31 'Managed Extension Settings'
-rw-------    1 stalker adm   110592 nov 30 18:24  MediaDeviceSalts
-rw-------    1 stalker adm        0 nov 30 18:24  MediaDeviceSalts-journal
-rw-------    1 stalker adm   106496 dez  1 08:22 'Network Action Predictor'
-rw-------    1 stalker adm        0 dez  1 08:22 'Network Action Predictor-journal'
-rw-------    1 stalker adm   111402 dez  1 08:22 'Network Persistent State'
-rw-------    1 stalker adm  4316145 nov 11 18:43 'Network Persistent State.bad'
-rw-------    1 stalker adm      756 jul 17 13:13  Notes
drwx--S---+   2 stalker adm     4096 dez  1 08:02  parcel_tracking_db
drwx--S---+   2 stalker adm     4096 dez  1 08:02  PersistentOriginTrials
drwx--S---+   2 stalker adm     4096 dez  1 08:02 'Platform Notifications'
-rw-------    1 stalker adm   325924 dez  1 08:22  Preferences
-rw-------    1 stalker adm   883040 nov 11 18:42  Preferences.bad
-rw-rw-rw-    1 stalker adm       33 jul 17 12:51  PreferredApps
-rw-------    1 stalker adm    20480 jul 27 21:32  PrivateAggregation
-rw-------    1 stalker adm        0 jul 27 21:32  PrivateAggregation-journal
-rw-rw-rw-    1 stalker adm      168 jul 17 12:51  README
-rw-------    1 stalker adm  1343488 dez  1 08:22 'Reporting and NEL'
-rw-------    1 stalker adm        0 dez  1 08:22 'Reporting and NEL-journal'
-rw-------    1 stalker adm    20480 out 24 07:54 'Safe Browsing Cookies'
-rw-------    1 stalker adm        0 out 24 07:54 'Safe Browsing Cookies-journal'
-rw-------    1 stalker adm        2 dez  1 08:02 'SCT Auditing Pending Reports'
-rw-------    1 stalker adm       95 jul 17 12:51 'Secure Preferences'
drwx--S---+   5 stalker adm     4096 jul 17 13:30 'Service Worker'
drwx--S---+   2 stalker adm     4096 dez  1 08:22  Sessions
drwx--S---+   2 stalker adm     4096 dez  1 08:03 'Session Storage'
drwx--S---+   3 stalker adm     4096 jul 17 12:51 'Shared Dictionary'
drwx--S---+   3 stalker adm     4096 dez  1 08:02  shared_proto_db
-rw-------    1 stalker adm    36864 nov 30 23:05  SharedStorage
-rw-------    1 stalker adm    20480 jul 17 17:01  Shortcuts
-rw-------    1 stalker adm        0 jul 17 17:01  Shortcuts-journal
drwx--S---+   2 stalker adm     4096 dez  1 08:02 'Site Characteristics Database'
drwx--S---+   3 stalker adm     4096 jul 17 12:51  Storage
drwx--S---+   2 stalker adm     4096 nov 20 11:25 'Sync App Settings'
drwx--S---+   3 stalker adm     4096 dez  1 08:18 'Sync Data'
drwx--S---+   2 stalker adm     4096 jul 17 13:13  SyncedFiles
drwx--S---+   8 stalker adm     4096 nov 30 18:03 'Sync Extension Settings'
-rw-------    1 stalker adm    20480 nov 30 19:16 'Top Sites'
-rw-------    1 stalker adm        0 nov 30 19:16 'Top Sites-journal'
-rw-------    1 stalker adm      905 ago 28 10:42  translatehistory.json
-rw-------    1 stalker adm    37315 dez  1 08:22  TransportSecurity
-rw-------    1 stalker adm       38 dez  1 08:02  trusted_vault.pb
-rw-------    1 stalker adm    36864 nov 24 12:07 'Trust Tokens'
-rw-------    1 stalker adm        0 nov 24 12:07 'Trust Tokens-journal'
drwx--S---+   2 stalker adm     4096 dez  1 08:03  VideoDecodeStats
-rw-rw-rw-    1 stalker adm  2097040 dez  1 08:21 'Visited Links'
drwx--S---+   2 stalker adm     4096 nov 26 07:52  VivaldiDirectMatchIcons
drwx--S---+   2 stalker adm     4096 dez  1 07:21  VivaldiThumbnails
-rw-------    1 stalker adm   294912 nov 30 23:09 'Web Data'
-rw-------    1 stalker adm        0 nov 30 23:09 'Web Data-journal'
drwx--S---+ 202 stalker adm     4096 nov 30 18:24  WebStorage

Last edited by Strangiato (Yesterday 12:50:49)

Offline

#14 Yesterday 19:24:26

seth
Member
Registered: 2012-09-03
Posts: 58,964

Re: Arch runs fsck before almost every boot

For reference: https://forum.vivaldi.net/topic/103472/ … opening/16

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#15 Yesterday 19:55:42

Strangiato
Member
Registered: 2020-01-10
Posts: 406

Re: Arch runs fsck before almost every boot

Details in Vivaldi forum:

@Strangiato so to sum up (as I interpret) the debugfs output:

the file spans 8 blocks (4kB → minimal EXT4 block size)
it (also!) has a size of 16TiB and
its first (and only!) extent starts at (ext4-file-)block offset 4294967295.
Not sure what the original error was but I think:

somthing™ in file system internals wrote uint32 (-1) to the EXTENTS list
an inconsistency was detected (somehow), the file system was marked dirty
e2fsck "discovers" this (invalid!) block in the EXTENTS list
and "fixes" the file size based on that new "information"
→ (last_block + 1) * block_size
→ (4294967295 + 1) * 4096
→ 17592186044416
You could save this thing for posterity.
Or to have a good example in which error condition the fixup approach in e2fsck definitely behaves pathologically at the moment.

But I think more interesting would be which part of ext4 driver code was responsible for this (alleged) -1 to end up in the f***ing EXTENDS list. ?

For you personally:
I have no idea if the state of block 84024050 is correct at the moment.
Or if it is even a valid position on your partition.
If not, this may be to origin of the whole issue:
EXT4 may consider /dev/sda1 larger than it actually is according to file system table.
And there was an (uncaught) error when trying to write past the end of the device.

So no idea what could go wrong when you try to get rid of the file using debugfs operations. ?

Something extremely weird happened to my ext4 file system.

Offline

#16 Yesterday 20:23:46

seth
Member
Registered: 2012-09-03
Posts: 58,964

Re: Arch runs fsck before almost every boot

My money was on the smart data, but it looks ok.

* Do you apply an overly aggressive trimming strategy?
* Does the drive fail at times, maybe because of https://wiki.archlinux.org/title/Power_ … Management (many drives default to med_power_with_dipmsince a couple of kernel versions, but probably should not)
* Are there firmware updates for the drive available?

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#17 Yesterday 20:36:37

Strangiato
Member
Registered: 2020-01-10
Posts: 406

Re: Arch runs fsck before almost every boot

trimming is set with "discard" parameter in /etc/fstab

$ cat /etc/fstab
# /dev/sda1 LABEL=ARCH
UUID=4c1b8d88-ae03-4daa-9733-103cfeffdd81       /               ext4            rw,relatime,discard     0 1
#UUID=d7916482-6106-47c1-86b8-fdd50739e2f7 none swap defaults 0 0
LABEL=DADOS /mnt/DADOS ext4 user,nosuid,nodev,nofail,discard,x-gvfs-show,x-systemd.required-by=smb.service 0 0

LABEL=WD /mnt/WD ext4 user,nosuid,nodev,nofail,x-gvfs-show,x-systemd.required-by=smb.service 0 0
LABEL=2TB /mnt/2TB ext4 user,nosuid,nodev,nofail,x-gvfs-show,x-systemd.required-by=smb.service 0 0

#ntfs3
LABEL=WIN10 /mnt/WIN10 ntfs3 user,nosuid,nodev,nofail,discard,x-gvfs-show,uid=1003,windows_names,x-systemd.required-by=smb.service 0 0

#ntfs-3g
#LABEL=WIN10 /mnt/WIN10 ntfs-3g nosuid,nodev,nofail,x-gvfs-show,uid=1003,x-systemd.required-by=smb.service 0 0

The drive is 1 year old, it has never failed so far.

My SATA Active Link Power Management settings:

$ grep . /sys/class/scsi_host/host*/link_power_management_policy
/sys/class/scsi_host/host0/link_power_management_policy:med_power_with_dipm
/sys/class/scsi_host/host1/link_power_management_policy:med_power_with_dipm
/sys/class/scsi_host/host2/link_power_management_policy:med_power_with_dipm
/sys/class/scsi_host/host3/link_power_management_policy:med_power_with_dipm
/sys/class/scsi_host/host4/link_power_management_policy:med_power_with_dipm
/sys/class/scsi_host/host5/link_power_management_policy:med_power_with_dipm

Last edited by Strangiato (Yesterday 20:37:20)

Offline

#18 Yesterday 21:06:21

seth
Member
Registered: 2012-09-03
Posts: 58,964

Re: Arch runs fsck before almost every boot

Try "medium_power" and consider https://wiki.archlinux.org/title/Solid_ … iodic_TRIM but that's of course guesswork - it's hard to tell what corrupted the filesystem, but likely a lower layer (ie. issues w/ the drive)
Maybe your older journal show issues reg. sda 

sudo journalctl -g sda

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

#19 Yesterday 21:25:17

Strangiato
Member
Registered: 2020-01-10
Posts: 406

Re: Arch runs fsck before almost every boot

Previously I forgot to say that there is no firmware update for this drive.

Probably this bug was caused by a power outage. I'm not sure though.

The output of your command:
https://0x0.st/X7sQ.txt

OK, now I have replaced the "discard" parameter in /etc/fstab with fstrim.timer.

And I have set "medium_power":

$ grep . /sys/class/scsi_host/host*/link_power_management_policy
/sys/class/scsi_host/host0/link_power_management_policy:medium_power
/sys/class/scsi_host/host1/link_power_management_policy:medium_power
/sys/class/scsi_host/host2/link_power_management_policy:medium_power
/sys/class/scsi_host/host3/link_power_management_policy:medium_power
/sys/class/scsi_host/host4/link_power_management_policy:medium_power
/sys/class/scsi_host/host5/link_power_management_policy:medium_power

Offline

#20 Yesterday 21:34:08

seth
Member
Registered: 2012-09-03
Posts: 58,964

Re: Arch runs fsck before almost every boot

Journl only goes 5 days back and is full of the known error, but if there was a power outage this might indeed just be it.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Online

Pages: 1

Board footer

Powered by FluxBB