Path: utzoo!censor!geac!jtsv16!uunet!ginosko!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!cica!iuvax!purdue!gatech!wa4mei!rsj
From: rsj@wa4mei.UUCP (Randy Jarrett WA4MEI)
Newsgroups: comp.unix.microport
Subject: Re: Help needed installing 2.4.0
Message-ID: <2418@wa4mei.UUCP>
Date: 25 Jul 89 21:11:35 GMT
References: <1939@cbnewsc.ATT.COM>
Reply-To: rsj@wa4mei.UUCP (Randy Jarrett WA4MEI)
Distribution: usa
Organization: Amateur Radio Gateway WA4MEI, Chamblee Ga.
Lines: 29

In article <1939@cbnewsc.ATT.COM> imdave@cbnewsc.ATT.COM (david.e.bodenstab) writes:
++>
++>My upgraded 2.4.0L system will not recognize my second disk -- 2.3.0 worked
++>fine.  Has anyone run into this before?
++> 
++>My system: NEC APC/IV (AT)
++>	   disk 0: NEC 40M,  1 dos + 1 unix partition (root, usr, swap and tmp)
++>	   disk 1: Seagate 4096 80M, 1 dos + 1 unix partition (usr/src and
++>								     usr/local)
++> 
++>When I booted 2.4, it wouldn't access disk 1.  So, I backed everything off
++>to diskettes, and ran `fdisk' to re-assign bad blocks and then `divvy 1' to
++>make my file systems.  Divvy worked fine.  *But* when I tried to `labelit
++>/dev/dsk/1s0' I got "cannot read superblock".  It turned out I could not
++>access disk 1 period.  
++> 


When you use divvy to setup the file systems on drive 1 don't use the
root entry.  I had the same problems and they all cleared up when I used
the usr entry '/dev/dsk/1s2' for the system.  I now have a larger drive and
am using all 4 of the file systems for drive 1 and not having any problems but
when it was the only one it wanted to be 1s2.


-- 
Randy Jarrett  WA4MEI 
UUCP  ...!gatech!wa4mei!rsj        | US SNAIL: P.O. Box 941217
PHONE +1 404 493 9017		   |           Atlanta, GA 30341-0217