[4627] in testers

home help back first fref pref prev next nref lref last post

Solaris athena-9.0 beta update

daemon@ATHENA.MIT.EDU (Ken Raeburn)
Thu May 17 18:59:21 2001

To: testers@mit.edu
From: Ken Raeburn <raeburn@MIT.EDU>
Date: 17 May 2001 18:59:16 -0400
Message-ID: <tx1n18b37ln.fsf@mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

I ran into the same problem reported by ajfox on 02-May when I
attempted to update dcl (also an ultra 10):

/dev/rdsk/c0t0d0s1: CANNOT READ: BLK 16
/dev/rdsk/c0t0d0s1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

After a long time poking about, Tom and I discovered that the major
device number for the disk entries in /devices/... were wrong for my
machine and/or the new kernel; they were using 134, and the kernel
wants 136.

Changing them, which required mounting a tmpfs file system over part
of /devices on the miniroot, since I couldn't remount the root as
read/write, allowed me to fsck the partition.  Then I could remount
the root read-write.  Then I could write a script to correct the
device nodes (the "drvconf" program looked useful from the man page,
but just gave error messages).  Then I could reboot and the system
came up running the miniroot....

"unable to examine the kernel" was printed during the update process,
after starting AFS.  But the update seems to be moving along....

home help back first fref pref prev next nref lref last post