Date: Mon, 02 Dec 2013 00:17:23 -0800 From: cary <cary@sdf.org> To: Polytropon <freebsd@edvax.de>, dgmm <freebsd01@dgmm.net> Cc: freebsd-questions@freebsd.org Subject: Re: System reboots ~3am during daily periodic 450.status-security run Message-ID: <529C4213.2010307@sdf.org> In-Reply-To: <20131202071502.a72c0029.freebsd@edvax.de> References: <201312012352.01075.freebsd01@dgmm.net> <201312020027.18293.freebsd01@dgmm.net> <20131202071502.a72c0029.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Polytropon wrote:
> On Mon, 2 Dec 2013 00:27:18 +0000, dgmm wrote:
>> On Sunday 01 December 2013 23:52:00 dgmm wrote:
>>> My system reboots at 3am when /etc/periodic/daily/450.status-security
>>
>> I've now narrowed it down to:
>>
>> /etc/periodic/security/100.chksetuid
>>
>> ...but have no idea why it might a catastophic crash/reboot.
>
> A wild guess: File system damage side effect that is being
> triggered by something "non-obvious". To make sure this is
> _not_ the case, reboot into SUM or via live media and perform
> a forced (!) file system check. Note that just in case you
> might think "but I run background fsck and preen, that should
> be sufficient" - it's not; there are few things that only a
> full, _normal_ file system check can detect and repair.
>
> I'm mentioning this because similar situations have been
> discussed on this list, and finally there was some strange
> file system defect responsible...
>
> But also make sure system power is good, and the system does
> not become unstable when on load.
>
>
Had a 3 a.m. reboot last week.
/usr was corrupted because of my own
errors made while compiling ports.
$ fsck -t ufs -fv /dev/{usr-partition}
--
cary@sdf.org
SDF Public Access UNIX System - http://sdf.org
------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?529C4213.2010307>