Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!hao!oddjob!mimsy!chris
From: chris@mimsy.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: panic: iinit on booting 4.3bsd miniroot, VAX 11/750
Message-ID: <7986@mimsy.UUCP>
Date: Fri, 14-Aug-87 20:36:03 EDT
Article-I.D.: mimsy.7986
Posted: Fri Aug 14 20:36:03 1987
Date-Received: Sat, 15-Aug-87 17:58:52 EDT
References: <8799@brl-adm.ARPA>
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 16

In article <8799@brl-adm.ARPA> mullen@nrl-css.arpa (Preston Mullen) writes:
>Trying to bring up 4.3bsd on a VAX 11/750, I booted vmunix from the
>miniroot on disk ra0; upon specifying ra0* as my root device, I got an
>immediate panic: iinit.  Does this imply something like bad blocks in
>the swap area of the RA81 disk I am using?

An iinit panic means that the kernel could not mount the root file
system.  The reason is never mentioned, but it is either an I/O
error (preceded by a message from the appropriate disk driver), a
bad super block, or a nonexistent root device (not the case for
the generic kernel).  The bad super block error could occur if the
standalone copy program and the kernel do not agree as to the
offsets of the `b' partition.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7690)
Domain:	chris@mimsy.umd.edu	Path:	seismo!mimsy!chris