Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 16 Nov 2015 11:16:09 +0100
From:      Polytropon <freebsd@edvax.de>
To:        Gerhard Schmidt <schmidt@ze.tum.de>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Random Lockup with FreeBSD 10.2 on SuperMicro Boards
Message-ID:  <20151116111609.a9757a4a.freebsd@edvax.de>
In-Reply-To: <5649A761.7040303@ze.tum.de>
References:  <56498205.3060806@ze.tum.de> <20151116094334.GS2604@mordor.lan> <5649A761.7040303@ze.tum.de>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 16 Nov 2015 10:52:33 +0100, Gerhard Schmidt wrote:
> My Workstation is running 10.2 for about at least 4 Month. I've never
> had a problem event with SU+J. The difference is that on my workstation
> /var is not on a raid array. So SU+J isn't the real problem.

Maybe there's a file system inconsistency? How do you
perform file system checks (automatic in background,
which is discouraged, or in SUM, as recommended)?
I'm asking because I've noticed the following lines
in your previous message:

> Trying to mount root from ufs:/dev/raid/r0p3 [rw]...
> WARNING: / was not properly dismounted

Is /var affected as well? If yes - give it a _clean_
fsck, running in foreground on the unmounted partition.

In case you have already done this, redirect my comment
to /dev/null immediately. :-)


-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20151116111609.a9757a4a.freebsd>