Date: Thu, 30 Dec 1999 11:23:28 -0500 From: Christopher Masto <chris@netmonger.net> To: David Gilbert <dgilbert@velocet.ca>, Bill Fumerola <billf@chc-chimes.com> Cc: freebsd-current@FreeBSD.ORG Subject: Re: fsck of /, related to last post. Message-ID: <19991230112328.A23129@netmonger.net> In-Reply-To: <14443.34050.325756.938310@trooper.velocet.net>; from David Gilbert on Thu, Dec 30, 1999 at 11:14:58AM -0500 References: <14443.33374.329712.324138@trooper.velocet.net> <Pine.BSF.4.10.9912301104160.70198-100000@jade.chc-chimes.com> <14443.34050.325756.938310@trooper.velocet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Dec 30, 1999 at 11:14:58AM -0500, David Gilbert wrote: > >>>>> "Bill" == Bill Fumerola <billf@chc-chimes.com> writes: > > Bill> On Thu, 30 Dec 1999, David Gilbert wrote: > >> Related to my last post, the system came up and started to fsck. > >> It appears, with current, that the system will refuse to r/w mount > >> root even though the fsck has complete successfully. Is this an > >> rc-file out-of-date issue, or has something changed in the kernel. > > Bill> Reboot. I don't know why it works, but it does. :-> > > Right... I already knew that, but it's a manual reboot... and this is > "suboptimal" (ie. requiring operator intervention). If you re-MAKEDEV your device nodes, it shouldn't happen again. It would be nice if something were fixed to actually say what's going on instead of confusing the hell out of people, since there seems to be a thread on this every day on -current. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991230112328.A23129>