Ok, re-loaded the box.
Same result. On the first boot, all goes well.
On the second boot, all goes to hell.
It won't boot the second time. It fails (or more accurately hangs) at:
Setting up Logical Volume Management. But here's the interesting part:
The boot sequence at the time of the failure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 23 February 2003 03:48 pm, Ric Tibbetts wrote:
That's as far as it gets.
I suppose I could re-load it (again), and look through the startup
scripts while it's booted the first time, and find the culprit.
But, I think this one needs to
Greg Meyer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 23 February 2003 03:48 pm, Ric Tibbetts wrote:
That's as far as it gets.
I suppose I could re-load it (again), and look through the startup
scripts while it's booted the first time, and find the culprit.
But, I think
Ric Tibbetts wrote:
Greg Meyer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 23 February 2003 03:48 pm, Ric Tibbetts wrote:
That's as far as it gets.
I suppose I could re-load it (again), and look through the startup
scripts while it's booted the first time, and find the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 23 February 2003 10:29 pm, Ric Tibbetts wrote:
Yeah, ok, tried that.
I went to submit the report. Filled out the form, and hit submit, and it
sat... and sat, and sat...
I killed it after some time.
Does nothing at Mandrakesoft work
On Sun, 2003-02-23 at 19:29, Ric Tibbetts wrote:
Greg Meyer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 23 February 2003 03:48 pm, Ric Tibbetts wrote:
That's as far as it gets.
I suppose I could re-load it (again), and look through the startup
scripts while
James Sparenberg wrote:
On Sun, 2003-02-23 at 19:29, Ric Tibbetts wrote:
Greg Meyer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 23 February 2003 03:48 pm, Ric Tibbetts wrote:
That's as far as it gets.
I suppose I could re-load it (again), and look through the startup