From: Kai Krakow <hurikhan77+btrfs@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Error from Trying to Mount Btrfs
Date: Wed, 13 Nov 2013 09:27:40 +0100 [thread overview]
Message-ID: <sopbla-03g.ln1@hurikhan77.spdns.de> (raw)
In-Reply-To: 1382915825.53433.YahooMailNeo@web125705.mail.ne1.yahoo.com
gatlin sullivan <gatlinsullivan@yahoo.com> schrieb:
> I have the attached error from trying to mount btrfs on external hard
> drive. The F.S. was my primary system, then I dd'd it to an external and
> reinstalled Fedora.
>
[...]
>
> What should I do?
>
> Appreciatively, Gatlin.
>
> P.S.
> This file system is very important to me becasue it has a large collection
> of songs.
>
> [root@dell-studio-1555 ~]# dmesg | tail
> [ 1773.320077] btrfs: open_ctree failed
> [ 1800.704035] mce: [Hardware Error]: Machine check events logged
> [ 1969.644418] CPU0: Core temperature above threshold, cpu clock throttled
> (total events = 42644)
> [ 1969.645068] CPU0: Core temperature/speed normal
> [ 1979.367137] device label fedora devid 1 transid 115316 /dev/sdb3
> [ 1979.369388] btrfs: superblock checksum mismatch
> [ 1979.374137] btrfs: open_ctree failed
> [ 2145.217088] device label fedora devid 1 transid 115316 /dev/sdb3
> [ 2145.229732] btrfs: superblock checksum mismatch
> [ 2145.234772] btrfs: open_ctree failed
Is that system overclocked? If yes, I suppose something bad happened to your
data during dd and it is just borked now.
Another idea: After dd, did you recreate the original fs so it got a new
uuid? Otherwise your system may now see the same uuid in two places.
Regards,
Kai
next prev parent reply other threads:[~2013-11-13 8:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-27 23:17 Error from Trying to Mount Btrfs gatlin sullivan
2013-11-13 8:27 ` Kai Krakow [this message]
2013-11-13 12:52 ` Duncan
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=sopbla-03g.ln1@hurikhan77.spdns.de \
--to=hurikhan77+btrfs@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/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).