From owner-freebsd-questions@FreeBSD.ORG Sun Mar 12 02:54:35 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3922F16A44C for ; Sun, 12 Mar 2006 02:54:35 +0000 (GMT) (envelope-from jakob@grimstveit.no) Received: from mail.hjemme.no (mail.hjemme.no [62.97.193.11]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5AD4045D5F for ; Sun, 12 Mar 2006 01:00:05 +0000 (GMT) (envelope-from jakob@grimstveit.no) Received: from corona.grimstveit.no (79.62-97-240.bkkb.no [62.97.240.79]) by mail.hjemme.no (8.13.4/8.13.4) with ESMTP id k2C0xoFT021152; Sun, 12 Mar 2006 01:59:51 +0100 Date: Sun, 12 Mar 2006 01:59:50 +0100 From: Jakob Breivik Grimstveit To: freebsd-questions@freebsd.org Message-ID: <20060312015950.5c6348d9@corona.grimstveit.no> In-Reply-To: <441wxb3h8i.fsf@be-well.ilk.org> References: <20060308025057.2ada3a35@corona.grimstveit.no> <441wxb3h8i.fsf@be-well.ilk.org> Organization: BitWise Computing X-Mailer: Sylpheed-Claws 2.0.0 (GTK+ 2.8.12; i386-portbld-freebsd5.4) X-Face: .4qx3fwC]Zs6i@H)n4+U7@:QPR,\(Q'z[`J-C"'v:; *cy8[}d]:x,*Z6I?e8m%a~O?f1',N \1g'^='~; B3WO"RqF(tt]5<1)z%.%hqWnyM|NG}|e[zDmf=j(F*p|Tq^C#{<_FvV|P/tB4aG81S)#i Ilo]%Gm<)uLyN List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Mar 2006 02:54:35 -0000 Lowell Gilbert wrote on Thu, 09 Mar 2006 08:00: > Jakob Breivik Grimstveit writes: >=20 > > I'm still experiencing same problems Christer Solskogen reported two ye= ars > > ago on FreeBSD 5.2.1 with msdosfs mount failure upon boot making it go > > into single-user-mode (having to press enter (into shell) and ctrl+d (to > > continue booting) to get box up after reboot: > >=20 > > http://groups.google.no/group/mailing.freebsd.current/browse_thread/thr= ead/4e660419935ea6e5/80580ef045e0e1d1 > >=20 > > However, doing a `mount -a` after boot brings them both in. > >=20 > > I have the following in my fstab: > >=20 > > $ grep msdosfs /etc/fstab =20 > > /dev/ad4s5 /mnt/share1 msdosfs rw 2 2 > > /dev/ad4s6 /mnt/share2 msdosfs rw 2 2 > >=20 > > $ uname -r > > 5.4-RELEASE-p7 > >=20 > > $ grep 'boot.c' /usr/src/sbin/fsck_msdosfs/boot.c=20 > > __RCSID("$NetBSD: boot.c,v 1.9 2003/07/24 19:25:46 ws Exp $"); > > "$FreeBSD: src/sbin/fsck_msdosfs/boot.c,v 1.4 2004/04/20 11:41:57 tjr > > Exp $"; > >=20 > > Any suggestions as to what to do with this? >=20 > Maybe it's having trouble loading the msdosfs kernel module before > boot? Try building that into your kernel. Actually, this seems to be a very strict parsing of the fstab when it comes= to msdosfs file systems. I Googled a lot (even further, I've been struggling with this problem for several years now), and suddenly, the below worked nicely. Case closed! $ cat /etc/fstab | grep share /dev/ad4s5 /mnt/share1 msdosfs rw,-m644,-M755,-ujakobbg,-gjakobbg 0 0 /dev/ad4s6 /mnt/share2 msdosfs rw,-m644,-M755,-ujakobbg,-gjakobbg 0 0 Thanks for a great list! --=20 Jakob Breivik Grimstveit, , 48298152 Bes=F8k Newsergalleriet: All power corrupts, but we need electricity.