Re: no output from /etc/daily

[Norman Golisz]

Hello Robert,

On Sat Sep 22 2012 15:16, Robert Connolly wrote:
> My local mail is not working, and I don't know how to diagnose it. I'm
> using OpenSMTP.

please check your /var/log/maillog. And, what version are you running?

Re: Router project on OpenBSD questions

[Christoph Leser]

Thanks for the replies.



You say, there have been problems with NAT-T but these have been fixed.



I am on openBSD 5.2 current and have problems with NAT-T to cisco, which I have 
not had when I was on openBSD 4.7.



The problem is, as seen in the debug output from isakmpd, that isakmpd detects 
that there is a NAT device in between ( it even tells that ‘we are behind 
it’ ) and then proposes ‘ENCAPULATION_MODE=TUNNEL’ instead of 
‘ENCAPLULATION_MODE=UDP_ENC_TUNNEL’ for phase two, which is ( correctly ? ) 
rejected by the remote peer.





Regards

Christoph



Von: Stuart Henderson [mailto:s...@spacehopper.org]

Gesendet: Samstag, 22. September 2012 16:52

An: Christoph Leser; misc@openbsd.org

Betreff: Re: Router project on OpenBSD questions



Search the archives for the cisco nat-t problem, I sent a mail with more 
details and I think there was a patch with it. Pretty sure that would have 
affected older OpenBSD versions too though.

Christoph Leser mailto:le...@sup-logistik.de>> wrote:







On Feb 28, 2012, Stuart Henderson wrote:





List:   openbsd-misc



Subject:Re: Router project on OpenBSD 
questions



From:   Stuart Henderson 



Date:   2012-02-28 
13:57:45



Message-ID: slrnjkpnao.r14.stu () naiad ! spacehopper ! 
org



[Download message RAW]











>IPsec is mostly compatible but there's a bit of breakage if the ipsec



>gateways are behind NAT (because Cisco still follows a very old nat-t draft



>rather than the standard).











I think I have read similar remarks about NAT-T and Cisco interoperability. But 
I have found no details about what the problem is with cisco.







I completely failed when I tried to move from OBSD 4.6 to OBSD 5.2, because of 
NAT-T trouble with cisco. I described my experience in a message to this list 
'ISAMPD NAT trouble with openBSD 5.2







Any hints to information about interoperabilty issues with cisco ( and possible 
solutions ) would be highly welcome















Mit freundlichen Grüßen



Christoph Leser



S&P Computersysteme GmbH

Zettachring 4

70567 Stuttgart Fasanenhof



EMail: le...@sup-logistik.de

Re: Router project on OpenBSD questions

[Christoph Leser]

It seems that the patch from Stuart Henderson, proposed on Aug.4 2012 on tech@  
has not made it into –current yet.



Von: Stuart Henderson [mailto:s...@spacehopper.org]

Gesendet: Samstag, 22. September 2012 16:52

An: Christoph Leser; misc@openbsd.org

Betreff: Re: Router project on OpenBSD questions



Search the archives for the cisco nat-t problem, I sent a mail with more 
details and I think there was a patch with it. Pretty sure that would have 
affected older OpenBSD versions too though.

Christoph Leser mailto:le...@sup-logistik.de>> wrote:







On Feb 28, 2012, Stuart Henderson wrote:





List:   openbsd-misc



Subject:Re: Router project on OpenBSD 
questions



From:   Stuart Henderson 



Date:   2012-02-28 
13:57:45



Message-ID: slrnjkpnao.r14.stu () naiad ! spacehopper ! 
org



[Download message RAW]











>IPsec is mostly compatible but there's a bit of breakage if the ipsec



>gateways are behind NAT (because Cisco still follows a very old nat-t draft



>rather than the standard).











I think I have read similar remarks about NAT-T and Cisco interoperability. But 
I have found no details about what the problem is with cisco.







I completely failed when I tried to move from OBSD 4.6 to OBSD 5.2, because of 
NAT-T trouble with cisco. I described my experience in a message to this list 
'ISAMPD NAT trouble with openBSD 5.2







Any hints to information about interoperabilty issues with cisco ( and possible 
solutions ) would be highly welcome















Mit freundlichen Grüßen



Christoph Leser



S&P Computersysteme GmbH

Zettachring 4

70567 Stuttgart Fasanenhof



EMail: le...@sup-logistik.de

Re: Router project on OpenBSD questions

[Stuart Henderson]

On 2012/09/24 13:24, Christoph Leser wrote:
> It seems that the patch from Stuart Henderson, proposed on Aug.4 2012
> on tech@  has not made it into –current yet.

I only forwarded it, the patch is from hshoexer. Also it is only a partial
diff, not suitable to be committed, the encap mode value needs to be
controllable per-peer so it needs a config option, changes to ipsecctl, etc.

This problem certainly would have affected older OpenBSD versions though,
if they negotiated NAT-T they would have used the value from the RFC not the
one from the internet-draft that cisco use.

Have you tried just disabling nat-t completely, see the options list in
isakmpd(8), to see what happens?

Compiling from the source on -current Failed

[Insan Praja SW]

Hi Misc@,

I was just trying to upgrade to -current by compiling from the source, on  
an old (6 years) server. I updated make(1) first to the latest (compiling  
from the source, of course) and compiling the kernel. Using the FAQ  
instruction, make(1) failed at;


{standard input}: Assembler messages:
{standard input}:376: Error: no such instruction: `rdrand %edx'
*** Error code 1 in target cpu.o

Stop in /usr/src/sys/arch/i386/compile/GENERIC.MP:
 Exit status 1 (line 933 of Makefile, target cpu.o)

Thanks,

Insan Praja

DMESG:
--
OpenBSD 5.2-current (GENERIC.MP) #6: Wed Aug 29 19:01:43 WIT 2012
r...@dev.xxx.net:/usr/src/sys/arch/i386/compile/GENERIC.MP
RTC BIOS diagnostic error e
cpu0: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz ("GenuineIntel" 686-class) 2.41  
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,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF

real mem  = 2142711808 (2043MB)
avail mem = 2096783360 (1999MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 03/26/07, SMBIOS rev. 2.4 @  
0x7fbe4000 (43 entries)
bios0: vendor Intel Corporation version  
"S3000.86B.02.00.0054.061120091710" date 06/11/2009

bios0: Intel S3000AH
acpi0 at bios0: rev 2
acpi0: sleep states S0 S1 S4 S5
acpi0: tables DSDT SLIC FACP APIC WDDT HPET MCFG ASF! SSDT SSDT SSDT SSDT  
SSDT HEST BERT ERST EINJ
acpi0: wakeup devices SLPB(S4) P32_(S4) UAR1(S1) PEX4(S4) PEX5(S4)  
UHC1(S1) UHC2(S1) UHC3(S1) UHC4(S1) EHCI(S1) AC9M(S4) AZAL(S4)

acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 266MHz
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz ("GenuineIntel" 686-class) 2.41  
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,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF

cpu2 at mainbus0: apid 1 (application processor)
cpu2: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz ("GenuineIntel" 686-class) 2.41  
GHz
cpu2:  
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,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF

cpu3 at mainbus0: apid 3 (application processor)
cpu3: Intel(R) Xeon(R) CPU X3220 @ 2.40GHz ("GenuineIntel" 686-class) 2.41  
GHz
cpu3:  
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,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,LAHF

ioapic0 at mainbus0: apid 5 pa 0xfec0, version 20, 24 pins
ioapic0: misconfigured as apic 0, remapped to apid 5
acpihpet0 at acpi0: 14318179 Hz
acpimcfg0 at acpi0 addr 0xf000, bus 0-127
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 4 (P32_)
acpiprt2 at acpi0: bus 1 (PEX0)
acpiprt3 at acpi0: bus -1 (PEX1)
acpiprt4 at acpi0: bus -1 (PEX2)
acpiprt5 at acpi0: bus -1 (PEX3)
acpiprt6 at acpi0: bus 2 (PEX4)
acpiprt7 at acpi0: bus 3 (PEX5)
acpicpu0 at acpi0: PSS
acpicpu1 at acpi0: PSS
acpicpu2 at acpi0: PSS
acpicpu3 at acpi0: PSS
acpibtn0 at acpi0: SLPB
bios0: ROM list: 0xc/0x9000 0xc9000/0x1000 0xca000/0x1000
cpu0: Enhanced SpeedStep 2401 MHz: speeds: 2394, 1596 MHz
pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel E7230 Host" rev 0x00
ppb0 at pci0 dev 28 function 0 "Intel 82801GB PCIE" rev 0x01: apic 5 int 17
pci1 at ppb0 bus 1
ppb1 at pci0 dev 28 function 4 "Intel 82801G PCIE" rev 0x01: apic 5 int 17
pci2 at ppb1 bus 2
em0 at pci2 dev 0 function 0 "Intel PRO/1000 PT (82571EB)" rev 0x06: apic  
5 int 16, address 00:15:17:86:54:08
em1 at pci2 dev 0 function 1 "Intel PRO/1000 PT (82571EB)" rev 0x06: apic  
5 int 17, address 00:15:17:86:54:09

ppb2 at pci0 dev 28 function 5 "Intel 82801G PCIE" rev 0x01: apic 5 int 16
pci3 at ppb2 bus 3
em2 at pci3 dev 0 function 0 "Intel PRO/1000MT (82573E)" rev 0x03: msi,  
address 00:15:17:25:0a:9d

"Intel 82573E Serial" rev 0x03 at pci3 dev 0 function 3 not configured
"Intel 82573E KCS" rev 0x03 at pci3 dev 0 function 4 not configured
uhci0 at pci0 dev 29 function 0 "Intel 82801GB USB" rev 0x01: apic 5 int 23
uhci1 at pci0 dev 29 function 1 "Intel 82801GB USB" rev 0x01: apic 5 int 19
uhci2 at pci0 dev 29 function 2 "Intel 82801GB USB" rev 0x01: apic 5 int 18
uhci3 at pci0 dev 29 function 3 "Intel 82801GB USB" rev 0x01: apic 5 int 16
ehci0 at pci0 dev 29 function 7 "Intel 82801GB USB" rev 0x01: apic 5 int 23
ehci0: timed out waiting for BIOS
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb3 at pci0 dev 30 function 0 "Intel 82801BA Hub-to-PCI" rev 0xe1
pci4 at ppb3 bus 4
skc0 at pci4 dev 0 function 0 "D-Link DGE-530T B1" rev 0x11, Yukon Lite  
(0x9): apic 5 int 21

sk0 at skc0 port A: address 00:1b:11:10:07:26
eeph

Re: Compiling from the source on -current Failed

[Stefan Sperling]

On Tue, Sep 25, 2012 at 12:29:25AM +0700, Insan Praja SW wrote:
> Hi Misc@,
> 
> I was just trying to upgrade to -current by compiling from the
> source, on an old (6 years) server. I updated make(1) first to the
> latest (compiling from the source, of course) and compiling the
> kernel. Using the FAQ instruction, make(1) failed at;
> 
> {standard input}: Assembler messages:
> {standard input}:376: Error: no such instruction: `rdrand %edx'
> *** Error code 1 in target cpu.o
> 
> Stop in /usr/src/sys/arch/i386/compile/GENERIC.MP:
>  Exit status 1 (line 933 of Makefile, target cpu.o)

Upgrade the linker and compiler first, see
http://www.openbsd.org/faq/current.html#20120823 and
http://www.openbsd.org/faq/current.html#20120831

Re: Compiling from the source on -current Failed

[Stefan Sperling]

On Mon, Sep 24, 2012 at 07:52:44PM +0200, Stefan Sperling wrote:
> On Tue, Sep 25, 2012 at 12:29:25AM +0700, Insan Praja SW wrote:
> > Hi Misc@,
> > 
> > I was just trying to upgrade to -current by compiling from the
> > source, on an old (6 years) server. I updated make(1) first to the
> > latest (compiling from the source, of course) and compiling the
> > kernel. Using the FAQ instruction, make(1) failed at;
> > 
> > {standard input}: Assembler messages:
> > {standard input}:376: Error: no such instruction: `rdrand %edx'
> > *** Error code 1 in target cpu.o
> > 
> > Stop in /usr/src/sys/arch/i386/compile/GENERIC.MP:
> >  Exit status 1 (line 933 of Makefile, target cpu.o)
> 
> Upgrade the linker and compiler first, see
> http://www.openbsd.org/faq/current.html#20120823 and
> http://www.openbsd.org/faq/current.html#20120831

And... did you really say 6 years old A source upgrade from
a system that old is not supported and the FAQ clearly states that:
http://www.openbsd.org/faq/faq5.html#BldBinary

Just upgrade to the latest snapshot, and then compile from source.
Trying to do anything else is a waste of time.

Re: Compiling from the source on -current Failed

[Nick Holland]

On 09/24/2012 01:52 PM, Stefan Sperling wrote:

On Tue, Sep 25, 2012 at 12:29:25AM +0700, Insan Praja SW wrote:

Hi Misc@,

I was just trying to upgrade to -current by compiling from the
source, on an old (6 years) server. I updated make(1) first to the
latest (compiling from the source, of course) and compiling the
kernel. Using the FAQ instruction, make(1) failed at;

{standard input}: Assembler messages:
{standard input}:376: Error: no such instruction: `rdrand %edx'
*** Error code 1 in target cpu.o

Stop in /usr/src/sys/arch/i386/compile/GENERIC.MP:
  Exit status 1 (line 933 of Makefile, target cpu.o)


Upgrade the linker and compiler first, see
http://www.openbsd.org/faq/current.html#20120823 and
http://www.openbsd.org/faq/current.html#20120831



or actually follow the FAQ instructions...

"5.3.2 - Install or Upgrade to closest available binary
The first step in building from source is to make sure you have the 
closest available binary installed."


You upgrade to -current by installing snapshots.
Compiling from source is just what you do for fun, it is not part of the 
upgrade process.  I think this is made pretty clear in the FAQ.


Nick.

Re: Router project on OpenBSD questions

[Christoph Leser]

Thanks for clarification.



I disabled NAT-T with isakmpd -K -T.



A few of my VPNs came to life with this setting, but were instable ( rapid 
renegotiation ).



Still only about one third of my vpns (that worked with OpenBSD 4.6 ) work with 
OpenBSD 5.2.



Many negotiations get rejected by OpenBSD with 'NO PROPOSAL CHOSEN', or 
'PAYLOAD MALFORMED' or 'INVALID ID'



For some of those I see messages in /var/log/messages like :



Sep 24 20:00:09 q-dsl isakmpd[3828]: attribute_unacceptable: attr 
ENCRYPTION_ALGORITHM does not exist in 
phase1-transform-peer-a.b.c.d-PRE_SHARED-MD5-AES128



( for a VPN peer  which is configured with MD5-AES-128 in ipsec.conf and which, 
according to tcpdump, tries to negotiate exactly MD5 and AES-128  ).



No idea what this means.



Regards



> -Ursprüngliche Nachricht-

> Von: Stuart Henderson [mailto:s...@spacehopper.org]

> Gesendet: Montag, 24. September 2012 16:41

> An: Christoph Leser

> Cc: misc@openbsd.org

> Betreff: Re: Router project on OpenBSD questions

> 

> On 2012/09/24 13:24, Christoph Leser wrote:

> > It seems that the patch from Stuart Henderson, proposed on Aug.4 2012

> > on tech@  has not made it into –current yet.

> 

> I only forwarded it, the patch is from hshoexer. Also it is only a partial 
> diff,

> not suitable to be committed, the encap mode value needs to be

> controllable per-peer so it needs a config option, changes to ipsecctl, etc.

> 

> This problem certainly would have affected older OpenBSD versions though,

> if they negotiated NAT-T they would have used the value from the RFC not

> the one from the internet-draft that cisco use.

> 

> Have you tried just disabling nat-t completely, see the options list in

> isakmpd(8), to see what happens?

Reading a damaged disk

[STeve Andre']

Is there a way, with something like the scsi(1) command, to tell
the sd driver to ignore the error below?  I've some data on this
disk that I'd like to get back.  I realize that all hell may break
loose trying something like this but I'd like to try..  Any other
ideas on how to get the disk stable enough to look at a few
files would be appreciated.  I have a backup but wouldn't mind
the latest data.

tnx, STeve Andre'



Sep 24 15:22:18 paladin /bsd: umass0 at uhub0
Sep 24 15:22:18 paladin /bsd:  port 1 configuration 1 interface 0 
"JMicron USB to ATA/ATAPI Bridge" rev 2.00/1.00 addr 2

Sep 24 15:22:18 paladin /bsd: umass0: using SCSI over Bulk-Only
Sep 24 15:22:18 paladin /bsd: scsibus4 at umass0: 2 targets, initiator 0
Sep 24 15:22:18 paladin /bsd: sd3 at scsibus4 targ 1 lun 0: 00JS-75NCB3, > SCSI2 0/direct fixed serial.152d2352DCA4469971FF
Sep 24 15:22:18 paladin /bsd: sd3: 238418MB, 512 bytes/sector, 488281250 
sectors
Sep 24 15:22:18 paladin /bsd: sd3(umass0:1:0): Check Condition (error 
0x70) on opcode 0x28

Sep 24 15:22:18 paladin /bsd: SENSE KEY: Media Error
Sep 24 15:22:18 paladin /bsd:  ASC/ASCQ: Unrecovered Read Error
Sep 24 15:22:18 paladin /bsd: sd3(umass0:1:0): Check Condition (error 
0x70) on opcode 0x28

Sep 24 15:22:18 paladin /bsd: SENSE KEY: Media Error
Sep 24 15:22:18 paladin /bsd:  ASC/ASCQ: Unrecovered Read Error
Sep 24 15:22:18 paladin /bsd: sd3(umass0:1:0): Check Condition (error 
0x70) on opcode 0x28

Sep 24 15:22:18 paladin /bsd: SENSE KEY: Media Error
Sep 24 15:22:18 paladin /bsd:  ASC/ASCQ: Unrecovered Read Error

Re: Router project on OpenBSD questions

[Otto Moerbeek]

On Mon, Sep 24, 2012 at 06:57:26PM +, Christoph Leser wrote:

> Thanks for clarification.
> 
> I disabled NAT-T with isakmpd -K -T.
> 
> A few of my VPNs came to life with this setting, but were instable ( rapid 
> renegotiation ).
> 
> Still only about one third of my vpns (that worked with OpenBSD 4.6 ) work 
> with OpenBSD 5.2.
> 
> Many negotiations get rejected by OpenBSD with 'NO PROPOSAL CHOSEN', or 
> 'PAYLOAD MALFORMED' or 'INVALID ID'
> 
> For some of those I see messages in /var/log/messages like :
> 
> Sep 24 20:00:09 q-dsl isakmpd[3828]: attribute_unacceptable: attr 
> ENCRYPTION_ALGORITHM does not exist in 
> phase1-transform-peer-a.b.c.d-PRE_SHARED-MD5-AES128
> 
> ( for a VPN peer  which is configured with MD5-AES-128 in ipsec.conf and 
> which, according to tcpdump, tries to negotiate exactly MD5 and AES-128  ).
> 
> No idea what this means.

Are you running an ipsecctl from about a week ago?

For two days or so there was a bug in it. This bug was fixed by this commit:
http://www.openbsd.org/cgi-bin/cvsweb/src/sbin/ipsecctl/ike.c.diff?r1=1.76;r2=1.77;only_with_tag=MAIN

-Otto

> 
> Regards
> 
> > -Urspr??ngliche Nachricht-
> > Von: Stuart Henderson [mailto:s...@spacehopper.org]
> > Gesendet: Montag, 24. September 2012 16:41
> > An: Christoph Leser
> > Cc: misc@openbsd.org
> > Betreff: Re: Router project on OpenBSD questions
> > 
> > On 2012/09/24 13:24, Christoph Leser wrote:
> > > It seems that the patch from Stuart Henderson, proposed on Aug.4 2012
> > > on tech@  has not made it into ???current yet.
> > 
> > I only forwarded it, the patch is from hshoexer. Also it is only a partial 
> > diff,
> > not suitable to be committed, the encap mode value needs to be
> > controllable per-peer so it needs a config option, changes to ipsecctl, etc.
> > 
> > This problem certainly would have affected older OpenBSD versions though,
> > if they negotiated NAT-T they would have used the value from the RFC not
> > the one from the internet-draft that cisco use.
> > 
> > Have you tried just disabling nat-t completely, see the options list in
> > isakmpd(8), to see what happens?

Re: Reading a damaged disk

[Geoff Steckel]

On 09/24/2012 03:30 PM, STeve Andre' wrote:
> Is there a way, with something like the scsi(1) command, to tell
> the sd driver to ignore the error below?  I've some data on this
> disk that I'd like to get back.  I realize that all hell may break
> loose trying something like this but I'd like to try..  Any other
> ideas on how to get the disk stable enough to look at a few
> files would be appreciated.  I have a backup but wouldn't mind
> the latest data.
>
> tnx, STeve Andre'
>
>
>
> Sep 24 15:22:18 paladin /bsd: umass0 at uhub0
> Sep 24 15:22:18 paladin /bsd:  port 1 configuration 1 interface 0 
> "JMicron USB to ATA/ATAPI Bridge" rev 2.00/1.00 addr 2
> Sep 24 15:22:18 paladin /bsd: umass0: using SCSI over Bulk-Only
> Sep 24 15:22:18 paladin /bsd: scsibus4 at umass0: 2 targets, initiator 0
> Sep 24 15:22:18 paladin /bsd: sd3 at scsibus4 targ 1 lun 0:  00JS-75NCB3, > SCSI2 0/direct fixed serial.152d2352DCA4469971FF
> Sep 24 15:22:18 paladin /bsd: sd3: 238418MB, 512 bytes/sector, 
> 488281250 sectors
> Sep 24 15:22:18 paladin /bsd: sd3(umass0:1:0): Check Condition (error 
> 0x70) on opcode 0x28
> Sep 24 15:22:18 paladin /bsd: SENSE KEY: Media Error
> Sep 24 15:22:18 paladin /bsd:  ASC/ASCQ: Unrecovered Read Error
> Sep 24 15:22:18 paladin /bsd: sd3(umass0:1:0): Check Condition (error 
> 0x70) on opcode 0x28
> Sep 24 15:22:18 paladin /bsd: SENSE KEY: Media Error
> Sep 24 15:22:18 paladin /bsd:  ASC/ASCQ: Unrecovered Read Error
> Sep 24 15:22:18 paladin /bsd: sd3(umass0:1:0): Check Condition (error 
> 0x70) on opcode 0x28
> Sep 24 15:22:18 paladin /bsd: SENSE KEY: Media Error
> Sep 24 15:22:18 paladin /bsd:  ASC/ASCQ: Unrecovered Read Error
It's unlikely that anything would help. This looks like reading block 0 
fails.
If the disk goes click-click-click, nothing will help.

Attempting to mount any partition will probably fail.

Try:

dd if=/dev/rsd3c of=/dev/null count=1 skip=5

If this command succeeds, then you have a chance of finding something.
You have two options: search through the raw disk for possibly useful data
or attempt to make a partial disk image on a new drive, filling in the 
correct
fdisk and disklabel data. In either case, don't attempt any operation on 
block 0
or anything in the first (say) 1000 blocks.

If you get errors from attempting to read blocks far away from 0, it's
likely that the disk is now a paperweight or a source of two powerful 
magnets.

Geoff Steckel

Re: Reading a damaged disk

[Brian Seklecki (Mobile)]

CloneZilla has a provision for backing-off invalid/unreadble sectors using 
a configurable set of thresholds.


  ~BAS (Hates to recommend GNU/Linux based systems, but G4U didn't cut it
with my last failed drive)

Microsoft Wireless Mobile Mouse 3500

[Justin Lindberg]

Hello again misc,

I recently bought a Microsoft Wireless Mobile Mouse 3500, and I assumed
it would work like most any other mouse on OpenBSD.  Unfortunately it
did not.  After googling, I found a patch on the following page,
which again unfortunately seems down at the moment, and moreover it's in
Japanese, of which I don't understand a word:

http://yasuoka.net/~yasuoka/hack-2012.html

At first I thought the patch was working perfectly in an amd64 otherwise
generic MP kernel, but the mouse has a tendency to "slow down" and
become unresponsive over time, and then I have to power-cycle the mouse
itself in order to get it to work again.

I'm inclined to think it's just a piece of junk, but is there any hope
to support this mouse, or should I simply avoid all Microsoft mice?

Thanks,
Justin

Re: Reading a damaged disk

[Robert Halberg]

I'm not sure if it's available for OpenBSD, but there's dd_rescue as well,
which I gather substitutes blocks of zeros for any unreadable sectors.

That would allow you to create an image file with some "holes" filled in
with zeros.  You then would be able to avoid I/O errors by working against
that image file instead of the disk itself.


Good luck!


On Mon, Sep 24, 2012 at 3:33 PM, Brian Seklecki (Mobile) <
laval...@spiritual-machines.org> wrote:

> CloneZilla has a provision for backing-off invalid/unreadble sectors using
> a configurable set of thresholds.
>
>   ~BAS (Hates to recommend GNU/Linux based systems, but G4U didn't cut it
> with my last failed drive)
>
>


-- 
*This email is intended only for its recipients.  If you are reading this,
and are not a recipient of this email, won't you please explain to me how
this happened?  Luck must be on your side, or perhaps you're just a
shoulder-surfer extraordinaire.

Please think about the environment, then print this email.
*

Re: no output from /etc/daily

[Robert Connolly]

Thanks. That log file got me in the right direction to fixing it.

It was because I forward local mail to gmail, and I changed my password.

On Mon, Sep 24, 2012 at 2:04 AM, Norman Golisz  wrote:

> Hello Robert,
>
> On Sat Sep 22 2012 15:16, Robert Connolly wrote:
> > My local mail is not working, and I don't know how to diagnose it. I'm
> > using OpenSMTP.
>
> please check your /var/log/maillog. And, what version are you running?

Re: Reading a damaged disk

[Paolo Aglialoro]

Possible causes and solutions:

1. magnetically damaged surface ---> spinrite then mount ro and use
dd_rescue
2. damaged electronics ---> mount ro and try dd_rescue; if it fails find a
board of same hd with SAME FW and try to swap
3. damaged mechanics ---> send it to white room
4. damaged (debris scratched) surface ---> go on pilgrimage

Bye & good luck!

Compiling from the source on -current Failed

[Insan Praja SW]

Hi Misc@,

Forgot one thing that on newer machine, this is not happening;

Thanks,

Insan Praja

DMESG:
--
OpenBSD 5.2-current (GENERIC.MP) #36: Mon Sep 24 00:28:08 WIT 2012
r...@yyy.xxx.zzz:/usr/src/sys/arch/i386/compile/GENERIC.MP
RTC BIOS diagnostic error 80
cpu0: Intel(R) Xeon(R) CPU X3430 @ 2.40GHz ("GenuineIntel" 686-class) 2.40  
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,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,LAHF

real mem  = 2135588864 (2036MB)
avail mem = 2089746432 (1992MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 07/23/10, BIOS32 rev. 0 @ 0xfd7e1,  
SMBIOS rev. 2.5 @ 0x7f6b9000 (55 entries)

bios0: vendor IBM Corp. version "-[GYE144AUS-1.09]-" date 12/16/2010
bios0: IBM 81Y6793
acpi0 at bios0: rev 2
acpi0: sleep states S0 S1 S5
acpi0: tables DSDT FACP TCPA APIC MCFG SLIC HPET SSDT SSDT ERST DMAR
acpi0: wakeup devices PCIB(S4) POP3(S4) POP1(S4) POP6(S4) POP5(S4)  
PEX1(S4) PEX2(S4) PEX3(S4) PEX4(S4) PEX5(S4) EHI1(S3) EHI2(S3) PWRB(S3)

acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: apic clock running at 132MHz
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Xeon(R) CPU X3430 @ 2.40GHz ("GenuineIntel" 686-class) 2.40  
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,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,LAHF

cpu2 at mainbus0: apid 4 (application processor)
cpu2: Intel(R) Xeon(R) CPU X3430 @ 2.40GHz ("GenuineIntel" 686-class) 2.40  
GHz
cpu2:  
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,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,LAHF

cpu3 at mainbus0: apid 6 (application processor)
cpu3: Intel(R) Xeon(R) CPU X3430 @ 2.40GHz ("GenuineIntel" 686-class) 2.40  
GHz
cpu3:  
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,PBE,NXE,LONG,SSE3,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,SSE4.1,SSE4.2,POPCNT,LAHF

ioapic0 at mainbus0: apid 8 pa 0xfec0, version 20, 24 pins
acpimcfg0 at acpi0 addr 0x8000, bus 0-255
acpihpet0 at acpi0: 14318179 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 36 (PCIB)
acpiprt2 at acpi0: bus 26 (POP3)
acpiprt3 at acpi0: bus -1 (POP1)
acpiprt4 at acpi0: bus -1 (POP6)
acpiprt5 at acpi0: bus 31 (POP5)
acpiprt6 at acpi0: bus 1 (PEX1)
acpiprt7 at acpi0: bus 6 (PEX2)
acpiprt8 at acpi0: bus 11 (PEX3)
acpiprt9 at acpi0: bus 16 (PEX4)
acpiprt10 at acpi0: bus 21 (PEX5)
acpicpu0 at acpi0: PSS
acpicpu1 at acpi0: PSS
acpicpu2 at acpi0: PSS
acpicpu3 at acpi0: PSS
acpibtn0 at acpi0: PWRB
bios0: ROM list: 0xc/0x8000 0xc8000/0x1000 0xc9000/0x1000  
0xca000/0x1000

ipmi0 at mainbus0: version 2.0 interface KCS iobase 0xc92/2 spacing 1
cpu0: Enhanced SpeedStep 2394 MHz: speeds: 2394, 2261, 2128, 1995, 1862,  
1729, 1596, 1463, 1330, 1197 MHz

pci0 at mainbus0 bus 0: configuration mode 1 (bios)
pchb0 at pci0 dev 0 function 0 "Intel Core DMI" rev 0x11
ppb0 at pci0 dev 3 function 0 "Intel Core PCIE" rev 0x11: apic 8 int 16
pci1 at ppb0 bus 26
ppb1 at pci0 dev 5 function 0 "Intel Core PCIE" rev 0x11: apic 8 int 16
pci2 at ppb1 bus 31
em0 at pci2 dev 0 function 0 "Intel I340-T2 (82580)" rev 0x01: msi,  
address 00:1b:21:90:00:d0
em1 at pci2 dev 0 function 1 "Intel I340-T2 (82580)" rev 0x01: msi,  
address 00:1b:21:90:00:d1

"Intel Core Management" rev 0x11 at pci0 dev 8 function 0 not configured
"Intel Core Scratch" rev 0x11 at pci0 dev 8 function 1 not configured
"Intel Core Control" rev 0x11 at pci0 dev 8 function 2 not configured
"Intel Core Misc" rev 0x11 at pci0 dev 8 function 3 not configured
"Intel Core QPI Link" rev 0x11 at pci0 dev 16 function 0 not configured
"Intel Core QPI Routing" rev 0x11 at pci0 dev 16 function 1 not configured
ehci0 at pci0 dev 26 function 0 "Intel 3400 USB" rev 0x05: apic 8 int 19
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 "Intel EHCI root hub" rev 2.00/1.00 addr 1
ppb2 at pci0 dev 28 function 0 "Intel 3400 PCIE" rev 0x05: apic 8 int 17
pci3 at ppb2 bus 1
ppb3 at pci0 dev 28 function 4 "Intel 3400 PCIE" rev 0x05: apic 8 int 17
pci4 at ppb3 bus 6
ppb4 at pci4 dev 0 function 0 unknown vendor 0x101b product 0x0452 rev 0x01
pci5 at ppb4 bus 7
vga1 at pci5 dev 0 function 0 vendor "Matrox", unknown product 0x0530 rev  
0x00

wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
ppb5 at pci0 dev 28 function 5 "Intel 3400 PCIE" rev 0x05: apic 8 int 16
pci6 at ppb5 bus 11
em2 at pci6 dev 0 function 0 "Intel PRO/1000 MT (82574L)" rev 0x00: msi,  
address 00:21:5e:6b:b7:42

ppb6 at pci0 dev 28 

Re: Compiling from the source on -current Failed

[Insan Praja SW]

Hi Misc@,
On Tue, 25 Sep 2012 01:09:10 +0700, Stefan Sperling   
wrote:



On Mon, Sep 24, 2012 at 07:52:44PM +0200, Stefan Sperling wrote:

On Tue, Sep 25, 2012 at 12:29:25AM +0700, Insan Praja SW wrote:
> Hi Misc@,
>
> I was just trying to upgrade to -current by compiling from the
> source, on an old (6 years) server. I updated make(1) first to the
> latest (compiling from the source, of course) and compiling the
> kernel. Using the FAQ instruction, make(1) failed at;
>
> {standard input}: Assembler messages:
> {standard input}:376: Error: no such instruction: `rdrand %edx'
> *** Error code 1 in target cpu.o
>
> Stop in /usr/src/sys/arch/i386/compile/GENERIC.MP:
>  Exit status 1 (line 933 of Makefile, target cpu.o)

Upgrade the linker and compiler first, see
http://www.openbsd.org/faq/current.html#20120823 and
http://www.openbsd.org/faq/current.html#20120831


Well, a coffee-less night is... like it is.. Obviously I miss that one. My  
bad. I got done.


And... did you really say 6 years old A source upgrade from
a system that old is not supported and the FAQ clearly states that:
http://www.openbsd.org/faq/faq5.html#BldBinary


Noo.. the "hardware/machine" is.. the kernel is 3 weeks old.


Just upgrade to the latest snapshot, and then compile from source.
Trying to do anything else is a waste of time.



Thanks,

Insan Praja SW
--
Using Opera's revolutionary email client: http://www.opera.com/mail/

Re: Compiling from the source on -current Failed

[Ted Unangst]

On Mon, Sep 24, 2012 at 20:09, Stefan Sperling wrote:

> Just upgrade to the latest snapshot, and then compile from source.
> Trying to do anything else is a waste of time.

Compiling is a waste of time.  Are you changing the source?  No?  Then
you don't need to build it.

Re: Compiling from the source on -current Failed

[Philip Guenther]

On Mon, Sep 24, 2012 at 7:38 PM, Ted Unangst  wrote:
> On Mon, Sep 24, 2012 at 20:09, Stefan Sperling wrote:
>
>> Just upgrade to the latest snapshot, and then compile from source.
>> Trying to do anything else is a waste of time.
>
> Compiling is a waste of time.  Are you changing the source?  No?  Then
> you don't need to build it.

...particularly since the snapshots often contain work-in-progress.
If you instantly rebuild, then you can't provide any real feedback on
those changes.

(If you're wonder how you can provide feedback on fixes that you don't
know about, it's often *more* important to get testing of a fix on the
99% that it *shouldn't* affect than on the 1% that it fixes.  If you
run a snapshot and it breaks, let us know.  If you immediately
rebuild, then, well, *yawn*)


Philip Guenther

Re: Microsoft Wireless Mobile Mouse 3500

[YASUOKA Masahiko]

On Mon, 24 Sep 2012 15:45:15 -0700
"Justin Lindberg"  wrote:
> I recently bought a Microsoft Wireless Mobile Mouse 3500, and I assumed
> it would work like most any other mouse on OpenBSD.  Unfortunately it
> did not.  After googling, I found a patch on the following page,
> which again unfortunately seems down at the moment, and moreover it's in
> Japanese, of which I don't understand a word:
> 
> http://yasuoka.net/~yasuoka/hack-2012.html
> 
> At first I thought the patch was working perfectly in an amd64 otherwise
> generic MP kernel, but the mouse has a tendency to "slow down" and
> become unresponsive over time, and then I have to power-cycle the mouse
> itself in order to get it to work again.
> 
> I'm inclined to think it's just a piece of junk, but is there any hope
> to support this mouse, or should I simply avoid all Microsoft mice?

The patch is for myself.  It fixes the problem of my laptop.

I already sent the patch to yuo@.  I heard from him the mouse doesn't
work because openbsd cannot read the usb hid descriptors properly and
it is not easy to fix.  He is trying to fix that.

--yasuoka

Replaced commercial vendor of network gear?

[Tomáš Bodžár]

Hi all,

I’m quite sure that there are people which were able to replace Cisco and
similar with OpenBSD or related products (and/or other open source) in
their companies or helped to do that. However it’s quite hard to find real
examples (NDA, lack of time to write about, etc.).

Is there someone willing to share such an info and ideas? Can be in private
discussion as well.

Thanks a lot

Re: Microsoft Wireless Mobile Mouse 3500

[Justin Lindberg]

On Tue, 25 Sep 2012 12:23:52 +0900 (JST)
YASUOKA Masahiko  wrote:

> The patch is for myself.  It fixes the problem of my laptop.
> 
> I already sent the patch to yuo@.  I heard from him the mouse doesn't
> work because openbsd cannot read the usb hid descriptors properly and
> it is not easy to fix.  He is trying to fix that.
> 
> --yasuoka

I haven't tried it on a very recent kernel, but as far as I can tell
the patch works perfectly for getting the device recognized properly,
and it was very helpful to me for that part, so thank you very much.

The weirdness I experience with the mouse might be a more general issue
with X or a deeper issue with the mouse itself.  It tends to happen
when I move a lot of windows around, and then things remain seized up
until I turn the mouse off and back on again.