From owner-freebsd-questions@FreeBSD.ORG Sun Mar 20 08:35:52 2005 Return-Path: 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 04C8D16A4CE for ; Sun, 20 Mar 2005 08:35:52 +0000 (GMT) Received: from smtp11.wanadoo.fr (smtp11.wanadoo.fr [193.252.22.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7160A43D2F for ; Sun, 20 Mar 2005 08:35:51 +0000 (GMT) (envelope-from atkielski.anthony@wanadoo.fr) Received: from me-wanadoo.net (unknown [127.0.0.1]) by mwinf1101.wanadoo.fr (SMTP Server) with ESMTP id 945151C00090 for ; Sun, 20 Mar 2005 09:35:50 +0100 (CET) Received: from pix.atkielski.com (ASt-Lambert-111-2-1-3.w81-50.abo.wanadoo.fr [81.50.80.3]) by mwinf1101.wanadoo.fr (SMTP Server) with ESMTP id 6AB7B1C00089 for ; Sun, 20 Mar 2005 09:35:50 +0100 (CET) X-ME-UUID: 20050320083550437.6AB7B1C00089@mwinf1101.wanadoo.fr Date: Sun, 20 Mar 2005 09:35:50 +0100 From: Anthony Atkielski X-Priority: 3 (Normal) Message-ID: <1210047979.20050320093550@wanadoo.fr> To: freebsd-questions@freebsd.org In-Reply-To: <1111232419.1737.25.camel@airen> References: <583197724.20050319103813@wanadoo.fr> <1111232419.1737.25.camel@airen> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: Serious issue with SATA disks again X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Mar 2005 08:35:52 -0000 Erik de Jong writes: > FWIW, I had WRITE_DMA time outs as well, on a non-SATA disk of about 3 > years old. My instict told me to make that last backup real quick, so > that's what I did. The disk crashed about a week or two later. I'm an > absolute FreeBSD newbie, but hardware problems transcend OS > differences ;-) What made you think it was a hardware problem? > I worked in a large software company for a while and found out (much to > my own surprise at the time) that it's not always that easy. It's not > always a matter of "I wrote the code so I know what this message means". > Those messages could be anywhere in any piece of code involved at the > time of the error. It could be passed on by another piece of code > (firmware?). Somebody, somewhere knows what causes this error. > Second, code comes in many shapes and forms (and I think this is one > area where open and closed source are probably very similar): neat code, > sloppy code, quick fixes, things that really shouldn't be there, > absolute gems and everything in between. Such as code without any trace of comments, like I see in FreeBSD. > The BEST troubleshooting tip not matter what you trying to > resolve is: do not rule out anything. Including the operating system. > Obviously, I think you have a hardware issue, but that's only my > opinion. I'm just writing to share my own experience. Which hardware issue do I have? > You're writing that noone knows what these mysterious error messages > mean? This could very well be the case right now. Somebody wrote the code. > Perhaps the issue hasn't been troubleshot enough yet. It has been around for a least a year, judging by what I've found on the Net. > I think that having problems and having difficulty resolving them is far > from a FreeBSD problem. Report myserious error messages to any software > company and there's always a risk that they won't be easily resolved. That doesn't make it okay for FreeBSD. -- Anthony