I had a nas with a raid 0 configuration in it and it crashed...Apperently the 2 drives where still intact because i could read them properly with my linux machine.It was a raid config with 2 drives (1TB each) and they gave the following output when running the command (after i pluged them in my linux computer):mdadm --examine /dev/sd[fg]for the /dev/sdf drive:/dev/sdf:   MBR Magic : aa55Partition[0] :   1953520002 sectors at           63 (type fd)for the /dev/sdg drive:/dev/sdg:   MBR Magic : aa55Partition[0] :   1953520002 sectors at           63 (type fd)when I look at the partition on the 2 drives, I get:mdadm --examine /dev/sd[fg]1for /dev/sdf1:/dev/sdf1:          Magic : a92b4efc        Version : 0.90.00           UUID : 67b44c24:56edfa86:22f8d746:427f672b  Creation Time : Sun Jul 29 19:33:20 2012     Raid Level : raid0   Raid Devices : 2  Total Devices : 2Preferred Minor : 1    Update Time : Thu Jan  1 01:00:26 1970          State : active Active Devices : 2Working Devices : 2 Failed Devices : 0  Spare Devices : 0       Checksum : 1d5c49aa - correct         Events : 245     Chunk Size : 64K      Number   Major   Minor   RaidDevice State this     0       8        1        0      active sync    0     0       8        1        0      active sync    1     1       8       17        1      active syncand for the /dev /sdg1:/dev/sdg1:          Magic : a92b4efc        Version : 0.90.00           UUID : 67b44c24:56edfa86:22f8d746:427f672b  Creation Time : Sun Jul 29 19:33:20 2012     Raid Level : raid0   Raid Devices : 2  Total Devices : 2Preferred Minor : 1    Update Time : Thu Jan  1 01:00:26 1970          State : active Active Devices : 2Working Devices : 2 Failed Devices : 0  Spare Devices : 0       Checksum : 1d5c49bc - correct         Events : 245     Chunk Size : 64K      Number   Major   Minor   RaidDevice Statethis     1       8       17        1      active sync   0     0       8        1        0      active sync   1     1       8       17        1      active sync)I googled this problem and soon i got to the official wiki of mdadm for raid recovery:https://raid.wiki.kernel.org/index.php/RAID_RecoverySo I tried to recreate the raid array with the following command:(the labels to the drives changed because I plugged them out of the computer in the mean time... I'm sorry for the possible confussion)   ~ $ sudo mdadm --create -v --assume-clean --level=stripe --chunk=64 --raid-devices=2 /dev/md01 /dev/sdc1 /dev/sdb1mdadm: /dev/sdc1 appears to be part of a raid array:   level=raid0 devices=2 ctime=Sat Mar 11 17:50:56 2017mdadm: /dev/sdb1 appears to be part of a raid array:   level=raid0 devices=2 ctime=Sat Mar 11 17:50:56 2017Continue creating array? ymdadm: Defaulting to version 1.2 metadatamdadm: array /dev/md01 started.which gave the following result:~ $ sudo mdadm --detail /dev/md1/dev/md1:        Version : 1.2  Creation Time : Sat Mar 11 17:59:05 2017     Raid Level : raid0     Array Size : 1953257856 (1862.77 GiB 2000.14 GB)   Raid Devices : 2  Total Devices : 2    Persistence : Superblock is persistent    Update Time : Sat Mar 11 17:59:05 2017          State : clean  Active Devices : 2Working Devices : 2 Failed Devices : 0  Spare Devices : 0     Chunk Size : 64K           Name : PJT-ARCH-L:01  (local to host PJT-ARCH-L)           UUID : 13ea8db4:b275a220:32ec08dd:d8e2c9e6         Events : 0    Number   Major   Minor   RaidDevice State       0       8       17        0      active sync   /dev/sdb1       1       8       33        1      active sync   /dev/sdc1~ $ sudo mdadm --examine /dev/sdb1/dev/sdb1:          Magic : a92b4efc        Version : 1.2    Feature Map : 0x0     Array UUID : 13ea8db4:b275a220:32ec08dd:d8e2c9e6           Name : PJT-ARCH-L:01  (local to host PJT-ARCH-L)  Creation Time : Sat Mar 11 17:59:05 2017     Raid Level : raid0   Raid Devices : 2 Avail Dev Size : 1953257858 (931.39 GiB 1000.07 GB)    Data Offset : 262144 sectors   Super Offset : 8 sectors   Unused Space : before=262056 sectors, after=0 sectors          State : clean    Device UUID : b4f14492:722da49e:e2b92e7c:f7c24207    Update Time : Sat Mar 11 17:59:05 2017  Bad Block Log : 512 entries available at offset 72 sectors       Checksum : c25cb746 - correct         Events : 0     Chunk Size : 64K   Device Role : Active device 0   Array State : AA ('A' == active, '.' == missing, 'R' == replacing)~ $ sudo mdadm --examine /dev/sdc1/dev/sdc1:          Magic : a92b4efc        Version : 1.2    Feature Map : 0x0     Array UUID : 13ea8db4:b275a220:32ec08dd:d8e2c9e6           Name : PJT-ARCH-L:01  (local to host PJT-ARCH-L)  Creation Time : Sat Mar 11 17:59:05 2017     Raid Level : raid0   Raid Devices : 2 Avail Dev Size : 1953257858 (931.39 GiB 1000.07 GB)    Data Offset : 262144 sectors   Super Offset : 8 sectors   Unused Space : before=262056 sectors, after=0 sectors          State : clean    Device UUID : 6bd6a7e0:0455e3e9:8d5e82d3:62f2ca77    Update Time : Sat Mar 11 17:59:05 2017  Bad Block Log : 512 entries available at offset 72 sectors       Checksum : 23da97a8 - correct         Events : 0     Chunk Size : 64K   Device Role : Active device 1   Array State : AA ('A' == active, '.' == missing, 'R' == replacing)now fdisk -l returns the following output:Disk /dev/md1: 1.8 TiB, 2000136044544 bytes, 3906515712 sectorsUnits: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 512 bytesI/O size (minimum/optimal): 65536 bytes / 131072 bytesDisk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectorsUnits: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 512 bytesI/O size (minimum/optimal): 512 bytes / 512 bytesDisklabel type: dosDisk identifier: 0x00000000Device     Boot Start        End    Sectors   Size Id Type/dev/sdb1          63 1953520064 1953520002 931.5G fd Linux raid autodetectDisk /dev/sdc: 931.5 GiB, 1000204886016 bytes, 1953525168 sectorsUnits: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 512 bytesI/O size (minimum/optimal): 512 bytes / 512 bytesDisklabel type: dosDisk identifier: 0x00000000Device     Boot Start        End    Sectors   Size Id Type/dev/sdc1          63 1953520064 1953520002 931.5G fd Linux raid autodetectwhich looks good at the first sight, but there are no partitions in the new created /dev/md1 disk. :/  So it isn't possible to mount the created raid array.can someone tell me what I did wrong and/or how I can fix it? I hope to retrieve my data from the array if it would slightly be possible
mdadm recreating failed raid 0 array from crashed nas
linux;raid;mdadm