From owner-freebsd-questions Sat Mar 1 9:23:44 2003 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C6ACE37B401 for ; Sat, 1 Mar 2003 09:23:42 -0800 (PST) Received: from mired.org (ip68-97-54-220.ok.ok.cox.net [68.97.54.220]) by mx1.FreeBSD.org (Postfix) with SMTP id A374843F85 for ; Sat, 1 Mar 2003 09:23:39 -0800 (PST) (envelope-from mwm-dated-1046971418.07b8e3@mired.org) Received: (qmail 85255 invoked from network); 1 Mar 2003 17:23:38 -0000 Received: from localhost.mired.org (HELO guru.mired.org) (127.0.0.1) by localhost.mired.org with SMTP; 1 Mar 2003 17:23:38 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15968.60567.965666.864174@guru.mired.org> Date: Sat, 1 Mar 2003 11:23:35 -0600 To: kitsune Cc: freebsd-questions@freebsd.org Subject: Re: kernel panic question In-Reply-To: <20030228160755.4e34ba4b.kitbsdlists@HotPOP.com> References: <20030228160755.4e34ba4b.kitbsdlists@HotPOP.com> X-Mailer: VM 7.07 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`; h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ From: Mike Meyer X-Delivery-Agent: TMDA/0.70 (Pensive) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [Format recovered. Please insert newlines.] In <20030228160755.4e34ba4b.kitbsdlists@HotPOP.com>, kitsune typed: > Would this be a problem with the hardware, kernel, or what? > What is happening is I mount /dev/ad2s1e and them move files to it > from /dev/ad0s1e. It will go nicely for a second or two then I will > get a kernel panic. I also risk getting a kernel panic if > /dev/ad2s1e is even mounted. I have had trouble with this befor but > did not look to closely into it. The first time I had this problem > was when I tried mounting what is now /dev/ad0s1e from > /dev/ad2s1e. That drive works nicely on /dev/ad0s1e but did the same > thing as this new drive is doing when I tried to put it on > /dev/ad2s1e. I managed to create the fs and ect succesfully on the > drive when it was mounted on /dev/ads1e originally and manage to > write a bit to it, but if I tried to move or write any thing large > to it would kernel panic just like this new one is doing. This sounds like a flaky ide controller. Broken file systems can cause the system to panic, and if you're getting bogus reads, that would do it. Of course, more information - a traceback from an unstripped kernel, for instance - would allow more accurate diagnosis. http://www.mired.org/consulting.html Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message