Re: mount ntfs (windows) file system in /etc/fstab fails at boot
From: Kevin Smith (smithcam_at_adelphia.net)
Date: 11/26/04
- Previous message: Kris Kennaway: "Re: mount ntfs (windows) file system in /etc/fstab fails at boot"
- In reply to: Kris Kennaway: "Re: mount ntfs (windows) file system in /etc/fstab fails at boot"
- Next in thread: Kris Kennaway: "Re: mount ntfs (windows) file system in /etc/fstab fails at boot"
- Reply: Kris Kennaway: "Re: mount ntfs (windows) file system in /etc/fstab fails at boot"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 26 Nov 2004 02:16:45 -0800 To: Kris Kennaway <kris@obsecurity.org>, freebsd-questions@freebsd.org
Yes, putting a "0" in the sixth field takes care of the problem and the
/windows file system is now mounted. thanks.
> P.S. It's usually helpful to transcribe the exact error, instead of
> describing vague symptoms.
Yes,I agree. I was not able to retreive the exact error message from
dmesg on boot as I had rebooted again and lost that. If you can tell me
where I can get previous boot messages (dmesg.today didn have it
either), I will post the message for the benefit of others in case they
have this problem.
Thanks again.
-K
Kris Kennaway wrote:
>On Fri, Nov 26, 2004 at 01:53:11AM -0800, Kevin Smith wrote:
>
>
>>I am able to mount my windows partition manually by either:
>>
>>
>>
>>>mount -t ntfs /dev/ad0s1 /windows
>>>
>>>
>>or by putting an entry in by /dev/fstab that looks like:
>>
>>/dev/ad0s1 /windows ntfs ro 2 2
>>
>>and using command:
>>
>>
> ^^^
>
> The sixth field, (fs_passno), is used by the fsck(8) program to determine
> 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 filesys-
> tems should have a fs_passno of 2. Filesystems within a drive will be
> checked sequentially, but filesystems on different drives will be checked
> 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 checked.
>
>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
>>errors on bootup when it tries to mount and goes into single-user mode.
>>I then had to remount / for read-write and delete the line in the fstab
>>before it would boot again.
>>
>>
>
>P.S. It's usually helpful to transcribe the exact error, instead of
>describing vague symptoms.
>
>Kris
>
>
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"
- Previous message: Kris Kennaway: "Re: mount ntfs (windows) file system in /etc/fstab fails at boot"
- In reply to: Kris Kennaway: "Re: mount ntfs (windows) file system in /etc/fstab fails at boot"
- Next in thread: Kris Kennaway: "Re: mount ntfs (windows) file system in /etc/fstab fails at boot"
- Reply: Kris Kennaway: "Re: mount ntfs (windows) file system in /etc/fstab fails at boot"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|