Craig Ian Dewick wrote:
>
> I'm trying to upgrade a machine (Ultra 60) from Solaris 9 HW 12/03 to HW
> 9/05 using CD-R copies of the Solaris 9 CD's burnt from ISO's downloaded
> from Sun and extracted out the downloaded zipfiles
>
> The Solaris 9 1 of 2 CD-R is fine, but the second one isn't doing
> anything and I've burnt a second disk from the second ISO image to
> compare, and it's giving the same behaviour. I've tried different CD-ROM
> drives, also with the same result. Not sure what's causing the second CD
> to not be scanned, but I'm not in a position to do much more now since I
> start work at 3.30 pm (bit over half hour!).
>
> I realise it's a risk, but I've just skipped installing the extra
> software off the second CD so I can reboot the machine and see what
> happens. I know of some problems that are pre-existing (mainly related
> to Perl - need to upgrade that to 5.8.7).
>
> I'll have a go at upgrading the machine to Solaris 10 tonight using the
> set of 4 CD-ROM's.
>
> That aside, is there a way to get Solaris to re-try installing the
> software it needs off the second Solaris 9 CD? When I rebooted the
> system the kernel reported SCSI timeouts trying to talk to the CD-ROM
> drive - perhaps something in the ISO for the second Solaris 9 CD makes
> the drive get into an unknown state which Sun's 'glm' driver can't
> understand...
>
> In any case, the machine is running but some things are broken since I
> tried to build the new version of Perl (using CPAN) and gcc's giving
> linker errors. That probably means one of the packages on the second
> Solaris 9 CD contains libraries that the linker is expecting to find. hmm
>
> Craig.
>


I had a similar problem with the Solaris 10 zipped ISO images that I
downloaded. I orginally downloaded them to my Mac OS X system and
unzip'd them there. The only CD burner that I have available is on my G4
Powerbook. I had all kinds of weird problems. So I copied the zip files
to a Solaris 9 system and unzip'd them there. The odd thing was that the
byte count of the .iso files was the same on Solaris as they were on my
Mac. Never the less, I copied the ISO files from the Solaris system to
my Mac and used cdrecord on my Mac to burn a new set a of CD's. After
that, all the CD's worked perfect.

The important thing is, unzip the files on a Solaris system.

--
Bob Harris
Sprint
IP Services
Reston, VA USA

Bob Harris <pendavi@hotmail.com> writes:

>I had a similar problem with the Solaris 10 zipped ISO images that I
>downloaded. I orginally downloaded them to my Mac OS X system and
>unzip'd them there. The only CD burner that I have available is on my G4
>Powerbook. I had all kinds of weird problems. So I copied the zip files
>to a Solaris 9 system and unzip'd them there. The odd thing was that the
>byte count of the .iso files was the same on Solaris as they were on my
>Mac. Never the less, I copied the ISO files from the Solaris system to
>my Mac and used cdrecord on my Mac to burn a new set a of CD's. After
>that, all the CD's worked perfect.

I don't know if it's just because I'm using CD-R's instead of real CD's, or
something in the actual data or the way the ISO image was created. Maybe an
idea would be to download the previous HW update ISO's and try with those.

>The important thing is, unzip the files on a Solaris system.

I did that. I downloaded the ISO zip file again too, then burnt another
copy. Identical result.

Craig.
--
Craig Dewick (craig@poison.lios.apana.org.au). http://lios.apana.org.au/~craig
APANA Sydney Deputy Regional Co-ordinator. Operator of Jedi (APANA Sydney POP)
Always striving for a secure long-term future in an insecure short-term world
Have you exported a crypto system today? Do your bit to undermine the NSA.