>No, it isn't HiJack and single disk speedup (at least not explicitly).

Yes, it probably is that feature, since nothing else can cause this behaviour. The feature is not a config.ini feature, but rather a bit stored in flash memory. If that bit happens to have the wrong setting, then you're basically screwed as far as hijack is concerned.

I'll see if I can't fix this. In your logs, I notice the slave drive coming up before the master.. I suppose this is "standard" required drive behaviour (master waits for slave on reset), so maybe it will always happen this way.. In any case, this is detectable, and if a slave appears, the code can just wait for the master regardless of the setting in Hijack.

If the problem happens the other way around, master comes up and slave is ignored, then this is easy to fix by just going into the hijack menu and changing the 1/2 drive setting -- so nothing new needed for that scenario. The reason the first scenario is more difficult is because the stupid filesystem code panic's and shuts down, rather than just sitting there managing life as it's supposed to do..

I'll put the fix out in v122 later today.

-ml