Can't mount disks

Support
1

Hi there, I wonder if anyone could give me a hand trying to sort this issue - I’m pretty new to this so any help would be appreciated - I had suspected drive failure, as shortly after mounting the two drives within my raid 1 pool, I would get the error shown below.

If anyone could help me make sense of this it would be appreciated.

IMG_0494.PNG750×1334 2.37 MB

2

Soooo this is a btrfs packing up on you because it has a corrupted transaction that it’s trying to commit to disk every time you try to mount it. This corrupt transactions are usually caused by qgroups … but hey.

Right now, it’s time for you to employ a “rescue as much as you can before touching anything” strategy. If:

  • you had a backup and everything is there - just nuke this FS and start fresh
  • there is no backup, you need to consider using a “btrfs restore” to get as much data as possible out of this FS.
  • if you don’t have a spare storage you can dedicate for backup - well you are in pickle … it will be very hard to rescue you self out of this … I tried for a month … and ended up putting in extra drives in, restoring what ever I could and nuking the FS.
1 Like
3

Okay thank you!! Advice appreciated!

4

Any idea what would cause me to get this error when trying to use the restore function?

image.jpg4032×3024 2.82 MB

5

can you provide output of
mount

it should tell you what’s mounted where. So far I see you’ve got a fs called “Backup” (be wary of capital B) and you try to backup to “/mnt2/backup”

another thing is that there might be some stuff in this folder alredy and restore refuses to put stuff there

also you should use few more options with your restore. First of all try -vd which will make it verbose and dry run, ie it will just show you what it would do.

6

I think simply missing the capital B may have been the problem, the dry run appears to be working correctly now.
Will Update when it finishes which may be some time.

Thanks

7

Just going on a hunch here - if you are very new to console and linux/unix: BE VERY CAREFULL ! all posix systems are generally case sensitive, and a single typo can cost you a lot of data / time / headache !

as a simple example you can just write:
dd if=/dev/zero of=/dev/sda
and your disk (sda) will be completely overwritten with zeros
typing those:
:(){ :|: & };:
gives you a “fork bomb”

so a lot of powerful stuff is at your fingertips, and even seasoned users tend to shoot them self in the foot with typos !