Unable to upgrade to Sol Express B54 on SB1000

I'm trying to upgrade an SB1000 from Solaris 10 3/05 to Solaris Express 
B54 with no success.

The installer gets to the point where it is "Gathering upgrade 
information" and then a dialog pops up with the message:

"Error!"  "Could not reinitialize system state. Please exit the 
installer and restart the installation."

Once I select 'Exit' a terminal window opens and I can try restarting 
the installation -- no joy.

Any ideas?

[It just occurred to me this might not be the correct place to ask this 
question -- if not, guidance will be appreciated.]

Thanks,
-- 
HZ

Hank Zoeller < XXXX@XXXXX.COM > writes:

That's bit of a catch-all message, but it tends to occur when the
install process attempts to scan the available disks for one that can
be upgraded, and then runs into trouble mounting or unmounting the
disk.  The work-around is to remove unneeded disks temporarily.  (See
CRs 6224955 and 5086453.)


Since it's Solaris Express, either Sun support or one of the
opensolaris.org mailing lists might be a better place to start.

-- 
James Carlson, KISS Network                    < XXXX@XXXXX.COM >
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

Thank you for that insight.  I've removed an extra disk that I mount on 
~/Documents and also removed an NFS mount from the automounter.  And, 
that got me a little bit further but the upgrade still fails.  Here is 
the resulting /tmp/install_log:

// quote (spelling verbatim)
Error: ERROR: Mount failed for either root, swap, or other file system
Pfinstall failed. Exit stat= java.lang.UNIXProcess@dcb03b 2
cified if an upgrade with disk space reallocation is required

Processing profile

Checking C2t1d0s0 for an upgradeable Solaris image

ERROR: Mount failed for either root, swap or other file system
// end quote

Is this log entry telling me that there is not sufficient space in a 
particular slice to perform an upgrade?

# df -k
Filesystem            kbytes    used   avail capacity  Mounted on
/dev/dsk/c1t1d0s0     383887  132656  212843    39%    /
/devices                   0       0       0     0%    /devices
ctfs                       0       0       0     0%    /system/contract
proc                       0       0       0     0%    /proc
mnttab                     0       0       0     0%    /etc/mnttab
swap                 1530576     920 1529656     1%    /etc/svc/volatile
objfs                      0       0       0     0%    /system/object
/dev/dsk/c1t1d0s6    5459598 2942890 2462113    55%    /usr
fd                         0       0       0     0%    /dev/fd
/dev/dsk/c1t1d0s3     383887  150305  195194    44%    /var
swap                 1529696      40 1529656     1%    /tmp
swap                 1529712      56 1529656     1%    /var/run
/dev/dsk/c1t1d0s5    14108795 3830849 10136859  28%    /opt
/dev/dsk/c1t1d0s7    14382923 3327215 10911879  24%    /export/home
/dev/dsk/c1t2d0s0    35009161 14253957 20405113 42% 
/export/home/hz/Documents

Thanks,
-- 
HZ

Hank Zoeller < XXXX@XXXXX.COM > writes:

No.  It appears to be saying that it can't mount up the root file
system on /dev/dsk/c2t1d0s0 in order to run the upgrade process.  This
likely means that /dev/dsk/c2t1d0s0 is corrupt, or that the list of
file systems specified to be mounted in it is incorrect.

I suspect you're going to need help from support to troubleshoot this;
it doesn't look like a failure I've seen before.

-- 
James Carlson, KISS Network                    < XXXX@XXXXX.COM >
Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

OH!  I had not carefully read that line -- thank you for pointing out 
that the problem is c2t1d0s0.  I hadn't noticed the *2*.

Now, I'm really confused as I do not have a third controller in this 
SB1000.

# ls /dev/dsk
c0t6d0s0 c0t6d0s3 c0t6d0s6 c1t1d0s1 c1t1d0s4 c1t1d0s7 c1t2d0s2 c1t2d0s5
c0t6d0s1 c0t6d0s4 c0t6d0s7 c1t1d0s2 c1t1d0s5 c1t2d0s0 c1t2d0s3 c1t2d0s6
c0t6d0s2 c0t6d0s5 c1t1d0s0 c1t1d0s3 c1t1d0s6 c1t2d0s1 c1t2d0s4 c1t2d0s7

c0 controls the DVD-ROM and the DAT tape drive.
c1 controls the two FC-AL disk drives.

The only extra boards in this machine are a SunPCI-II and an XVR-500.

Hmmmm..
-- 
HZ

Which devices did the installer tell you were upgradeable?  Was
/dev/dsk/c2t1d0s0 one of them, or is this device listed in /etc/vfstab?

-- 
Ian Collins.

I don't recall the installer telling me about which devices were 
upgradeable or asking me to choose one.  Nothing in my notes but I can 
run it again..

$ cat /etc/vfstab
#device    device       mount         FS      fsck    mount   mount
#to mount  to fsck      point         type    pass    at boot options
#
fd                  -                   /dev/fd fd -  no     -
/proc               -                   /proc proc -  no     -
/dev/dsk/c1t1d0s1   -                    -    swap -  no     -
/dev/dsk/c1t1d0s0   /dev/rdsk/c1t1d0s0   /    ufs  1  no     - 
/dev/dsk/c1t1d0s6   /dev/rdsk/c1t1d0s6   /usr ufs  1  no     -
/dev/dsk/c1t1d0s3   /dev/rdsk/c1t1d0s3   /var ufs  1  no     -
/dev/dsk/c1t1d0s7   /dev/rdsk/c1t1d0s7   /export/home ufs 2 yes -
/dev/dsk/c1t1d0s5   /dev/rdsk/c1t1d0s5   /opt ufs  2  yes    -
/devices            -                    /devices devfs - no -
ctfs                -            /system/contract ctfs - no -
objfs               -            /system/object  objfs - no -
swap                -            /tmp            tmpfs - yes -
/dev/dsk/c1t2d0s0   /dev/rdsk/c1t2d0s0 /export/home/hz/Documents ufs 
    2  yes  -

So, no, the c2 device is not listed in /etc/vfstab or in /dev/dsk.

Thanks,
-- 
HZ