This is sadly my server I am running most of my things on so I can't really replace it that easily. I think I will have to continue trying to figure it out (my current suspicion is towards the fact of the two discs that are not seen in /proc/mdstat. If they can't be seen I guess mdadm might avoid running properly, but why are they not seen, since a subsequent manual assemble work without a hitch.
Is it possible to add an additional delay at bootup to make sure the discs have sufficcient time to spin up?
The drives are found as evidence from dmesg show. But this happens after
the other disks are found and the md command run for them.
...The other discs found...
ata8.00: ATA-7: WDC WD2500YD-01NVB1, 10.02E01, max UDMA/133
ata8.00: 490234752 sectors, multi 0: LBA48 NCQ (depth 0/1)
ata8.00: configured for UDMA/133
scsi 7:0:0:0: Direct-Access ATA WDC WD2500YD-01N 10.0 PQ: 0 ANSI: 5
sd 7:0:0:0: Attached scsi generic sg7 type 0
sd 7:0:0:0: [sdh] 490234752 512-byte logical blocks: (251 GB/233 GiB)
sd 7:0:0:0: [sdh] Write Protect is off
sd 7:0:0:0: [sdh] Mode Sense: 00 3a 00 00
sd 7:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 7:0:0:0: [sdh] Attached SCSI disk
ata9.00: ATA-5: WDC WD400BB-60DGA0, 05.03E05, max UDMA/100
ata9.00: 78165360 sectors, multi 0: LBA
ata9.00: configured for UDMA/100
scsi 8:0:0:0: Direct-Access ATA WDC WD400BB-60DG 05.0 PQ: 0 ANSI: 5
sd 8:0:0:0: Attached scsi generic sg8 type 0
sd 8:0:0:0: [sdi] 78165360 512-byte logical blocks: (40.0 GB/37.2 GiB)
sd 8:0:0:0: [sdi] Write Protect is off
sd 8:0:0:0: [sdi] Mode Sense: 00 3a 00 00
sd 8:0:0:0: [sdi] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 8:0:0:0: [sdi] Attached SCSI disk