1

A day ago, my SSD was perfectly usable. Then it suddenly corrupted my home filesystem, resulting in the following fsck output at the most verbose debugging level:

Info: Fix the reported corruption.
Info: Force to fix corruption
Info: Force to fix corruption
Info: Debug level = 3
    Info: can't find /sys, assuming normal block device
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 536870912 (262144 MB)
Info: MKFS version
  "Linux version 5.4.0-72-generic (buildd@lcy01-amd64-019) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #80-Ubuntu SMP Mon Apr 12 17:35:00 UTC 2021"
Info: FSCK version
  from "Linux version 5.4.0-74-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #83-Ubuntu SMP Sat May 8 02:35:39 UTC 2021"
    to "Linux version 6.2.0-20-generic (buildd@lcy02-amd64-035) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU Binutils for Ubuntu) 2.40) #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr  6 07:48:48 UTC 2023"
Info: superblock features = 0 : 
Info: superblock encrypt level = 0, salt = 00000000000000000000000000000000

+--------------------------------------------------------+
| Super block                                            |
+--------------------------------------------------------+
magic                               [0xf2f52010 : 4076150800]
major_ver                           [0x       1 : 1]
volum_name                          []
minor_ver                           [0x       b : 11]
log_sectorsize                      [0x       9 : 9]
log_sectors_per_block               [0x       3 : 3]
log_blocksize                       [0x       c : 12]
log_blocks_per_seg                  [0x       9 : 9]
segs_per_sec                        [0x       1 : 1]
secs_per_zone                       [0x       1 : 1]
checksum_offset                     [0x       0 : 0]
block_count                         [0x 4000000 : 67108864]
section_count                       [0x   1fe85 : 130693]
segment_count                       [0x   1ffff : 131071]
segment_count_ckpt                  [0x       2 : 2]
segment_count_sit                   [0x       a : 10]
segment_count_nat                   [0x      6e : 110]
segment_count_ssa                   [0x     100 : 256]
segment_count_main                  [0x   1fe85 : 130693]
segment0_blkaddr                    [0x     200 : 512]
cp_blkaddr                          [0x     200 : 512]
sit_blkaddr                         [0x     600 : 1536]
nat_blkaddr                         [0x    1a00 : 6656]
ssa_blkaddr                         [0x    f600 : 62976]
main_blkaddr                        [0x   2f600 : 194048]
root_ino                            [0x       3 : 3]
node_ino                            [0x       1 : 1]
meta_ino                            [0x       2 : 2]
cp_payload                          [0x       0 : 0]
crc                                 [0x       0 : 0]
version                       Linux version 5.4.0-74-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #83-Ubuntu SMP Sat May 8 02:35:39 UTC 2021
Info: total FS sectors = 536870912 (262144 MB)
    Invalid CP CRC offset: 0
    Invalid CP CRC offset: 0
[f2fs_do_mount:3512] Can't find valid checkpoint

What are my options to restore the filesystem to a working condition? I am willing to write code to restore the superblock and/or checkpoints, including to assemble a valid checkpoint out of existing invalid checkpoints and existing superblock. Other filesystems in the drive are fine.

Improve this question
2
  • OMG! Reading f2fs-tools' changelog ("fsck.f2fs checks file system consistency, but does not repair a broken file system yet.") and considering the date of last commit… do not suggest a tremendous optimism for getting a "canonical" answer… Good luck to you anyway. Commented Oct 2, 2023 at 17:26
  • I tried to email them, but the mailing list seems to have eaten the mail. Someone else has actually emailed the devs on a similar issue and was told to email the devs ASAP if a similar issue occurs again. The type of corruption I have would have been salvageable if f2fs-tools was able to salvage the system into a valid statep out of multiple invalid checkpoints and a partially valid superblock. Commented Oct 11, 2023 at 21:23

0

Reset to default

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.