Advertisements Well, since KS codes were pre-eSATA, I actually figured they could hurt, perhaps by permanently returning the drive to a totally-unmarried state, so I've been waiting until I couldn't see any other option and then I tried KS 57. What do you know... it worked! Could have knocked me over with a feather when the darn thing booted up correctly. I wish I knew what it fixed. I'm sort of wondering if the OS marking the filesystem bad fails to start up a GSOD automatically when you have external storage attached, and instead pops up the wrong-storage error screen. That could happen if they're checking for filesystem issues in the wrong order, e.g. "Is it married right? If not, then pop up an error. Otherwise, is the filesystem clean? If not, pop up a GSOD and check it." Since it probably can't marry a dirty fs, it would bail at the first question.