[5498] in testers
Solaris 9 update issue
daemon@ATHENA.MIT.EDU (Garry Zacheiss)
Tue Jun 17 19:06:33 2003
Message-Id: <200306172306.h5HN6VUb006518@brad-majors.mit.edu>
To: miki@MIT.EDU, testers@MIT.EDU
Date: Tue, 17 Jun 2003 19:06:31 -0400
From: Garry Zacheiss <zacheiss@MIT.EDU>
alexp had his Ultra 5 fail to update to 9.2.7 this morning, and asked me
to take a look at it. I found it having failed to mount a root
filesystem off the miniroot, displaying the usual:
INIT: couldn't create /var/adm/utmpx
or whatever the exact wording is.
After playing around with it for a while, I was able to fix the problem
by booting single user off of the install server, mounting the miniroot
on /mnt, changing the entry for the dad driver in /mnt/etc/name_to_major
to 136, and rerunning drvconfig/devlinks/disks to recreate the device
nodes on the miniroot with major number 136. The update then happened
and completed uneventfully.
Surprisingly, the machine didn't require attention when it finished the
update, and booted just fine off of its normal root partition with
name_to_major containing a "dad 134" entry and corresponding device
nodes. This implies the miniroot is somehow pickier about the device
major number than the installed machine, which doesn't make any sense,
and I'm looking for errors in how I gathered the data.
In the meantime, what this means is that Ultra 5s and 10s that were
installed at 8.3 or earlier aren't able to update to 9.2. This probably
isn't the end of the world, but we should either fix it before the
release happens, or make it not possible for those machines to update
without a reinstall.
Garry
