From owner-freebsd-current Sat May 30 21:26:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA28809 for freebsd-current-outgoing; Sat, 30 May 1998 21:26:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freya.circle.net (freya.circle.net [209.95.95.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA28793; Sat, 30 May 1998 21:26:51 -0700 (PDT) (envelope-from tcobb@staff.circle.net) Received: by freya.circle.net with Internet Mail Service (5.5.1960.3) id ; Sun, 31 May 1998 00:26:12 -0400 Message-ID: <509A2986E5C5D111B7DD0060082F32A402FAF6@freya.circle.net> From: tcobb To: "'Mike Smith'" Cc: "'shimon@simon-shapiro.org'" , "freebsd-scsi@freebsd.org" , "freebsd-current@freebsd.org" Subject: RE: DPT Redux Date: Sun, 31 May 1998 00:26:07 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@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. The kernel file I can certainly supply. > 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. > 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. My instinct is that, assuming someone could setup a RAID-5 array with HOT SWAP disk, and then yanked a live drive, that they'd see the same symptoms that I did. Or, even simpler would be to tell the array to rebuild, then try to boot FreeBSD... -Troy Cobb Circle Net, Inc. http://www.circle.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message