SUMMARY: fatal error from fsck

From: *** Wallace *** <wkha_at_it.uts.edu.au>
Date: Thu Mar 21 2002 - 19:30:38 EST
Thanks to everyone who replied:
Jay Chembakassery
Jan Stankovsky
Jay Lessert
Steve Hammond
Michael Horton
Andrew Stueve and
Bevan Broun

(Eck, Hope I didn't miss out anyone)
Basically what fixed my problem was to boot the system off the
network/cdrom and fsck the system from there. This seemed to work fine.
I was also advised to use the -y option (fsck -y /dev/rdsk/c0t0d0s0),
unfortunately this didn't work.

Other tips pointed out (which either didn't work or I didn't get to
try out):

1. fsck -o b=32 /dev/rdsk/c0t0d0s0
2. Extract from Jay Lessert:
"One would be concerned that perhaps one of

    /usr/sbin/fsck
    /usr/lib/libcmd.so.1
    /usr/lib/libdl.so.1
    /usr/lib/libc.so.1
    /usr/lib/fs/ufs/fsck
    /usr/lib/libadm.so.1
    /usr/lib/libc2.so
    /usr/lib/libelf.so.1
    /usr/platform/SUNW,Ultra-5_10/lib/libc_psr.so.1

is corrupted, or that the file system is hopelessly corrupted."
3. If I still got an fsck error through booting of cdrom, this means there
is a ufs inconsistancy - Time to re-install (Thanks to Andrew Stueve)



On Fri, 22 Mar 2002, *** Wallace *** wrote:

>
> Managers,
> Im getting the following error when my Ultra 1 (Solaris 8) boots up:
>
> The / file system (/dev/rdsk/c0t0d0s0) is being checked
> fsck: Warning: The following command (process 37) was terminated by signal
> 4
> fsck -F ufs -o p /dev/rdsk/c0t0d0s0
> WARNING: fatal error from fsck - error 132
> Unable to repair the / filesystem
> Run fsck manually (fsck -F ufs /dev/rdsk/c0t0d0s0).
>
> After this warning, I give the root password to enter system maintenance
> mode, this is when I try to repair the filesystem with the following
> errors:
>
> #fsck -F ufs /dev/rdsk/c0t0d0s0
>
> ** /dev/rdsk/c0t0d0s0
> ** Last mounted on /
> ** Phase 1 - Check Blocks and Sizes
>
> fsck: WARNING: the following command (process 48) was terminated by signal
> 4
> fsck -F ufs /dev/rdsk/c0t0d0s0
>
> #fsck -F ufs -o p /dev/rdsk/c0t0d0s0
> fsck: WARNING: The followg command (process 51) was terminated by signal 4
> fsck -F ufs -o p /dev/rdsk/c0t0d0s0
>
> Because of these errors, I can't seem to get to the start up prompt. After
> I exit from the system maintenance mode/single user mode, it just does a
> reboot and comes back with the fsck errors. Any help would be appreciated!
>
>
>
> Thanks
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
Received on Thu Mar 21 19:42:20 2002

This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:42:37 EST