SUMMARY: dud slice

From: Amanda Simondson (ajs@IEOR.Berkeley.EDU)
Date: Fri Jun 06 1997 - 10:27:44 CDT

Hi everyone,

I am very embarrassed. The problem was indeed, my /etc/vfstab file
which I was convinced was not the problem as I had checked it a number
of times.

My thanks to the overwhelming number of responses I got convincing me
that I needed to go back and check it one more time, locating the typo
which was causing the problem.

Original post:

> Hi everyone,
> I am running Solaris 2.5.1 on a SS20.
> I have just repartitioned a hard drive, removing two of the
> slices/partitions so that I now have only /dev/dsk/c0t1d0s6 and
> /dev/dsk/c0t1d0s7 on this particular drive.
> However, on boot, the system finds inconsistencies on /dev/dsk/c0t1d0s4.
> It drops me into the option of going into system maintenance, but of
> course an fsck on the raw device fails because the slice no longer
> exists, and an exit into normal mode brings everything (seemingly ...)
> up OK.
> I'm wondering how to get rid of this and if it will cause further damage
> - i.e. is it bypassing fsck on the slices it would normally check after
> this?
> I have rebooted with the -r option to no avail.
> I am wondering if I could remove the device files for this partular
> slice and try rebooting again?
> Thanks in advance.
> Amanda

Amanda Simondson ajs@IEOR.Berkeley.EDU
IEOR Department, UC Berkeley
4121 Etcheverry Hall Ph: 510-643-8657
Berkeley, CA 94720-1777 FAX: 510-642-1403

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:56 CDT