RAID6 unable to mount EXT4-fs: bad geometry: block count exceeds size of device

On my server, I had an SSD as the boot drive with 11 6TB HDDs in a RAID6 setup as additional storage. However, after running into some issues with the motherboard, I switched the motherboard to one with only 4 SATA ports, so I reduced the size of the RAID6 setup from 11 to 4 drives. With ? no Pass 1: Checking inodes, blocks, and sizes Error reading block 3401580576 (Invalid argument) while getting next inode from scan. Ignore error? yes Force rewrite? yes Error reading block 3401580577 (Invalid argument) while getting next inode from scan. Ignore error? yes Force rewrite? yes Error reading block 3401580578 (Invalid argument) while getting next inode from scan. Ignore error? yes Force rewrite? yes Error reading block 3401580579 (Invalid argument) while getting next inode from scan. Ignore error? yes Force rewrite? yes Error reading block 3401580580 (Invalid argument) while getting next inode from scan. Ignore error? yes Force rewrite? yes Error reading block 3401580581 (Invalid argument) while getting next inode from scan. Ignore error? yes Force rewrite? yes Error reading block 3401580582 (Invalid argument) while getting next inode from scan. Ignore error? yes Force rewrite?

My hypothesis is that there is probably some inconsistency in the reported size of the drives. I do not believe I had any partitions on the RAID nor any LVM volumes.

sudo fdisk -l ... Disk /dev/sda: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors Disk model: WDC WD60EZAZ-00S 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 /dev/sdb: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors Disk model: WDC WD60EZAZ-00S 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 /dev/sdc: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors Disk model: WDC WD60EZAZ-00S 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 /dev/sdd: 5.46 TiB, 6001175126016 bytes, 11721045168 sectors Disk model: WDC WD60EZAZ-00S 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 /dev/md127: 10.92 TiB, 12002079539200 bytes, 23441561600 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 524288 bytes / 1048576 bytes ``` The data on the 4 currently in use may or may not be altered by fsck / e2fsck, but the data should also be on the other 7 unused drives with the zeroed superblocks. It is not important to me which drives I recover the data from, so working solutions to recover from any grouping of the drives would be highly appreciated! If any additional information is needed, I would be more than happy to provide it.