harmakhis Posted January 25, 2020 Share #1 Posted January 25, 2020 hi, my server stopped during file moving beetween hdds it results in crashed volume, no repair button and big red button if you need to to that on synology they said "you cant repair it yourself call technical" yeah yeah yeah i will do that....lol in fact, you can, if you are experienced first, i read that, but no effect for me and commands dont runs on me http://www.vsam.pro/crashed-synology-volume-and-how-to-restore-ds415-play/ after, i read BTRFS wiki https://btrfs.wiki.kernel.org/index.php/Btrfsck you need to sign root user, and make sudo commands so i made it, go to ssh after activated it on DSM, search your volumes in /etc/fstab mine was volume 1 who crashed, mounted on /dev/md2 as the volume is crashed its unmounted so you can proceed, it will not run on mounted volumes they are busy i used this to repair the volume, answer "yes" when it ask to delete root logs tree sudo btrfs check --repair /dev/md2 it needs time to repair, it will make messages as incorrect checksum and repair file system when its finished reboot the system as DSM can restart service and mount volume by itsefl but its done its usually as the well known FS2CK command used by linux users when file system is corrupted hope it helps ;-) 1 Quote Link to comment Share on other sites More sharing options...
supermounter Posted April 10, 2020 Share #2 Posted April 10, 2020 Hello @harmakhis, in my case when I do the check --repair, he can't setup extent tree, setup the device tree and can't open the file system. /# btrfs check --repair /dev/vg1000/lv enabling repair mode parent transid verify failed on 394340270080 wanted 940895 found 940897 parent transid verify failed on 394340270080 wanted 940895 found 940897 parent transid verify failed on 394340270080 wanted 940895 found 940897 parent transid verify failed on 394340270080 wanted 940895 found 940897 Ignoring transid failure Couldn't setup extent tree parent transid verify failed on 394340270080 wanted 940895 found 940897 Ignoring transid failure Couldn't setup device tree extent buffer leak: start 394340171776 len 16384 extent buffer leak: start 394340171776 len 16384 Couldn't open file system any advise or other possibility ? Quote Link to comment Share on other sites More sharing options...
Napalmd Posted June 19, 2020 Share #3 Posted June 19, 2020 This is happening to me to. I'm seeing a lot of crashed btrfs volumes. is this a general problem? All drives are fine but btrfs volume crashed and mounts only read only. tried the repair but does not repair. 1 Quote Link to comment Share on other sites More sharing options...
IG-88 Posted June 20, 2020 Share #4 Posted June 20, 2020 18 hours ago, Napalmd said: This is happening to me to. I'm seeing a lot of crashed btrfs volumes. is this a general problem? All drives are fine but btrfs volume crashed and mounts only read only. tried the repair but does not repair. can't be a general problem, lots of xpenology and synology users with btrfs and i dont see then complaining synology had lots of updates related to btrfs over the years (as all linux distributions) make sure you use a recent version of dsm to minimize "known" problems also look for other sources of trouble like ram errors, psu stability, suspicious capacitors, hdd errors (check s.m.a.r.t.) file corruption is often related to hardware problems, can be software bugs in btrfs itself but thats not as likely as hardware trouble Quote Link to comment Share on other sites More sharing options...
Napalmd Posted June 20, 2020 Share #5 Posted June 20, 2020 I have another server an hp microserver gen8 with dsm 6.1 with btrfs for more than a year and never got any problem. this one is an older board with the more recent dsm 6.2.2. I now see that there is already dsm 6.2.3. maybe I'll try it. I tested memory for 2hours and no problems, now the server is doing a raid resync because it wasn't responding after I rebooted it. anyway I started a post, if you could check the logs I'll appreciate it. Quote Link to comment Share on other sites More sharing options...
IG-88 Posted June 20, 2020 Share #6 Posted June 20, 2020 10 hours ago, Napalmd said: now the server is doing a raid resync because it wasn't responding after I rebooted it. so a disk droped from the raid? check the logs that not normal Quote Link to comment Share on other sites More sharing options...
Napalmd Posted June 20, 2020 Share #7 Posted June 20, 2020 no. all disks are fine. I already had bad drives in the past but replaced them with no problems. this time was that i could not enter on the server by ssh or browser so I did a reset Quote Link to comment Share on other sites More sharing options...
flyride Posted June 21, 2020 Share #8 Posted June 21, 2020 Something in here might help you. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.