On Sun, Feb 21, 2010 at 09:25:45AM +0200, Daniel Braniss wrote:
> > I'm willing to bet this is something simple I've overlooked, but I'm out
> > of ideas. Client is 8.0-RELEASE i386, server is 8.0-STABLE amd64
> > (kernel/world 2010/01/16). NFS version used is v3. Server filesystem
> > is UFS2.
> I'm willing to bet this is something simple I've overlooked, but I'm out
> of ideas. Client is 8.0-RELEASE i386, server is 8.0-STABLE amd64
> (kernel/world 2010/01/16). NFS version used is v3. Server filesystem
> is UFS2.
at boot time, the NFS is V2!, if the server is FreeBSD it can be upgrade
On 2010-Feb-20 22:32:01 +0100, Torfinn Ingolfsen
wrote:
>On Sat, 20 Feb 2010 12:53:51 +1100
>Peter Jeremy wrote:
>
>> Looks reasonable. Let us know the results. I'd be interested in
>> the output from "ntpdc -c loopi -c sysi".
>
>Ok, here we go (the server panic'ed again last night):
>r...@kg-
On Sun, Feb 21, 2010 at 12:35 AM, Jeremy Chadwick
wrote:
> We can safely rule out the Silicon Image controller (otherwise "ataX"
> wouldn't be involved), which leaves the AMD SB700 SATA controller and
> the AMD SB700 PATA controller.
>
> What exact disks (e.g. adX) are attached to ata5 and ata6?
On Sat, Feb 20, 2010 at 10:55:21PM +0100, Torfinn Ingolfsen wrote:
> On Sat, 20 Feb 2010 22:32:01 +0100
> Torfinn Ingolfsen wrote:
>
>
> This output looks ... wrong ... somehow to my eyes:
> r...@kg-f2# date
> Sat Feb 20 22:51:24 CET 2010
> r...@kg-f2# ntpq -p
> remote refid
On Sat, Feb 20, 2010 at 10:49:59PM +0100, Torfinn Ingolfsen wrote:
> On Sat, 20 Feb 2010 11:37:18 -0800
> Jeremy Chadwick wrote:
>
> > Can you re-run smartctl -a instead of -H? Some of the SMART attributes
> > may help determine what's going on, or there may be related errors in
> > the SMART er
2010/1/27 Brandon Gooch :
> The machine, a Dell Optiplex 755, has been locking up recently. The
> situation usually occurs while using VirtualBox (running a 64-bit
> Windows 7 instance) and doing anything else in another xterm (such as
> rebuilding a port). I've been unable to reliably reproduce i
On Sat, 20 Feb 2010 22:32:01 +0100
Torfinn Ingolfsen wrote:
This output looks ... wrong ... somehow to my eyes:
r...@kg-f2# date
Sat Feb 20 22:51:24 CET 2010
r...@kg-f2# ntpq -p
remote refid st t when poll reach delay offset jitter
===
On Sat, 20 Feb 2010 11:37:18 -0800
Jeremy Chadwick wrote:
> Can you re-run smartctl -a instead of -H? Some of the SMART attributes
> may help determine what's going on, or there may be related errors in
> the SMART error log.
smartctl -a output attached. Test sequence: ad4 - ad12, ada0.
> Othe
On Fri, Feb 19, 2010 at 01:12:01PM -0800, Pyun YongHyeon wrote:
> Normally you should not have any FCS errors, it could be related
> with signal quality and these errors might not be correctly
> counted.
I can't check cable and switch counters on bge1 before Feb 24.
> > 3. packets don't lost on
On Sat, 20 Feb 2010 12:53:51 +1100
Peter Jeremy wrote:
> Looks reasonable. Let us know the results. I'd be interested in
> the output from "ntpdc -c loopi -c sysi".
Ok, here we go (the server panic'ed again last night):
r...@kg-f2# uptime
10:28PM up 2:26, 3 users, load averages: 0.00, 0.00,
On Sat, Feb 20, 2010 at 08:21:08PM +0100, Torfinn Ingolfsen wrote:
> Another day, another crash.
> >From /var/log/messages:
> Feb 20 08:52:26 kg-f2 ntpd[58609]: time reset +1.169751 s
> Feb 20 08:54:57 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd =
> 007f
> Feb 20 08:54:57 kg-f
Another day, another crash.
>From /var/log/messages:
Feb 20 08:52:26 kg-f2 ntpd[58609]: time reset +1.169751 s
Feb 20 08:54:57 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd =
007f
Feb 20 08:54:57 kg-f2 kernel: ata5: hardware reset timeout
Feb 20 19:18:51 kg-f2 syslogd: kernel bo
13 matches
Mail list logo
