Encrypted RAID broken after change to windows partioning scheme

English Install/Boot/Login
1

I have (had) a RAID1 set-up. The RAID consists of 2 devices and I have applied encryption to the RAID.

Today I had to make a modification to my Windows partitioning scheme (dedicated disk). Booted Windows made the changes and rebooted. Modifications were made (the expected 3 steps). Reboot, check in Windows all seems fine.

I reboot my machine and I’m presented with the Luks prompt (expected). I provide the password and am presented with the maintenance prompt. This has happened before that the UUID changed, so I modify my crypttab to point to the new UUID. Reboot and no change.

It appears my encryption (and the data) is no more. OpenSUSE still recognizes that there is a RAID config, but the device does not want to mount.

Is there an option to have my data still (and how to access it) or is all the data lost?

2

I booted gparted live and gparted detects that /dev/md0 has no partition allocation. When I select one of the underlying devices it shows a key in the overview. Does that indicate that the data is still present, but my raid array is broken? If that would be the case, how to gain access to one of the drives?

3

Maybe they are expected to you, but we have no idea what you changed.

What does it mean? Dedicated for what?

There are multiple boot stages that may do it. You need to show facts - e.g. photo of the screen.

Show the command(s) you used to find out the need to do it and the commands you used to determine “the new UUID”. When I say “commands” it means the full command line and the complete command output.

Instead of telling stories you need to show facts. Start with the complete output of

fdisk -l
blkid
lsblk -f
4

Move partition 3 to end of free space
Move partition 2 to end of free space
Enlarge partition 1 to include free space between 1 &2

Dedicated for Windows

There is only 1 time the question to provide the password for luks during boot.

cat /etc/crypttab
lsblk -f

NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1 ntfs SystemW10 68F68789F687566A
├─sda2 ntfs ECA08029A07FF882
├─sda3 vfat FAT32 5D03-8C00
├─sda4 ntfs 4489597A19D6F76A
└─sda5 ntfs music - house - files CC007EA6007E9764
sdb linux_raid_member 1.0 any:0 972654a6-fd4d-9f5e-6a6f-11762f47cad5
sdc linux_raid_member 1.0 any:0 972654a6-fd4d-9f5e-6a6f-11762f47cad5
sdd
├─sdd1 vfat FAT16 AE69-B593 493.7M 1% /boot/efi
├─sdd2 crypto_LUKS 1 a51b3ab0-a7c1-4e67-a67f-9b8ca08ddb00
│ └─cr-auto-2 xfs ea06a690-dfb5-42c5-a7c9-afa188b12a6b 191.1G 24% /home
├─sdd3 xfs 5738eda4-45fd-4aa4-9986-0b7950106f4b 92G 21% /web
└─sdd4 btrfs c98482bd-4765-4a7a-bcf8-9fdc72b62d7f 67G 31% /var
/usr/local
/boot/grub2/x86_64-efi
/opt
/root
/srv
/boot/grub2/i386-pc
/.snapshots
/

I noticed that /dev/sdb and /dev/sdb did not contain the partition anymore. There for I booted into gparted live to run testdisk on the raid array. After hours of searching for a partition table that could not be found I have recreated the array completely anew and put back an old back-up.

So I’ll close this one.

5

As an afterthought, please next time use the Preformatted text button </> instead of the Blockquote button " for copied/pasted terminal text.

And please include the prompt/command line inside the copy/paste. It is only one more line and it shows us what you did (and as who and where) without you typing anything extra.

1 Like