From owner-freebsd-questions Tue Dec 18 0:36:14 2001 Delivered-To: freebsd-questions@freebsd.org Received: from catalyst.sasknow.net (catalyst.sasknow.net [207.195.92.130]) by hub.freebsd.org (Postfix) with ESMTP id 4098337B41C for ; Tue, 18 Dec 2001 00:36:09 -0800 (PST) Received: from localhost (ryan@localhost) by catalyst.sasknow.net (8.11.6/8.11.6) with ESMTP id fBI8c7i31218; Tue, 18 Dec 2001 02:38:07 -0600 (CST) (envelope-from ryan@sasknow.com) X-Authentication-Warning: catalyst.sasknow.net: ryan owned process doing -bs Date: Tue, 18 Dec 2001 02:38:07 -0600 (CST) From: Ryan Thompson X-X-Sender: To: Undisclosed Name Cc: Subject: Re: MD5 Checksum Weirdness In-Reply-To: Message-ID: <20011218023004.H30898-100000@catalyst.sasknow.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 Administrivia: Make sure you remember to CC -questions in your reply. (Hotmail is evil and does not do this automatically). Undisclosed Name wrote to ryan@sasknow.com: > > Yea its the same file on my drive seems to be constantly changing > so im going this route of testing: harddrive,cable,nic since I've > already done memory. and if all that's correct then I quit the > gnome wins =o( > It is possible as I have had the following problems. wintendos > restart during hardware detection, spontanious reboots very very > unpredictible on those, strage sybols being written from harddrive > to floppy like files being > [... snip further horror stories ...] Definitely sounds like flaky hardware... You'll have to follow the standard hardware troubleshooting flowcharts (pull it all out and start putting stuff back in until it complains). If you've got nothing left but the motherboard, don't forget to test the PS too. I'd try a different HD first, though, if you have ONLY noticed data corruption problems, and have had no other unrelated stability problems. Check dmesg and /var/log/messages for relevant errors. Usually a failing HD will raise some pretty blatant red flags in the system logs. In any case, it isn't a FreeBSD problem ;-) > show the memory is good. So if anyone has every had this gremlin > please share his name so we can put him on the list with Bin > Makingbigmistakes =o). Thanks to everyone for there help and > input as I could use all I can get right now. Since I cant seem to > reproduce these bugs in a timely manner to find there origin. Just > needed to make sure it was just me. Yep, I think it's pretty safe to say it's just you :-) Happy debugging! - Ryan -- Ryan Thompson Network Administrator, Accounts SaskNow Technologies - http://www.sasknow.com #106-380 3120 8th St E - Saskatoon, SK - S7H 0W2 Tel: 306-664-3600 Fax: 306-664-1161 Saskatoon Toll-Free: 877-727-5669 (877-SASKNOW) North America To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message