From owner-freebsd-current@FreeBSD.ORG Sat Nov 10 12:09:56 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 51A5216A417 for ; Sat, 10 Nov 2007 12:09:56 +0000 (UTC) (envelope-from danger@FreeBSD.org) Received: from virtual.micronet.sk (smtp.micronet.sk [84.16.32.237]) by mx1.freebsd.org (Postfix) with ESMTP id 08D7C13C4B9 for ; Sat, 10 Nov 2007 12:09:55 +0000 (UTC) (envelope-from danger@FreeBSD.org) Received: from localhost (localhost [127.0.0.1]) by virtual.micronet.sk (Postfix) with ESMTP id 78F5E10EA26; Sat, 10 Nov 2007 12:45:40 +0100 (CET) X-Virus-Scanned: by amavisd-new at virtual.micronet.sk Received: from virtual.micronet.sk ([127.0.0.1]) by localhost (virtual.micronet.sk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rp8Clz5peidM; Sat, 10 Nov 2007 12:45:38 +0100 (CET) Received: from DANGER-PC (danger.mcrn.sk [84.16.37.254]) by virtual.micronet.sk (Postfix) with ESMTP id B4C5510EA24; Sat, 10 Nov 2007 12:45:38 +0100 (CET) Date: Sat, 10 Nov 2007 12:45:27 +0100 From: Daniel Gerzo Organization: The FreeBSD Project X-Priority: 3 (Normal) Message-ID: <1306808611.20071110124527@rulez.sk> To: freebsd-current@freebsd.org In-Reply-To: <20071109191821.V639@10.0.0.1> References: <20071109191821.V639@10.0.0.1> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: nickpiggin@yahoo.com.au Subject: Re: FreeBSD corruption problems on barcelona X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Gerzo List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Nov 2007 12:09:56 -0000 Hello Nick, Saturday, November 10, 2007, 4:21:05 AM, you wrote: > Here it is attached. Now there is a cdrom error there, however I > don't believe it is the cause of the problem (or at least, there > is a bigger problem with the sata disk). The install has run > perfectly every time I've run it, so it is pulling the data off > the CD OK. > Now I have actually got as far as root login, I filled up a 1MB > file with /dev/urandom and took an md5. Then copied that to 50 > files on the /tmp filesystem, unmounted and remounted it, and then > read back the md5 sums. Practially all of them are wrong, but they > seem to be wrong in the same ways (eg. many share the same > incorrect md5 sum). Reading the files back from disk consistently > gives the same information, so it seems like reads are OK. Did you by any chance tried to install some other OS and checked if that is really a FreeBSD problem? You mentioned that you've got a new box, so I suppose that you tried only FreeBSD on it so far on it. In the past, I had a bit similar problem. The symptons were that I checked some file's md5 hash, then copied it some other location and checked the new md5 hash of that file, it was different. The problem was resolved after we replaced CPU (AFAIR). So the things you are describing in your email seem to me more like a hardware problem than a FreeBSD problem, could you please run some kind of hardware test and try to replace your controllers, sata cable, disk and so on? > Interestingly, a second test didn't show up corruption, so I don't > know how reproduceable it is > Hope this helps. -- Best regards, Daniel mailto:danger@FreeBSD.org