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.

Rick Copeland

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
>> 
>
>