From owner-freebsd-questions  Tue Dec 23 15:11:13 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id PAA18642
          for questions-outgoing; Tue, 23 Dec 1997 15:11:13 -0800 (PST)
          (envelope-from owner-freebsd-questions)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA18637
          for <freebsd-questions@FreeBSD.ORG>; Tue, 23 Dec 1997 15:11:10 -0800 (PST)
          (envelope-from julian@whistle.com)
Received: (from daemon@localhost)
	by alpo.whistle.com (8.8.5/8.8.5) id PAA26371;
	Tue, 23 Dec 1997 15:08:31 -0800 (PST)
Received: from UNKNOWN(), claiming to be "current1.whistle.com"
 via SMTP by alpo.whistle.com, id smtpd026369; Tue Dec 23 15:08:23 1997
Message-ID: <34A043BC.15FB7483@whistle.com>
Date: Tue, 23 Dec 1997 15:05:32 -0800
From: Julian Elischer <julian@whistle.com>
Organization: Whistle Communications
X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386)
MIME-Version: 1.0
To: Charlie Roots <osiris2002@yahoo.com>
CC: freebsd-questions@FreeBSD.ORG
Subject: Re: /dev corrupt?
References: <19971223212515.6433.rocketmail@send1a.yahoomail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Charlie Roots wrote:
you forgot a step:

after entering the shell type:
mount -f -u /

OR if you really have smashed  /dev, you may need to 
use the fixit floppy.

> 
> Hi Lannes;
> You seem to be in DEEP trouble,
> nevertheless, FreeBSD is Disaster-Resistant,
> and it is most likely that you can recover this mess,
> 
> Suggested procedure;
> 1. Reboot into Single user mode
>         at the FreeBSD boot prompt enter  -s
> 2. cd /dev
> 3. ls -l | more ( check out what's there)
> 4. if you find a file named MAKEDEV then you are NOT out of luck.
> 5. ee MAKEDEV
> 6. read the names of the devices 'CAREFULLY' , write some on paper.
> 7. type 'ESC' to exit from the editor (DO NOT SAVE the FILE)
>  exit without saving from the ee editor.
> 8. to create a device issue the command (exactly);
>         ./MAKEDEV dev0 dev1 .... etc where dev0 and dev1
>         are VALID device names 'from the MAKEDEV itself'
> 9. after ALL devices are created, reboot. (Multiuser mode-just hit
> enter)
> 10. test whatever you were testing before the mishap.
> 11 if in trouble ASK US AGAIN, DO NOT do anything RATIONAL.
> 
> Greetings
> 
> ---Lannes <Lannes@mwweb.com> wrote:
> >
> > Hello,
> >       I'm somewhat new to unix, and I am trying to keep a box running.
> Finding
> > it a bit difficult too. I'm normally a windows user, and not sure
> how to
> > repair this. Is it a /dev, a kernel error, or something else? When
> my shell
> > users try to log on, they get no connection, and the box will not
> respond
> > to me in any way. I've tried a restart, but nothing worked. I have a
> load
> > of important files/accts on the box, and was hoping I could somehow
> create
> > it again and bring it back up without losing them.
> >
> >                                                                Thanks,
> >                                                               R.Lambert
> >
> 
> ==
> MAY THE FORCE BE WITH YOU.
> _________________________________________________________
> DO YOU YAHOO!?
> Get your free @yahoo.com address at http://mail.yahoo.com