Hi,
Today we started the procedure of upgrading our AlphaServer 2100A which
was running 4.0B to 4.0F via 4.0D. First, I upgraded the firmware to
version 5.3. That went fine. Backed up / and /usr with vdump 0 - no
problems. Followed the instructions posted on this list some time ago to
repartition the system disk to make / partition bigger, as required by
4.0D. No problem. Restored / partition from tape, rebooted, no problem.
Started the installupdate procedure. No layered products detected. It
made it all the way through, merged the software sets. No problem. Then,
it rebooted using the infamous "generic kernel". At this point, all hell
breaks loose.
Upon reboot, I notice that it has completely screwed up where it thinks
all of the disks are. It understands that the system disk is /dev/rz0,
and it has these partitions correct. However, what used to be /dev/rz1 is
now /dev/rz4, what used to be /dev/rz4 is not /dev/rz16, and so on and so
on. Of course, many of these disks are partitioned differently, so it
fails miserably on the filesystem check and won't reboot.
Does anyone have any idea what has happened, or where I can look, or what
I can do? I can always reinstall 4.0B from backup, but since the
installupdate seemed to go so smoothly, I hate to start all over again,
and I am not sure what I would change in any case....
Help !!!!!!!!!!!!!!
Cheers,
Ed.
Received on Tue Jan 18 2000 - 01:50:55 NZDT