md0上设置超级块标志”

有电源故障，现在我的mdadmarrays有问题。

sudo mdadm -D / dev / md0 [hodge @ hodge-fs〜] $ sudo mdadm -D / dev / md0 / dev / md0：版本：0.90创build时间：星期日4月25日01:39:25 2010 Raid Level：raid5 Array大小：8790815232（8383.57 GiB 9001.79 GB）使用开发大小：1465135872（1397.26 GiB 1500.30 GB）Raid设备：7设备总数：7首选次要：0持久性：超级块持久性

Update Time : Sat Aug 7 19:10:28 2010 State : clean, degraded, recovering Active Devices : 6 Working Devices : 7 Failed Devices : 0 Spare Devices : 1 Layout : left-symmetric Chunk Size : 128K Rebuild Status : 10% complete UUID : 44a8f730:b9bea6ea:3a28392c:12b22235 (local to host hodge-fs) Events : 0.1307608 Number Major Minor RaidDevice State 0 8 81 0 active sync /dev/sdf1 1 8 97 1 active sync /dev/sdg1 2 8 113 2 active sync /dev/sdh1 3 8 65 3 active sync /dev/sde1 4 8 49 4 active sync /dev/sdd1 7 8 33 5 spare rebuilding /dev/sdc1 6 8 16 6 active sync /dev/sdb

sudo mount -a

 [hodge@hodge-fs ~]$ sudo mount -a mount: wrong fs type, bad option, bad superblock on /dev/md0, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so

sudo fsck.ext4 / dev / md0

 [hodge@hodge-fs ~]$ sudo fsck.ext4 /dev/md0 e2fsck 1.41.12 (17-May-2010) fsck.ext4: Group descriptors look bad... trying backup blocks... /dev/md0: recovering journal fsck.ext4: unable to set superblock flags on /dev/md0

sudo dumpe2fs / dev / md0 | grep -i超级块

 [hodge@hodge-fs ~]$ sudo dumpe2fs /dev/md0 | grep -i superblock dumpe2fs 1.41.12 (17-May-2010) Primary superblock at 0, Group descriptors at 1-524 Backup superblock at 32768, Group descriptors at 32769-33292 Backup superblock at 98304, Group descriptors at 98305-98828 Backup superblock at 163840, Group descriptors at 163841-164364 Backup superblock at 229376, Group descriptors at 229377-229900 Backup superblock at 294912, Group descriptors at 294913-295436 Backup superblock at 819200, Group descriptors at 819201-819724 Backup superblock at 884736, Group descriptors at 884737-885260 Backup superblock at 1605632, Group descriptors at 1605633-1606156 Backup superblock at 2654208, Group descriptors at 2654209-2654732 Backup superblock at 4096000, Group descriptors at 4096001-4096524 Backup superblock at 7962624, Group descriptors at 7962625-7963148 Backup superblock at 11239424, Group descriptors at 11239425-11239948 Backup superblock at 20480000, Group descriptors at 20480001-20480524 Backup superblock at 23887872, Group descriptors at 23887873-23888396 Backup superblock at 71663616, Group descriptors at 71663617-71664140 Backup superblock at 78675968, Group descriptors at 78675969-78676492 Backup superblock at 102400000, Group descriptors at 102400001-102400524 Backup superblock at 214990848, Group descriptors at 214990849-214991372 Backup superblock at 512000000, Group descriptors at 512000001-512000524 Backup superblock at 550731776, Group descriptors at 550731777-550732300 Backup superblock at 644972544, Group descriptors at 644972545-644973068 Backup superblock at 1934917632, Group descriptors at 1934917633-1934918156

sudo e2fsck -b 32768 / dev / md0

 [hodge@hodge-fs ~]$ sudo e2fsck -b 32768 /dev/md0 e2fsck 1.41.12 (17-May-2010) /dev/md0: recovering journal e2fsck: unable to set superblock flags on /dev/md0

sudo dmesg | 尾巴

 [hodge@hodge-fs ~]$ sudo dmesg | tail EXT4-fs (md0): ext4_check_descriptors: Checksum for group 0 failed (59837!=29115) EXT4-fs (md0): group descriptors corrupted! EXT4-fs (md0): ext4_check_descriptors: Checksum for group 0 failed (59837!=29115) EXT4-fs (md0): group descriptors corrupted!

请帮忙！！！

从您的描述和错误，它在我看来好像有一些严重的数据损坏问题。请记住，RAID可以防止一个非常特殊的问题。有限的磁盘故障。停电不受保护; 这就是为什么你使用UPS和备份以及使用RAID。

对我来说看起来很奇怪的是在RAID设备列表中包含/dev/sdb而不是/dev/sdb1 。这是正确的，还是最后一个字符被切断？

以防万一，我会尝试其余的备份超级块。

除此之外，你可能会寻找磁盘恢复软件。理想情况下，您将能够获取磁盘当前状态的备份映像; 这将减less进一步更改将无法挽回的数据损坏的可能性。

你的RAID设置有几个缺陷：

磁盘数量≥3-4的RAID-5相当脆弱。一个磁盘被踢出，您的数据有问题。
不使用写意图位图是危险的，只会使项目＃1变差。
备用可以更合理地用作主RAID-6或RAID-10 …

（我可以添加小块大小，而不是使用LVM-2作为缺点，当然，它们并不强烈地影响整体状态。）

现在 – 不要对数组（fsck等）做任何事情，直到完全修复。我强烈build议你不要自行恢复数据。你最好找一个专家（当然，如果你看重他们的话）。