On 30/09/20 19:58, David Madore wrote: > On Wed, Sep 30, 2020 at 03:09:05PM +0100, antlists wrote: >> > So my guess was spot on :-) >> > >> > You'll guess that this is a common problem, with a well-known solution... >> > >> > https://raid.wiki.kernel.org/index.php/Easy_Fixes#Debian_9_and_Ubuntu > OK, I've just retried with a new version of mdadm, > > mdadm - v4.1 - 2018-10-01 > > - which I think is roughly contemporaneous to the kernel version I'm > using. But the problem still persists (with the exact same symptoms > and details). Except that mdadm is NOT the problem. The problem is that the kernel and mdadm are not matched date-wise, and because the kernel is a franken-kernel you need to use a different kernel. Use a rescue disk!!! That way, you get a kernel and an mdadm that are the same approximate date. As it stands, your frankenkernel is too new for mdadm 3.4, but too ancient for a modern kernel. Cheers, Wol
