From owner-freebsd-current Fri Aug 23 02:29:04 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA08283 for current-outgoing; Fri, 23 Aug 1996 02:29:04 -0700 (PDT) Received: from dot.ishiboo.com (user@dot.ishiboo.com [208.128.22.10]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id CAA08278 for ; Fri, 23 Aug 1996 02:29:01 -0700 (PDT) From: nirva@ishiboo.com Received: (qmail-queue invoked by uid 509); 23 Aug 1996 02:07:09 -0000 Message-ID: <19960823020709.2402.qmail@dot.ishiboo.com> Subject: -current kills harddrives To: freebsd-current@freebsd.org Date: Thu, 22 Aug 1996 20:07:08 -0600 (MDT) X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Here's my situation, 2 perfectly happy HDs, both SCSI-II, were working great for months. I upgraded to -current like 2 months ago, and my Micropolis 2 gig 7200rpm drive (running very cool to awesome scsi box) just crashed, i mean like hard, the Buslogic 946C it was on couldn't verify or low level it. I figured it was a HD problem so I ignored it and just got the drive RMA'd. I ran 2.1.0-release for a while, and then upgraded to -current once again about a week ago when i got my Matrox Meteor and wanted a better driver for it. Everything was going great, until last night a Quantum 2 gig drive died. Now, this drive was rock solid for almost a year, and i even switched to an adaptec 2940.. it could be a coincidence, but then again, its just a bit too suspicous to be right after -current install, again. These are the kinda errors I started getting: sd0(ahc0:0:0): UNIT ATTENTION asc:29,0 sd0(ahc0:0:0): Power on, reset, or bus device reset occurred , retries:4 sd3(ahc0:4:0): UNIT ATTENTION asc:29,0 sd3(ahc0:4:0): Power on, reset, or bus device reset occurred , retries:2 sd2(ahc0:3:0): UNIT ATTENTION asc:29,0 sd2(ahc0:3:0): Power on, reset, or bus device reset occurred , retries:2 But they were all on sd1, and then it finanlly died and I get this: sd1(ahc0:1:0): timed out in datain phase, SCSISIGI == 0x0 sd1(ahc0:1:0): asserted ATN - device reset in message buffer sd1(ahc0:1:0): timed out in datain phase, SCSISIGI == 0x0 ahc0: Issued Channel A Bus Reset #1. 1 SCBs aborted sd1(ahc0:1:0): UNIT ATTENTION asc:29,0 sd1(ahc0:1:0): Power on, reset, or bus device reset occurred , retries:3 I've never seen the screen scroll so fast with errors. Its been like an hour since I disabled that drive, it only had the errors on sd0, sd2, and sd3 on bootup, but all is happy now.. hopefully it will stay this way.. Should I worry? Should I downgrade to -stable with the Meteor driver from -current? I don't relaly want to loose more drives if it is FreeBSD thats killing them. This is my dmesg: FreeBSD 2.2-CURRENT #0: Wed Aug 21 22:00:26 MDT 1996 nirva@blookitty.ishiboo.com:/usr/src/sys/compile/blookitty Calibrating clock(s) relative to mc146818A clock... i586 clock: 199441674 Hz, i8254 clock: 1193242 Hz CPU: Pentium Pro (199.43-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x617 Stepping=7 Features=0xf9ff,MTRR,PGE,MCA,CMOV> real memory = 134217728 (131072K bytes) avail memory = 128217088 (125212K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 0 on pci0:7: 0 pci0:7:1: Intel Corporation, device=0x7010, class=storage (ide) [no driver assig ned] vga0 rev 1 int a irq 11 on pci0:11 meteor0 rev 0 int a irq 5 on pci0:15:0 meteor0: rev 0x1 bt0 rev 0 int a irq 5 on pci0:17 bt0: Bt946C/ 0-(32bit) bus bt0: reading board settings, dma=5, int=11 bt0: version 4.25J, fast sync, parity, 32 mbxs, 32 ccbs bt0: targ 2 sync rate= 5.00MB/s(200ns), offset=12 bt0: targ 6 sync rate= 6.66MB/s(150ns), offset=15 bt0: Using Strict Round robin scheme bt0 waiting for scsi devices to settle (bt0:2:0): "NEC CD-ROM DRIVE:500 2.5" type 5 removable SCSI 2 cd0(bt0:2:0): CD-ROM cd present [326402 x 2048 byte records] (bt0:6:0): "ARCHIVE Python 28388-XXX 5.72" type 1 removable SCSI 2 st0(bt0:6:0): Sequential-Access density code 0x13, drive empty ahc0 rev 0 int a irq 9 on pci0:19 ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "SEAGATE ST5660N 0592" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 520MB (1065664 512 byte sectors) (ahc0:1:0): "QUANTUM EMPIRE_2100S 1022" type 0 fixed SCSI 2 sd1(ahc0:1:0): Direct-Access 2006MB (4108600 512 byte sectors) (ahc0:3:0): "QUANTUM EMPIRE_2100S 1022" type 0 fixed SCSI 2 sd2(ahc0:3:0): Direct-Access 2006MB (4108600 512 byte sectors) (ahc0:4:0): "HP C2490A 3256" type 0 fixed SCSI 2 sd3(ahc0:4:0): Direct-Access 2033MB (4165272 512 byte sectors) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x280-0x29f irq 10 on isa ed0: address 00:c0:f0:0a:f3:6c, type NE2000 (16 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x63 irq 12 on motherboard fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in bt: unit number (1) too high bt1 not found at 0x330 npx0 on motherboard npx0: INT 16 interface IP packet filtering initialized, divert enabled, unlimited logging --------------------------------------------------------------------------- Danny Dulai Feet. Pumice. Lotion. http://www.ishiboo.com/~nirva/ nirva@ishiboo.com ---------------------------------------------------------------------------