Message-Id: <sa6edfe3.037@barr.com> Date: Wed, 24 Jan 2001 13:59:32 -0600 From: Stuart Powell <SPOWELL@barr.com> Subject: Re: [suse-sparc] Troublesome SS10 - Hard Drive Problems During Installation
The two drives came straight out of a replacement for a dead SS10. We
transplanted the drives from the dead one into the new one, so the drives
that shipped with the new one were surplus. I am doing all the
troubleshooting I can on *both* of these two boxes. I don't really have a
preference as to which chassis winds up as the worker and which one goes in
the dustbin, just as long as one of them works.
About the only difference I can find between them is the firmware revision.
One is 2.12, the other is 2.7?. Can't remember exactly what the ? is
right now, but if it becomes an issue, I can cetainly fire that one up and
check it.
Bye for now,
Stuart.
>>> "Mike Nicewonger" <twmaster@twmaster.com> 01/24 1:26 PM >>>
Did the pair of drives come from the SS10's? Did you try the drives in the
other SS10?
Mike N
----- Original Message -----
From: "Stuart Powell" <SPOWELL@barr.com>
To: <suse-sparc@suse.com>
Sent: Wednesday, January 24, 2001 2:19 PM
Subject: [suse-sparc] Troublesome SS10 - Hard Drive Problems During
Installation
> Hello, everyone.
>
> I have a pair of SS10s here, and would like to build one good one from
the
> pair. So far, it has a pair of 40MHz CPUs (not a screamer, I know), an
> additional 100MBit NIC/SCSI combo, 320MB RAM and a pair of 2.1GB drives
> inside. Please bear in mind that I am very new to the Sun platform,
having
> been an x86 user for the past decade+.
>
> The problem I am having is that neither SuSE7 nor the old Solaris that
came
> with the box will configure the hard drives. As per the SS10 standard,
one
> drive is set to ID3, the other is ID1. If I pull either out leaving the
> other one in, I get the same errors. The same errors occur on both
> machines, so it does not appear to be a hardware fault, but it does look
> like a conflict somewhere, or a mis-configuration. Unless the SCSI
> controllers in both machines are fried.
>
> In Solaris, Quick Install sees the drives as 0MB and won't install.
Expert
> Config bombs out when I try to manually configure the drives with the
> following error:
>
> ttinstall aborting (caught signal 8)
>
> As for SuSE7, I have been trying both YaST1 and YaST2, both with the same
> result. I am able to select my Language and Keyboard options, and even
> select the packages in YaST2, but they both abort with errors when they
try
> to create the partition info on the hard drives. Regardless of the
choice
> of YaST version, the text portion of the boot sequence spends a lot of
time
> doing SCSI operations. Some of the errors are as follows:
>
> SCSI host 0 channel 0 reset (pid 3) timed out - trying harder
> SCSI bus is being reset for host 0 channel 0
> esp0: Resetting scsi bus
> esp0: SCSI bus reset interrupt
> esp0: SCSI bus reset interrupt
> probably an unrecoverable SCSI bus or device hang
>
> When I select <Partitioning> in YaST1 with just one drive present, it
> returns an error stating:
>
> No Hard Disk Found
> No hard drives were found on your system.
> Maybe your hardware was not correctly
> recognized by the Linux kernel.
>
> If I type probe-scsi at the ok prompt, it displays the correct number and
> type of drives, including the external Plextor CD-ROM 8x I'm booting the
> installation CDs from.
>
> These are clean hard drives, by the way. Another machine died on us, and
> these are the two drives we pulled out of the replacement unit. I have
> also tried removing the NIC/SCSI combo card, and it does not make a
> difference.
>
> Any ideas as to how I can make this work would be much appreciated. My
> boss is warming to Linux, and I would like to show him its cross-platform
> appeal. He is also keen to try porting our in-house Oracle apps between
> Sun, NT and Linux versions of Oracle, just to see how well that works.
>
> Thanks,
> Stuart.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
This archive was generated by hypermail 2.1.0 : Wed Jun 06 2001 - 11:08:36 PDT