Upgraded from last stable as I had a spin-up problem with my Seagate Ironwolf parity drive under RC2. I see the same quirk again under the new kernel - this time having attached diagnostics.   From what I can tell, it appears once the mover kicks in and forces the spin up of the parity.  It tripped up once as you can see from the logs but came up and wrote fine.   I've done repeated manual spin downs of the parity, writing into the array via the cache, and forcing a move
    • Thanks
    • Like