Re: Server down, and will not boot up

2004-04-20 Thread Matthew Seaman
On Mon, Apr 19, 2004 at 11:51:20PM -0500, Ming Tang wrote:

> Here is the message when I turn on the computer after Memory test is ok:
> 
> 
> Verifying DMI Pool Data 
> 
> F1FreeBSD
> 
> Default: F1
> Invalid slice
> Invalid slice
> No /boot/loader
> 
> >> FreeBSD/i386 Boot
> Default:0:ad(0,a)/kernel
> Boot:
> Invalid slice
> No /kernel
> 
> >> FreeBSD/i386 Boot
> Default:0:ad(0,a)/kernel
> Boot:
> 
> 
> It stopped here forever, but I could hear 5-6 relay clicking sound inside the 
> computer box.

That's pretty clearly a hard drive failure.  Still, if that machine
has been running continuously since the days of 4.2-RELEASE it hasn't
done badly at all.

Cheers,

Matthew

-- 
Dr Matthew J Seaman MA, D.Phil.   26 The Paddocks
  Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614  Bucks., SL7 1TH UK


pgp0.pgp
Description: PGP signature


Server down, and will not boot up

2004-04-19 Thread Ming Tang
Hi -

My server was running FreeBSD 4.2. It was down one morning last week while I was busy 
at filing tax
return. It won't reboot up any more and gives me the attached messages repeatedly. I 
am not sure if
it was a hard disk failure or the kernel file corrupted. If any of you experienced the 
computer
trouble/problem or know how to fix it please share it with me. I do need to recover my 
files from
the server if possible. I appreciate your help very much. Any ideas/input are welcome.

Here is the message when I turn on the computer after Memory test is ok:


Verifying DMI Pool Data 

F1FreeBSD

Default: F1
Invalid slice
Invalid slice
No /boot/loader

>> FreeBSD/i386 Boot
Default:0:ad(0,a)/kernel
Boot:
Invalid slice
No /kernel

>> FreeBSD/i386 Boot
Default:0:ad(0,a)/kernel
Boot:


It stopped here forever, but I could hear 5-6 relay clicking sound inside the computer 
box.

Thanks a lot.


--
Ming Tang
[EMAIL PROTECTED]

___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"