no, i will explain, just for the benefit of those here:
needed to increase size of array, so i init 1. was going to destroy array
and remake in single user mode. system would not unmount the md device,
cause i had stopped knfsd in an odd manner (or so i thought).
i am not sure if cpu0 was working at this time or not. i try init 6,
system gives the same error on ALL the raid devices (this system has 4
raid1 sets) and hangs. i hit the switch. when the box comes up, linux
kernel bitches about a "abnormal fdc" (which i had noticed before, as
the system takes 10 minutes to mkbootdisk) and also about cpu0 not
responding, so it SHUT IT OFF! i thought it was one of the coolest things
i had ever seen. i almost compiled 2.0.35 just to see if it did it too.
but i have another box, same setup just single proc and less ram, and i
cant get that thing to stay up for more than a week :)
ymmv i guess.
allan
"so don't tell us it can't be done, putting down what you don't know.
money isn't our god, integrity will free our souls" - Max Cavalera
