我最近创建了一个 raid 文件系统，遇到了一些问题，运气不太好。我开始为一个磁盘创建一个 raid0，打算之后再使用它。我的数据在两个驱动器上，只有一个备用驱动器可以从 ntfs windows 迁移到 linux raid ext4。
我创建了 raid 并在其中复制了数据，一切都按计划进行。之后，我将空磁盘添加到 raid 中，该 raid 变为 raid4，而不是我预期的 raid0。我想让它填充驱动器，然后更改 raid 级别以继续迁移（这是个人数据，因此可用性和延迟不是问题）。
但是，我遇到了一次断电，Debian 机器崩溃了。我无法重新启动服务器，因为它抱怨磁盘损坏（系统未安装在 raid 上，但显然它仍然已损坏）。
我重新安装了服务器，并尝试在其上创建一个新的 raid 阵列作为 raid0，这显然是可行的。但是，安装失败，并显示以下错误消息：
mount: wrong fs type, bad option, bad superblock on /dev/md0, missing codepage or helper program, or other error.
以下是一些有趣的输入：
mdadm -D /dev/md0
dev/md0:
Version : 1.2
Creation Time : Wed Apr 12 18:46:15 2023
Raid Level : raid0
Array Size : 35156391936 (33527.75 GiB 36000.15 GB)
Raid Devices : 2
Total Devices : 2
Persistence : Superblock is persistent
Update Time : Wed Apr 12 18:46:15 2023
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
Layout : -unknown-
Chunk Size : 512K
Consistency Policy : none
Name : debianServer:0 (local to host debianServer)
UUID : 694acc71:c3c4a319:fffd737c:97d86f63
Events : 0
Number Major Minor RaidDevice State
0 8 16 0 active sync /dev/sdb
1 8 32 1 active sync /dev/sdc
mdadm --misc --检查 /dev/sdb
/dev/sdb:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : 694acc71:c3c4a319:fffd737c:97d86f63
Name : debianServer:0 (local to host debianServer)
Creation Time : Wed Apr 12 18:46:15 2023
Raid Level : raid0
Raid Devices : 2
Avail Dev Size : 35156391936 (16763.87 GiB 18000.07 GB)
Data Offset : 264192 sectors
Super Offset : 8 sectors
Unused Space : before=264112 sectors, after=0 sectors
State : clean
Device UUID : a6be797a:9864c7de:a2eaad96:d5960132
Update Time : Wed Apr 12 18:46:15 2023
Bad Block Log : 512 entries available at offset 8 sectors
Checksum : 74880b2d - correct
Events : 0
Chunk Size : 512K
Device Role : Active device 0
Array State : AA ('A' == active, '.' == missing, 'R' == replacing)
mdadm --misc --检查 /dev/sdc
/dev/sdc:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : 694acc71:c3c4a319:fffd737c:97d86f63
Name : debianServer:0 (local to host debianServer)
Creation Time : Wed Apr 12 18:46:15 2023
Raid Level : raid0
Raid Devices : 2
Avail Dev Size : 35156391936 (16763.87 GiB 18000.07 GB)
Data Offset : 264192 sectors
Super Offset : 8 sectors
Unused Space : before=264112 sectors, after=0 sectors
State : clean
Device UUID : 4ff549bf:6b4012ef:6dea5c3c:5163822f
Update Time : Wed Apr 12 18:46:15 2023
Bad Block Log : 512 entries available at offset 8 sectors
Checksum : 6cd2e9f1 - correct
Events : 0
Chunk Size : 512K
Device Role : Active device 1
Array State : AA ('A' == active, '.' == missing, 'R' == replacing)
mdadm --assemble --scan --verbose
mdadm: looking for devices for /dev/md/0
mdadm: No super block found on /dev/sda3 (Expected magic a92b4efc, got a4862c0a)
mdadm: no RAID superblock on /dev/sda3
mdadm: No super block found on /dev/sda2 (Expected magic a92b4efc, got 0000041f)
mdadm: no RAID superblock on /dev/sda2
mdadm: No super block found on /dev/sda1 (Expected magic a92b4efc, got 00000000)
mdadm: no RAID superblock on /dev/sda1
mdadm: No super block found on /dev/sda (Expected magic a92b4efc, got 00000000)
mdadm: no RAID superblock on /dev/sda
mdadm: /dev/sdc is identified as a member of /dev/md/0, slot 1.
mdadm: /dev/sdb is identified as a member of /dev/md/0, slot 0.
mdadm: added /dev/sdc to /dev/md/0 as 1
mdadm: added /dev/sdb to /dev/md/0 as 0
mdadm: /dev/md/0 has been started with 2 drives.
猫/proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md0 : active raid0 sdb[0] sdc[1]
35156391936 blocks super 1.2 512k chunks
unused devices: <none>
fdisk -l
Disk /dev/sdb: 16.37 TiB, 18000207937536 bytes, 35156656128 sectors
Disk model: ASM1153E
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/sdc: 16.37 TiB, 18000207937536 bytes, 35156656128 sectors
Disk model: M000J-2TV103
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/md0: 32.74 TiB, 36000145342464 bytes, 70312783872 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes
e2fsck /dev/md0
e2fsck 1.46.2 (28-Feb-2021)
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/md0
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
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>
or
e2fsck -b 32768 <device>
消息 |尾巴
[12414.953934] pcieport 0000:00:1c.0: device [8086:4dbc] error status/mask=00000001/00002000
[12414.953938] pcieport 0000:00:1c.0: [ 0] RxErr
[12437.084602] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[12437.084619] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[12437.084625] pcieport 0000:00:1c.0: device [8086:4dbc] error status/mask=00000001/00002000
[12437.084629] pcieport 0000:00:1c.0: [ 0] RxErr
[12451.086860] pcieport 0000:00:1c.0: AER: Corrected error received: 0000:00:1c.0
[12451.086878] pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
[12451.086883] pcieport 0000:00:1c.0: device [8086:4dbc] error status/mask=00000001/00002000
[12451.086888] pcieport 0000:00:1c.0: [ 0] RxErr
mdadm -E /dev/md0
mdadm: No md superblock detected on /dev/md0.
编辑-添加
mke2fs -nv /dev/md0
mke2fs 1.46.2 (28-Feb-2021)
mke2fs: Size of device (0x20bdefe00 blocks) /dev/md0 too big to be expressed
in 32 bits using a blocksize of 4096.
我的问题是：
- 我可以恢复文件系统并恢复数据以继续吗？
- 如果没有，我可以通过其他方式恢复数据吗？
非常感谢你的帮助 ！
干杯，