James Ray wrote: > All, > > I am having problems with an upgrade of a Sun Fire v240 from Solaris 10 > U1 (01/06) to Solaris 10 U2 (06/06). > I get through the system id process and get to the part where it detects > drives which can be upgraded, at this point the installer shows me: > Solaris Version Slice > [X] Solaris 10 d0 (c2t0d0s0) > [ ] Solaris 10 d0 (c2t0d0s0) > > Which is strange since there is only one install onto mirrored disks. > When I select either of them I get the following message: > "A file system listed in the file system table (vfstab) could not be > checked by fsck." > > Here is the vfstab: > fd - /dev/fd fd - no - > /proc - /proc proc - no - > #/dev/md/dsk/d30 - - swap - no - > /dev/md/dsk/d0 /dev/md/rdsk/d0 / ufs 1 no - > /dev/md/dsk/d10 /dev/md/rdsk/d10 /usr ufs 1 no - > /dev/md/dsk/d20 /dev/md/rdsk/d20 /var ufs 1 no - > /devices - /devices devfs - no - > ctfs - /system/contract ctfs - no - > objfs - /system/object objfs - no - > swap - /tmp tmpfs - yes - > /dev/md/dsk/d43 /dev/md/rdsk/d43 /var/spool/exim-imap ufs 1 yes - > /dev/md/dsk/d44 /dev/md/rdsk/d44 /var/core ufs 1 yes - > > Here is the metastat -c: > Here is metastat -c: > d44 p 100MB d40 > d43 p 8.0GB d40 > d40 m 23GB d41 > d41 s 23GB c3t0d0s6 > d30 m 4.9GB d31 > d31 s 4.9GB c3t0d0s1 > d20 m 2.0GB d21 > d21 s 2.0GB c3t0d0s4 > d10 m 2.0GB d11 > d11 s 2.0GB c3t0d0s3 > d0 m 2.0GB d1 > d1 s 2.0GB c3t0d0s0 > d42 s 23GB c3t1d0s6 > d32 s 4.9GB c3t1d0s1 > d22 s 2.0GB c3t1d0s4 > d12 s 2.0GB c3t1d0s3 > d2 s 2.0GB c3t1d0s0 > > I had detached the sub-mirrors prior to the upgrade attempt as a way of > rolling back if it went wrong. > Quite a few answers to this... Thanks to: Rainer.Heilke@atcoitek.com, "Peter Kunst" <Peter.Kunst@swissrisk.com>, Richard Skelton <Richard.Skelton@infineon.com>. And also the guys at Sun who replied with the answer through my support call. Here is the answer from Sun since its the most complete: > To confirm for future ref, the complete documented procedure is: > > 1. Find the physical devices that are being used for the root partition's RAID-0 volumes or submirrors, as in the following example: > # df -k / > Filesystem kbytes used avail capacity Mounted on > /dev/md/dsk/d0 4459950 3089180 1326171 70% / > > # metastat -p d0 > d0 -m d10 d11 1 > d10 1 1 c1t0d0s0 > d11 1 1 c1t1d0s0 > > 2. Remove the mirror that is not being upgraded. In the example, if the disk to be upgraded is c1t0d0s0, you need to remove d11. Type the following: > # metadetach d0 d11 > > 3. Revert to using the appropriate physical device to be upgraded. For the previous example, you issue the following command. > # metaroot c1t0d0s0 > > 4. If necessary, verify that the /etc/vfstab has been updated with the required device. > # grep c1t0d0s0 /etc/vfstab > /dev/dsk/c1t0d0s0 /dev/rdsk/c1t0d0s0 / ufs 1 no - > > 5. Shut down the system. > > 6. Boot the system from the DVD or CD media. > In the panel Select upgrade or initial install, you can now choose to upgrade. You can also select the device to upgrade from the list of devices in the panel. Typically, the list contains the devices that comprise the original root subvolume. > However, if the option to upgrade remains unavailable, then skip to the alternative workaround. > > 7. To proceed with the upgrade, select the device. > > To rebuild your RAID configurations after the upgrade has been completed, follow these steps. > > 1. Redefine the boot device. > > # metaroot d0 > 2. Reboot the system. > 3. Add the subvolume. > > # metattach d0 d11 > -- James Ray. <j.ray@qmul.ac.uk> Computing Services Queen Mary, University of London _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Wed Jul 19 11:24:47 2006
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:43:59 EST