Error from Trying to Mount Btrfs

Error from Trying to Mount Btrfs

[gatlin sullivan]

[-- Attachment #1: Type: text/plain, Size: 495 bytes --]

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.


I tried to follow https://btrfs.wiki.kernel.org/index.php/Problem_FAQ#Filesystem_can.27t_be_mounted_by_label. I used "# btrfs device scan --all-devices" before attempting to mount.

 
What should I do?

Appreciatively, Gatlin.

P.S.
This file system is very important to me becasue it has a large collection of songs.

[-- Attachment #2: ErrorMessage.png --]
[-- Type: image/png, Size: 30930 bytes --]

[-- Attachment #3: ErrorMessage.txt --]
[-- Type: text/plain, Size: 1339 bytes --]

Error mounting /dev/sdb3 at /run/media/gatlibs/fedora: Command-line `mount -t "btrfs" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdb3" "/run/media/gatlibs/fedora"' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/sdb3,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.
       
       
[root@dell-studio-1555 ~]# mount -t "btrfs" -o recovery "/dev/sdb3" "/run/media/gatlibs/fedora"
mount: wrong fs type, bad option, bad superblock on /dev/sdb3,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.
[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

Re: Error from Trying to Mount Btrfs

[Kai Krakow]

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

Re: Error from Trying to Mount Btrfs

[Duncan]

gatlin sullivan posted on Sun, 27 Oct 2013 16:17:05 -0700 as excerpted:

> 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.
> 
> 
> I tried to follow
> https://btrfs.wiki.kernel.org/index.php/
Problem_FAQ#Filesystem_can.27t_be_mounted_by_label.
> I used "# btrfs device scan --all-devices" before attempting to mount.
> 
> 
> What should I do?
> 
> Appreciatively, Gatlin.
> 
> P.S.
> This file system is very important to me becasue it has a large
> collection of songs.

Commenting on that P.S.:

Of course if you've read the wiki you know this, but it's worth repeating 
for others who may come across this in their googles, etc...

As noted both on the wiki and in description for the kernel's btrfs 
option itself, btrfs remains classified as an experimental filesystem, 
suitable only for testing with data that you don't care about losing, 
either because it's well backed up to tested usable backups (preferably 
on something more stable than btrfs), or because it's low-value data you 
don't particularly care about losing if the test goes wrong and btrfs 
eats your data for breakfast in the first place.

IOW, importance is relative, and relative to the value of the time it 
would have taken to research the filesystem and ensure backups 
appropriate to the importance of the data, if you didn't do that research 
and have those backups, by definition your time saved in skipping that 
was more important to you than the potential loss of that data on what 
you would have known if you /really/ cared about the data you put on it, 
was an experimental filesystem unfit to the purpose you evidently used it 
for.

So you saved the time on the research and backups because you considered 
that more important than the data, and are now paying the tradeoff cost 
for that time saved with the potential loss of the obviously relatively 
unimportant data.  No big deal, since self-evidently that time was more 
important to you than the data you were risking by not spending it.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman