[rescue] SS2 SS10 not able to see disks......

Steve Sandau rescue at sunhelp.org
Mon Oct 1 20:23:33 CDT 2001


>At Sun, 30 Sep 2001 22:09:12 -0700 Rob Bains <rbains at ieee.org> wrote:
>
>>Anyone had this happen to them before?  I've got a SS2 with 64M RAM, and
>>a SS10 also with 64M RAM. When I boot the machines, I get:.
>>
>>SCSI Device 3, 0 is not responding
>>Can't open boot device
>>
>>Shouldn't the machine be able to see the disk any way at boot time
>>regardless of whether or not it has OS on it?
>
>probe-scsi-all from firmware will see the drive even if there is no OS or 
>partition table on it, as long as the drive is viable, it is configured to 
>work in a Sparcstation, and there is nothing in the external SCSI chain that 
>is causing a problem on the SCSI bus.
>
>>So far, I've tried:
>>
>>Booting both with two different disks (Seagate ST30xxx), & Quantum
>>(can't remember the exact product ID's).
>>Changing jumpers on the disks to change SCSI ID's (same problem)
>>Installing OS on the disk by booting from the CD (Sol 2.5.1, & 2.6, just
>>to be safe)
>>Doing probe-scsi (came back to the ok prompt without reporting any
>>errors)
>
>Two machines failing with two different drives looks to me like a drive
>configuration problem.  Disable termination on the drive.  Set the first drive
>for ID 3; if you use a second drive set it for ID 1.  I believe that parity is
>ignored and auto-spinup doesn't matter with a single drive.  On IBM and Quantum
>drives I had in a Sparc 10 the only jumpers set were for the IDs.
>
>Do you have anything connected to the external SCSI ports besides the CD?  It
>could be that something external has an ID that is interfering with the internal
>drive ID.  It sounds like your CD drive is okay if you can boot a CD with it; the
>CD's ID should be 6 and termination is necessary at the end of the external
>chain.
>
>-- SP

Checking the termination is a really good idea. Probe-scsi should detect
any drive on the system unless the SCSI bus is messed up. Does
probe-scsi show all the devices you have installed? If not, the SCSI bus
is confused...

Installation of the software (at least Solaris 8) will warn you if you
install the OS on a drive with an ID that's not 3, and will change the
boot prom to boot from the drive you install on. Did you see any message
like that? If you look into the commands on the firmware, you can tell
the machine to boot from the drive that probe-scsi tells you is there.
If none of these things work, I'd put the drives in a known good machine
and verify that they're both working. BTW, did the drives have another
OS on them before this? Funny things happen for example when going from
a bootable Linux drive to a bootable DOS/Win drive...

-- 
Steve Sandau
IS Technician, TMA, Bath, Maine
ssandau at bath.tmac.com



More information about the rescue mailing list