My guess is that it is having trouble with your fids directory, right?

Nope, it just craps out the second anything even tries to touch it. No files are on drive0 whatsoever. mkdir, cat, cp, or anything else that would touch the disk spawn that error.

Reading peters note below, it looks like it's not going to work without a ton of tinkering. I'll post my kernel and compiled utilities, and leave it at "still insanely hard" to get working.