Date: Tue, 17 Nov 2015 11:23:41 -0600 From: Will Senn <will.senn@gmail.com> To: CyberLeo Kitsana <cyberleo@cyberleo.net>, freebsd-questions@freebsd.org Subject: Re: Kernel panic and hard disk failure Message-ID: <564B629D.4060909@gmail.com> In-Reply-To: <564B4062.30301@cyberleo.net> References: <5649F4D1.8070105@gmail.com> <564B4062.30301@cyberleo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/17/15 8:57 AM, CyberLeo Kitsana wrote: > You'll notice the crashdump files are named with .0, .1, .2 suffixes. > This file contains the next available number. If you leave the bounds > file with a '3' in it, but delete the crashdump files, the next > crashdump will have the suffix .3 . This ensures it will not > inadvertently overwrite a previous crashdump. Consult the savecore > manpage for further information. >> 2. What is minfree? > From savecore(8): > > The savecore utility also checks the available disk space before > attempting to make the copies. If there is insufficient disk space in > the file system containing directory, or if the file directory/minfree > exists and the number of free kilobytes (for non-superusers) in the > file system after the copies were made would be less than the number in > the first line of this file, the copies are not attempted. > >> 3. What does it mean that the device went missing? > The hard drive stopped responding and the controller decided it was no > longer connected. > >> 4. Does the information above sound like a faulty hard drive or are >> there additional tests that will tell me more about the failure? > Could be a failing hard drive; but it could also be a bad data cable or > weak or failing power supply. > Thanks for the pointer to savecore and for the answers. I'll keep an eye out for additional failures and if there are any with the replacement drive, I'll check into cables and such. -will
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?564B629D.4060909>