Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 25 Nov 2004 18:04:46 -0800
From:      Kris Kennaway <kris@obsecurity.org>
To:        Kevin Smith <smithcam@adelphia.net>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: mount ntfs (windows) file system in /etc/fstab fails at boot
Message-ID:  <20041126020446.GA81791@xor.obsecurity.org>
In-Reply-To: <41A6FD07.1020900@adelphia.net>
References:  <41A6FD07.1020900@adelphia.net>

next in thread | previous in thread | raw e-mail | index | archive | help

--TB36FDmn/VVEgNH/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Nov 26, 2004 at 01:53:11AM -0800, Kevin Smith wrote:
> I am able to mount my windows partition manually by either:
>=20
> > mount -t ntfs /dev/ad0s1 /windows
>=20
> or by putting an entry in by /dev/fstab that looks like:
>=20
> /dev/ad0s1             /windows          ntfs     ro              2      =
 2
>=20
> and using command:
                                                                           =
^^^=20

     The sixth field, (fs_passno), is used by the fsck(8) program to determ=
ine
     the order in which filesystem checks are done at reboot time.  The root
     filesystem should be specified with a fs_passno of 1, and other filesy=
s-
     tems should have a fs_passno of 2.  Filesystems within a drive will be
     checked sequentially, but filesystems on different drives will be chec=
ked
     at the same time to utilize parallelism available in the hardware.  If
     the sixth field is not present or is zero, a value of zero is returned
     and fsck(8) will assume that the filesystem does not need to be checke=
d.

Since you don't want to run fsck on the ntfs volume, set this to zero.

> If I leave this entry in my /etc/fstab, the OS reports inconsistency=20
> errors on bootup when it tries to mount and goes into single-user mode. =
=20
> I then had to remount / for read-write and delete the line in the fstab=
=20
> before it would boot again.

P.S. It's usually helpful to transcribe the exact error, instead of
describing vague symptoms.

Kris

--TB36FDmn/VVEgNH/
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)

iD8DBQFBpo8+Wry0BWjoQKURAgTEAJ4r2jr112j26JowEJeik9zbElczewCgvORn
iHX6bScYDTPeyozdRwCo8Vo=
=Mfly
-----END PGP SIGNATURE-----

--TB36FDmn/VVEgNH/--



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