Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 22 Jan 2007 00:14:21 -0600
From:      Eric Anderson <anderson@centtech.com>
To:        Rod Person <personrp@hotpop.com>
Cc:        "freebsd-current@freebsd.org" <freebsd-current@freebsd.org>
Subject:   Re: Problem with fsck on CURRENT??
Message-ID:  <45B4563D.8010507@centtech.com>
In-Reply-To: <20070119173627.15ff4286@atomizer.opensourcebeef.net>
References:  <20070119173627.15ff4286@atomizer.opensourcebeef.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On 01/19/07 16:36, Rod Person wrote:
> -----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?

Without doing a background fsck, fsck won't allow writes to the disk if 
the partition is mounted.  Try unmounting the file system, and running 
fsck again.

Also, you should include more details about your 
device/partition/slices/etc in order to get a better response on the 
second part of your question.


Eric




-- 
------------------------------------------------------------------------
Eric Anderson        Sr. Systems Administrator        Centaur Technology
An undefined problem has an infinite number of solutions.
------------------------------------------------------------------------



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45B4563D.8010507>