我们的一台 QNAP NAS 在磁盘警报时发生故障，因此它们都在阵列上工作/可访问。我正在尝试恢复数据，因为 QNAP NAS 既没有启动，也没有响应（无论有没有磁盘）。
我使用 Ubuntu 实时磁盘启动了所有硬盘管理命令。我不确定磁盘 1 发生了什么，因为它显示HPFS/NTFS/exFAT位于一个磁盘的第 3 个分区上。此外，UUID* 假定为一些唯一的数字，现在显示为 **0000:0000....随着突袭等级：未知。
以下是我收集的一些有用的输出。
fdisk -l
root@ubuntu:/home/ubuntu# fdisk -l | more
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
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 identifier: 0x00009a4a
Device Boot Start End Blocks Id System
/dev/sda1 40 1060289 530125 83 Linux
/dev/sda2 1060296 2120579 530142 83 Linux
/dev/sda3 2120584 1952507969 975193693 7 HPFS/NTFS/exFAT
/dev/sda4 1952507976 1953503999 498012 83 Linux
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
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 identifier: 0x000ac6cc
Device Boot Start End Blocks Id System
/dev/sdb1 40 1060289 530125 83 Linux
/dev/sdb2 1060296 2120579 530142 83 Linux
/dev/sdb3 2120584 1952507969 975193693 83 Linux
/dev/sdb4 1952507976 1953503999 498012 83 Linux
Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
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 identifier: 0x000b7ac5
Device Boot Start End Blocks Id System
/dev/sdc1 40 1060289 530125 83 Linux
/dev/sdc2 1060296 2120579 530142 83 Linux
/dev/sdc3 2120584 1952507969 975193693 83 Linux
/dev/sdc4 1952507976 1953503999 498012 83 Linux
Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
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 identifier: 0x000b7ac5
Device Boot Start End Blocks Id System
/dev/sdc1 40 1060289 530125 83 Linux
/dev/sdc2 1060296 2120579 530142 83 Linux
/dev/sdc3 2120584 1952507969 975193693 83 Linux
/dev/sdc4 1952507976 1953503999 498012 83 Linux
Disk /dev/sdd: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
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 identifier: 0x000d2a20
Device Boot Start End Blocks Id System
/dev/sdd1 40 1060289 530125 83 Linux
/dev/sdd2 1060296 2120579 530142 83 Linux
/dev/sdd3 2120584 1952507969 975193693 83 Linux
/dev/sdd4 1952507976 1953503999 498012 83 Linux
mdmadm 检查
root@ubuntu:/home/ubuntu# mdadm -E /dev/sd[abcd]3
/dev/sda3:
Magic : a92b4efc
Version : 0.90.00
UUID : 00000000:00000000:00000000:00000000
Creation Time : Fri Sep 25 07:04:44 2015
Raid Level : -unknown-
Raid Devices : 0
Total Devices : 3
Preferred Minor : 0
Update Time : Fri Sep 25 07:19:04 2015
State : active
Active Devices : 0
Working Devices : 3
Failed Devices : 0
Spare Devices : 3
Checksum : 8f463afd - correct
Events : 1
Number Major Minor RaidDevice State
this 2 8 3 2 spare /dev/sda3
0 0 8 35 0 spare /dev/sdc3
1 1 8 19 1 spare /dev/sdb3
2 2 8 3 2 spare /dev/sda3
/dev/sdb3:
Magic : a92b4efc
Version : 0.90.00
UUID : 00000000:00000000:00000000:00000000
Creation Time : Fri Sep 25 07:04:44 2015
Raid Level : -unknown-
Raid Devices : 0
Total Devices : 3
Preferred Minor : 0
Update Time : Fri Sep 25 07:19:04 2015
State : active
Active Devices : 0
Working Devices : 3
Failed Devices : 0
Spare Devices : 3
Checksum : 8f463b19 - correct
Events : 1
Number Major Minor RaidDevice State
this 0 8 35 0 spare /dev/sdc3
0 0 8 35 0 spare /dev/sdc3
1 1 8 19 1 spare /dev/sdb3
2 2 8 3 2 spare /dev/sda3
/dev/sdc3:
Magic : a92b4efc
Version : 0.90.00
UUID : 00000000:00000000:00000000:00000000
Creation Time : Fri Sep 25 07:04:44 2015
Raid Level : -unknown-
Raid Devices : 0
Total Devices : 3
Preferred Minor : 0
Update Time : Fri Sep 25 07:19:04 2015
State : active
Active Devices : 0
Working Devices : 3
Failed Devices : 0
Spare Devices : 3
Checksum : 8f463b0b - correct
Events : 1
Number Major Minor RaidDevice State
this 1 8 19 1 spare /dev/sdb3
0 0 8 35 0 spare /dev/sdc3
1 1 8 19 1 spare /dev/sdb3
2 2 8 3 2 spare /dev/sda3
/dev/sdd3:
Magic : a92b4efc
Version : 0.90.00
UUID : 00000000:00000000:00000000:00000000
Creation Time : Fri Sep 25 09:28:22 2015
Raid Level : -unknown-
Raid Devices : 0
Total Devices : 1
Preferred Minor : 0
Update Time : Fri Sep 25 09:31:03 2015
State : active
Active Devices : 0
Working Devices : 1
Failed Devices : 0
Spare Devices : 1
Checksum : 8f467b40 - correct
Events : 1
Number Major Minor RaidDevice State
this 0 8 3 0 spare /dev/sda3
0 0 8 3 0 spare /dev/sda3
mdadm 配置
root@ubuntu:/home/ubuntu# cat /etc/mdadm/mdadm.conf
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#
# by default (built-in), scan all partitions (/proc/partitions) and all
# containers for MD superblocks. alternatively, specify devices to scan, using
# wildcards if desired.
#DEVICE partitions containers
# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes
# automatically tag new arrays as belonging to the local system
HOMEHOST <system>
# instruct the monitoring daemon where to send mail alerts
MAILADDR root
# definitions of existing MD arrays
ARRAY /dev/md4 UUID=a5ef83a2:3df739b9:7e77f235:9827a98f
ARRAY /dev/md0 UUID=00000000:00000000:00000000:00000000
spares=3
ARRAY /dev/md9 UUID=c39aa918:f8de04d3:bb375993:177a40db
ARRAY /dev/md4 UUID=bb500a60:f1f7edde:07b598b5:09c70531
spares=1
ARRAY /dev/md0 UUID=00000000:00000000:00000000:00000000
spares=1
ARRAY /dev/md13 UUID=62a22532:1a265501:07a38901:1b2b353e
# This file was auto-generated on Sat, 26 Sep 2015 05:23:53 +0000
# by mkconf $Id$
发出并汇编命令后执行 mdstat
root@ubuntu:/home/ubuntu# cat /proc/mdstat
Personalities :
unused devices: <none>
有人能指出我在这里做错了什么，或者我遗漏了什么吗？
我真的被这个问题难住了，想知道是否有人可以通过拉回 RAID 来帮助检索数据。
答案1
好吧，我不想永远把这个问题悬而未决。所以，我发了一个答案来结束这个问题。
这完全被我的一个同事搞砸了，我刚拍下它就差点被撕掉。由于使用了一些恢复应用程序，不知道驱动器实际上在 RAID 阵列上，它完全丢失了 ID 和奇偶校验。这得到了威联通技术人员在进行删除会话时。
但是，我只能看到 QNAP 相关数据，因为它们位于驱动器上的不同分区中。我能够组合 RAID 阵列并安装数据。
最终的结果是使用管理这--create可能会有所帮助，或者让我别无选择。但是，我没有成功，这几乎证明阵列丢失并且磁盘不见了。
别无选择，只能忍受痛苦。我在此结束我的讨论。
我使用过的完整研究和命令可以在“在 Ubuntu 12.04 上使用 mdmadm 修复损坏的 QNAP RAID5“。希望如果有人遇到这种情况，能够找到一两条线索。