Date: Sun, 05 Dec 1999 12:05:06 -0800 From: "Ronald F. Guilmette" <rfg@monkeys.com> To: freebsd-hackers@FreeBSD.ORG Subject: Strange SCSI sickness Message-ID: <21541.944424306@monkeys.com>
next in thread | raw e-mail | index | archive | help
My apologies for posting this digression from the usual weighty matters that are discussed here on -hackers, but I'm really in a tizzy about this. Going through my waiting mail this morning (on my personal desktop system named `segfault.monkeys.com') I found the following message from the nightly Security Check run. (This system is running stock 3.3 from a CD.) I'm really quite worried about this, and I want to know what it all means. `da0' is my primary SCSI drive and holds a LOT of stuff that is near and dear to me (including a lot of stuff which I DO NOT HAVE BACKED UP) along with all of the OS files. The controller is an AHA-2940U (not wide). The da0 disk is a Quantum Viking 4.5GB SCSI. I have never had any problem with this drive before, even though I used it on Linux for several months. This (FreeBSD) system has been running just fine, with no problems, for several weeks. And now this! I looked at the log files in /var/log and found out that these SCSI errors mostly seem to have occured at around 2:00 local time last night... when I was in bed and asleep. This morning, the system still _seems_ to be running just fine, but I'm worried... I just want to know, on a scale from 1 to 10, what level of panic should I now be experiencing relative to the kernel SCSI errors shown below? Should I be furiously backing everything up to tape as we speak? ------- Forwarded Message Return-Path: root Received: (from root@localhost) by monkeys.com (8.9.3/8.9.3) id BAA20422 for root; Sun, 5 Dec 1999 01:59:42 -0800 (PST) Date: Sun, 5 Dec 1999 01:59:42 -0800 (PST) From: Charlie Root <root> Message-Id: <199912050959.BAA20422@monkeys.com> Subject: segfault.monkeys.com security check output X-Original-Recipient: RFC822;root@monkeys.com checking setuid files and devices: checking for uids of 0: root 0 toor 0 checking for passwordless accounts: segfault.monkeys.com kernel log messages: > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10d > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10e > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10e > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10e > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10e > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10e > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10d > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10e > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10e > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10d > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10e > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10e > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10d > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10e > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10e > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10d > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10e > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x53 > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10d > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10d > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x53 > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10d > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10d > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10d > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10d > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10d > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10d > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10d > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10e > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10e > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Message-In phase. > SEQADDR == 0x152 > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10e > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10e > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10d > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Command phase. > SEQADDR == 0x152 > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10e > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10d > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10d > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10e > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Message-In phase. > SEQADDR == 0x152 > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10d > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Message-In phase. > SEQADDR == 0x152 > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10d > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10d > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x118 > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10e > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10e > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10e > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x10e > SCSIRATE == 0xf > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x53 > SCSIRATE == 0xf segfault.monkeys.com login failures: segfault.monkeys.com refused connections: ------- End of Forwarded Message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?21541.944424306>