[indiana-discuss] pkg image-update works just fine
Dennis Clarke
blastwave at gmail.com
Tue Jul 1 21:37:47 PDT 2008
Thank you for the details ... but whooops ... see below
On Wed, Jul 2, 2008 at 4:26 AM, sanjay nadkarni (Laptop)
<Sanjay.Nadkarni at sun.com> wrote:
> Dennis Clarke wrote:
>>
>> OKay, so I have been sending emails all day to you guys in which I was
>> trying to figure out what to do and how to do it and why was I doing
>> this anyways ? :-)
>>
>> well here is the good news my friends ... earlier today I upgrade the
>> SUNWipkg software to the absolute latest and greatest and I did that
>> blindly without thinking too much.
>>
>> That went smoothly like so :
>>
>> -bash-3.2# pkg version
>> d974bb176266
>> -bash-3.2# pkg install -v SUNWipkg at 0.5.11-0.91:20080620T101740Z
>> Before evaluation:
>> UNEVALUATED:
>> +pkg:/SUNWipkg at 0.5.11,5.11-0.91:20080620T101740Z
>>
>> After evaluation:
>> pkg:/SUNWipkg at 0.5.11,5.11-0.86:20080426T174940Z ->
>> pkg:/SUNWipkg at 0.5.11,5.11-0.91:20080620T101740Z
>> None
>> DOWNLOAD PKGS FILES XFER (MB)
>> Completed 1/1 100/100 0.89/0.89
>>
>> PHASE ACTIONS
>> Removal Phase 2/2
>> Update Phase 92/92
>> Install Phase 11/11
>> -bash-3.2# pkg version
>> 0ae5e72ba7ee
>>
>> Now maybe I wasn't supposed to do that and I should have just stuck
>> with something related to snv_86 or something like that. I really
>> don't know .. I just wanted to do what a John Doe average user would
>> do. Grab the latest and then upgrade to that.
>>
>> Seems to work fine for me. What were other people talking about ? I
>> don't see a problem and .. I couldn't find one.
>>
>> I then decided to just update the whole shooting match with this sort
>> of thing :
>>
>> -bash-3.2# pkg image-update -v
>> Before evaluation:
>> UNEVALUATED:
>> +pkg:/SUNWlibsmbclient at 3.0.28,5.11-0.91:20080613T174525Z
>> +pkg:/entire at 0.5.11,5.11-0.91:20080616T184243Z
>> +pkg:/slim_cd at 0.5.11,5.11-0.91:20080613T182134Z
>> +pkg:/slim_install at 0.1,5.11-0.91:20080613T182617Z
>>
>> After evaluation:
>> pkg:/SUNWlibsmbclient at 3.0.28,5.11-0.86:20080426T175140Z ->
>> pkg:/SUNWlibsmbclient at 3.0.28,5.11-0.91:20080613T174525Z
>> .
>> .
>> .
>> None -> pkg:/SUNWstmf at 0.5.11,5.11-0.91:20080613T180217Z
>> None -> pkg:/SUNWpython-cherrypy at 0.5.11,5.11-0.91:20080613T182501Z
>> None -> pkg:/SUNWixgbe at 0.5.11,5.11-0.91:20080613T174340Z
>> None -> pkg:/SUNWural at 0.5.11,5.11-0.91:20080613T182505Z
>> None
>> DOWNLOAD PKGS FILES XFER (MB)
>> Completed 557/557 15551/15551
>> 1334.65/1334.65
>>
>> PHASE ACTIONS
>> Removal Phase 3207/3207
>> Update Phase 14966/14966
>> Install Phase 6234/6234
>> Jul 2 04:01:27 aequitas pseudo: pseudo-device: lofi0
>> Jul 2 04:01:27 aequitas genunix: lofi0 is /pseudo/lofi at 0
>> A clone of opensolaris exists and has been updated and activated. On
>> next boot the Boot Environment opensolaris-1 will be mounted on '/'.
>> Reboot when ready to switch to this updated BE.
>> -bash-3.2# beadm list
>>
>> BE Active Active on Mountpoint Space
>> Name reboot Used
>> ---- ------ --------- ---------- -----
>> opensolaris-1 no yes - 5.29G
>> opensolaris yes no legacy 3.50M
>> -bash-3.2#
>>
>> So there you have it ... it did exactly what it should and I didn't
>> see a single problem.
>> No network lag or timeouts or anything like that.
>>
>> see details at :
>> http://www.blastwave.org/dclarke/OpenSolaris/image-update-woohoo.txt
>>
>> so gee ... now what ? reboot I guess ?
>>
>> Before I do that .. is there anything new in the GRUB config for me to
>> look at? I have this machine set to run with a serial console and I
>> hope that is retained.
>>
>
> Since you are upgrading from 2008.05 to build 91 you need to do the
> following.
>
>
>> Instructions to update OpenSolaris 2008.05 to build 89 or later
>> ================================================================
>>
>> The command "pkg image-update" can be used to update an OpenSolaris
>> 2008.05 system to build 89 or later. However due to changes in the
>> GRUB boot system, one must manually update the Master Boot Record (MBR)
>> to include these latest changes.
>>
>> When "pkg image-update" completes successfully, it will print a message
>> of the form
>>
>> A clone of opensolaris exists and has been updated and
>> activated. On next boot the Boot Environment opensolaris-1 will
>> be mounted on '/'. Reboot when ready to switch to this updated
>> BE.
>>
>> The name of the newly created clone can also be seen by looking for the
>> "Active on reboot" entry in the output of the "beadm list" command
>>
>> $ beadm list
>> BE Active Active on Mountpoint Space
>> Name reboot Used
>> ---- ------ --------- ---------- -----
>> opensolaris-1 no yes - 17.06M
>> opensolaris yes no - 33.92M
>>
>> First, mount the clone under the /mnt directory
>>
>> $ pfexec mount -F zfs rpool/ROOT/opensolaris-1 /mnt
>>
>> Next, update the GRUB configuration on your ZFS boot device(s) using
>>
>> $ pfexec /mnt/boot/solaris/bin/update_grub -R /mnt
>>
>> When you're ready to boot into the updated boot environment, you can
>> reboot(1M) or init(1M) as usual.
Things don't go quite as smoothly with me because I have a zpool that
is a mirror :
-bash-3.2# zpool status
pool: rpool
state: ONLINE
scrub: resilver completed after 0h8m with 0 errors on Tue Jul 1 00:45:29 2008
config:
NAME STATE READ WRITE CKSUM
rpool ONLINE 0 0 0
mirror ONLINE 0 0 0
c4d0s0 ONLINE 0 0 0
c4d1s0 ONLINE 0 0 0
errors: No known data errors
-bash-3.2# beadm list
BE Active Active on Mountpoint Space
Name reboot Used
---- ------ --------- ---------- -----
opensolaris-1 no yes - 5.29G
opensolaris yes no legacy 3.50M
-bash-3.2# zfs list
NAME USED
AVAIL REFER MOUNTPOINT
rpool 5.66G
28.8G 57K /rpool
rpool at install 18.5K
- 55K -
rpool/ROOT 5.29G
28.8G 18K /rpool/ROOT
rpool/ROOT at install 0
- 18K -
rpool/ROOT/opensolaris 3.50M
28.8G 2.45G legacy
rpool/ROOT/opensolaris-1 5.29G
28.8G 3.04G legacy
rpool/ROOT/opensolaris-1 at install 69.5M
- 2.22G -
rpool/ROOT/opensolaris-1 at static:-:2008-07-02-03:20:17 168M
- 2.45G -
rpool/ROOT/opensolaris-1/opt 842M
28.8G 842M /opt
rpool/ROOT/opensolaris-1/opt at install 73K
- 3.60M -
rpool/ROOT/opensolaris-1/opt at static:-:2008-07-02-03:20:17 0
- 842M -
rpool/ROOT/opensolaris/opt 105K
28.8G 842M /opt
rpool/export 371M
28.8G 19K /export
rpool/export at install 15K
- 19K -
rpool/export/home 371M
28.8G 371M /export/home
rpool/export/home at install 19K
- 21K -
-bash-3.2# mount -F zfs rpool/ROOT/opensolaris-1 /mnt
-bash-3.2# /mnt/boot/solaris/bin/update_grub -R /mnt
Creating GRUB menu in /mnt
bootadm: biosdev command failed for disk: /dev/dsk/c4d1s0.
bootadm: is_bootdisk(): cannot determine BIOS disk ID 'hd?' for disk:
/dev/dsk/c4d1s0
Installing grub on /dev/rdsk/c4d0s0
stage1 written to partition 0 sector 0 (abs 16065)
stage2 written to partition 0, 265 sectors starting at 50 (abs 16115)
Creating GRUB menu in /mnt
bootadm: biosdev command failed for disk: /dev/dsk/c4d1s0.
bootadm: is_bootdisk(): cannot determine BIOS disk ID 'hd?' for disk:
/dev/dsk/c4d1s0
bootadm: biosdev command failed for disk: /dev/rdsk/c4d1s0.
Installing grub on /dev/rdsk/c4d1s0
stage1 written to partition 0 sector 0 (abs 16065)
stage2 written to partition 0, 265 sectors starting at 50 (abs 16115)
I guess I'm okay with the GRUB things written to disk c4d0s0 but the
mirror disk causes problems.
I'll now go searching for the menu.lst file.
Dennis
More information about the indiana-discuss
mailing list