chickenstealers

Transition Members
  • Content Count

    12
  • Joined

  • Last visited

Everything posted by chickenstealers

  1. Restore is also doesn't work IPUserverOLD:~# btrfs restore /dev/md2 /volume2/volume1 parent transid verify failed on 165385699328 wanted 587257 found 587265 parent transid verify failed on 165385699328 wanted 587257 found 587265 parent transid verify failed on 165385699328 wanted 587257 found 587265 parent transid verify failed on 165385699328 wanted 587257 found 587265 Ignoring transid failure parent transid verify failed on 138367598592 wanted 587198 found 587196 parent transid verify failed on 138367598592 wanted 587198 found 587196 parent transid verify failed on 138367598592 wanted 58
  2. I mount to volume2 because volume2 has 1 TB space and works well IPUserverOLD:~# mkdir /volume2/volume1 IPUserverOLD:~# mount -o recovery,ro /dev/md2 /volume2/volume1 mount: wrong fs type, bad option, bad superblock on /dev/md2, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. and this is the dmesg | tail response IPUserverOLD:~# dmesg | tail [ 1516.107893] md/raid1:md2: syno_raid1_self_heal_set_and_submit_read_bio(1226): No suitable device for self healing retry read at round 2 at sector
  3. I have rebooted the NAS, but still the same got error IPUserverOLD:~# sudo mount -o recovery,ro /dev/md2 /volume1 mount: mount /dev/md2 on /volume1 failed: Stale file handle NFS is disable Also i'm using VMware ESXi 6.7 and install Xpenology inside ESXi using virtual drive
  4. Result of next command based on the thread you recommend btrfs check --init-extent-tree /dev/md2 root@IPUserverOLD:~# btrfs check --init-extent-tree /dev/md2 Syno caseless feature off. Checking filesystem on /dev/md2 UUID: 9021108d-e771-4e90-8b1c-ec4f5da3de97 Creating a new extent tree Failed to find [164311859200, 168, 16384] btrfs unable to find ref byte nr 165385601024 parent 0 root 1 owner 1 offset 0 Failed to find [406977511424, 168, 16384] btrfs unable to find ref byte nr 408051253248 parent 0 root 1 owner 0 offset 1 parent transid verify failed on 408051269632 wanted 587260 f
  5. Hi, thanks for your reply This is the result of first suggestion sudo mount -o recovery,ro /dev/md2 /volume1 IPUserverOLD:~# sudo mount -o recovery,ro /dev/md2 /volume1 mount: mount /dev/md2 on /volume1 failed: Stale file handle sudo btrfs rescue super /dev/md2 IPUserverOLD:~# sudo btrfs rescue super /dev/md2 All supers are valid, no need to recover sudo btrfs-find-root /dev/md2 root@IPUserverOLD:~# sudo btrfs-find-root /dev/md2 Superblock thinks the generation is 587261 Superblock thinks the level is 1 Found tree root at 165385601024 gen 587261 level 1 Well block 300
  6. My volume only contain 1 disk each IPUserverOLD:~# cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [raidF1] md2 : active raid1 sdb3[0] 1068919808 blocks super 1.2 [1/1] [U] md3 : active raid1 sdc3[0] 1068919808 blocks super 1.2 [1/1] [U] md1 : active raid1 sdb2[0] sdc2[1] 2097088 blocks [12/2] [UU__________] md0 : active raid1 sdb1[0] sdc1[1] 2490176 blocks [12/2] [UU__________] unused devices: <none> IPUserverOLD:~# mdadm --detail /dev/md2 /dev/md2: Version : 1.2 Creation Time : Fri Jun 21 11:03:51 2019
  7. Here is the result IPUserverOLD:~# vgchange -ay IPUserverOLD:~# vgdisplay -v Using volume group(s) on command line. No volume groups found. IPUserverOLD:~# mount -o clear_cache /dev/md2 /volume1 mount: mount /dev/md2 on /volume1 failed: Stale file handle IPUserverOLD:~# mount -o clear_cache /dev/vg1000/lv /volume1 mount: special device /dev/vg1000/lv does not exist Well i install xpenology using VMware ESXi 6.7 and my disk is virtual vmdk, i use two virtual disk 1TB each 1 for volume1 which is had problem with volume crash 1 for volume2 that is working
  8. IPUserverOLD:~# pvdisplay IPUserverOLD:~# btrfs check /dev/md2 Syno caseless feature off. Checking filesystem on /dev/md2 UUID: 9021108d-e771-4e90-8b1c-ec4f5da3de97 checking extents parent transid verify failed on 138367680512 wanted 587198 found 587196 parent transid verify failed on 138367680512 wanted 587198 found 587196 parent transid verify failed on 138367680512 wanted 587198 found 587196 parent transid verify failed on 138367680512 wanted 587198 found 587196 Ignoring transid failure leaf parent key incorrect 138367680512 bad block 138367680512 Errors found in extent allocation tree or c
  9. No It's btrfs filesystem not ext4 IPUserverOLD:~# btrfs restore /dev/md2 /volume1 parent transid verify failed on 138367598592 wanted 587198 found 587196 parent transid verify failed on 138367598592 wanted 587198 found 587196 parent transid verify failed on 138367598592 wanted 587198 found 587196 parent transid verify failed on 138367598592 wanted 587198 found 587196 Ignoring transid failure IPUserverOLD:~# mdadm --assemble --scan -v mdadm: looking for devices for further assembly mdadm: no recogniseable superblock on /dev/md2 mdadm: no recogniseable superblock on /dev/md3 mdadm: no recogn
  10. Hello everyone, Please Help, my xpenology has Volume 1 crashed error and all the data in it is not accessible How do i fix that? I install xpenology on ESXi 6.7 Here is the screenshot of the error
  11. Hi, Do you successfully manage to install Xpenology on Lenovo X3500 M5? I try to install DSM 6.2 but got error Hard disk not found