On 2016-02-06, Lampshade wrote:
> Feb 6 17:57:25 host ntpd[7585]: peer 150.254.183.15 now valid
> Feb 6 17:58:17 host ntpd[9279]: adjusting local clock by 9.096751s
> Feb 6 18:02:02 host ntpd[9279]: adjusting local clock by 7.971861s
> I don't think that clock is adjusted "by" that values.
I
012345678901234567890123456789012345678901234567890123456789
It is probably just aesthetics.
When I have clock not synchronized and differs a few seconds,
I have following output:
grep ntpd /var/log/daemon | tail -n 30
Feb 6 17:57:00 host ntpd[7585]: constraint reply from ip: offset 8.928573
Feb
hello,
earlier this week a host I have at an offsite location went dark (I
have no remote console), today I drove out to take a look. It had
panicked, I have pictures of the panic, trace and ps here:
http://www.huldtgren.com/panics/
When I tried to bring it back online the softraid volume would
Not sure. Perhaps these drives don't have good meta data due to the
crash?
Can you set sr_debug = SR_D_STATE | SR_D_META and see if that prints
anything informative?
well we now get lots more:
softraid0 at root
scsibus5 at softraid0: 256 targets
softraid0: sr_boot_assembly
softraid0: sr_meta_n
On Sat, Feb 06, 2016 at 02:44:00PM -0500, Johan Huldtgren wrote:
> >This should show chunk states. To map from number this prints to a state,
> >see the #defines listed at struct bioc_disk.bd_status in sys/dev/biovar.h
> >starting line 92.
>
> scsibus5 at softraid0: 256 targets
> softraid0: trying
This should show chunk states. To map from number this prints to a
state,
see the #defines listed at struct bioc_disk.bd_status in
sys/dev/biovar.h
starting line 92.
scsibus5 at softraid0: 256 targets
softraid0: trying to bring up sd9 degraded
softraid0: sd9 was not shutdown properly
softraid0
I was unable to trigger this with
OpenBSD 5.9 (GENERIC.MP) #1869: Thu Feb 4 09:50:59 MST 2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
//mxb
> On 5 feb. 2016, at 19:12, mxb wrote:
>
>
> Any one from @devs have time to pick it up?
>
> This is a new env. , so I ha
On Sat, Feb 06, 2016 at 02:00:25PM -0500, Johan Huldtgren wrote:
> >I would compile a kernel with 'option SR_DEBUG', and with
> >'uint32_t sr_debug = SR_D_STATE' in sys/dev/softraid.c line 63.
> >
> >This might shed light on which chunks have a problem.
>
> at boot I now see this:
>
> softraid0 a
I would compile a kernel with 'option SR_DEBUG', and with
'uint32_t sr_debug = SR_D_STATE' in sys/dev/softraid.c line 63.
This might shed light on which chunks have a problem.
at boot I now see this:
softraid0 at root
scsibus5 at softraid0: 256 targets
softraid0: trying to bring up sd9 degrade
On Sat, Feb 06, 2016 at 11:01:21AM -0500, Johan Huldtgren wrote:
> >Looking at the raid5 code, it looks like you get into this state if
> >more than 2 chunks in the RAID5 volume fail.
> >Are you sure all the disks are OK?
>
> As far as I can tell yes, I don't see anything in dmesg, S.M.A.R.T
> isn
I think transcribing these images yourself improves likelyhood of them
being read...
ok, here goes:
panic: Non dma-reachable buffer at curaddr 0x81115888(raw)
Stopped at Debugger+0x9: leave
TID PID UID PRFLAGS PFLAGS CPU COMMAND
*25637 25637 0 0x14000 0x200 1 srdis
Debugger() at Debugge
Looking at the raid5 code, it looks like you get into this state if
more than 2 chunks in the RAID5 volume fail.
Are you sure all the disks are OK?
As far as I can tell yes, I don't see anything in dmesg, S.M.A.R.T
isn't reporting any errors (but I've been told that means little).
Anything in pa
On Sat, Feb 06, 2016 at 03:48:30PM +0100, Stefan Sperling wrote:
> On Sat, Feb 06, 2016 at 03:47:29PM +0100, Stefan Sperling wrote:
> > On Sat, Feb 06, 2016 at 08:59:42AM -0500, Johan Huldtgren wrote:
> > > dmesg is below.
> >
> > There should be an sd9 device in your dmesg but I cannot see it.
>
On Sat, Feb 06, 2016 at 03:47:29PM +0100, Stefan Sperling wrote:
> On Sat, Feb 06, 2016 at 08:59:42AM -0500, Johan Huldtgren wrote:
> > dmesg is below.
>
> There should be an sd9 device in your dmesg but I cannot see it.
> Seems the drive has died and needs to be replaced?
Sorry, sd9 should be th
On Sat, Feb 06, 2016 at 08:59:42AM -0500, Johan Huldtgren wrote:
> dmesg is below.
There should be an sd9 device in your dmesg but I cannot see it.
Seems the drive has died and needs to be replaced?
As I am struggling with a softraid raid-5 volume myself...
http://marc.info/?l=openbsd-bugs&m=145450495812579
johan+openbsd-m...@huldtgren.com (Johan Huldtgren), 2016.02.06 (Sat) 14:59
(CET):
> http://www.huldtgren.com/panics/
I think transcribing these images yourself improves likelyhood of the
(apologies if this comes through more than once, I tried
unsuccessfully to send this yesterday)
hello,
earlier this week a host I have at an offsite location went dark (I
have no remote console), today I drove out to take a look. It had
panicked, I have pictures of the panic, trace and ps here:
Kenneth Westerback was kind enough to give detailed explanation but
forgot to CC misc@, with his permission here it is:
++
Date: Thu, 4 Feb 2016 10:18:39 -0500
From: Kenneth Westerback
Subject: re: dhclient iwn0 *and* run0 -> lea
18 matches
Mail list logo
