Date: Thu, 14 Dec 2000 10:08:59 +0100 From: "Morten A . Middelthon" <morten@freenix.no> To: freebsd-stable@freebsd.org Subject: Vinum or hardware fault? Message-ID: <20001214100859.C466@freenix.no>
next in thread | raw e-mail | index | archive | help
I'm using vinum to set up a striped plex with three 9GB scsi disks: da2: <IBM DMVS09V 0250> Fixed Direct Access SCSI-3 device da3: <IBM DMVS09V 0100> Fixed Direct Access SCSI-3 device da4: <IBM DMVS09V 0100> Fixed Direct Access SCSI-3 device I'm not using soft-updates here. The SCSI controller is integrated on an Asus P2B-DS mainboard: ahc0: <Adaptec aic7890/91 Ultra2 SCSI adapter> port 0xb000-0xb0ff mem 0xe1000000-0xe1000fff irq 10 at device 6.0 on pci0 aic7890/91: Wide Channel A, SCSI Id=7, 32/255 SCBs da0 and da1 are not using vinum. Other than that the box has got two Pentium III 500MHz CPUs, 512MB of ram and is running FreeBSD 4.1.1-STABLE. The vinum plex had been running for a week or two, and the activity was reasonably low. But then my server froze and I got these error-messages: Dec 12 12:35:05 enterprise /kernel: ahc0:A:4: parity error detected in Message-in phase. SEQADDR(0x171) SCSIRATE(0x0) (several of these) Dec 12 12:35:05 enterprise /kernel: ahc0: Unexpected busfree in Message-out phase Dec 12 12:35:05 enterprise /kernel: SEQADDR == 0x170 To me this looks like there's something wrong the fifth and last disk (ahc0:A:4). I had to reboot the box, but upon reboot fsck didn't complain about anything out of the ordinary, and I was able remount the vinum plex. Can anyone tell me if this is vinum's or the hardware's fault? -- Morten A. Middelthon Freenix Norge http://www.freenix.no/ -- Do not meddle in the affairs of dragons, 'cuz, like, you are crunchy and taste good with ketchup. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001214100859.C466>