1: Just because the array is inactive doesn't mean the information is not valuable, actually it's even more, as your most likely needs your attention 2: The information is available and is printed when not doing --export 3: I'm aware of --examine, but why use it when the kernel already read the superblocks when the disks were initialize, the information is already there In my view I don't see any argument for not including the raid level etc. when the raid is inactive. I'm building a administration-system where the use of --export is very handy. I can do work-around calling additional commands to get the info, but it would be nice if --export just provided the information in the first place. On Thu, Jul 8, 2021 at 12:25 AM NeilBrown <neilb@xxxxxxx> wrote: > > On Wed, 07 Jul 2021, BW wrote: > > I'm using ver. mdadm-4.1-24.3.1.x86_64 / openSUSE kernel 15.3 > > > > It's only when the array is active you get a raid-level, if the array > > is inactive, as in my example, you will not get the raid-level (and > > State, Persistence). > > > > Yes, that is correct. > When the array is inactive, it is not an active array. It has no level > or state. It is just a bunch of drives. > > If you want to see what might happen when you activate the array, you > need to --examine the indiividual drives. > > NeilBrown
