mrpeabody Posted November 13, 2019 Share #1 Posted November 13, 2019 Hello, Below is what I am getting while trying to repair my crashed volume using SSH. There is no repair option via the GUI. The Volume is the only part I see with any errors. Any help would be much appreciated. I have search and got the command below to resolve it , but as you can see it does not work. sudo e2fsck -ccDfttvy -C 0 /dev/vg1/volume_1 e2fsck 1.42.6 (21-Sep-2012) ext2fs_open2: Bad magic number in super-block e2fsck: Superblock invalid, trying backup blocks... e2fsck: Bad magic number in super-block while trying to open /dev/vg1/volume_1 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> Quote Link to comment Share on other sites More sharing options...
mrpeabody Posted November 14, 2019 Author Share #2 Posted November 14, 2019 Am I not able to repair my volume? Quote Link to comment Share on other sites More sharing options...
jensmander Posted November 14, 2019 Share #3 Posted November 14, 2019 3 hours ago, mrpeabody said: Am I not able to repair my volume? First: please be calm and wait for an answer from other forum members. There's no need to post another answer within a few hours to push your thread. Regarding your problem: please describe your setup. Which RAID type did you set up? SHR? RAID X? Filesystem? Quote Link to comment Share on other sites More sharing options...
bearcat Posted November 14, 2019 Share #4 Posted November 14, 2019 14 hours ago, mrpeabody said: If the device is valid and it really contains an ext2 filesystem Are you sure you are not using ext4 (or Btrfs)? This guide might help if you are using ext4. Quote Link to comment Share on other sites More sharing options...
mrpeabody Posted November 14, 2019 Author Share #5 Posted November 14, 2019 It was btrfs Quote Link to comment Share on other sites More sharing options...
flyride Posted November 14, 2019 Share #6 Posted November 14, 2019 6 hours ago, mrpeabody said: It was btrfs Then using an ext filesystem utility (e2fsck) is ill advised. btrfs really doesn't have any user-accessible repair options in Synology. It's mostly designed for self-healing and then if that doesn't work, Synology remote access recovery. Here's a data recovery thread from awhile back. If you want better advice, post some screenshots or more information about your issue. 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.