bittorrent corruption problems
I have been getting this error: data corrupted on disk - maybe you have two copies running? I have looked on the net and the only causes I can see are bad ram and bad software. I noticed this after I started using the gui, never noticed it on the command line. I used to never get this. It has happen since before my current build, but here is my current build: $ uname -a FreeBSD BARTON 5.4-PRERELEASE FreeBSD 5.4-PRERELEASE #3: Tue Mar 1 02:04:40 EST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/NINAMORI i386 If no one else has had any trouble with there system I will start to test my hardware. I checked my hardware when I built my pc a while back, so maybe something went bad? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bittorrent corruption problems
On Mon, 07 Mar 2005 03:26:11 +, Jason Henson [EMAIL PROTECTED] wrote: I have been getting this error: data corrupted on disk - maybe you have two copies running? I have looked on the net and the only causes I can see are bad ram and bad software. I noticed this after I started using the gui, never noticed it on the command line. I used to never get this. It has I had this a while back on one of my Linux boxes. Turned out to be bad ram. Memtest86+ should do the trick, just leave it testing over night and see what it says in the morning. -- Bevan Coleman -- What Signature? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: bittorrent corruption problems
On 03/06/05 22:36:38, Bevan Coleman wrote: On Mon, 07 Mar 2005 03:26:11 +, Jason Henson [EMAIL PROTECTED] wrote: I have been getting this error: data corrupted on disk - maybe you have two copies running? I have looked on the net and the only causes I can see are bad ram and bad software. I noticed this after I started using the gui, never noticed it on the command line. I used to never get this. It has I had this a while back on one of my Linux boxes. Turned out to be bad ram. Memtest86+ should do the trick, just leave it testing over night and see what it says in the morning. -- Bevan Coleman -- What Signature? ___ Thanks, and I am still hoping its not the ram. :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
