NAS540: Volume down, repairing failed, how to restore data?
Options
All Replies
-
Here it is, sir :~ # e2fsck -n /dev/md2e2fsck 1.42.12 (29-Aug-2014)Warning! /dev/md2 is in use.ext2fs_open2: Bad magic number in super-blocke2fsck: Superblock invalid, trying backup blocks...e2fsck: Bad magic number in super-block while trying to open /dev/md2The superblock could not be read or does not describe a valid ext2/ext3/ext4filesystem. If the device is valid and it really contains an ext2/ext3/ext4filesystem (and not swap or ufs or something else), then the superblockis corrupt, and you might try running e2fsck with an alternate superblock:e2fsck -b 8193 <device>ore2fsck -b 32768 <device>0
-
Good news!
I finally have my data back!
I tried to recover the superblock index with e2fsck using backups listed, but none of them worked
So I decided to come back to the old plan and try again logical devs combinations.
The procedure I followed is this one : 1) Deactivating the volume with vgchange -an 2) Stop md2 3) Create array with new combination
And when I arrived at C / B / D / A and rebooted, NAS is finally gives my data back.
I'm really happy now, thanks to everyone involved.
Good Luck and all the best!
0 -
Thanks ksr7. Your response helped me.0
Categories
- All Categories
- 398 Beta Program
- 2.1K Nebula
- 117 Nebula Ideas
- 83 Nebula Status and Incidents
- 5.2K Security
- 99 USG FLEX H Series
- 247 Security Ideas
- 1.3K Switch
- 69 Switch Ideas
- 923 WirelessLAN
- 35 WLAN Ideas
- 5.9K Consumer Product
- 212 Service & License
- 337 News and Release
- 71 Security Advisories
- 21 Education Center
- 5 [Campaign] Zyxel Network Detective
- 2.1K FAQ
- 1K Nebula FAQ
- 445 Security FAQ
- 238 Switch FAQ
- 213 WirelessLAN FAQ
- 47 Consumer Product FAQ
- 142 Service & License FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 72 About Community
- 62 Security Highlight