All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Ruehl <chris.ruehl@gtsys.com.hk>
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] F2fs failed on fresh installation 1st boot
Date: Sat, 12 Sep 2020 12:20:17 +0800	[thread overview]
Message-ID: <b278baec-65df-312e-5d26-89dc1ea25c86@gtsys.com.hk> (raw)

Hi,

we encounter random crash on new installed partition at
first boot.
Kernel: 4.9.235
Kernel: 5.4.64 (blow)
f2fs-tools: 1.4.0

[    1.520829] mmc1: new DDR MMC card at address 0001 
 

[    1.526223] mmcblk1: mmc1:0001 DG4008 7.28 GiB 
 

[    1.531037] mmcblk1boot0: mmc1:0001 DG4008 partition 1 4.00 MiB 
 

[    1.537244] mmcblk1boot1: mmc1:0001 DG4008 partition 2 4.00 MiB 
 

[    1.543416] mmcblk1rpmb: mmc1:0001 DG4008 partition 3 4.00 MiB, chardev 
(247:0) 

[    1.554445]  mmcblk1: p1 p2 
 

[    1.572323] F2FS-fs (mmcblk1p2): Mismatch valid blocks 512 vs. 508 
 

[    1.578552] F2FS-fs (mmcblk1p2): Failed to initialize F2FS segment manager 
(-117) 

[    1.586374] VFS: Cannot open root device "mmcblk1p2" or unknown-block(179,2): 
error -117 

[    1.594496] Please append a correct "root=" boot option; here are the 
available partitions:

I reboot into the installation SDCard and run the fsck.f2fs with no errors

root@ba81ba8b6125:~# fsck.f2fs /dev/mmcblk1p2
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 7520000 (3671 MB)
Info: MKFS version
   "Linux version 5.4.64 (xxx) (gcc version 8.3.0 (Debian 8.3.0-2)) #74 SMP Sat 
Sep 12 10:56:24 HKT 2020"
Info: FSCK version
   from "Linux version 5.4.64 (xxx) (gcc version 8.3.0 (Debian 8.3.0-2)) #74 SMP 
Sat Sep 12 10:56:24 HKT 2020"
     to "Linux version 5.4.64 (xxx) (gcc version 8.3.0 (Debian 8.3.0-2)) #74 SMP 
Sat Sep 12 10:56:24 HKT 2020"
Info: superblock features = 0 :
Info: superblock encrypt level = 0, salt = 00000000000000000000000000000000
Info: total FS sectors = 7520000 (3671 MB)
Info: CKPT version = 14f987b7
Info: Checked valid nat_bits in checkpoint
Info: checkpoint state = 1c5 :  trimmed nat_bits crc compacted_summary unmount

[FSCK] Unreachable nat entries                        [Ok..] [0x0]
[FSCK] SIT valid block bitmap checking                [Ok..]
[FSCK] Hard link checking for regular file            [Ok..] [0x7]
[FSCK] valid_block_count matching with CP             [Ok..] [0x1c29f]
[FSCK] valid_node_count matching with CP (de lookup)  [Ok..] [0x596b]
[FSCK] valid_node_count matching with CP (nat lookup) [Ok..] [0x596b]
[FSCK] valid_inode_count matched with CP              [Ok..] [0x5953]
[FSCK] free segment_count matched with CP             [Ok..] [0x625]
[FSCK] next block offset is free                      [Ok..]
[FSCK] fixing SIT types
[FSCK] other corrupted bugs                           [Ok..]

Done: 5.592724 secs

Regards
Chris


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

             reply	other threads:[~2020-09-12  4:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-12  4:20 Chris Ruehl [this message]
2020-09-12  6:19 ` [f2fs-dev] F2fs failed on fresh installation 1st boot Chris Ruehl
2020-09-14  7:30   ` Chao Yu
2020-09-14  7:38     ` Chris Ruehl
2020-09-14  7:55       ` Chao Yu
2020-09-17  5:56         ` Chris Ruehl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b278baec-65df-312e-5d26-89dc1ea25c86@gtsys.com.hk \
    --to=chris.ruehl@gtsys.com.hk \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.