ES250 will boot ney only

[rmmagow]

Hi All,
Have an antique SUN ES250 server that I am trying to upgrade to Solaris 10. I boot from the CDROM fine and it goes through the install process. After the first stage of the install it wants to reboot to the new OS but it only seems to want to run the "boot net" which of course fails. How do I set the boot default to be from the disk that the OS was just installed on? When I re-install this time what should I make note of at disk format time vis-a-vis scsi addresses, slices etc so I can the machine to boot from the hard drive by default. I haven't touched this box in a few years and am using it to feel out Solaris 10 before upgrading my other ancient SUN ES450. Thanks for any and all advice.

 

[coffeysm]

I think you can enter either setenv boot-device disk net or set-default boot-device. I cannot remember the exact syntax for the command.

 

[bfitzmai]

From the ok# prompt... Enter command: setenv boot-device disk

 

[rmmagow]

OK. setenv boot-device disk didn't work, still tried to boot from net on a reset command. But I tried boot disk, then boot disk1, then boot disk2 then finally boot disk3 and it then proceeded to boot from whatever the hell disk3 is. What actually controls this? Was there something I was supposed to do at install time to tell it what I want the boot device to be? One thing I neglected to mention at the beginning was that my CDROM had died. I found an old one and set the jumpers for the scsi and it seemed to come up right and did work fine. The CD isn't on the same channel as the drives is it? I am going to do a setenv boot-device disk3 once it finishes the install stage it is in now so I can see if that permanently fixes the old girl.
Thanks for the replys.

 

[bfitzmai]

From the ok# prompt you can type "devalias". This will show you the alias for the disks. Looks like your root partition is not on the disk 0. You can set the following command from the ok# prompt:

setenv boot-device disk3

This should work.

 

[cndcadams]

To check and see if you have target conflicts do a
probe-scsi from the ok prompt.

The cdrom is on the same bus as the internal drives. General rule of thumb is the cdrom is set to target 6.

Also do a boot cdrom -s and run format to see if the drive is seen from software level.

Thanks

CA

 

[bfitzmai]

Another thing you can look at is which device has the root partition. The command df -k will display all mounted devices. Normally the root partition is on /dev/dsk/c0t0d0s#. Meaning Controller 0, Target 0, Disk 0 and slice number.

 

[Annihilannic]

printenv nvramrc at the 'ok' prompt (or eeprom nvramrc while the system is up and running) to see which devices are defined at boot-time. You can use the nvalias and nvunalias commands to define or undefine these respectively.

Annihilannic.