From owner-freebsd-questions Thu Oct 2 23:43:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA23777 for questions-outgoing; Thu, 2 Oct 1997 23:43:51 -0700 (PDT) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA23762 for ; Thu, 2 Oct 1997 23:43:47 -0700 (PDT) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.8.5) with SMTP id XAA26545; Thu, 2 Oct 1997 23:43:45 -0700 (PDT) Date: Thu, 2 Oct 1997 23:43:45 -0700 (PDT) From: Doug White Reply-To: Doug White To: George cc: freebsd-questions@FreeBSD.ORG Subject: Re: superblock no reboot In-Reply-To: <3433A649.C02C0DC4@airmail.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 2 Oct 1997, George wrote: > i have this problem that says superblock not set fix(yn)? > i type y and it fixes it but the system wont reboot now > i type reboot and it says syncing disks 4 3 done. but just sits there > and dont reboot i gotta hit reset button. and when i do a fsck it always > says superblock not set on each partition. Some systems don't reboot properly for whatever reason. If the Syncing disks... item goes to ``done'' then you should be synced out. Try compiling a kernel with options BROKEN_KEYBOARD_RESET and see if that helps. For your fsck problems, I don't know what to say; try using ``halt'' instead of reboot. When you come back up, fsck should fix up those dirty bits if needed, you shouldn't need to run fsck manually. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major