From owner-freebsd-questions Thu Oct 23 21:16:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA20121 for questions-outgoing; Thu, 23 Oct 1997 21:16:26 -0700 (PDT) (envelope-from owner-freebsd-questions) Received: from jason02.u.washington.edu (root@jason02.u.washington.edu [140.142.76.8]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA20116 for ; Thu, 23 Oct 1997 21:16:23 -0700 (PDT) (envelope-from jcwells@u.washington.edu) Received: from saul3.u.washington.edu (root@saul3.u.washington.edu [140.142.83.1]) by jason02.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.05) with ESMTP id VAA37682; Thu, 23 Oct 1997 21:16:20 -0700 Received: from S8-37-26.student.washington.edu (S8-37-26.student.washington.edu [128.208.37.26]) by saul3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW97.04) with SMTP id VAA01700; Thu, 23 Oct 1997 21:16:19 -0700 (PDT) Message-Id: <3.0.3.32.19971024041942.007b5100@jcwells.deskmail.washington.edu> X-Sender: jcwells@jcwells.deskmail.washington.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Fri, 24 Oct 1997 04:19:42 +0000 To: champlin@stolaf.edu From: Jason Wells Subject: Re: syncing disks Cc: freebsd-questions@FreeBSD.ORG In-Reply-To: References: <199710151728.MAA00650@stat168-001.residents.stolaf.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >On Wed, 15 Oct 1997 champlin@stolaf.edu wrote: > >> Everytime I try to install freebsd on my computer the computer freezes. >> It happens when syncing disks but there is a kernel panic message just >> prior to syncing disks. Why would this happen? What can I do about it? > >Your disk controller is quitting prematurely. What are the details on >your machine? I might be wrong. This is the behaviour that occurs as system is booting. The sequence of events is (more or less) changing root device to /dev/fd0 panic: double fault syncing disks It is more correct to say that the system panics after changing root than it is to say that it panics before syncing. This was the problem that I had with the 2.2.2 boot.flp image. It can be fixed by using the 3.0snap floppy image instead. It seems the 2.2.2-RELEASE boot image is broke. It is broke on my CD too. (No, it is not possible that my system caused this error :)) Be sure to set the release value under the options menu before you install or you will get the beta OS instead of the released OS. The correct value is precisely '2.2.2-RELEASE' sans quotes. How is St. Olaf this time of year? Cold yet? Later, Jason Wells