luismoreira

Hello everyone, I'm a bit desperate here! My xpenolgy VM crashed after I copied all my data. I got a nasty Volume 1:crashed. I can get the results from cat /proc/mdstat and everything seems ok: ash-4.3# cat /proc/mdstat Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] [raidF1] md3 : active raid1 sdb3[0] 6249933824 blocks super 1.2 [1/1] md2 : active raid1 sda3[0] 16149504 blocks super 1.2 [1/1] md1 : active raid1 sda2[0] sdb2[1] 2097088 blocks [12/2] [UU__________] md0 : active raid1 sda1[0] sdb1[1] 2490176 blocks [12/2] [UU__________] and: ash-4.3# mdadm --detail /dev/md3 /dev/md3: Version : 1.2 Creation Time : Fri Jun 21 19:08:00 2019 Raid Level : raid1 Array Size : 6249933824 (5960.40 GiB 6399.93 GB) Used Dev Size : 6249933824 (5960.40 GiB 6399.93 GB) Raid Devices : 1 Total Devices : 1 Persistence : Superblock is persistent Update Time : Mon Jul 15 06:50:55 2019 State : clean Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 Name : LM_Server:3 (local to host LM_Server) UUID : 538bbadf:b8e76d4a:ae1e786d:6ae773a7 Events : 167 Number Major Minor RaidDevice State 0 8 19 0 active sync /dev/sdb3 ... but I can't get any return from vgdisplay: ash-4.3# lvm vgscan Reading all physical volumes. This may take a while... and I don't get anything else. I also tried: ash-4.3# mdadm --assemble --scan -v mdadm: looking for devices for further assembly mdadm: no recogniseable superblock on /dev/md3 mdadm: no recogniseable superblock on /dev/md2 mdadm: no recogniseable superblock on /dev/zram1 mdadm: no recogniseable superblock on /dev/zram0 mdadm: no recogniseable superblock on /dev/md1 mdadm: no recogniseable superblock on /dev/md0 mdadm: no recogniseable superblock on /dev/sdm3 mdadm: Cannot assemble mbr metadata on /dev/synoboot2 mdadm: Cannot assemble mbr metadata on /dev/synoboot1 mdadm: Cannot assemble mbr metadata on /dev/synoboot mdadm: /dev/sdb3 is busy - skipping mdadm: /dev/sdb2 is busy - skipping mdadm: /dev/sdb1 is busy - skipping mdadm: Cannot assemble mbr metadata on /dev/sdb mdadm: /dev/sda3 is busy - skipping mdadm: /dev/sda2 is busy - skipping mdadm: /dev/sda1 is busy - skipping mdadm: Cannot assemble mbr metadata on /dev/sda mdadm: No arrays found in config file or automatically And finaly: ash-4.3# btrfs check /dev/md3 checksum verify failed on 2953562390528 found E4E3BDB6 wanted 00000000 checksum verify failed on 2953562390528 found E4E3BDB6 wanted 00000000 checksum verify failed on 2953562390528 found E4E3BDB6 wanted 00000000 checksum verify failed on 2953562390528 found E4E3BDB6 wanted 00000000 bytenr mismatch, want=2953562390528, have=0 Couldn't read tree root Couldn't open file system But I don't know how to interpret it ... Anyone willing to give me a hand? I don't know what to do after this ...