linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
To: linux-f2fs-devel@lists.sourceforge.net
Subject: f2fs not mountable: CRC validation failed
Date: Sun, 26 Mar 2017 22:12:03 +0200	[thread overview]
Message-ID: <20170326201203.GA9286@lazy.lzy> (raw)

Hi all,

I apologize in advance in case this is the
wrong place for support (if so, please
point me in the right direction).

I've an USB stick formatted with f2fs,
used under Linux on a RPi2.
To be clear, it is a USB device, not
an SD card.

After a crash, the USB stick is not mountable
any more.
There is no HW error on the stick.

A "fsck" returns, among other information:

[f2fs_crc_valid: 486] CRC validation failed: cal_crc = 3543933224, blk_crc = 719768680 buff_size = 0xffc
[f2fs_crc_valid: 486] CRC validation failed: cal_crc = 1071250051, blk_crc = 2385854943 buff_size = 0xffc
[f2fs_do_mount:2018] Can't find valid checkpoint

And it does not perform any check / repair.

I'm a bit puzzled, I wonder if there is way
to force a repair, partially could be OK too.

Clearly, "fsck.f2fs -f" did not work.

Any chance to save some data?

f2fs-tools is version 1.8.0 (I guess it's latest).

System is Fedora 25, the tool is self compiled.

Thanks a lot in advance, in case other information
are required, please let me know.

bye,

-- 

piergiorgio

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

             reply	other threads:[~2017-03-26 20:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-26 20:12 Piergiorgio Sartor [this message]
2017-03-26 23:45 ` f2fs not mountable: CRC validation failed Jaegeuk Kim
2017-03-27 17:37   ` Piergiorgio Sartor

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=20170326201203.GA9286@lazy.lzy \
    --to=piergiorgio.sartor@nexgo.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).