From owner-freebsd-questions Mon Feb 12 23:32:21 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA18992 for questions-outgoing; Mon, 12 Feb 1996 23:32:21 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA18987 for ; Mon, 12 Feb 1996 23:32:18 -0800 (PST) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id IAA12861; Tue, 13 Feb 1996 08:34:48 +0100 Message-Id: <199602130734.IAA12861@gilberto.physik.rwth-aachen.de> Subject: Re: 2.1.0 Boot Problem... To: 74532.1322@compuserve.com (Shawn P. Murphy) Date: Tue, 13 Feb 1996 08:34:47 +0100 (MET) Cc: questions@FreeBSD.ORG In-Reply-To: <960213000852_74532.1322_EHH85-1@CompuServe.COM> from "Shawn P. Murphy" at Feb 12, 96 07:08:52 pm From: Christoph Kukulies Reply-To: Christoph Kukulies X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-questions@FreeBSD.ORG Precedence: bulk > > Hi, > > I have FreeBSD 2.1.0, and am now having some problems booting up... Here is what > it says... > > >> > > ... > > npx0: INT 16 interface > swapon: /dev/wd0s2b: No such file or directory > Automatic reboot in progress... > /dev/rwd0a: clean. 10401 free (5 frags, 2599 blocks, 0.0% fragmentation) > /dev/wd0s2f: No such file or directory > Can't stat /dev/wd0s2f > Automatic file system check fialed... help! > Enter pathname of shell or RETURN for sh: You are at the single user shell out prompt here. Did you do the installation yourself or how did you get the OS to the disk? Shell out and type /sbin/disklabel -r wd0 to see what partitions there are. To modify /etc/fstab you have to mount -u /dev/wd0a / first to make the root fs writable. Then you can edit /etc/fstab and mount -a. > > << > > I believe that it cannot find any of my other shells, so I hit return, and it > says... > > >> > > mesg: not found > erase ^H, kill ^U, intr ^C > # > > << > > I did recently build a custom kernel, but it has booted several times with it, > so I don't suspect that is the problem. The only thing I did to chance the > machines's configuration, was take the simms out, in the morning... I was > thinking of selling them at the computer show, but didn't. When I got back in > the evening, I put the memory back in, and went to boot up the system... Now > this happens. The machine boots up and runs fine under Dos/Windows. Could you > help me figure out what is wrong, and how to fix it? > > Thank you! > > -Shawn Murphy > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de