From owner-freebsd-current Thu Dec 23 9:36:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 488C514F4E; Thu, 23 Dec 1999 09:36:45 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id KAA08181; Thu, 23 Dec 1999 10:08:51 -0800 (PST) Date: Thu, 23 Dec 1999 10:08:50 -0800 (PST) From: Alfred Perlstein To: Matthew Dillon Cc: Andreas Klemm , current@FreeBSD.ORG, phk@FreeBSD.ORG Subject: Re: fsck successfull on checking root-fs but OS still can't mount it In-Reply-To: <199912230805.AAA00671@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Dec 1999, Matthew Dillon wrote: > > :Hi ! > : > :I'm seeing strange behaviour of fsck in -current. > :FreeBSD titan.klemm.gtn.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Wed Dec 22 07:07:11 CET 1999 root@:/usr/src/sys/compile/TITAN i386 > : > :SCSI bus hang, so I had to reboot. fsck checked every filesystem. > :But then mount was unable to mount the filesystem and tells you to > :check the fs using fsck. Did that again, nothing changed. > :You have to reboot. > : > :I was bitten by that 3 times. > : > :Another thing are the (I assume SCSI) hangs I got 3 times since > :I upgraded from 3.4-STABLE to -current. Next time I'll write down > :the messages. Two times the messages were hidden by another X Window. > :Nothing in /var/log/messages. > > I've been bitten by this several times myself recently. The system comes > up after a crash, fsck's the media, and then can't mount it and drops > into single-user. The only solution is to reboot. I thought so too, but you can actually 'tunefs -n (enbale|disable) /' after that you should be able to mount your /. > > It didn't used to do this. > > -Matt I know... If anyone else cares, the current situation about being unable to auto-reboot (halting on /) is pretty annoying and ought to be fixed. There were various promises made that all the changes going on with devices wouldn't cause such problems. This makes running -current in somewhat production enviornments impossible. unless you hack /etc/rc. Of course I may have just not remade my /dev/ properly, please flame if appropriate. thanks, -Alfred > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -Alfred Perlstein - [bright@rush.net|alfred@freebsd.org] Wintelcom systems administrator and programmer - http://www.wintelcom.net/ [bright@wintelcom.net] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message