Thanks Roger.  dmesg has nothing in it referring to md126 or md127....
any other thoughts on how to investigate?

thanks,
allie

On 3/27/2020 3:55 PM, Roger Heflin wrote:

A non-assembled array always reports raid1.

I would run "dmesg | grep md126" to start with and see what it reports it saw.

On Fri, Mar 27, 2020 at 10:29 AM Alexander Shenkin [off-list ref] wrote:

quoted

Thanks Wol,

Booting in SystemRescueCD and looking in /proc/mdstat, two arrays are
reported.  The first (md126) in reported as inactive with all 7 disks
listed as spares.  The second (md127) is reported as active
auto-read-only with all 7 disks operational.  Also, the only
"personality" reported is Raid1.  I could go ahead with your suggestion
of mdadm --stop array and then mdadm --assemble, but I thought the
reporting of just the Raid1 personality was a bit strange, so wanted to
check in before doing that...

Thanks,
Allie

On 3/26/2020 10:00 PM, antlists wrote:

quoted

On 26/03/2020 17:07, Alexander Shenkin wrote:

quoted

I surely need to boot with a rescue disk of some sort, but from there,
I'm not sure exactly when I should do.  Any suggestions are very welcome!

Okay. Find a liveCD that supports raid (hopefully something like
SystemRescueCD). Make sure it has a very recent kernel and the latest
mdadm.

All being well, the resync will restart, and when it's finished your
system will be fine. If it doesn't restart on its own, do an "mdadm
--stop array", followed by an "mdadm --assemble"

If that doesn't work, then

https://raid.wiki.kernel.org/index.php/Linux_Raid#When_Things_Go_Wrogn

Cheers,
Wol