Re: Missing tape library device in OBSD 4.0
On 2006/12/25 at 04:48:12PM -0800, Jeff Richards wrote: I just rebuilt my server from 3.9 to 4.0. I was able to get everything working except that I can no longer see my tape library unit (HP Surestore 40x6..) I am using the 4.0 GENERIC#1107 i386 kernel. Here's from my dmesg: siop0 at pci0 dev 13 function 0 Symbios Logic 53c875 rev 0x03: irq 15, using 4 K of on-board RAM scsibus0 at siop0: 16 targets siop0: target 5 now using 8 bit async xfers siop0: target 5 now using 8 bit 20.0 MHz 16 REQ/ACK offset xfers st0 at scsibus0 targ 5 lun 0: HP, C5713A, H307 SCSI3 1/sequential removable Hmm ... shouldn't there be an entry for ch0 in the dmesg as well? Was the changer connected and powered up when the system was installed/booted? Check for /dev/ch0. If it is present then it should be used by default by chio(1). If it is not present, cd to /dev and type: ./MAKEDEV ch0 and see whether that makes a difference. I don't have a dmesg result from my 3.9 boot, but I was using my tape library unit. Has there been a change in the kernel so I can't use my tape library unit? I have my 3.9 system on a seperate HD so I can always go back, but I really would like to be on a current system. Well ... I can't tell you anything about the HP library, but I can tell you that OpenBSD 4.0 worked fine (on a Sun Ultra-60) with an Exabyte EXB-430 -- up to 30 tapes, and up to four Mammoth-2 drives, of which two were present in my library. I can't give you the dmesg output from that now, because I am now using Solaris-10 in that system -- for other reasons. (E.g. I prefer the extra information that mt status gives on Solaris which is missing on OpenBSD -- in particular the information about how many files and blocks into the current file the tape is at present. Good Luck, DoN. -- Email: [EMAIL PROTECTED] | Voice (all times): (703) 938-4564 (too) near Washington D.C. | http://www.d-and-d.com/dnichols/DoN.html --- Black Holes are where God is dividing by zero ---
Re: LUN-Probing on Multi-LUN Devices
On 2006/11/27 at 03:04:55AM +0100, Moritz Kiese wrote: Greetings, I just hooked up a rather old 6x CD-changer (Pioneer DRM-624X) to my SUN Ultra 1 (fast SCSI provided by a combi SBUS card with additional esp, le cereal). The CD-changer usually presents its six cds at six different devices appearing under six LUNs, however neither 4.0 GENERIC nor a custom kernel with an additional option SCSIFORCELUN_BUSES=0x0001 which I vaguely remember from an elderly discussion about multi-LUN devices on misc@ seems to find more than the first cd (cd1) of the six (which seems to be working fine). In case it helps: Under Lunix and (IIRC) Slowlaris this beast appeared under six different LUNs, generating six cd-devices. All devices could be mounted simultaneously, but only one at a time could be read of course. So I wonder whether there is some way to force LUN probing on all devices? Any hints highly appreciated, Look at sd(4) -- especially the synopsis: == sd* at scsibus? #sd0 at scsibus0 target 3 lun 0 (fixed-configuration example) == And at cd(4) == cd* at scsibus? #cd0 at scsibus0 target 6 lun 0 (fixed-configuration example) == Note that the first line is what you will find in your GENERIC kernel configuration, and AFIK, it *only* selects lun 0. You will need, instead, to change that line to multiple lines (assuming that you have only one SCSI drive other than the CD-ROM changer): == # Your boot drive -- adjust SCSI ID as appropriate. IIRC, the # Ultra-1 wants target 0 as the first internal drive. # # Yes -- I just checked, and the internal drives are SCSI ID 0 # and SCSI-ID 1, so let's allow for both, even if both are not # currently present. # sd0 at scsibus0 target 0 lun 0 sd1 at scsibus0 target 1 lun 0 # # Assume the CD-changer to be at the usual SCSI-ID 6 for # Suns -- change as necessary # cd2 at scsibus0 target 6 lun 0 cd3 at scsibus0 target 6 lun 1 cd4 at scsibus0 target 6 lun 2 cd5 at scsibus0 target 6 lun 3 cd6 at scsibus0 target 6 lun 4 cd7 at scsibus0 target 6 lun 5 == To be honest, I don't know what happens if some disks are hard coded as above, and others are not -- but I do know that the hard-coding of *disks* is needed for reliable behavior with the RAID system if you boot with a missing or failed disk. So -- make the changes to a copy of /usr/src/sys/arch/sparc64/conf/GENERIC (Perhaps call it WITHCDS or something similar), compile it, and install it as the current kernel (/bsd) -- saving a copy of the old one, of course, as something like /bsd-GENERIC to make it easier to recover if something went wrong with the kernel which you built. I hope that this helps, DoN. -- Email: [EMAIL PROTECTED] | Voice (all times): (703) 938-4564 (too) near Washington D.C. | http://www.d-and-d.com/dnichols/DoN.html --- Black Holes are where God is dividing by zero ---
Re: Using Exabyte Mammoth-2 tapes on OpenBSD
On 2006/09/25 at 04:02:45PM -0400, DoN. Nichols wrote: I've explicitly Cc'd the three who e-mailed me directly about this after I posted, to fill them in on things. (Though I strongly suspect that all would see it in the list as well.) All, I posted this a few days ago to comp.unix.bsd.openbsd.misc, and the only answer I got was mostly a suggestion that I post it here. So, here it is: I've got an Exabyte 430 tape jukebox with two drives (Mammoth-2). [ ... ] This is OpenBSD 3.8 on a Sun Ultra5 (sparc64 kernel). The only part of the system which does not come with it is the LVD SCSI card, which is documented in the dmesg information quoted below. [ ... ] And -- when we start having problems: == siop1: target 10 now using 16 bit 40.0 MHz 31 REQ/ACK offset xfers st0(siop1:10:0): unhandled message 0x23 st0(siop1:10:0): unhandled message 0x23 st0(siop1:10:0): unhandled message 0x23 siop1: target 9 now using 8 bit async xfers ch0: 30 slots, 2 drives, 1 picker, 1 portal siop1: target 11 now using 16 bit 40.0 MHz 31 REQ/ACK offset xfers st1(siop1:11:0): unhandled message 0x23 st1(siop1:11:0): unhandled message 0x23 st1(siop1:11:0): unhandled message 0x23 st0(siop1:10:0): Check Condition (error 0x70) on opcode 0x0 SENSE KEY: Not Ready ASC/ASCQ: Logical Unit Is in Process Of Becoming Ready st0(siop1:10:0): unhandled message 0x23 st0(siop1:10:0): unhandled message 0x23 st0(siop1:10:0): unhandled message 0x23 st0(siop1:10:0): unhandled message 0x23 st0(siop1:10:0): unhandled message 0x23 == So -- does OpenBSD 3.8 or 3.9 deal properly with Exabyte Mammoth 2 drives? [ ... ] If all else fails, I'll pick up another Ultra-5 or Ultra-10, stuff Solaris 10 into it, and use the PCI LVD card in that, since I do know that Solaris 10 *will* write to the drives -- even with the wrong SCSI interface. (I wish that I could find a LVD SCSI card in sBus format for the Ultra-2. :-) O.K. I now have OpenBSD 4.0, and it works nicely in an Ultra-60 which I picked up for the purpose. (It also works nicely with Solaris 10 U 2 in the same box, so I now have my choices here.) I did have to download a driver for Solaris for the LVD card (the driver was labeled as being for Solaris 8 and 9, but it works nicely with Solaris 10). So -- the improved tape driver, or the improved driver for the LVD card did it -- or some combination. BTW One of you suggested that I try using a Sun D1000 as a HVD to LVD level translator -- but examination of the Sun FEH shows that it really would work only as a HVD to SE translator, as it presents a SE SCSI bus to the drives. Now all I need to do is wait for the packages to be opened up so I can populate this as I like. Thanks all -- 4.0 did it. DoN. P.S.I really like the new package. (And the song seems just about right for Obelix's singing overriding everyone else. :-) -- Email: [EMAIL PROTECTED] | Voice (all times): (703) 938-4564 (too) near Washington D.C. | http://www.d-and-d.com/dnichols/DoN.html --- Black Holes are where God is dividing by zero ---
Re: setting up NIS
On 2006/10/19 at 12:50:47AM -0200, Gustavo Rios wrote: Dear list members, i am setting a personal NIS server. At the momment; the output for the command line is the following: # ypinit -m mojave Server Type: MASTER Domain: mojave [ ... ] At this point, we have to construct a list of this domain's YP servers. etosha is already known as master server. Please continue to add any slave servers, one per line. When you are done with the list, type a control D. master server : etosha next host to add: ^D The current list of NIS servers looks like this: etosha So -- you added no slave servers. [ ... ] etosha has been setup as an YP master server without any errors. # make === mojave updated netid yppush: could not get ypservers map pushed netid # Ok, why the yppush: could not get ypservers map error message is being echoed ? O.K. I'm not quite sure why the specific *wording* of the error message, but I don't see a need to run make here, which pushes updated maps to slave servers. Since you don't have any slave servers, why push? It may be that the ypservers map in this implementation strips off the master server automatically prior to trying to push -- and finding nothing left, it gives the above error message. The real question is whether it does what you want otherwise? Does it serve maps as it should? You could try ypcat -k ypservers to see what it put in that map. Maybe you should have not used the quit on any errors option. I normally don't use it. Granted, I've been running NIS servers only on Suns running SunOs and later Solaris -- not on OpenBSD, so there may be something different there -- but it should not be *too* different. I like the ypinit -u addition, which I see documented in OpenBSD 3.9. Hmm ... all the way back to 3.4 at least. That is nice -- because it is a pain to add more slave servers, or to remove them, from a running instance of yp under Solaris or SunOs. Enjoy, DoN. -- Email: [EMAIL PROTECTED] | Voice (all times): (703) 938-4564 (too) near Washington D.C. | http://www.d-and-d.com/dnichols/DoN.html --- Black Holes are where God is dividing by zero ---
Re: Problem sendmail won't
On 2006/10/15 at 05:25:25AM -0700, Rob Baldassano wrote: Help, I need some advice. Sendmail stopped sending out and receiving mails. I looked at top, and sendmail is running (Numerous instances), but it just won't send anything. Additionally, trying to login takes up to 3 minutes (kerberos problem? Thanks for any assistance you can provide. Do you have your own domain? There is a spamer out there (in Russia, IIRC) who is making a practice of forging lots of the same domain name in one massive spam run, with bogus usernames of the form: first-nametwo-initialslastname all run together And -- he does not have a particularly clean list of addresses, so there are *lots* of bounce messages. I'm running qmail, not sendmail, and if I don't do anything about it, my systems run to a load average of 256 and then lock up (these happen to be older Solaris systems, not OpenBSD). However, since qmail can be run from inetd.conf, I have set up a shell script which checks the system load average (with a small quick binary program which simply tests whether the load average is above or below a threshold passed on the command line, and returns a status corresponding to that). If the load average is over eight, it swaps in a second inetd.conf which has the qmail incoming SMTP entry commented out, and when the load average finally falls below that, it re-enables the incoming SMTP connections. This allows the systems (with peak load averages of somewhere around 64) to survive the flood, and eventually drain the pool of incoming bounce messages. Of course -- there is nothing so simple as blocking the source, as you are receiving the bounces from his victim's systems, not the original spam, which are themselves coming from a large number of compromised machines around the world. These seem to be happening about once a week now, with one starting this morning. If you have your own domain, and he happens to be forging your domain today, you will also have a massively overloaded sendmail, and the only easy cure is to disconnect from the net until sendmail catches up. (You might want to look in the queue to see what is being processed. Today's spam seems to be a weight loss spam.) Good Luck, DoN. -- Email: [EMAIL PROTECTED] | Voice (all times): (703) 938-4564 (too) near Washington D.C. | http://www.d-and-d.com/dnichols/DoN.html --- Black Holes are where God is dividing by zero ---
Re: Fwd: Oldest Server you run
On 2006/10/12 at 05:04:10PM -0400, Jason Crawford wrote: And I ment to send this to the whole list A nuisance, having the From: set to the individual poster, not the list, isn't it? [ ... ] Oldest machine I had running (until I moved to an appartment that can't accomodate more than a couple machines) was a sparc station2 at 40MHz and 32MB ram with two 512MB hard drives. Didn't have an onboard nic, Huh? I though that the SS-2 had an AUI connector, so all you need is an external transceiver, not a NIC. I've used them with Thicknet, Thinnet, and 10BaseT at various times. but I put one on it and it was my DNS server just fine with OpenBSD up to 3.7 or so until I moved, and as far as I know it should still work. I also run a friend's firewall on a p166 machine with 64MB of ram. The oldest one which I am still running (at present) is an old Sun LX -- running an older Solaris, but a planned changeover to OpenBSD. Intended function is DNS server. Enjoy, DoN. -- Email: [EMAIL PROTECTED] | Voice (all times): (703) 938-4564 (too) near Washington D.C. | http://www.d-and-d.com/dnichols/DoN.html --- Black Holes are where God is dividing by zero ---
Re: Oldest Server you run
On 2006/10/12 at 11:08:21PM -0400, Nick Holland wrote: [ ... ] I can't believe people with PIIs and PIIIs even responded to this thread, however. You GOT to be kidding me...That ain't old. That's almost as new as I get! Well ... it is the you run part which is limiting me. I've got Suns back to a 2/120, lots of Sun-3 machines, several UnixPCs (7300 and 3B1) and a couple of Tektronix 6130s (National Semiconductor 32016 CPUs (or was that 16032?). However, the oldest box is a Cosmos CMS-16/UNX -- an 8MHz 68000 running a Unisoft port of v7 unix. No bets whether I could even get the oldest OpenBSD running on that one. :-) (Not too sure about the Tektronix boxes either -- though they are running a 4.2 BSD port called UTek. However -- all boxen older than the Sun LX are retired, so they don't count here. Enjoy, DoN. -- Email: [EMAIL PROTECTED] | Voice (all times): (703) 938-4564 (too) near Washington D.C. | http://www.d-and-d.com/dnichols/DoN.html --- Black Holes are where God is dividing by zero ---
Re: mandoc question
On 2006/10/01 at 06:05:24AM +0100, Jason McIntyre wrote: On Sun, Oct 01, 2006 at 12:41:40AM +0159, Han Boetes wrote: ~/nfs/manpage% grep '.*' *.log cvs.1.log:cvs.1:1732: warning: numeric expression expected (got `l') [ ... ] the cvs.1 will be from the gnu page, right? you could try sending it to them. I don't know about the others, but it appears to be complaining about receiving a letter 'l' (L), when it expected the numeral '1' (one). Did the others result from this one error? Good Luck, DoN. -- Email: [EMAIL PROTECTED] | Voice (all times): (703) 938-4564 (too) near Washington D.C. | http://www.d-and-d.com/dnichols/DoN.html --- Black Holes are where God is dividing by zero ---
Using Exabyte Mammoth-2 tapes on OpenBSD
All, I posted this a few days ago to comp.unix.bsd.openbsd.misc, and the only answer I got was mostly a suggestion that I post it here. So, here it is: I've got an Exabyte 430 tape jukebox with two drives (Mammoth-2). They need to be connected to LVD SCSI, so I have found a PCI LVD SCSI card to put in an Ultra-5. (Exabyte's own documentation says that while most LDV devices will work on SE SCSI, these will not.) The drive most distant from the terminator with SE SCSI works most of the time read and write up to certain sizes -- Under Solaris 10 on an Ultra-2. More than Exabyte promised. It works quite well for reading, and reasonably, but not perfectly for writing. (The drive closer to the SE terminator does not work well at all, but swapping them causes the one which did not work well before to work well afterwards. With the system connected to the LVD SCSI controller on an OpenBSD 3.8 system (mostly because I am too lazy to move that system to OpenBSD 3.9 for the moment, as it is serving its main function with no problems), I can control the jukebox with chio with no problems, and read tapes written on other machines (even very long files) in either drive (with a differential terminator in place, of course). However -- I cannot *write* to the drives at all. It doesn't even write enough to render previously-written files unaccessible. :-( This is OpenBSD 3.8 on a Sun Ultra5 (sparc64 kernel). The only part of the system which does not come with it is the LVD SCSI card, which is documented in the dmesg information quoted below. Partial information from the dmesg output on that system: == console is keyboard/display Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2005 OpenBSD. All rights reserved. http://www.OpenBSD.org OpenBSD 3.8 (GENERIC) #607: Sat Sep 10 16:03:59 MDT 2005 [EMAIL PROTECTED]:/usr/src/sys/arch/sparc64/compile/GENERIC total memory = 536870912 avail memory = 480067584 using 3276 buffers containing 26836992 bytes of memory bootpath: /[EMAIL PROTECTED],0/[EMAIL PROTECTED],1/[EMAIL PROTECTED],0/[EMAIL PROTECTED],0 mainbus0 (root): Sun Ultra 5/10 UPA/PCI (UltraSPARC-IIi 333MHz) cpu0 at mainbus0: SUNW,UltraSPARC-IIi @ 333 MHz, version 0 FPU cpu0: physical 32K instruction (32 b/l), 16K data (32 b/l), 2048K external (64 b/l) psycho0 at mainbus0 addr 0xfffc4000 SUNW,sabre: impl 0, version 0: ign 7c0 bus range 0 to 2; PCI bus 0 DVMA map: c000 to e000 IOTDB: 26a8000 to 2728000 [ ... ] siop0 at pci2 dev 1 function 0 Symbios Logic 53c896 rev 0x07: ivec 1810, using 8K of on-board RAM scsibus1 at siop0: 16 targets siop1 at pci2 dev 1 function 1 Symbios Logic 53c896 rev 0x07: ivec 1811, using 8K of on-board RAM scsibus2 at siop1: 16 targets ch0 at scsibus2 targ 9 lun 0: EXABYTE, Exabyte 430, 2.18 SCSI2 8/changer removable st0 at scsibus2 targ 10 lun 0: EXABYTE, Mammoth2, v07g SCSI2 1/sequential removable st0: density code 0x28, 1024-byte blocks, write-enabled st1 at scsibus2 targ 11 lun 0: EXABYTE, Mammoth2, v07g SCSI2 1/sequential removable st1: density code 0x28, 1024-byte blocks, write-enabled == And -- when we start having problems: == siop1: target 10 now using 16 bit 40.0 MHz 31 REQ/ACK offset xfers st0(siop1:10:0): unhandled message 0x23 st0(siop1:10:0): unhandled message 0x23 st0(siop1:10:0): unhandled message 0x23 siop1: target 9 now using 8 bit async xfers ch0: 30 slots, 2 drives, 1 picker, 1 portal siop1: target 11 now using 16 bit 40.0 MHz 31 REQ/ACK offset xfers st1(siop1:11:0): unhandled message 0x23 st1(siop1:11:0): unhandled message 0x23 st1(siop1:11:0): unhandled message 0x23 st0(siop1:10:0): Check Condition (error 0x70) on opcode 0x0 SENSE KEY: Not Ready ASC/ASCQ: Logical Unit Is in Process Of Becoming Ready st0(siop1:10:0): unhandled message 0x23 st0(siop1:10:0): unhandled message 0x23 st0(siop1:10:0): unhandled message 0x23 st0(siop1:10:0): unhandled message 0x23 st0(siop1:10:0): unhandled message 0x23 == So -- does OpenBSD 3.8 or 3.9 deal properly with Exabyte Mammoth 2 drives? Does something special need to be put into the kernel source and a recompilation performed -- similar to the st.conf changes in Solaris 10 as below? == tape-config-list= EXABYTE Mammoth2, Mammoth2 8mm Helical Scan, M2; M2 = 1,0x35,0,0x19e39,1,0x28,0; == If all else fails, I'll pick up another Ultra-5 or Ultra-10, stuff Solaris 10 into it, and use the PCI LVD
