Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 09 Aug 2012 16:30:21 +0100
From:      Matthew Seaman <matthew@FreeBSD.org>
To:        dude golden <dudegolden@yahoo.com>
Cc:        "freebsd-questions@FreeBSD.org" <freebsd-questions@FreeBSD.org>
Subject:   Re: kernel panic
Message-ID:  <5023D78D.6070404@FreeBSD.org>
In-Reply-To: <1344523941.96245.YahooMailNeo@web160604.mail.bf1.yahoo.com>
References:  <1340356289.73682.YahooMailNeo@web160602.mail.bf1.yahoo.com> <4FE448AF.5070906@FreeBSD.org> <1344523551.88887.YahooMailNeo@web160604.mail.bf1.yahoo.com> <1344523941.96245.YahooMailNeo@web160604.mail.bf1.yahoo.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig9DE1341A574121C7113C9E71
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 09/08/2012 15:52, dude golden wrote:
> hope my email find you well,first of all thank you very much for your
> grate response always in answering my emails, now i am using freeBSD
> 8.3 in a Intel corI5 server with 12 G of RAM and 500 G HDD sata .we
> have a voip soft switch application installed on it and do
> telecommunication business, yesterday night we experience a strange
> kernel panic and our server hanged, just contact collocation as asked
> for physical reboot,

> in attached, you can find screen shot of rebooting the server . i
> really thank full if you take a look and advise me any update.

The freebsd-questions@ probably won't have seen the screen shot, but it
showed me that the problem was in ffs_blkfree, ie. that the system
panicked because of filesystem corruption.

Unfortunately you haven't enabled a dump device, so no more detailed
debugging info will be available.  There's not a huge amount that can be
determined just from the panic screen unfortunately.

However, in terms of general advice:

  * You need to ensure that there is no lingering filesystem corruption
which could trigger a repeat.  Reboot the system into single user mode,
and then run:

    fsck -fy /dev/ad7s4a

etc. for all the devices listed in /etc/fstab or elsewhere that have
active filesystems on them.  Run fsck like that repeatedly for each
partition until it says 'filesystem clean.'

  * Enable system dumps, so if this happens again, there is more to go
on.  Just add:

dumpdev=3D"AUTO"

to /etc/rc.conf and reboot.

  * The problem could well be due to disk malfunction, or maybe
something as trivial as a loose or kinked data cable leading to the
drive, or overheating.  Powering the machine down, opening the case and
checking for any obvious problems would be a good idea.  Also, check the
system logs to see if there are any kernel messages indicating non-fatal
trouble.  Install the sysutils/smartmontools port and use that to get a
health report on the drive:

   smartctl  -A /dev/ad7

  * It seems you don't have any sort of hard drive resilience set up.
If this server is important for your business, then using mirrored hard
drives is just plain common sense.  If there's room in the chassis,
simply adding another drive identical to the one you have and setting up
gmirror RAID should be fairly simple and will offer adequate levels of
protection against such failures.



--=20
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey



--------------enig9DE1341A574121C7113C9E71
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlAj15QACgkQ8Mjk52CukIyvVQCggWJEyPT32cqC8XxRksJW9N+f
7f8An2mit/QwP+DpI0d4rpf/uJ2T2p9L
=BmWg
-----END PGP SIGNATURE-----

--------------enig9DE1341A574121C7113C9E71--



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?5023D78D.6070404>