Brian A. Seklecki schreef:
raid(4) hasn't been touched in a while (years), so short answer: No.
NetBSD is still actively committing to it, though, and has functional
background parity recalculation.
I understand there is interest in replacing RAIDFrame instead of
resynchronizing the subtree.
Hi dear all
I've updated my OpenBSD 4.1's ports using cvsup with tag=. to most
recent version of ports. When i try to install some ports for example
apache 2.2.6 then following error occurs. What's the problem? What did i
wrong? Anyone help me?
# make install
===> Checking files for apache-http
Damien Bergamini schrieb:
> | # ifconfig wpi0 down
> | # ifconfig wpi0 nwid NAME up
> | wpi0: timeout waiting for thermal sensors calibration
> | wpi0: fatal firmware error
>
> This means that your radio switch is off.
>
> Damien
>
>
>
>
Hay Damien,
i have install OBSD 4.1 last day on Sony VAYO VG
Hi ,
I've requested to add you as a friend on SiliconIndia, an invite-only career
Indian community. You
can use SiliconIndia to find a job or internship, network, and access valuable
career information
from peers and industry professionals.
Thanks,
Chandni
SiliconIndia members have successfull
Hi,
On 9/28/07, Leonardo Marques <[EMAIL PROTECTED]> wrote:
> Hey guys,
>
> I've a HD which are returning a lot of errors. Someone know some good
> tool to analyze this disk and tell me if i've to replace it or if
> exist some way to repair it?
I don't know, which tools exist for OpenBSD, but if
On Fri, 28 Sep 2007, Stijn wrote:
> Hi,
>
> I've built Java 1.5 as explained on:
> "http://openbsd.org/faq/faq13.html#javaplugin";
>
> After the "make install" I created the symbolic link to use the Java-plugin
> in firefox.
> "ln -s /usr/local/jdk-1.5.0/jre/plugin/i386/ns7/libjavaplugin_oji.
[EMAIL PROTECTED] schrieb:
> You're using the wrong firmware.
> On OpenBSD 4.1, you should be using revision 1.13 of the firmware
> package as stated in the 4.1 wpi(4) man page.
> But you should consider upgrading to OpenBSD-current because a lot
> of improvements have been made in the wpi driver s
On Fri, Sep 28, 2007 at 01:37:52PM +0200, Peter N. M. Hansteen wrote:
> "Leonardo Marques" <[EMAIL PROTECTED]> writes:
>
> > I've a HD which are returning a lot of errors. Someone know some good
> > tool to analyze this disk and tell me if i've to replace it or if
> > exist some way to repair it?
You're using the wrong firmware.
On OpenBSD 4.1, you should be using revision 1.13 of the firmware
package as stated in the 4.1 wpi(4) man page.
But you should consider upgrading to OpenBSD-current because a lot
of improvements have been made in the wpi driver since 4.1.
Damien
> Hay Damien,
>
>
Hi,
I've built Java 1.5 as explained on:
"http://openbsd.org/faq/faq13.html#javaplugin";
After the "make install" I created the symbolic link to use the Java-plugin in
firefox.
"ln -s /usr/local/jdk-1.5.0/jre/plugin/i386/ns7/libjavaplugin_oji.so \
/home/stijn/.mozilla/plugins"
After I start
Hi Ben,
> Has it really, or is someone really doing something nasty?
I saw sth whisk by via source-changes, but you might want to check for
yourself:
http://www.openbsd.org/anoncvs.html#CVSROOT
HTH... Nico
Matt writes:
>
> As for the suggestion of hardware raid - unfortunately this is a live
> server. If I migrate it to another machine I will definitely try
> hardware raid
> I know it is a lot faster
Really? :) There is no guarantee that a hardware RAID is faster than
a software RAID, or vice-v
On Fri, Sep 28, 2007 at 08:35:10AM +1000, David Gwynne wrote:
On 27/09/2007, at 8:06 PM, Stephan A. Rickauer wrote:
A new server shippped by a local vendor fails to boot bsd.mp, with and
without acpi enabled (amd64, 4.2). Without acpi it will reboot directly
after mounting the root device. Wi
Index: SharedLibs.pm
===
RCS file: /cvs/src/usr.sbin/pkg_add/OpenBSD/SharedLibs.pm,v
retrieving revision 1.29
diff -u -r1.29 SharedLibs.pm
--- SharedLibs.pm 20 Jun 2007 13:44:40 - 1.29
+++ SharedLibs.pm 28 Sep 2007 12:41:19 -
As of the past week or so, my nightly cron job to update /usr/src
has been bombing out, complaining that the ``RSA host key for
anoncvs3.usa.openbsd.org has changed.''
Has it really, or is someone really doing something nasty?
Cheers,
b&
[demime 1.01d removed an attachment of type applica
hi,
i have successfully setup a carp setup with 10 carp devices. on box is
master and another box is backup, so if the master fails the backup box
takes over.
i have sysctl net.inet.carp.preempt=1 and the backup box announces with
"advskew 100".
most of the time everything is fine, but after s
On 2007/09/28 08:17, Leonardo Marques wrote:
> I've a HD which are returning a lot of errors. Someone know some good
> tool to analyze this disk and tell me if i've to replace it or if
> exist some way to repair it?
It's worth trying a different cable, if that doesn't help,
replace the disk...
"Leonardo Marques" <[EMAIL PROTECTED]> writes:
> I've a HD which are returning a lot of errors. Someone know some good
> tool to analyze this disk and tell me if i've to replace it or if
> exist some way to repair it?
To my mind that kind of errors say "run, don't walk to the store for
replacemen
On Fri, 28 Sep 2007, Matt wrote:
> Brian A. Seklecki schreef:
>
> As for the suggestion of hardware raid - unfortunately this is a live
> server. If I migrate it to another machine I will definitely try
> hardware raid
> I know it is a lot faster but would that solve the parity problem on
> boot c
Really thanks for all guys!
I'm running now for the store to buy another HD for the BACKUP server :P
On 9/28/07, Peter N. M. Hansteen <[EMAIL PROTECTED]> wrote:
> "Leonardo Marques" <[EMAIL PROTECTED]> writes:
>
> > I've a HD which are returning a lot of errors. Someone know some good
> > tool to
hi,
yes im quite sure, since pf is disabled.
its working from time to time, after rebooting the master,
some of the devices one the backup machine are not falling back
to BACKUP state like they should, they stay MASTER...
Rui Miguel Silva Seabra schrieb:
On Fri, Sep 28, 2007 at 01:44:53PM +0
On Fri, Sep 28, 2007 at 01:44:53PM +0200, Erich wrote:
> hi,
>
> i have successfully setup a carp setup with 10 carp devices. on box is
> master and another box is backup, so if the master fails the backup box
> takes over.
> i have sysctl net.inet.carp.preempt=1 and the backup box announces wit
Peter N. M. Hansteen pisze:
> "Leonardo Marques" <[EMAIL PROTECTED]> writes:
>
>
>> I've a HD which are returning a lot of errors. Someone know some good
>> tool to analyze this disk and tell me if i've to replace it or if
>> exist some way to repair it?
>>
>
> To my mind that kind of error
Leonardo Marques wrote:
Hey guys,
I've a HD which are returning a lot of errors. Someone know some good
tool to analyze this disk and tell me if i've to replace it or if
exist some way to repair it?
HD: WDC WD1200JD-00HBB0
Errors:
dmesg |grep -i wd0
wd0 at pciide0 channel 0 drive 0:
wd0: 16-
Thus spoke Erdenebat Guntomor ([EMAIL PROTECTED]):
> I've updated my OpenBSD 4.1's ports using cvsup with tag=. to most
> recent version of ports. When i try to install some ports for example
> apache 2.2.6 then following error occurs. What's the problem? What did i
> wrong? Anyone help me?
>
> #
On 2007/09/28 15:28, Erdenebat Guntomor wrote:
> I've updated my OpenBSD 4.1's ports using cvsup with tag=. to most
> recent version of ports.
http://www.openbsd.org/faq/faq15.html#NoFun
Hi dear all
Is there a anyone tried to update and install most recent version of
ports? When i try to install then bsd.port.mk file displaying error. Has
anyone faced this problem?
--
Best regards,
Erdenebat Guntomor mailto:[EMAIL PROTECTED]
Hey guys,
I've a HD which are returning a lot of errors. Someone know some good
tool to analyze this disk and tell me if i've to replace it or if
exist some way to repair it?
HD: WDC WD1200JD-00HBB0
Errors:
dmesg |grep -i wd0
wd0 at pciide0 channel 0 drive 0:
wd0: 16-sector PIO, LBA48, 114473M
> I know it is a lot faster but would that solve the parity problem on
> boot completely? 'man bio' doesn't seem to answer that.
For a variety of reasons, hardware raid controllers handle ungraceful
shutdown better -- onboard batteries for the HBA's RAM/Cache, etc.
Hardware RAID almost never goe
"Brian A. Seklecki" writes:
> raid(4) hasn't been touched in a while (years), so short answer: No.
>
> NetBSD is still actively committing to it, though, and has functional
> background parity recalculation.
Just to be clear here: the background parity checking in NetBSD as of
today is function
Hi
If the problem is intermittent, this is probably correct, but have you
checked that you _really_ have different vhids for all devices?
You might also want to set different passwords for each carp device,
just to go sure they don't interfere with each other.
krgds /markus
Erich wrote:
the
Greg Oster wrote:
I worry more about a hardware RAID card forgetting its configuration
after a power outage than I do about parity checking in the
background :) ("What do you mean these 14 disks in this 2TB hardware
RAID array are now all 'unassigned'!?!?!?!". That wasn't a fun day.)
Rea
On Fri, Sep 28, 2007 at 05:07:47PM +0200, Stephan A. Rickauer wrote:
> On Fri, Sep 28, 2007 at 08:35:10AM +1000, David Gwynne wrote:
>>
>> On 27/09/2007, at 8:06 PM, Stephan A. Rickauer wrote:
>>
>>> A new server shippped by a local vendor fails to boot bsd.mp, with and
>>> without acpi enabled (a
hi,
yes each device has a different vhid, some have the same password, but
one of those
which is still in master state has a different password..
Markus Wernig schrieb:
Hi
If the problem is intermittent, this is probably correct, but have you
checked that you _really_ have different vhids
> Anyone got any similar experiences with hardware RAID cards? Hardware
> RAID has always been misery for me.
I've never lost data under RAIDframe - 3 years plus using cheap SATA
gear and featuring a number of unplanned hard boots and flaky air
conditioning.
Can't say the same for a certain hardw
I've got a Compaq DL380G1 with a SA5300 controller running 4.1. Today
the thing died; I could still ping it, but it would refuse connections
and the console was mostly unresponsive. (The console monitor came back
on when I hit a key on the keyboard.) The following message was on the
screen:
I am sorry to keep bringing this up... but I have still not heard any
authoritative answer to my question. It seems very likely that
the newer Intel ia32e chips do indeed support W^X.
By newer I mean since early 2005. Right now the AMD64 page
says:
"It also runs on the Intel ia32e processors (..
Hello, I read through the FAQ and searched the archives but couldn't find an
answer to this question. In /src/distrib/sets/lists/etc/mi, why does openbsd
include the .cshrc and .profile files in the root directory?
Thanks for any insights!
_
Uhm sorry claudio but it is the other way around. The only time you can
detect failed sectors is on reads. When a read fails the disk goes into
a proprietary algorithm to try to recover as much of the sector as
possible. Depending on the manufacturer they'll do something in excess
of 15000 reads
Rob Waite wrote:
"It also runs on the Intel ia32e processors (...) but since Intel
left out support for the page table NXE bit (No-EXecute)
there is no W^X support on the Intel CPUs."
Perhaps that last line should be "...on the Intel ia32e CPUs."?
RedShift wrote:
Anyone got any similar experiences with hardware RAID cards? Hardware
RAID has always been misery for me.
I've had two instances where older Adaptec RAID cards had a disk failure
and then reverted to a week-old copy of the data. I'm not quite sure
how that's possible, but hav
Hi,
I recently installed two OpenBSD systems from an i386 snapshot dated
September 13th; one in a VMware machine and one on actual physical
hardware.
A couple of days later I noticed that both servers were *not*
date/time synced with the NTP server in my lab, even though I run
OpenNTPD on all my
On Sat, Sep 29, 2007 at 12:30:39AM -0400, Martin Gignac wrote:
> I recently installed two OpenBSD systems from an i386 snapshot dated
> September 13th; one in a VMware machine and one on actual physical
> hardware.
>
> A couple of days later I noticed that both servers were *not*
> date/time synce
But it does work on certain ia32e chips...
I think the last line should read... "some (earlier) ia32e chips
do not have W^X support".
At least to give some information so that people can research
their chip further.
- Original Message -
From: "Steve Shockley" <[EMAIL PROTECTED]>
To:
44 matches
Mail list logo
