From: keith@ksmith.uucp (Keith Smith)
Subject: Re: SCO - PANIC after filesystem resizing using 'divvy'
Organization: Keith's Computer, Hope Mills, NC
Date: Thu, 13 Aug 92 21:17:52 GMT
Keywords: divvy, panic, filesystem, SCO

In article <1992Aug8.165413.21255@tigger.jvnc.net> mtcusa@tigger.jvnc.net (Multilingual Technogies Corporation) writes:
>HI:
>
>REF: SCO version 2
>
>Well, I've apparently done something really stupid.  I resized my hard
>disk, combining a few file systems (Not 'root') into one bigger
>filesystem, and now I can't boot using the current /unix. 
>It just panics.  Can't even get beyond main().

Well, sorta stupid.

what does /etc/default/filesys look like?

Also sounds like you might have hosed up some major minor numbers
somewhere.

>I used 'divvy' to resize things.  Is this a dangerous command to use if
>not re-installing the system?  Is it possible that something in

YES!

>/etc/conf/cf.d has been rendered brain-damaged by 'divvy'?  Divvy
>doesn't seem to have a 'delete' command, so the way I deleted previous
>partitions was by making their size 0.  I did this by setting the end
>point to equal the beginning.  'Divvy' would then show their size to be
>'-'.  I did this for all the ones I wanted to get rid of, and then
>sized the one I wanted to expand  to have an end point equal to the
>endpoint of the last 'shrunken' partition.  Given a lack of guidance by
>the manual page, this was the only method that seemd to produce
>results.  Then I let 'divvy' make the new filesystem, and loaded the
>tape.  All seemed to go well until re-boot time.  Then a big "F*** You
>- system dumped."  (I just KNOW somebody will now tell me about the
>warning on page 'x', footnote 'y' of the 'Z' manual).

It seems to me you have 2 problems.  One with the new filesystem, and
another with your link kit.

On the new filesystem.  You should have deleted all the ones you wanted
to combine first, THEN create a NEW filesystem.  This is the filesystem
problem.  That way at the end of divvy after (i)nstalling the division
setup it will 'Making Filesystems' stall while it sets the filesystem
up.  ALSO,  at the tail end AFTER the filesystem is created it is a good
idea to fsck it once, or until it run thru clean.

You need to hand edit /etc/default/filesys and remove references to the
now non-existant ones.

>
>What is curious is that 'unix.old' works, so I've saved that into
>'unix.works'.  Rebuilding /unix doesn't help.  If a system file has
>been trashed, perhaps I could restore it from the
>'emergency boot floppy' (which also lights up correctly)?

REMOVE the LINK KIT, and re-install it.  Then rebuild the kernel.  Also,
fsck your root filesystem from the "emergency" boot floppies, or N1, N2
(breaking out of install).  NOTE:  Do this in pieces one step at the
time adding the device drivers on, one at a time if at all possible.

>
>Fortunatly, there's a complete backup of the new filesystem, so no data
>was lost, but I really don't look forward to having to reinstall
>the system again.
>

Might be your BEST bet.

>If there's any way to save this disaster, I'd appreciate knowing.
>
>GB - mtcusa@tigger.jvnc.net

Write me a note if you need more info.  The filesys problem is / may be
discreet from the other one.

-- 
Keith Smith          uunet!ksmith!keith            5719 Archer Rd.
Digital Designs      BBS 1-919-423-4216            Hope Mills, NC 28348-2201
Somewhere in the Styx of North Carolina ...
Newsgroups: comp.unix.sysv386