Sun E220 notes Q. I acquired a Sun Enterprise 220R that I’m trying to install the OS on. I’m trying to boot from CD-ROM (I don’t have a jumpstart server yet), but the system just seems to hang during the boot and never come up. I have a VT terminal attached to it, but I don’t see any out of the ordinary messages. Do I have bad media, or a bad CD-ROM drive, or what? A. Of course, start by verifying that you can boot another machine off your media. If you have bad media, you can always download and burn your own Solaris 8 CD-ROMs from Sun’s Web site. Once you know that the media is good, make sure that the diagnostics are set to full. From the “ok” prompt, do the following: setenv diag-level max setenv diag-switch? true setenv auto-boot? false This should set the diag level to the maximum and stop the machine from attempting to actually boot. You can also try testing components individually (if they are completely failed, they won’t show up in POST). Test the SCSI bus with the following: probe-scsi-all If you don’t see your CD-ROM device, there’s an issue with the CD-ROM drive. Make sure all of the cables are seated correctly and try again. I’ve also seen the system fail to boot in this manner because of bad memory. Make sure that you have all four slots in a bank full with either 32, 64, or 128M DIMMs (you can’t use 256M or 512M in the 220Rs). If POST indicates an error with one of the memory modules, it should be listed with a U number. Figure 1 shows an example identifying which slot has the bad DIMM: If POST isn’t showing you any errors at all, and you’ve tried various things from the Sun 220R diagnostics page at: http://docs.sun.com/ab2/coll.583.2/RAZORSVC/%40Ab2PageView/6016 you can swap out parts to try and identify the problem, or place a service call to Sun. If you don’t have a Sun contract and don’t want to pay the per-incident fee, start by replacing the CD-ROM drive with a known working one (or put the suspect CD-ROM drive into another machine to verify that it works). After that, strip the memory in the machine to the bare minimum (4 DIMMs in one bank) and use known good DIMMs. --- Ahh I see the problem now... ok set-defaults That cleared it up. It looks like it was set for diags from the factory. ~kevin "Kevin P. Inscoe (KE3VIN)" wrote: > > I am having an interesting prom problem with heaney. I set boot-device > to disk and boot-file to /pci@1f,4000/scsi@3/disk > > ok printenv > Variable Name Value Default Value > ... > boot-file /pci@1f,4000/scsi@3/disk ... > boot-device disk disk net > > How what what happens when I just say boot (or reboot from the O/S) by > itself: > > Rebooting with command: boot > Boot device: net File and args: > Using Onboard Transceiver - Link Up. > Timeout waiting for ARP/RARP packet > Timeout waiting for ARP/RARP packet > ... > > However if I say "boot disk" it comes up fine. ----