jehan

Members
  • Posts

    6
  • Joined

  • Last visited

jehan's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Ok - just to clearify: recovering the data from btrfs is my only option? No chance to restore from parity?
  2. I have not saved this diags before rebooting. I tried several things to get the data from the btrfs disk but without success. At the moment I'm running a "rescue chunk-recover -v". Here is what I tried so far: "btrfs restore -vi" parent transid verify failed on 7053440794624 wanted 12999 found 13003 parent transid verify failed on 7053440794624 wanted 12999 found 13003 parent transid verify failed on 7053440794624 wanted 12999 found 13003 Ignoring transid failure WARNING: could not setup extent tree, skipping it Couldn't setup device tree Could not open root, trying backup super "btrfs rescue super-recover" All supers are valid, no need to recover "btrfs rescue zero-log" parent transid verify failed on 7053440794624 wanted 12999 found 13003 parent transid verify failed on 7053440794624 wanted 12999 found 13003 parent transid verify failed on 7053440794624 wanted 12999 found 13003 Ignoring transid failure WARNING: could not setup extent tree, skipping it Couldn't setup device tree ERROR: could not open ctree "mount -t btrfs -o usebackuproot" wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error. dmesg while mounting with "usebackuproot": BTRFS warning (device sdb1): 'usebackuproot' is deprecated, use 'rescue=usebackuproot' instead BTRFS info (device sdb1): trying to use backup root at mount time BTRFS info (device sdb1): disk space caching is enabled BTRFS info (device sdb1): has skinny extents BTRFS info (device sdb1): flagging fs with big metadata feature BTRFS error (device sdb1): parent transid verify failed on 7053440794624 wanted 12999 found 13003 BTRFS error (device sdb1): parent transid verify failed on 7053440794624 wanted 12999 found 13003 BTRFS warning (device sdb1): couldn't read tree root BTRFS error (device sdb1): open_ctree failed
  3. Yes! I read the documentation and made the mistake anyway. Damn I was too sure of myself. Thank you - here are the diagnostics. FYI: at the time I downloaded the diagnostics only the 8TB parity and the new 4TB data drive are attached because I'm doing a "btrfs rescue chunk-recover" on the 8TB data drive. unraid-diagnostics-20210620-1152.zip
  4. I added a new drive and started the array with "parity is already valid". Unfortunately the disk was not precleared but formatted. I'm unsure what this does with the parity drive - if I understand you correctly I have no chance to restore the data from the parity, right? Concerning the post to the gurus: could you give me a hint how to reach them?
  5. In my case I had no problems with the dock, all disks are individually detected and all information like the serial number are detected also correctly. Attached you can find an example.
  6. Hi! I tested unraid with one 8TB btrfs data disk and one 8TB parity disk in a 5 bay orico usb case for nearly a month and all went very well. Yesterday I decided to add another 4TB btrfs data disk since the 8TB was nearly full. I rebuilt the parity from the 8TB data drive just the day before. Now - after starting the array with "Parity is already valid" the 8TB data disk was not mountable with these errors: BTRFS error (device sdb1): parent transid verify failed on 7053440794624 wanted 12999 found 13003 BTRFS error (device sdb1): parent transid verify failed on 7053440794624 wanted 12999 found 13003 BTRFS warning (device sdb1): couldn't read tree root BTRFS error (device sdb1): open_ctree failed To repair the 8TB data disk I tried several things without success so far (recover a btrfs partition). Next I took steps 1-3 from "Rebuilding a drive onto itself" in the docs to let the parity disk emulate the missing disc but after starting the array with the now missing 8TB disk I couldn't find the expected data under /mnt/user/[...] , only some directories but no files where visible. I tried this with and without the new attached 4TB drive. BTW: I always had to create a "New Config" because the distribution of disks to slots where always mixed up. Currently I'm running "btrfs rescue chunk-recover" on the 8TB disk and since this takes a very long time I decided to ask for help/alternatives in the unraid forum. My questions are: shouldn't the parity drive emulate the missing data drive after I removed the 8TB drive like I described before and what does it tells me if I only can see the directory structue in the emulatd drive - most likely all data lost? Is there any way to recover the data from the parity disk to the 8TB data disk? Any help is very apricated.