So, dual-booting Windows and Linux inevitably has ended up in stuff breaking.
Looks like one of the two mdraid RAID0 disks got "initialized" under Windows 10 (my fault - I was attempting to add another disk for Windows with identical capacity) and now I'm seeing that my array disk is containing only a single 16MB Microsoft Reserved Partition, which, has resulted in a destroyed array.
The RAID0 mdraid array consisted of two 1TB disks (/dev/sdb and /dev/sdd):
❯ sudo mdadm -D /dev/md127
/dev/md127:
Version : 1.0
Raid Level : raid0
Total Devices : 1
Persistence : Superblock is persistent
State : inactive
Working Devices : 1
Name : any:data
UUID : e7ee729e:81c9fc54:9ef2cf45:8173dd35
Events : 0
Number Major Minor RaidDevice
- 8 16 - /dev/sdb
❯ sudo lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 1 238,5G 0 disk
├─sda1 8:1 1 1G 0 part /boot/efi
└─sda2 8:2 1 237,5G 0 part /
sdb 8:16 1 931,5G 0 disk
sdc 8:32 1 111,8G 0 disk
sdd 8:48 1 931,5G 0 disk
└─sdd1 8:49 1 16M 0 part
Fdisk output:
Disk /dev/sdb: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: ST1000DX001-1CM1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/sdb1 1 1953525167 1953525167 931,5G ee GPT
Partition 1 does not start on physical sector boundary.
Disk /dev/sdd: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: ST1000DM010-2EP1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: F6FFD6CE-CAB7-424A-ABB8-5A6D13E5B5D7
Device Start End Sectors Size Type
/dev/sdd1 34 32767 32734 16M Microsoft reserved
Partition 1 does not start on physical sector boundary.
This didn't work:
sudo mdadm --assemble --scan -v
mdadm: Cannot assemble mbr metadata on /dev/sdd
And inspecting it with mdadm doesn't seem to find anything either:
❯ sudo mdadm --examine /dev/sdd
/dev/sdd:
MBR Magic : aa55
Partition[0] : 4294967295 sectors at 1 (type ee)
❯ sudo mdadm --examine /dev/sdb
/dev/sdb:
Magic : a92b4efc
Version : 1.0
Feature Map : 0x0
Array UUID : e7ee729e:81c9fc54:9ef2cf45:8173dd35
Name : any:data
Creation Time : Fri Dec 4 18:03:31 2020
Raid Level : raid0
Raid Devices : 2
Avail Dev Size : 1953525144 sectors (931.51 GiB 1000.20 GB)
Super Offset : 1953525152 sectors
State : clean
Device UUID : f5682d8a:9d938fc3:1d6d9493:b13a34a9
Update Time : Fri Dec 4 18:03:31 2020
Bad Block Log : 512 entries available at offset -8 sectors
Checksum : e73a7989 - correct
Events : 0
Chunk Size : 64K
Device Role : Active device 0
Array State : AA ('A' == active, '.' == missing, 'R' == replacing)
GParted couldn't find anything either. I've done disk data and partition recovery in the past as well as RAID rescue, but never from a RAID0 array with one of the drives, effectively deleted. Is it even possible to recover a RAID0 from this state, or should I just throw in the towel?
User contributions licensed under CC BY-SA 3.0