From owner-freebsd-hackers Thu Sep 21 18:24:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jason.argos.org (a1-3a105.neo.rr.com [24.93.180.105]) by hub.freebsd.org (Postfix) with ESMTP id 3975737B42C for ; Thu, 21 Sep 2000 18:24:24 -0700 (PDT) Received: from localhost (mike@localhost) by jason.argos.org (8.10.1/8.10.1) with ESMTP id e8M1J9h26898 for ; Thu, 21 Sep 2000 21:19:09 -0400 Date: Thu, 21 Sep 2000 21:19:08 -0400 (EDT) From: Mike Nowlin To: freebsd-hackers@freebsd.org Subject: udma file system corruption Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Had an interesting one tonight... I've been using rrestore to duplicate the filesystems on a bunch of machines that I'm mass-producing. Things seemed to be going OK, but one of these machines (Compaq Presario 5340) booted up twice, started throwing up strange warnings about UDMA not working correctly (and falling back to PIO), then refused to boot - when it tried to mount /, it would panic every time... Took the HD out and popped it into another machine, and half of the files in / and /var were basically worthless - "ls" would show them, "ls -l" wouldn't, couldn't remove the entries, etc... Realizing that there's not enough detail here to get an accurate answer, is this something that can likely be contributed to iffy UDMA support on this particular machine? I'm just gonna turn this box into another diskless machine, but I'm curious... mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message