Can't boot from cdrom at ok prompt

UNIX Solaris
1

I want to install Solaris 9 on SUN ULTRA 10. The cdrom is attached to an ide controller. The server is currently running Solaris 2.6

I insert Solaris cd 1 of 2 and at the ok prompt I type boot cdrom i get the error below

Boot device: /pci@1f,0/pci@1,1/ide@3/cdrom@2,0:f file and args:
evaluating : boot cdrom

Cant open boot device

In Solaris 2.6 when I insert the Solaris 9 cd 1 of 2 it autoruns meaning the cdrom is functioning properly.

Kindly assist ?

Regards

Msoro

2

Boot the Solaris 9 Installation CD instead - or change the slice you are booting from on the 1st cd of 2. See layout info at docs.sun.com

3

do a:

setenv auto-boot? false
reset-all
probe-scsi-all
probe-ide

and post the output of the last two commands!

4

My Ultra 10 has an external SCSI disk & two internal disks attached to ide interface

probe-scsi-all
/pci@1f,0/pci@1scsi@2,1

probe-ide
Device 0 (primary master)
ATA model: st39140a

Device 1 (primary slave)
ATA model: 1BB-DTLA-305010

Device 2 (secondary master)
Not present

Device 3 (secondary slave)
Not present

still not booting from cdrom at ok prompt

5

Solaris 9 Installation CD is not booting from the ok prompt. I get the same error message ie

Boot device: /pci@1f,0/pci@1,1/ide@3/cdrom@2,0:f file and args:
evaluating : boot cdrom

Cant open boot device

How do I change the slice I'm booting from at the ok prompt ? a simple example will suffice

Regards

Msoro

6

Try booting the solaris 9 installation disk like this

ok> boot /pci@1f,0/pci@1scsi@2,1

7

that doesn't work either. I still get the same error message

8

Got the advice below from a buddy & made the nessesary changes.

If you have an Ultra 5/10 with 2 IDE hard drives with DiskSuite mirroring and a CD-ROM, then the "cdrom" device alias in the EEPROM needs modification. DiskSuite requires one IDE drive to be the master on the primary controller and the other IDE drive to be the master on the secondary controller. This forces you to make the CD-ROM a slave on one of the two controllers. At this point, the factory "nvalias" for the CD-ROM is broken and you can't boot from CD-ROM. You just have to modify the "cdrom" device alias in EEPROM.

Factory setting (display using the devalias command:

cdrom /pci@1f,0/pci@1,1/ide@3/cdrom@2,0:f

If the CD-ROM is a slave on the primary controller:

ok nvalias cdrom /pci@1f,0/pci@1,1/ide@3/cdrom@1,0:f

If the CD-ROM is a slave on the secondary controller:

ok nvalias cdrom /pci@1f,0/pci@1,1/ide@3/cdrom@3,0:f

Now you can boot from CD-ROM using the new alias just created. For example, boot cdrom.

***********************************************

this time I'm getting a slightly diffrent message ie

ok boot cdrom

Boot device: /pci@1f,0/pci@1,1/ide@3/cdrom@1,0:f file and args -r

 can't read disk label
 can't open disk label package

  can't open boot device
9

Could it be that you need to set the jumper for the blocksize on the cdrom?

10

Hi,
I am having a problem installing solaris 10 on a V100 because of the cdrom drive. I am using Jump server to do the install but, I am getting an error.

the error is:

message overflow in /dev/log .

I think it's something to do with nfs but i used it before.

Any ideas.

thanks

11

Boot device: /pci@1f,0/pci@1,1/ide@3/cdrom@1,0:f file and args -r

can't read disk label
can't open disk label package

can't open boot device

Aren't you trying to boot from a DVD on a cdrom drive ?
Don't laugh, it happened to me recently
I had the same message and it took me a few hours before realizing what was happening :rolleyes:

12

Hi,

In my case, it was the cdrom drive that needed changing. I managed to get the drive to work only to find Solaris has stopped installing half way :frowning: .

Anyway the Jump server is working now and yes I do have these moment where I think to myself why this is happening to me :confused: only to find I did something wrong.

Thanks