need help badly with RAID5 recovery

[bohnnyjliss]

iirc this is how the drive looked when i got it in disk

ss1.jpeg

[darkod]

Do you have maybe those screenshots of sdb and sdc?

[darkod]

Also, please post the same parted output for the other two 4TB disks, sdb and sdc.

[bohnnyjliss]

parted /dev/sdb unit MiB print
Error: The primary GPT table is corrupt, but the backup appears OK, so that will be used.
OK/Cancel? ok                                                             
Model: ATA WDC WD40EZRZ-00G (scsi)
Disk /dev/sdb: 3815448MiB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start    End         Size        File system  Name              Flags
 1      1.00MiB  2097152MiB  2097151MiB  ext4         Linux filesystem

parted /dev/sdc unit MiB print
Error: The primary GPT table is corrupt, but the backup appears OK, so that will be used.
OK/Cancel? ok                                                             
Model: ATA WDC WD40EMRX-82U (scsi)
Disk /dev/sdc: 3815448MiB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags: 

Number  Start    End         Size        File system  Name  Flags
 1      1.00MiB  2097152MiB  2097151MiB

[bohnnyjliss]

ss2.jpeg

ss3.jpeg

[darkod]

Unfortunately this looks worse and worse... If you take a good look at the parted output, sda has msdos table, and sdb and sdc have gpt (which we expect to see on sda too).

Not only that they installed OS over the raid disk, they created msdos table on it (and partitions of course).

Can you post one more output for comparison please?

lsblk

That will list the drives and partitions, I want to see how they compare with parted and blkid.

But honestly, you are far from getting this restored IMHO...

After you post the lsblk output we can try again to assemble.

[bohnnyjliss]

lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
loop0    7:0    0   956K  1 loop  /snap/gnome-logs/81
loop1    7:1    0  44.9M  1 loop  /snap/gtk-common-themes/1440
loop2    7:2    0  54.7M  1 loop  /snap/core18/1650
loop3    7:3    0  88.5M  1 loop  /snap/core/7270
loop4    7:4    0 260.7M  1 loop  /snap/kde-frameworks-5-core18/32
loop5    7:5    0  89.1M  1 loop  /snap/core/8268
loop6    7:6    0  54.4M  1 loop  /snap/core18/1066
loop7    7:7    0  14.8M  1 loop  /snap/gnome-characters/399
loop8    7:8    0  42.8M  1 loop  /snap/gtk-common-themes/1313
loop9    7:9    0 160.2M  1 loop  /snap/gnome-3-28-1804/116
loop10   7:10   0   4.2M  1 loop  /snap/gnome-calculator/544
loop11   7:11   0   3.7M  1 loop  /snap/gnome-system-monitor/123
loop12   7:12   0  1008K  1 loop  /snap/gnome-logs/61
loop13   7:13   0     4M  1 loop  /snap/gnome-calculator/406
loop14   7:14   0  14.8M  1 loop  /snap/gnome-characters/375
loop15   7:15   0  15.8M  1 loop  /snap/kolourpaint/44
loop16   7:16   0   3.7M  1 loop  /snap/gnome-system-monitor/127
loop17   7:17   0 156.7M  1 loop  /snap/gnome-3-28-1804/110
sda      8:0    0   3.7T  0 disk  
├─sda1   8:1    0     2T  0 part  
└─md0    9:0    0  10.9T  0 raid5 
sdb      8:16   0   3.7T  0 disk  
└─md0    9:0    0  10.9T  0 raid5 
sdc      8:32   0   3.7T  0 disk  
└─md0    9:0    0  10.9T  0 raid5 
sdd      8:48   0  55.9G  0 disk  
└─sdd1   8:49   0  55.9G  0 part  /
sde      8:64   0   7.3T  0 disk

[darkod]

I would keep sde out. Like I said, only work with the disks from the previous array which are sda, sdb and sdc.

I don't like the fact that sda has partition on it, but mdadm can work ignoring that. I think we might do more damage trying to remove it right now. It will have to remain pending to do later.

So, right now I would stop the current md0, and assemble it only with sda, sdb and sdc.

sudo mdadm --stop /dev/md0
sudo mdadm --create --assume-clean --verbose --chunk=16M --level=raid5 --raid-devices=4 /dev/md0 /dev/sda /dev/sdb /dev/sdc missing

Please paste all mdadm output here. It would be interesting to see how it assembles it, which messages it gives.

Don't try anything else, not even mounting it RO. Lets see the mdadm output first.

[bohnnyjliss]

mdadm --create --assume-clean --verbose --chunk=16M --level=raid5 --raid-devices=4 /dev/md0 /dev/sda /dev/sdb /dev/sdc missing
mdadm: layout defaults to left-symmetric
mdadm: layout defaults to left-symmetric
mdadm: /dev/sda appears to be part of a raid array:
       level=raid5 devices=4 ctime=Tue Jan 28 09:10:56 2020
mdadm: partition table exists on /dev/sda but will be lost or
       meaningless after creating array
mdadm: /dev/sdb appears to be part of a raid array:
       level=raid5 devices=4 ctime=Tue Jan 28 09:10:56 2020
mdadm: partition table exists on /dev/sdb but will be lost or
       meaningless after creating array
mdadm: /dev/sdc appears to be part of a raid array:
       level=raid5 devices=4 ctime=Tue Jan 28 09:10:56 2020
mdadm: partition table exists on /dev/sdc but will be lost or
       meaningless after creating array
mdadm: size set to 3906879488K
mdadm: automatically enabling write-intent bitmap on large array
Continue creating array? y
mdadm: Defaulting to version 1.2 metadata
mdadm: array /dev/md0 started.

[bohnnyjliss]

i have the original drives in the recovery program and it seems to be working now that i know about the 16MB size.

dont know how much or whatever it can get, i need to try and continue both avenues so dont give up on me