From owner-freebsd-current@FreeBSD.ORG Sat Jan 20 14:06:55 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 727EF16A401 for ; Sat, 20 Jan 2007 14:06:55 +0000 (UTC) (envelope-from personrp@hotpop.com) Received: from smtp-out.hotpop.com (smtp-out.hotpop.com [38.113.3.71]) by mx1.freebsd.org (Postfix) with ESMTP id 3F13D13C469 for ; Sat, 20 Jan 2007 14:06:55 +0000 (UTC) (envelope-from personrp@hotpop.com) Received: from hotpop.com (kubrick.hotpop.com [38.113.3.105]) by smtp-out.hotpop.com (Postfix) with SMTP id 8C01440CFEA8 for ; Fri, 19 Jan 2007 22:42:52 +0000 (UTC) Received: from atomizer.opensourcebeef.net (unknown [71.61.11.4]) by smtp-1.hotpop.com (Postfix) with ESMTP id 4413C1480A7 for ; Fri, 19 Jan 2007 22:42:49 +0000 (UTC) Date: Fri, 19 Jan 2007 17:36:27 -0500 From: Rod Person To: freebsd-current@freebsd.org Message-ID: <20070119173627.15ff4286@atomizer.opensourcebeef.net> Organization: Open Source Beef Computing X-Mailer: Claws Mail 2.6.1 (GTK+ 2.10.6; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-HotPOP: ----------------------------------------------- Sent By HotPOP.com FREE Email Get your FREE POP email at www.HotPOP.com ----------------------------------------------- X-Mailman-Approved-At: Sun, 21 Jan 2007 15:12:23 +0000 Subject: Problem with fsck on CURRENT?? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jan 2007 14:06:55 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm not sure if this is a problem or is normal but here it is. I have an external ATAPI drive that is connected to my machine via firewire (that case also has a usb2 connection). My system crashed so I needed to fsck this disk. Now however I start fsck it does not allow me to answer 'Y' to any of the question - it answer N automatically. I've tried starting fsck with -y and that seems to do nothing! The drive is formatted with a UFS2 file system and I have to invoke fsck like this: fsck -t ufs /mnt Otherwise it claims not to be able to tell what file system type it is? I'm just wondering is this normal for external drives even if they are formatted with a native file system? Fsck doesn't act this why with my internal SCSI drives? - -- Rod "it takes an unusual mind to see the obvious." - - Alfred Whitehead -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFr2K23rDijyy3LEcRAn15AJ9lLIX51ST1yTLLk2NwHW7rZ9wZbgCfXe4K CICDgjoqQSfcoRGUn0ArMsk= =oWzU -----END PGP SIGNATURE----- -- Rod "it takes an unusual mind to see the obvious." - Alfred Whitehead