Subject: Re: Can't stat /dev/sd0a
To: yRick Copeland <rickgc@calweb.com>
From: David Brownlee <abs@NetBSD.ORG>
List: port-sun3
Date: 02/15/1998 21:34:57
	Bingo. Looks like your filesystem is a little deranged, at least
	most of the useful nodes for sd0...

	Hmm.. You need to fsck it somehow.

	Obvious options
	    a) Netboot, fsck, mount, & rerun MAKEDEV.
	    b) Put another SCSI drive on the chain at a lower numbered
	       ID, then boot & fix the original drive as sd1 (hoping
	       its nodes are OK).
	    c) Use disklabel to set sd0f to match sd0a, then fsck it,
	       try mounting it elsewhere and running MAKDEV. Might not
	       work.
	    d) Improvise!

	Good luck - let us know how it goes...

		David/absolute

	--( Funny, I almost believed you for a minute... )--

On Sun, 15 Feb 1998, Rick Copeland wrote:
>
> ls -l /dev/*sd0*
> 
> ls: /dev/rsd0a: bad file descriptor
> ls: /dev/rsd0b: bad file descriptor
> ls: /dev/sd0a: bad file descriptor
> ls: /dev/sd0b: bad file descriptor
> ls: /dev/sd0c: bad file descriptor
> 
> crw-r----- 1  root  operator     17,    2 july 17 1988   /dev/rsd0c
> crw-r----- 1  root  operator     17,    2 july 17 1988   /dev/rsd0d
> crw-r----- 1  root  operator     17,    2 july 17 1988   /dev/rsd0e
> crw-r----- 1  root  operator     17,    2 july 17 1988   /dev/rsd0f
> crw-r----- 1  root  operator     17,    2 july 17 1988   /dev/rsd0g
> crw-r----- 1  root  operator     17,    2 july 17 1988   /dev/rsd0h
> brw-r----- 1  root  operator      7,    2 july 17 1988   /dev/sd0d
> brw-r----- 1  root  operator      7,    2 july 17 1988   /dev/sd0e
> brw-r----- 1  root  operator      7,    2 july 17 1988   /dev/sd0f
> brw-r----- 1  root  operator      7,    2 july 17 1988   /dev/sd0g
> brw-r----- 1  root  operator     17,    2 july 17 1988   /dev/sd0c
> 
> disklabel sd0
> 
> 8 partition
>     size  offset    fstype   fsize  bsize cpg
> a  50783       0    4.2BSD    1024   8192  16   #(cyl 0-275*)
> b 101383   50784    swap                        #(cyl 276-826)
> c 421175       0    unknown                     #(cyl 0-2288)
> e 421175  101384    4.2BSD    1024   8192  16   #(cyl 551-2839)
> 
> 
> 
> At 07:17 PM 2/15/98 -0800, David Brownlee wrote:
> >On Sun, 15 Feb 1998, Rick Copeland wrote:
> >
> >> I mean that fsck, fsck -f or fsck_ffs made no difference in the way the
> >> system responds. It (the system) continues to exibit the problem.
> >> 
> >	OK, can you send the output of:
> >
> >		ls -l /dev/*sd0*
> >		disklabel sd0
> >
> >	Have oyu any other means of booting the box (netboot etc?)
> >
> >	
> >> At 05:35 PM 2/15/98 -0800, David Brownlee wrote:
> >> >	When you say 'no results' do you mean it generated no output, the
> >> >	same output, or correctly fsck'ed the filesystems?
> >> >
> >> >	(I'm as much in the dark as you at this point, but hopefully
> >> >	someone can help with the extra info :)
> >> >
> >> >		David/absolute
> >> >
> >> >	--( Funny, I almost believed you for a minute... )--
> >> >
> >> >On Sun, 15 Feb 1998, Rick Copeland wrote:
> >> >
> >> >> Date: Sun, 15 Feb 1998 17:04:41 -0800 (PST)
> >> >> From: Rick Copeland <rickgc@calweb.com>
> >> >> To: port-sun3@NetBSD.ORG
> >> >> Subject: Can't stat /dev/sd0a
> >> >> 
> >> >> Hello list,
> >> >> 
> >> >> I have a problem booting up my trusty Sun 3/80 (NetBSD 1.2E).  During the
> >> >> automatic boot sequence the following message comes up and the system
> is put
> >> >> in single user mode:
> >> >> 
> >> >>         Automatic boot in progress: starting file system checks
> >> >>         /dev/sd0a: bad file descripter
> >> >>         Can't stat /dev/sd0a
> >> >>         Can't stat /dev/sd0a: bad file descriptor
> >> >>         /dev/rsd0e file system is clean, not checking
> >> >>         /dev/sd0a CAN'T CHECK FILE SYSTEM
> >> >>         /dev/sd0a UNEXPECTED INCONSISTANCY; Run Fsck_ffs Manually
> >> >>         /dev/rsd1e:file system is clean:not checking
> >> >>         THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTANCY:
> >> >>                         /dev/sd0a (/)
> >> >>         Automatic File system check failed; HELP!
> >> >> 
> >> >> I have run fsck_ffs, fsck -f etc. with no results! has anyone got any idea
> >> >> how to fix this problem?
> >> >> 
> >> >> Thanks,
> >> >> 
> >> >> Rick Copeland
> >> >> 
> >> >
> >> >
> >> 
> >
> >
> >
>