if you find the partitions missing if you initrd has kpartx on it that will create the mappings. kpartx -av <device> If something is not creating the partitions a workaround might be simply to add that command in before the commands that bring up the array. There did seem to be a lot of changes that did change how partitions were handled. Probably some sort of unexpected side-effect. I wonder if it is some sort of module loading order issue and/or build-in vs module for one or more of the critical drives in the chain. On Fri, Jul 22, 2022 at 5:11 AM Nix <nix@xxxxxxxxxxxxx> wrote: > > On 20 Jul 2022, Wols Lists outgrape: > > > On 20/07/2022 16:55, Nix wrote: > >> [ 9.833720] md: md126 stopped. > >> [ 9.847327] md/raid:md126: device sda4 operational as raid disk 0 > >> [ 9.857837] md/raid:md126: device sdf4 operational as raid disk 4 > >> [ 9.868167] md/raid:md126: device sdd4 operational as raid disk 3 > >> [ 9.878245] md/raid:md126: device sdc4 operational as raid disk 2 > >> [ 9.887941] md/raid:md126: device sdb4 operational as raid disk 1 > >> [ 9.897551] md/raid:md126: raid level 6 active with 5 out of 5 devices, algorithm 2 > >> [ 9.925899] md126: detected capacity change from 0 to 14520041472 > > > > Hmm. > > > > Most of that looks perfectly normal to me. The only oddity, to my eyes, is that md126 is stopped before the disks become > > operational. That could be perfectly okay, it could be down to a bug, whatever whatever. > > Yeah this is the *working* boot. I can't easily get logs of the > non-working one because, well, no writable filesystems and most of the > interesting stuff scrolls straight off the screen anyway. (It's mostly > for comparison with the non-working boot once I manage to capture that. > Somehow. A high-speed camera on video mode and hand-transcribing? Uggh.) > > -- > NULL && (void)
