Re: RAID1 powerloss - can parity rewrite be safely backgrounded?
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. In the mean time, find a hardware RAID Controller that can be managed by OpenBSD via bio(4) and grab a UPS that works with upsd(8). ~BAS On Thu, 27 Sep 2007, Rob wrote: On 9/25/07, Matt <[EMAIL PROTECTED]> wrote: I'm running a RAID1 mirror on OpenBSD 4.1 (webserver) On a power failure the parity becomes dirty and needs rewriting, which results in > 1.5 hours 'downtime'. Is it safe to background this in /etc/rc or is that a no-no? I found a reference this was possible/safe on-list but it was a) 2003 and b) dealt with RAID5. I'd like to make sure I am not doing something dangerous. I frankly don't know enough to guarantee that this is safe, or not, but I had a RAID1 with big disks on an ancient machine that took about 26 hours to check parity (! -- this wasn't my idea), and I modified its rc to boot up, and then begin performing the parity check in the background. The only caveat I would give is that the operating system was installed and running on a 3rd, separate disk, and that network access to the mirrored drives was disabled until the parity rewrite was complete. - R. Thanks. As I encountered a locked up system (due to quota weirdness) before I received your answers I actually took my chances and tried this. This was in the middle of the night and disk activity was very low (but not entirely silent, this is a live machine) and it worked out okay. Obviously that's no guarantee it will work next time. 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 completely? 'man bio' doesn't seem to answer that. Matt
OpenBSD most recent port installation problem
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-httpd-2.2.6 >> httpd-2.2.6.tar.gz doesn't seem to exist on this system. >> Fetch http://www.reverse.net/pub/apache/httpd/httpd-2.2.6.tar.gz. ftp: unknown option -- k usage: ftp [-46AadEegimnptVv] [-P port] [-r seconds] [host [port]] ftp [-o output] ftp://[user:[EMAIL PROTECTED]:port]/file[/] ftp [-o output] http://host[:port]/file ftp [-o output] https://host[:port]/file ftp [-o output] host:[/path/]file[/] >> Fetch http://www.mirrorservice.org/sites/ftp.apache.org/httpd/httpd-2.2.6.tar.gz. ftp: unknown option -- k usage: ftp [-46AadEegimnptVv] [-P port] [-r seconds] [host [port]] ftp [-o output] ftp://[user:[EMAIL PROTECTED]:port]/file[/] ftp [-o output] http://host[:port]/file ftp [-o output] https://host[:port]/file ftp [-o output] host:[/path/]file[/] >> Fetch http://www.meisei-u.ac.jp/mirror/apache/dist/httpd/httpd-2.2.6.tar.gz. ftp: unknown option -- k usage: ftp [-46AadEegimnptVv] [-P port] [-r seconds] [host [port]] ftp [-o output] ftp://[user:[EMAIL PROTECTED]:port]/file[/] ftp [-o output] http://host[:port]/file ftp [-o output] https://host[:port]/file ftp [-o output] host:[/path/]file[/] >> Fetch http://apache.belnet.be/httpd/httpd-2.2.6.tar.gz. ftp: unknown option -- k usage: ftp [-46AadEegimnptVv] [-P port] [-r seconds] [host [port]] ftp [-o output] ftp://[user:[EMAIL PROTECTED]:port]/file[/] ftp [-o output] http://host[:port]/file ftp [-o output] https://host[:port]/file ftp [-o output] host:[/path/]file[/] >> Fetch ftp://ftp.uni-erlangen.de/pub/mirrors/apache/httpd/httpd-2.2.6.tar.gz. ftp: unknown option -- k usage: ftp [-46AadEegimnptVv] [-P port] [-r seconds] [host [port]] ftp [-o output] ftp://[user:[EMAIL PROTECTED]:port]/file[/] ftp [-o output] http://host[:port]/file ftp [-o output] https://host[:port]/file ftp [-o output] host:[/path/]file[/] >> Fetch ftp://ftp.planetmirror.com/pub/apache/dist/httpd/httpd-2.2.6.tar.gz. ftp: unknown option -- k usage: ftp [-46AadEegimnptVv] [-P port] [-r seconds] [host [port]] ftp [-o output] ftp://[user:[EMAIL PROTECTED]:port]/file[/] ftp [-o output] http://host[:port]/file ftp [-o output] https://host[:port]/file ftp [-o output] host:[/path/]file[/] >> Fetch http://apache.sunsite.ualberta.ca/httpd/httpd-2.2.6.tar.gz. ftp: unknown option -- k usage: ftp [-46AadEegimnptVv] [-P port] [-r seconds] [host [port]] ftp [-o output] ftp://[user:[EMAIL PROTECTED]:port]/file[/] ftp [-o output] http://host[:port]/file ftp [-o output] https://host[:port]/file ftp [-o output] host:[/path/]file[/] >> Fetch http://www.apache.org/dist/httpd/httpd-2.2.6.tar.gz. ftp: unknown option -- k usage: ftp [-46AadEegimnptVv] [-P port] [-r seconds] [host [port]] ftp [-o output] ftp://[user:[EMAIL PROTECTED]:port]/file[/] ftp [-o output] http://host[:port]/file ftp [-o output] https://host[:port]/file ftp [-o output] host:[/path/]file[/] >> Fetch ftp://ftp.openbsd.org/pub/OpenBSD/distfiles//httpd-2.2.6.tar.gz. ftp: unknown option -- k usage: ftp [-46AadEegimnptVv] [-P port] [-r seconds] [host [port]] ftp [-o output] ftp://[user:[EMAIL PROTECTED]:port]/file[/] ftp [-o output] http://host[:port]/file ftp [-o output] https://host[:port]/file ftp [-o output] host:[/path/]file[/] >> Fetch ftp://ftp.usa.openbsd.org/pub/OpenBSD/distfiles//httpd-2.2.6.tar.gz. ftp: unknown option -- k usage: ftp [-46AadEegimnptVv] [-P port] [-r seconds] [host [port]] ftp [-o output] ftp://[user:[EMAIL PROTECTED]:port]/file[/] ftp [-o output] http://host[:port]/file ftp [-o output] https://host[:port]/file ftp [-o output] host:[/path/]file[/] >> Fetch ftp://ftp.freebsd.org/pub/FreeBSD/distfiles//httpd-2.2.6.tar.gz. ftp: unknown option -- k usage: ftp [-46AadEegimnptVv] [-P port] [-r seconds] [host [port]] ftp [-o output] ftp://[user:[EMAIL PROTECTED]:port]/file[/] ftp [-o output] http://host[:port]/file ftp [-o output] https://host[:port]/file ftp [-o output] host:[/path/]file[/] *** Error code 1 Stop in /usr/ports/www/apache-httpd (line 2233 of /usr/ports/infrastructure/mk/bsd.port.mk). *** Error code 1 Stop in /usr/ports/www/apache-httpd (line 1695 of /usr/ports/infrastructure/mk/bsd.port.mk). *** Error code 1 Stop in /usr/ports/www/apache-httpd (line 1892 of /usr/ports/infrastructure/mk/bsd.port.mk). *** Error code 1 Stop in /usr/ports/www/apache-httpd (line 1373 of /usr/ports/infrastructure/mk/bsd.port.mk). *** Error code 1 Stop in /usr/ports/www/apache-httpd (line 1861 of /usr/ports/infrastructure/mk/bsd.p
Re: Bug in the wireless wpi driver ?
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 VGN-C1S and have any problems with the wpi-driver, too. After i'm installed the wpi-firmware-2.14.1.5 and i make on with #ifconfig wpi0 up then, #wpi0: could not read the firmware also, i moved wpi-3945abg to wpi-ucode. Now, it's read firmware, but he "could not lock memory" best reagards Boris -- - [EMAIL PROTECTED] www.voelkle.eu --- - Schl|ssel-ID:0x53571272 --- pool.sks-keyservers.net - Fingerprint:BDEA F0DE 7485 0239 0659 D48F 3DC4 3AA9 5357 1272 -- - [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
I've added you as a friend on SiliconIndia...
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 successfully received offers from: Infosys, Wipro, Reliance, TCS, Google, HCL, Cognizant, Satyam, HDFC Bank, HSBC and hundreds more... Click on the link below to join the network of Chandini Kapoor and start your own network: http://www.siliconindia.com/register.php?id=AFWwfztg (Please note: Membership is through invitation only) Your Invitation ID: AFWwfztg Note: If you encounter any problem while registration, please send an email to [EMAIL PROTECTED] To subscribe to SI Dailydose e-newsletter click here http://www.siliconindia.com/newsletter/shownews.php - To unsubscribe from future mailing from SI, click here http://www.siliconindia.com/invitation/remove.php
Re: Tool for HD analyzing
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 you're on x86/AMD64 and are OK with a DOS bootdisk, search for MHDD. This is a really nice tool. Or just burn yourself an "ultimate boot cd" (ultimatebootcd.com), which also includes MHDD and a ton of other diagnosis and repair tools. greetings, knitti
Re: Java 1.5 issue - lazy binding
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.so \
> /home/stijn/.mozilla/plugins"
>
> After I start firefox and enter "about:plugins", firefox becomes
> unresponsive.
>
> On my xterm console I get the error message:
> "/usr/local/mozilla-firefox/firefox-bin:/usr/local/jdk-1.5.0/jre/plugin/i386/ns7/libjavaplugin_oji.so:
> undefined symbol '__cxa_atexit' lazy binding failed!"
>
> When I remove the symbolic link firefox works fine. Entering "about:plugins"
> returns information about installed plugins.
>
> Anybody knows how to fix this? I have no idea what the lazy binding means.
Check http://www.openbsd.org/faq/current.html#20070903
Probably firefox was compiled before the change, while the plugin
after, or something like that.
-Otto
>
> TIA,
> Stijn
>
> firefox version:
> Mozilla Firefox 2.0.0.6,
>
> dmesg (sorry if my web mail messed up the format):
>
> OpenBSD 4.2-current (GENERIC.MP) #258: Tue Sep 11 21:42:19 MDT 2007
> [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC.MP
> cpu0: Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz ("GenuineIntel" 686-class) 1.67
> GHz
> cpu0:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR
> real mem = 1063354368 (1014MB)
> avail mem = 1020440576 (973MB)
> mainbus0 at root
> bios0 at mainbus0: AT/286+ BIOS, date 04/03/07, BIOS32 rev. 0 @ 0xffa10,
> SMBIOS rev. 2.4 @ 0xf6ea0 (62 entries)
> bios0: vendor Dell Inc. version "A08" date 04/03/2007
> bios0: Dell Inc. Latitude D620
> pcibios0 at bios0: rev 2.1 @ 0xf/0x1
> pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfa990/224 (12 entries)
> pcibios0: PCI Interrupt Router at 000:31:0 ("Intel 82371 ISA and IDE" rev
> 0x00)
> pcibios0: PCI bus #12 is the last bus
> bios0: ROM list: 0xc/0xf000! 0xcf000/0x1000
> acpi0 at mainbus0: rev 0
> acpi0: tables DSDT FACP HPET APIC ASF! MCFG SLIC TCPA SSDT
> acpitimer at acpi0 not configured
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: apic clock running at 166 MHz
> cpu1 at mainbus0: apid 1 (application processor)
> cpu1: Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz ("GenuineIntel" 686-class) 1.67
> GHz
> cpu1:
> FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR
> ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
> ioapic0: misconfigured as apic 0, remapped to apid 2
> acpiprt0 at acpi0: bus 0 (PCI0)
> acpiprt1 at acpi0: bus -1 (AGP_)
> acpiprt2 at acpi0: bus 3 (PCIE)
> acpiprt3 at acpi0: bus 11 (RP01)
> acpiprt4 at acpi0: bus 12 (RP02)
> acpiprt5 at acpi0: bus 9 (PXP0)
> acpiprt6 at acpi0: bus -1 (RP04)
> acpiprt7 at acpi0: bus -1 (RP05)
> acpiprt8 at acpi0: bus -1 (RP06)
> acpicpu at acpi0 not configured
> acpicpu at acpi0 not configured
> acpitz at acpi0 not configured
> acpiac at acpi0 not configured
> acpibat at acpi0 not configured
> acpibat at acpi0 not configured
> acpibtn at acpi0 not configured
> acpibtn at acpi0 not configured
> acpibtn at acpi0 not configured
> acpidock at acpi0 not configured
> cpu0: unknown Enhanced SpeedStep CPU, msr 0x06130a2506000a25
> cpu0: using only highest and lowest power states
> cpu0: Enhanced SpeedStep 1667 MHz (1292 mV): speeds: 1667, 1000 MHz
> pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
> pchb0 at pci0 dev 0 function 0 "Intel 82945GM MCH" rev 0x03
> vga1 at pci0 dev 2 function 0 "Intel 82945GM Video" rev 0x03: aperture at
> 0xd000, size 0x1000
> wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
> wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
> "Intel 82945GM Video" rev 0x03 at pci0 dev 2 function 1 not configured
> azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x01: apic 2
> int 21 (irq 10)
> azalia0: host: High Definition Audio rev. 1.0
> azalia0: codec: Sigmatel STAC9200 (rev. 34.1), HDA version 1.0
> azalia0: codec: Conexant/0x2bfa (rev. 0.0), HDA version 0.9
> azalia0: codec[1]: No support for modem function groups
> azalia0: codec[1]: No audio function groups
> audio0 at azalia0
> ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x01
> pci1 at ppb0 bus 11
> ppb1 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x01
> pci2 at ppb1 bus 12
> wpi0 at pci2 dev 0 function 0 "Intel PRO/Wireless 3945ABG" rev 0x02: apic 2
> int 17 (irq 3), MoW2, address 00:1b:77:02:1d:9e
> ppb2 at pci0 dev 28 function 2 "Intel 82801GB PCIE" rev 0x01
> pci3 at ppb2 bus 9
> bge0 at pci3 dev 0 function 0 "Broadcom BCM5752" rev 0x02, BCM5752 A2
> (0x6002): apic 2 int 18 (irq 11), address 00:18:8b:c7:55:38
> brgphy0 at bge0 phy 1: BCM
Re: Bug in the wireless wpi driver ?
[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 since 4.1. > > Damien > > Oh, i'am sorry. Now it's runnig. BB Boris > >> Hay Damien, >> >> i have install OBSD 4.1 last day on Sony VAYO VGN-C1S and have any >> problems with the wpi-driver, too. >> >> After i'm installed the wpi-firmware-2.14.1.5 and i make on with >> #ifconfig wpi0 up >> then, >> #wpi0: could not read the firmware >> also, i moved wpi-3945abg to wpi-ucode. >> Now, it's read firmware, but he "could not lock memory" >> >> best reagards >> >> Boris >> > > > > -- - [EMAIL PROTECTED] www.voelkle.eu --- - Schl|ssel-ID:0x53571272 --- pool.sks-keyservers.net - Fingerprint:BDEA F0DE 7485 0239 0659 D48F 3DC4 3AA9 5357 1272 -- - [demime 1.01d removed an attachment of type application/pgp-signature which had a name of signature.asc]
Re: Tool for HD analyzing
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? > > To my mind that kind of errors say "run, don't walk to the store for > replacement". Modern disks remap bad parts away from active use, when > they've run out of remappable space, they start complaining like that. > Remapping is only possible when writing to blocks. The disk can not remap on reads. By forcing writes to such blocks you can remap them but the data on them is still lost. I use some partitions with almost only read access that had bad blocks and I could fix the problem with dd if=/dev/zero of=/dev/rsd0x (not important data so I did not replace the disk) -- :wq Claudio
Re: Bug in the wireless wpi driver ?
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, > > i have install OBSD 4.1 last day on Sony VAYO VGN-C1S and have any > problems with the wpi-driver, too. > > After i'm installed the wpi-firmware-2.14.1.5 and i make on with > #ifconfig wpi0 up > then, > #wpi0: could not read the firmware > also, i moved wpi-3945abg to wpi-ucode. > Now, it's read firmware, but he "could not lock memory" > > best reagards > > Boris
Java 1.5 issue - lazy binding
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 firefox and enter "about:plugins", firefox becomes unresponsive.
On my xterm console I get the error message:
"/usr/local/mozilla-firefox/firefox-bin:/usr/local/jdk-1.5.0/jre/plugin/i386/ns7/libjavaplugin_oji.so:
undefined symbol '__cxa_atexit' lazy binding failed!"
When I remove the symbolic link firefox works fine. Entering "about:plugins"
returns information about installed plugins.
Anybody knows how to fix this? I have no idea what the lazy binding means.
TIA,
Stijn
firefox version:
Mozilla Firefox 2.0.0.6,
dmesg (sorry if my web mail messed up the format):
OpenBSD 4.2-current (GENERIC.MP) #258: Tue Sep 11 21:42:19 MDT 2007
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz ("GenuineIntel" 686-class) 1.67 GHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR
real mem = 1063354368 (1014MB)
avail mem = 1020440576 (973MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 04/03/07, BIOS32 rev. 0 @ 0xffa10, SMBIOS
rev. 2.4 @ 0xf6ea0 (62 entries)
bios0: vendor Dell Inc. version "A08" date 04/03/2007
bios0: Dell Inc. Latitude D620
pcibios0 at bios0: rev 2.1 @ 0xf/0x1
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfa990/224 (12 entries)
pcibios0: PCI Interrupt Router at 000:31:0 ("Intel 82371 ISA and IDE" rev 0x00)
pcibios0: PCI bus #12 is the last bus
bios0: ROM list: 0xc/0xf000! 0xcf000/0x1000
acpi0 at mainbus0: rev 0
acpi0: tables DSDT FACP HPET APIC ASF! MCFG SLIC TCPA SSDT
acpitimer at acpi0 not configured
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 166 MHz
cpu1 at mainbus0: apid 1 (application processor)
cpu1: Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz ("GenuineIntel" 686-class) 1.67 GHz
cpu1:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 2
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus -1 (AGP_)
acpiprt2 at acpi0: bus 3 (PCIE)
acpiprt3 at acpi0: bus 11 (RP01)
acpiprt4 at acpi0: bus 12 (RP02)
acpiprt5 at acpi0: bus 9 (PXP0)
acpiprt6 at acpi0: bus -1 (RP04)
acpiprt7 at acpi0: bus -1 (RP05)
acpiprt8 at acpi0: bus -1 (RP06)
acpicpu at acpi0 not configured
acpicpu at acpi0 not configured
acpitz at acpi0 not configured
acpiac at acpi0 not configured
acpibat at acpi0 not configured
acpibat at acpi0 not configured
acpibtn at acpi0 not configured
acpibtn at acpi0 not configured
acpibtn at acpi0 not configured
acpidock at acpi0 not configured
cpu0: unknown Enhanced SpeedStep CPU, msr 0x06130a2506000a25
cpu0: using only highest and lowest power states
cpu0: Enhanced SpeedStep 1667 MHz (1292 mV): speeds: 1667, 1000 MHz
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "Intel 82945GM MCH" rev 0x03
vga1 at pci0 dev 2 function 0 "Intel 82945GM Video" rev 0x03: aperture at
0xd000, size 0x1000
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
"Intel 82945GM Video" rev 0x03 at pci0 dev 2 function 1 not configured
azalia0 at pci0 dev 27 function 0 "Intel 82801GB HD Audio" rev 0x01: apic 2 int
21 (irq 10)
azalia0: host: High Definition Audio rev. 1.0
azalia0: codec: Sigmatel STAC9200 (rev. 34.1), HDA version 1.0
azalia0: codec: Conexant/0x2bfa (rev. 0.0), HDA version 0.9
azalia0: codec[1]: No support for modem function groups
azalia0: codec[1]: No audio function groups
audio0 at azalia0
ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x01
pci1 at ppb0 bus 11
ppb1 at pci0 dev 28 function 1 "Intel 82801GB PCIE" rev 0x01
pci2 at ppb1 bus 12
wpi0 at pci2 dev 0 function 0 "Intel PRO/Wireless 3945ABG" rev 0x02: apic 2 int
17 (irq 3), MoW2, address 00:1b:77:02:1d:9e
ppb2 at pci0 dev 28 function 2 "Intel 82801GB PCIE" rev 0x01
pci3 at ppb2 bus 9
bge0 at pci3 dev 0 function 0 "Broadcom BCM5752" rev 0x02, BCM5752 A2 (0x6002):
apic 2 int 18 (irq 11), address 00:18:8b:c7:55:38
brgphy0 at bge0 phy 1: BCM5752 10/100/1000baseT PHY, rev. 0
uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x01: apic 2 int 20
(irq 9)
uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x01: apic 2 int 21
(irq 10)
uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x01: apic 2 int 22
(irq 7)
uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x01: apic 2 int 23
(irq 5)
ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev
Re: anoncvs3.usa.openbsd.org RSA host key changed?
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
Re: RAID1 powerloss - can parity rewrite be safely backgrounded?
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-versa. There is also no guarantee that a commercial software RAID solution is faster than RAIDframe... ;) Hardware RAID is just "software RAID on a card". And so whether a "hardware implmentation of software RAID" is faster or slower than a traditional software RAID just depends on where the bottlenecks have been moved to :) Filesystems, data mixes, and underlying hardware will still all be important parts... > but would that solve the parity problem on > boot completely? 'man bio' doesn't seem to answer that. It depends on how the hardware RAID card keeps track of what parity bits are up-to-date :) If you don't have a good battery in the thing, then you might just be in the same boat as you are with RAIDframe (but because it's all hidden, you might not know it!). Don't let the idea that "because it's hardware RAID it's automatically better" lull you into a false sense of security understand the features and benefits of both, do the analysis, and pick the one that will work best for you. Later... Greg Oster
Re: arc0: unable to query firmware for sensor info
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. With acpi enabled it will hang with "arc0: unable to query firmware for sensor info". Uniprocessor kernels would boot fine, both acpi and without. Pls. find dmesgs of those as well as more info below. I'm pretty sure that message from arc is a result of interrupts not being hooked up correctly. also, arc doesnt hang after printing that message, it gives control back to the rest of the kernel. presumably the kernel is hanging while waiting for io on the disk to work, but of course, the disk is on arc and interrupts arent wired up to it correctly so just blocks. dlg I see. However, only bsd.mp hangs, bsd boots fine. Is there anything else I can try? Stephan
pkg_add: SharedLibs.pm
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 -
@@ -124,7 +124,7 @@
$done_plist->{$pkgname} = 1;
my $plist = OpenBSD::PackingList->from_installation($pkgname,
\&OpenBSD::PackingList::LibraryOnly);
- next if !defined $plist;
+ return if !defined $plist;
$plist->mark_available_lib($pkgname);
}
--
giovanni
anoncvs3.usa.openbsd.org RSA host key changed?
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 application/pkcs7-signature which had a name of smime.p7s]
carp devices master/backup behavior
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 several reboots of the master sytem the backup system is in a state where the carp devices are in a mixed state. carp3 and carp4 for example are still MASTER and the rest of the interfaces has gone back to BACKUP state like they should. they are all in the same carp group. ideas what to check? mfg erich
Re: Tool for HD analyzing
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...
Re: Tool for HD analyzing
"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 replacement". Modern disks remap bad parts away from active use, when they've run out of remappable space, they start complaining like that. For measuring the health of your next hard drive, it's possible sysutils/smartmontools will do the job. -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.datadok.no/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
Re: RAID1 powerloss - can parity rewrite be safely backgrounded?
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 completely? 'man bio' doesn't seem to answer that. > Actually, we ended up moving all of our RAID1 machines to s/w mirroring with rsync. No rebuild time, and you can even swap cables to get the machine up immediately in the case of a catastropic failure. Depending on the application, an rsync job every 10-15 minutes will do what you need just fine. The only problem would be with huge databases - an entire table would rsync at once. We have tried rsnapshot also with good success (it maintains versions automatically), but not with database applications. Lee Leland V. Lammert[EMAIL PROTECTED] Chief Scientist Omnitec Corporation Network/Internet Consultants www.omnitec.net
Re: Tool for HD analyzing
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 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 > replacement". Modern disks remap bad parts away from active use, when > they've run out of remappable space, they start complaining like that. > > For measuring the health of your next hard drive, it's possible > sysutils/smartmontools will do the job. > > -- > Peter N. M. Hansteen, member of the first RFC 1149 implementation team > http://bsdly.blogspot.com/ http://www.datadok.no/ http://www.nuug.no/ > "Remember to set the evil bit on all malicious network traffic" > delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds. > > -- --- Leonardo Marques --- Blog: BeNerd.analyx.org Website: www.analyx.org
Re: carp devices master/backup behavior
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 +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 with "advskew 100". most of the time everything is fine, but after several reboots of the master sytem the backup system is in a state where the carp devices are in a mixed state. carp3 and carp4 for example are still MASTER and the rest of the interfaces has gone back to BACKUP state like they should. they are all in the same carp group. ideas what to check? Are you sure you're allowing carp to pass on all carpdev interfaces? Rui
Re: carp devices master/backup behavior
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 with > "advskew 100". > most of the time everything is fine, but after several reboots of the > master sytem > the backup system is in a state where the carp devices are in a mixed > state. carp3 and carp4 for example are still MASTER and the rest of the > interfaces has gone back to BACKUP state like they should. > they are all in the same carp group. ideas what to check? Are you sure you're allowing carp to pass on all carpdev interfaces? Rui -- Grudnuk demand sustenance! Today is Sweetmorn, the 52nd day of Bureaucracy in the YOLD 3173 + No matter how much you do, you never do enough -- unknown + Whatever you do will be insignificant, | but it is very important that you do it -- Gandhi + So let's do it...?
Re: Tool for HD analyzing
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 errors say "run, don't walk to the store for > replacement". Modern disks remap bad parts away from active use, when > they've run out of remappable space, they start complaining like that. > > For measuring the health of your next hard drive, it's possible > sysutils/smartmontools will do the job. > > What if you have an ata/serialata HD attached to scsi/ahci/jmb ? atactl is useless, will smartmontools work ? redargds M.K.
Re: Tool for HD analyzing
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-sector PIO, LBA48, 114473MB, 234441648 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 dkcsum: wd0 matches BIOS drive 0x82 wd0(pciide0:0:0): timeout wd0a: device timeout reading fsbn 96 of 96-127 (wd0 bn 159; cn 0 tn 2 sn 33), retrying wd0a: device timeout reading fsbn 96 of 96-127 (wd0 bn 159; cn 0 tn 2 sn 33), retrying wd0a: device timeout reading fsbn 96 of 96-127 (wd0 bn 159; cn 0 tn 2 sn 33), retrying wd0a: device timeout reading fsbn 96 of 96-127 (wd0 bn 159; cn 0 tn 2 sn 33), retrying wd0a: device timeout reading fsbn 96 of 96-127 (wd0 bn 159; cn 0 tn 2 sn 33), retrying wd0a: device timeout reading fsbn 96 of 96-127 (wd0 bn 159; cn 0 tn 2 sn 33) wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0) Thanks for all attention. Wasn't it up to the manufacturer to provide some diagnostic tool which also delivers an error code used for the RMA process. Thanks, Dorian
Re: OpenBSD most recent port installation problem
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? > > # make install > ===> Checking files for apache-httpd-2.2.6 > >> httpd-2.2.6.tar.gz doesn't seem to exist on this system. > >> Fetch http://www.reverse.net/pub/apache/httpd/httpd-2.2.6.tar.gz. > ftp: unknown option -- k > usage: ftp [-46AadEegimnptVv] [-P port] [-r seconds] [host [port]] $ cd /usr/src/usr.bin/ftp $ sudo make clean $ sudo make depend $ sudo make && sudo make install Read http://www.openbsd.org/faq/faq15.html#PortsFetch | Make sure you keep your ports tree and your OpenBSD system in sync! -- Nothing makes one so vain as being told that one is a sinner. Conscience makes egotists of us all. -- Oscar Wilde
Re: OpenBSD most recent port installation problem
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
OpenBSD 4.1 Most recent port installation problem
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]
Tool for HD analyzing
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, 114473MB, 234441648 sectors wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5 dkcsum: wd0 matches BIOS drive 0x82 wd0(pciide0:0:0): timeout wd0a: device timeout reading fsbn 96 of 96-127 (wd0 bn 159; cn 0 tn 2 sn 33), retrying wd0a: device timeout reading fsbn 96 of 96-127 (wd0 bn 159; cn 0 tn 2 sn 33), retrying wd0a: device timeout reading fsbn 96 of 96-127 (wd0 bn 159; cn 0 tn 2 sn 33), retrying wd0a: device timeout reading fsbn 96 of 96-127 (wd0 bn 159; cn 0 tn 2 sn 33), retrying wd0a: device timeout reading fsbn 96 of 96-127 (wd0 bn 159; cn 0 tn 2 sn 33), retrying wd0a: device timeout reading fsbn 96 of 96-127 (wd0 bn 159; cn 0 tn 2 sn 33) wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0), retrying wd0c: device timeout reading fsbn 0 (wd0 bn 0; cn 0 tn 0 sn 0) Thanks for all attention. -- --- Leonardo Marques --- Blog: BeNerd.analyx.org Website: www.analyx.org
Re: RAID1 powerloss - can parity rewrite be safely backgrounded?
> 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 goes into a blocking state recalculating parity before the OS starts -- you can do it manually though The PERC4 and PERC5 cards in PowerEdge servers have the ability to set the "background rebuild rate" anywhere from 10-99% of the controller bus/disk usage. ~BAS > > Matt
Re: RAID1 powerloss - can parity rewrite be safely backgrounded?
"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 functionally the same as what OpenBSD has right now.
The implications here are as follows: if the parity is checked in the
background, and a non-parity component should fail, there is a very
low, but non-zero probability of data loss. The longer it takes to
check (and correct, if necessary) the parity, the greater the chance
of loss. The value of your data should dictate whether you can live
with that increase in risk.
For the record, I do the parity checking in the background on all the
machines I look after. Since most of them can complete the check in
under an hour, there is that one hour window where some fragments of
corruption *may* have occurred (and that didn't get caught with a
filesystem check).
> I understand there is interest in replacing RAIDFrame instead of
> resynchronizing the subtree.
>
> In the mean time, find a hardware RAID Controller that can be managed by
> OpenBSD via bio(4) and grab a UPS that works with upsd(8).
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.)
Later...
Greg Oster
> On Thu, 27 Sep 2007, Rob wrote:
>
> > On 9/25/07, Matt <[EMAIL PROTECTED]> wrote:
> >> I'm running a RAID1 mirror on OpenBSD 4.1 (webserver)
> >> On a power failure the parity becomes dirty and needs rewriting, which
> >> results in > 1.5 hours 'downtime'.
> >> Is it safe to background this in /etc/rc or is that a no-no?
> >>
> >> I found a reference this was possible/safe on-list but it was a) 2003
> >> and b) dealt with RAID5.
> >> I'd like to make sure I am not doing something dangerous.
> >
> > I frankly don't know enough to guarantee that this is safe, or not,
> > but I had a RAID1 with big disks on an ancient machine that took about
> > 26 hours to check parity (! -- this wasn't my idea), and I modified
> > its rc to boot up, and then begin performing the parity check in the
> > background.
> >
> > The only caveat I would give is that the operating system was
> > installed and running on a 3rd, separate disk, and that network access
> > to the mirrored drives was disabled until the parity rewrite was
> > complete.
> >
> > - R.
Re: carp devices master/backup behavior
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 backup system is in a state where the carp devices are in a mixed state. carp3 and carp4 for example are still MASTER and the rest of the interfaces has gone back to BACKUP state like they should. they are all in the same carp group. ideas what to check?
Re: RAID1 powerloss - can parity rewrite be safely backgrounded?
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.)
Really? We've had something similar happening to us a while ago. The
system was running on a 3 disk RAID 5 array. A supermicro backplane went
up in flames[1] and the server was shut down. An engineer booted the
server without the backplane, but with one disk missing from the RAID 5
array, so upon next boot the missing disk was connected and a rebuild
was ordered.
However, the rebuild was taking too long and the server was rebooted to
do the rebuild in the background. The server came up fine and we were
searching for the necessary tools to start the background rebuild. We
thought we were in the clear when suddenly windows started acting all
weird, eventually crashed (I didn't see if it was a bluescreen, we were
working via terminal server at that time), and the server was rebooted
again. After this incident, the controller configuration was gone and
all three disks appeared as "Ready". Gone was the RAID.
We eventually were able to recover some data by re-creating the array
(luckily someone knew the blocksize originally used) and not
initializing when reconstructing the RAID. The operating system was
foobar though and couldn't be booted anymore.
This was with an intel-rebranded LSI card with an intel BIOS.
Anyone got any similar experiences with hardware RAID cards? Hardware
RAID has always been misery for me.
[1]
http://users.opengate.be/~glenn/album/index.php?folder=/Misc/Burnt%20Supermicro%20Backplane/
Re: arc0: unable to query firmware for sensor info
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 (amd64, 4.2). Without acpi it will reboot directly >>> after mounting the root device. With acpi enabled it will hang with >>> "arc0: unable to query firmware for sensor info". Uniprocessor kernels >>> would boot fine, both acpi and without. Pls. find dmesgs of those as well >>> as more info below. >> >> I'm pretty sure that message from arc is a result of interrupts not being >> hooked up correctly. >> >> also, arc doesnt hang after printing that message, it gives control back >> to the rest of the kernel. presumably the kernel is hanging while waiting >> for io on the disk to work, but of course, the disk is on arc and >> interrupts arent wired up to it correctly so just blocks. >> >> dlg > > I see. However, only bsd.mp hangs, bsd boots fine. Is there anything else I > can try? > > Stephan enable acpi so the interrupt routing in the MP case can be fixed up, broken MP BIOSes are sadly reasonably common now.
Re: carp devices master/backup behavior
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 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 backup system is in a state where the carp devices are in a mixed state. carp3 and carp4 for example are still MASTER and the rest of the interfaces has gone back to BACKUP state like they should. they are all in the same carp group. ideas what to check?
Re: RAID1 powerloss - can parity rewrite be safely backgrounded?
> 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 hardware raid solution (not supported under OpenBSD) which ate a 2.5TB filesystem due to a firmware bug -N
Odd crash with ciss
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:
CISS0: Unqueued CCB 0xe8abd200 Ready, State=1
CISS0: Unqueued CCB 0xe8abf800 Ready, State=1
Full dmesg below. After power-cycling the server, the controller told
me that there was valid data left in the cache. I had to manually run
fsck on reboot, it wouldn't auto-fix it. I didn't see anything
interesting in the logs, and the Compaq IML was empty. Any ideas what
went wrong? Thanks.
dmesg:
OpenBSD 4.1 (GENERIC.MP) #1225: Sat Mar 10 19:23:18 MST 2007
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC.MP
cpu0: Intel Pentium III ("GenuineIntel" 686-class) 931 MHz
cpu0:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real mem = 804859904 (785996K)
avail mem = 726265856 (709244K)
using 4278 buffers containing 40366080 bytes (39420K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+ BIOS, date 12/31/99, BIOS32 rev. 0 @ 0xf,
SMBIOS rev. 2.3 @ 0xf206c (25 entries)
bios0: Compaq ProLiant DL380
pcibios0 at bios0: rev 2.1 @ 0xf/0x2000
pcibios0: PCI BIOS has 7 Interrupt Routing table entries
pcibios0: PCI Interrupt Router at 000:15:0 ("ServerWorks OSB4" rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0x8000 0xc8000/0x4000! 0xcc000/0x4000
0xe8000/0x6000 0xee000/0x2000!
acpi at mainbus0 not configured
mainbus0: Intel MP Specification (Version 1.4)
cpu0 at mainbus0: apid 1 (boot processor)
cpu0: apic clock running at 132 MHz
cpu1 at mainbus0: apid 0 (application processor)
cpu1: Intel Pentium III ("GenuineIntel" 686-class) 931 MHz
cpu1:
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
mainbus0: bus 0 is type PCI
mainbus0: bus 3 is type PCI
mainbus0: bus 9 is type ISA
ioapic0 at mainbus0: apid 8 pa 0xfec0, version 11, 35 pins
ioapic0: misconfigured as apic 0, remapped to apid 8
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 "ServerWorks CNB20LE Host" rev 0x05
pchb1 at pci0 dev 0 function 1 "ServerWorks CNB20LE Host" rev 0x05
pci1 at pchb1 bus 3
ciss0 at pci1 dev 5 function 0 "Compaq Smart Array 5300 rev.2" rev 0x02:
apic 8 int 11 (irq 11)
ciss0: 1 LD, HW rev 0, FW 3.54/3.54
scsibus0 at ciss0: 1 targets
sd0 at scsibus0 targ 0 lun 0: SCSI0
0/direct fixed
sd0: 69455MB, 69455 cyl, 64 head, 32 sec, 512 bytes/sec, 142245120 sec total
cac0 at pci0 dev 1 function 0 "Symbios Logic 53c1510" rev 0x02: apic 8
int 5 (irq 5) Compaq Integrated Array
cac0: no volumes defined
fxp0 at pci0 dev 2 function 0 "Intel 8255x" rev 0x08, i82559: apic 8 int
10 (irq 10), address 00:02:a5:28:55:62
inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 4
"ATI Mach64 GV" rev 0x7a at pci0 dev 3 function 0 not configured
"Compaq Netelligent ASMC" rev 0x00 at pci0 dev 4 function 0 not configured
ppb0 at pci0 dev 5 function 0 "Intel S21152BB PCI-PCI" rev 0x00
pci2 at ppb0 bus 1
vga1 at pci2 dev 0 function 0 "ATI Rage XL" rev 0x27
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
"Compaq Netelligent ASMC" rev 0x00 at pci2 dev 1 function 0 not configured
vendor "Compaq", unknown product 0x005a (class memory subclass
miscellaneous, rev 0x00) at pci2 dev 2 function 0 not configured
vendor "Compaq", unknown product 0x00b1 (class memory subclass
miscellaneous, rev 0x01) at pci2 dev 4 function 0 not configured
piixpm0 at pci0 dev 15 function 0 "ServerWorks OSB4" rev 0x4f: SMBus
disabled
pciide0 at pci0 dev 15 function 1 "ServerWorks OSB4 IDE" rev 0x00: DMA
atapiscsi0 at pciide0 channel 0 drive 0
scsibus1 at atapiscsi0: 2 targets
cd0 at scsibus1 targ 0 lun 0: SCSI0 5/cdrom
removable
cd0(pciide0:0:0): using PIO mode 4, DMA mode 2
isa0 at mainbus0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
pckbc0: using irq 12 for aux slot
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
midi0 at pcppi0:
spkr0 at pcppi0
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo
pctr: 686-class user-level performance counters enabled
mtrr: Pentium Pro MTRR support
dkcsum: sd0 matches BIOS drive 0x80
root on sd0a
rootdev=0x400 rrootdev=0xd00 rawdev=0xd02
Re: Is AMD64 page out of date about W^X?
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 (...) but since Intel left out support for the page table NXE bit (No-EXecute) there is no W^X support on the Intel CPUs." If indeed this is supported (and the dmesg for my Core 2 on 4.1 does have NXE next to the processor) this really should be changed. I understand that there is a lot of unhappiness with Intel's Core architecture... however there are P4s that appear to have support for NXE. I understand that updates to the webpages could take a bit and that people might be very busy with development. I do feel that of the pages people look at when considering OpenBSD... the platform pages are very important. When I built my most recent computer... I very carefully checked various motherboards with those pages to make sure that things would run smoothly. If I am being unreasonable or am incorrect... please let me know. So far I have only heard from one person who seems to be knowledgeable but didn't really give me a clear answer on whether I should feel comfortable running AMD64 on my chip. A few other people replied but they did not seem to really know the answer. Could someone higher up comment or let me know if the page is planned to be changed one day in the future? - Original Message - From: <[EMAIL PROTECTED]> To: Sent: Thursday, September 20, 2007 6:21 PM Subject: Re: Is AMD64 page out of date about W^X? I am not so sure of that.If you go here: http://processorfinder.intel.com/Default.aspx and then select Core 2 Duo or some such... then filter by "Execute Disable Bit" under supported features... you will see a bunch of Core 2s. The Core 2 is ia32e. It is not EM64T. According to some sites... if anyone really cares I will find the links... Intel started putting ia32e chips out in late 2004.. this includes some Pentium 4's. I believe Theo was expressing his disappointment around Feb of 2004. Anyway... the page does seem to be updated semi-regularly.. if the date at the bottom is accurate.. it was last changed on 2007/08/10 If Intel did indeed start including it on chips in early 2005... it would be nice to know that instead of a blanket statement that Intel does not support the NXE bit at all. It is important when making purchasing decisions and architecture choices. Darren Spruell <[EMAIL PROTECTED]> wrote: On 9/20/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > According to: > http://www.openbsd.org/amd64.html > W^X will not work on Intel's 64 bit chips. I for one chose to go with > i386 on my Core 2 because of this fact alone. Intel produces 2 families of 64-bit processors; the EM64T and an AMD64 family chip. You're probably misinterpreting what is meant to indicate the former. http://en.wikipedia.org/wiki/64-bit#Current_64-bit_microprocessor_architectures http://www.xbitlabs.com/news/cpu/display/20040310223922.html DS
files in root directory
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! _ Discover the new Windows Vista http://search.msn.com/results.aspx?q=windows+vista&mkt=en-US&form=QBRE
Re: Tool for HD analyzing
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 of the same sector to try to recover the data. They then use heuristics to try to determine what the original data most likely was. If this process is successful enough the block gets re-assigned. Most disks don't do verifies on writes (too slow) and rely on the recovery algorithm to reassign these blocks; which are triggered by subsequent reads. RAID manufacturers implement algorithms that continuous read all sectors of idle disks to ensure data integrity. When they run into a failure they first let the disk try to recover and if that fails they use parity to recover the block. They also will "puncture" the sector so that the disk will skip it going forward. Some of the dmesg lines pasted in this message are likely LBA relocations that take too long. There is no set timeout in the spec and therefore vendors try really hard and long to recover the data resulting in OS timeouts. A good example is calculating how long it takes to read an LBA 15000 times on a 1 RPM disk. Add some fudge in there for the head to find the exact spot and you'll see that it gets in excess of seconds. Repeat that a few times due to various retries in various layers and you'll see where those lengthy timeouts come from. On Fri, Sep 28, 2007 at 02:47:48PM +0200, Claudio Jeker wrote: > 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? > > > > To my mind that kind of errors say "run, don't walk to the store for > > replacement". Modern disks remap bad parts away from active use, when > > they've run out of remappable space, they start complaining like that. > > > > Remapping is only possible when writing to blocks. The disk can not remap > on reads. By forcing writes to such blocks you can remap them but the data > on them is still lost. I use some partitions with almost only read access > that had bad blocks and I could fix the problem with dd if=/dev/zero > of=/dev/rsd0x (not important data so I did not replace the disk) > > -- > :wq Claudio
Re: Is AMD64 page out of date about W^X?
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."?
Re: RAID1 powerloss - can parity rewrite be safely backgrounded?
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 having it happen on two different machines, at two different employers, in two different brands of servers (Dell, HP Netserver) made me a real believer in Adaptec. I've had generally good luck with Compaq/HP and LSI controllers.
OpenNTPD not syncing anymore with recent i386 snaphots?
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 OpenBSD servers. Afterwards I checked two other OpenBSD servers in the lab (also one running on VMware and another on physical hardware), one running an i386 snapshot from the end of March and the other one running a snapshot from the beginning of June. These two laters servers were both synced perfectly with the NTP server. I took a look at the /var/log/daemon file on all four servers and realized that the two unsynced servers do *not* have any "adjusting local clock by X.XXs" messages, while the two synced ones do. >From the logs it looks like OpenNTPD on the new servers *does* take note of the time delta beetn the server's local clock and the NTP server's time, yet it doesn't do anything to sync up the OpenBSD server to the NTP server. I installed a new VMware machine from an i386 snapshot I downloaded just a few hours ago dated September 24th to see if I'd have the same behavior as the September 13th servers; it turns out that I do, meaning that the server does not seem to sync via NTP either. I haven't noticed any other similar and recent comment about OpenNTPD problems on the list, so I'm fairly sure this is not a bug. Has anybody else observed the same behavior on their system? Has something changed recently regarding OpenNTPD that I've simply missed? Thanks, -Martin
Re: OpenNTPD not syncing anymore with recent i386 snaphots?
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 synced with the NTP server in my lab, even though I run > OpenNTPD on all my OpenBSD servers. > I installed a new VMware machine from an i386 snapshot I downloaded > just a few hours ago dated September 24th to see if I'd have the same > behavior as the September 13th servers; it turns out that I do, > meaning that the server does not seem to sync via NTP either. > Has anybody else observed the same behavior on their system? Has > something changed recently regarding OpenNTPD that I've simply missed? I'm running the same i386 snapshot, and everything seems normal in /var/log/daemon. Some peer valid/invalid, some adjusting local clock, a clock is now synced, and then some adjusting clock frequency. 13:19:01 - ntp engine ready 13:52:05 - clock is now synced Which seems very typical for this machine. -- Darrin Chandler| Phoenix BSD User Group | MetaBUG [EMAIL PROTECTED] | http://phxbug.org/ | http://metabug.org/ http://www.stilyagin.com/ | Daemons in the Desert | Global BUG Federation
Re: Is AMD64 page out of date about W^X?
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: Sent: Friday, September 28, 2007 10:24 PM Subject: Re: Is AMD64 page out of date about W^X? 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."?
