Date: Wed, 13 Jun 2001 16:41:05 -0700 From: Sean Noonan <snoonan@cx952600-a.fed1.sdca.home.com> To: <questions@freebsd.org> Cc: <snoonan@cx952600-a.fed1.sdca.home.com> Subject: Is this a SCSI error or just informational? Message-ID: <KIEPJNLEBFIFHLFBELKMOECMCDAA.snoonan@cx952600-a.fed1.sdca.home.com>
next in thread | raw e-mail | index | archive | help
PROBLEM: Following gets logged to console and dmesg file occasionally (seen last today after a successful buildworld): (da0:ahc0:0:0:0): SCB 0xd - timed out while idle, SEQADDR == 0x7 STACK == 0x3, 0x19a, 0x15a, 0x0 SXFRCTL0 == 0x80 ahc0: Dumping Card State at SEQADDR 0x7 SCSISEQ = 0x12, SBLKCTL = 0x0, SSTAT0 0x5 SCB count = 50 Kernel NEXTQSCB = 22 Card NEXTQSCB = 22 QINFIFO entries: Waiting Queue entries: Disconnected Queue entries: 1:7 2:35 0:13 QOUTFIFO entries: Sequencer Free SCB List: Pending list: 7 3 23 24 17 35 13 Kernel Free SCB list: 8 0 29 14 2 33 12 15 11 38 21 20 19 36 18 37 1 16 5 31 10 32 4 34 28 39 26 6 9 27 43 30 44 45 46 25 47 48 49 42 41 40 sg[0] - Addr 0x1bec400 : Length 1024 (da0:ahc0:0:0:0): Queuing a BDR SCB (da0:ahc0:0:0:0): Bus Device Reset Message Sent (da0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Bus Device Reset on A:0. 7 SCBs aborted QUESTION #1: Is this an error or just an informational message? QUESTION #2: If this is an error, any advice towards solving? QUESTION #3: If this is just an informational message, how do I disable it from logging to the console? BACKGROUND: I'm putting together a tape backup server to backup my home LAN/lab of ten or so PCs. It's an old P133 with 32 MB RAM. I had an Adaptec 2940U sitting around, along with 4GB Seagate HD. I bought a used HP SureStore 12000E 6-tape DDS2 changer to use--cheap. My first problem was changing the Adaptec controller's default behavior of not recognizing multiple LUNs per device. My weirdo SureStore 12000E uses the same SCSI target ID but with different LUNs. Problem resolved. My second problem was termination. Seems the Seagate was so old it used the old-style resister diodes for termination, and, of course I had lost it. So I decided to add a 2GB Quantum drive to the mix, one that I could control the termination on ;-) Of course I also had to go buy a new SCSI ribbon cable that would accommodate more than the one drive. Once I hooked everything up, things appeared to work okay. But some commands like 'chio' would give inconsistent results--not often, but often enough to cause alarm. That's when I began suspecting termination problems. The SureStore is connected via a 6 ft. external cable, and adding a new, longer internal ribbon cable to the mix caused the bus to exceed specs. So, I removed the Seagate entirely and went back to using the old internal ribbon cable. Finally got reproducible, consistent results with programs like chio. So far so good. I also added a 17GB IDE drive to the box for to act as Amanda's holding area. My third problem, one that is not yet overcame, is tape errors. After every backup I've made with Amanda, I'd get the clean light on the tape changer to come on and the LED would read either "Clean Me" or "Worn Media". I knew it wasn't warn media cause it was new media. That left a cleaning problem. I used a brand new tape cleaning cartridge to new avail. So I've sent the drive off for repair. The funny thing is, my friend/acquaintance who sold me the drive swears it was working fine for him the week before. In addition, I'd sometimes get SCSI SCB-related messages on the console after Amanda had done its thing (didn't record them, sorry). I always had attributed these messages to Amanda/ch0 device funkiness and didn't pay much attention to them (stupid me, first time messing around with a changer). So now the drive's off for repair and I decided to do a buildworld. Lo and behold, buildworld finishes successfully but on the console right after the end of the buildworld is this: (da0:ahc0:0:0:0): SCB 0xd - timed out while idle, SEQADDR == 0x7 STACK == 0x3, 0x19a, 0x15a, 0x0 SXFRCTL0 == 0x80 ahc0: Dumping Card State at SEQADDR 0x7 SCSISEQ = 0x12, SBLKCTL = 0x0, SSTAT0 0x5 SCB count = 50 Kernel NEXTQSCB = 22 Card NEXTQSCB = 22 QINFIFO entries: Waiting Queue entries: Disconnected Queue entries: 1:7 2:35 0:13 QOUTFIFO entries: Sequencer Free SCB List: Pending list: 7 3 23 24 17 35 13 Kernel Free SCB list: 8 0 29 14 2 33 12 15 11 38 21 20 19 36 18 37 1 16 5 31 10 32 4 34 28 39 26 6 9 27 43 30 44 45 46 25 47 48 49 42 41 40 sg[0] - Addr 0x1bec400 : Length 1024 (da0:ahc0:0:0:0): Queuing a BDR SCB (da0:ahc0:0:0:0): Bus Device Reset Message Sent (da0:ahc0:0:0:0): no longer in timeout, status = 34b ahc0: Bus Device Reset on A:0. 7 SCBs aborted This is the same genre of messages I was getting earlier that I had attributed to the tape changer. But the tape changer is gone now and I'm still getting them. I notice the device in question is da0, my Quantum SCSI disk. Is this simply a message or an error? If it's an error I may have just sent off a perfectly good tape changer to be repaired to the tune of $250. Doh! If it's an informational message my tape changer probably needed repair anyways (so I don't feel so bad!). Thanks for any and all help, Sean Noonan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?KIEPJNLEBFIFHLFBELKMOECMCDAA.snoonan>