From owner-freebsd-scsi Sun May 31 13:45:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17970 for freebsd-scsi-outgoing; Sun, 31 May 1998 13:45:54 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles208.castles.com [208.214.165.208]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17514; Sun, 31 May 1998 13:44:13 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id MAA12982; Sun, 31 May 1998 12:39:29 -0700 (PDT) Message-Id: <199805311939.MAA12982@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: tcobb cc: "'Mike Smith'" , "'shimon@simon-shapiro.org'" , "freebsd-scsi@freebsd.org" , "freebsd-current@freebsd.org" Subject: Re: DPT Redux In-reply-to: Your message of "Sun, 31 May 1998 00:26:07 EDT." <509A2986E5C5D111B7DD0060082F32A402FAF6@freya.circle.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 31 May 1998 12:39:29 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > -----Original Message----- > > From: Mike Smith [mailto:mike@smith.net.au] > > > I shutdown and rebooted machine (SYNC failed on shutdown) > > > Allowed FreeBSD to boot, it returned the following for sd1 > > > sd1: type 0 fixed SCSI 2 > > > sd1: Direct-Access 0MB (1 512 byte sectors) > > > > > > Then, system continued booting and finally panic'd with a > > "Page Fault in > > > Supervisor Mode" error prior to mounting drives. > > > > Did you happen to write down the details from this message? In > > conjunction with your kernel image, these are required in order to > > determine what happened. > > This is the one thing I neglected to do, unfortunately - I just got the > error name, not the rest of the info. The situation was a surprise and > had become an emergency at the point it was clear that FreeBSD wasn't > going to reboot. Grr. This makes identifying the culprit extremely difficult. 8( > > It's possible that something doesn't like being asked to boot from a > > zero-sized disk. It's also possible that something else later got > > upset - it's not clear where in the chain of events the panic > > occurred > > (see above). > > Actually, it wasn't booting from the "zero-sized" disk. From my earlier > email, I noted that I have two arrays configured, the first sd0, is the > boot disk and RAID-1 and contains all relevant system directories, the > second sd1, is simply an NFS export partition and is RAID-5. It was the > second disk (sd1) which showed the "0 MB/1 sector" problem. Gotcha - I had discarded the reference to the specific disk in question. > > Thanks for the extra info. Are you able to simulate the > > failure by eg. > > disconnecting one of the 'active' drives? If you can't do this on a > > regular basis, I believe we are able to arrange temporary access to a > > similar but idle system where this can be simulate. Simon > > may also be > > able to offer some suggestions inre. possible poor > > interaction between > > the dpt driver and some firmware revisions. > > I'm hoping to be able to create a duplicate array to this one for > testing, also. I'm getting resistance to budgeting additional funds for > DPT/FreeBSD at the moment :( The machine in question is currently (and > still) a live NFS server. I'm working on scheduling some downtime for > it in the next few days get a hotswap drive back in there. I expect > that I'll have to keep it down (1.5hrs) for a complete array rebuild on > the RAID-5 given the interactions I've seen recently. If you can boot while the array is rebuilding and obtain a traceback (and preferably a kernel core dump), this would be *invaluable* in determining the actual problem. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message