Date: Fri, 27 Jan 2006 20:00:40 -0500 From: Chuck Swiger <cswiger@mac.com> To: Paul Schmehl <pauls@utdallas.edu> Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD drops to single user mode Message-ID: <43DAC238.2080802@mac.com> In-Reply-To: <B9D0F221218955434798EFD1@utd59514.utdallas.edu> References: <D35F1856C06510BC057B40AA@utd59514.utdallas.edu> <200601272249.26518.list-freebsd-2004@morbius.sent.com> <B9D0F221218955434798EFD1@utd59514.utdallas.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Paul Schmehl wrote: > --On Friday, January 27, 2006 22:49:25 +0000 RW > <list-freebsd-2004@morbius.sent.com> wrote: [ ... ] >>> Here's my fstab, if that illuminates anything: >>> >>> ... >>> /dev/ad5s1d /files ufs rw >>> 2 2 >> >> >> If you neglected to comment-out this line, FreeBSD would be looking for >> this partition, which doesn't exist on the Windows drive. > > I suspected that was the case, but if so, why did mount -a work? "mount -a" does the best it can, and will even remount / for historical reasons: /etc/rc used to mount / ro in single-user mode, run fsck, and then remount / "rw" once fsck had finished, before going multiuser. The system intends to have all of the listed filesystems in fstab mounted before starting daemons and the like which will expect their files to be available; if it can't make a filesystem available, it stays in single-user mode waiting for a human to solve the problem. If you remove a device containing a filesystem listed in fstab, you should either comment out that line or use the noauto keyword. -- -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43DAC238.2080802>