Rommel P. Pastrana wrote:
Normally, after answering "no" to that question, you would get a prompt> I've tried your suggestion as follows:
> OPTION 1:
> Boot and answered no to "root filesstem is dirty, OK to check it?".
> There was no shell prompt to write the next command; fsck -o full
> /dev/root; on so instead i just went ahead and type the command on the
> blank line.
asking you to type the root password to go into single-user mode, or ^D
to go multi-user. You would have entered the root password, gotten a
shell prompt, then run the fsck.
I suppose it is _possible_ that you did actually get to a shell prompt
that wasn't displaying (for some strange reason). One thing you can do
to see if you're at a shell prompt is type "echo ^G" (control-G). It
may beep when you hit ^G; it may beep when you hit return and it acts on
the command. If it beeps when you hit return, you are definitely at
some sort of shell prompt. If it doesn't beep, the test is inconclusive
(the bell character might have disappeared for the same reason the rest
of the shell output is invisible).
That actually sounds like a reasonable description of disk light> I dont know if it was just coincidence or i did it right, the hard
> disk's LED flickered continuously but no activities appearing on
> the monitor.
> 20minutes after, the LED activity seemed to be not right as it just
> flickered on and on and in constant interval as if a microsoft windows
> scans a hd bad sector.
> Is this normal? how long normally an fsck lasts witha 40GB hd.
activity during an `fsck -o full`. fsck has various phases it goes
through, which look different. Of course the whole thing should end
eventually. Total time depends on a bunch of factors -- speed of the
hard disk (mostly seek speed), number of files, amount of space that's
in use, etc. A full 40GB drive would probably take a long time, 20
minutes does not sound out of range.
You didn't say how this ended -- did you hit RESET after deciding it
must be hung? Maybe try it again, but let it run longer -- go to
Please give exact output when you report an error message. In fact,> OPTION 3:
> Using the floppy, i was able to do the mknod /dev/hd0root b 1 42, mount
> -r /dev/hd0root /mnt but failed with the chroot /mnt /bin/sh with an
> error of bad address.
it's best if you show the command and result as accurately as possible,
The chroot failed like this:
# chroot /mnt /bin/sh
I'm not sure what to make of that message, don't have enough context.> I did, cd /mnt/bin, echo * and showed STTY]...chmode, chroot cp...
> I tried the rest of the commands such as the cp, fdisk, vi, cat by
> calling them as is or by entering /mnt/bin/chroot but also resulted with
> the same error message.
In your first message you wrote:
It begins to seem like the system you bought was sick in the first> > > The bad thing is, i bought the server second hand without installer
> > > disks, boot/root floppies and manual to look up to so im just
> > > relying on the internet in finding cure to this problem.
place, somehow improperly installed. I can't think of what would cause
the symptoms you describe. It is probably repairable, but repair will
be very difficult when every step has to be discussed over several days