mralbobo

Right, that being the most common cause is why I mentioned I specifically called out the boot order. I rebooted a lot while looking into this, my literal workflow: Try a thing. Turn on, go to bios, verify and usually fix the boot order, save, continue boot. Also verified once that save was actually saving. Have suspected previously there's some bug in the bios causing it to not always actually apply changes, regardless of what it says. But this was the first time it seemed to have any relevance to an update, so I figured I'd report it. Will probably try again in a week when the preclear finishes <_<

Just the usual post/ initialization stuff. The part right before being the marvell controller initializing and listing the 2 drives using it.

Yeah, was my first thought as well, my system does that, so I pretty much just have "check the boot order" as one of the steps when changing drives. Wasn't that this time.

Jumped from 6.3.0 to 6.3.4, system wouldn't reboot (posts then sits on that lovely black screen with a blinking cursor. And yes, the boot order was fine...). After a bunch of testing I got it working again by jumping back to 6.3.1 (did not try 2 or 3). Other things of interest: - had a new unassigned drive plugged in - the system would boot on 6.3.4 with that drive removed