Funny you should say that. I am doing exactly the same thing on the same
hardware right now :-).
My first attempt was with a very old Toshiba CDROM (don't know what
model). Worked fine, no errors, even after reboot.
It was only a small system disk, so I ended up installing again (with
more suitable partition sizes), only this time I used an external CDROM
enclosure with 4 drives in it (making sure only one of them is on SCSI
address 6, and the rest are non clashing). During the installation, it
would keep giving me SCSI errors etc. Finally I opened the CDROM
enclosure and disconnected the 3 unused CDROM's, and this time it went
My second CDROM is an El-Cheapo brand, so I don't think your CDROM is at
fault, especially if it installed fine.
Your problem is more to do with not being able to read a disk label,
which sounds a bit like a bad disk, or bad connection, termination etc.
The only thing I can suggest is make sure you haven't overdone the SCSI
termination. i.e. If you are putting that disk in an external enclosure
as it is, don't terminate that end of the bus. The disk should already
Hope this helps,
Walter Lolham | Sanderson Local Government Solutions
| 13th Level, 33 Berry St, North Sydney, NSW, Australia
| Phone: +61-2-9926-2800 (-2888 FAX)
> I have a SparcII and an old ('95) 4x external Toshiba CDROM drive in a 411
> case. yesterday i was clean installing Solaris 2.6 onto the system from
> CDROM when i started getting errors. it was at the point after
> installation, reboot, and then it launches CDE to complete installation. so
> i figured i'd boot from CD again and start over. at this point i started
> getting this:
> Rebooting with command: cdrom
> Can't read disk label.
> Can't open disk label package
> Can't open boot device
> any ideas? is this cdrom incompatible with Solaris 2.6? i installed 2.6 on
> this system before without any problems, although i stopped being able to
> boot off my 2.5.1 CD after that. i figured the 2.5.1 disc was bad, but
> maybe 2.6 made the drive unhappy. or maybe the drive is kaput.
> also, i just replaced the nvram chip a few months ago. i don't know if
> that's important to this issue.