3rd party SCSI disks on Solaris 2.x

3rd party SCSI disks on Solaris 2.x

Post by Simon Pick » Tue, 18 Jan 1994 17:10:02



We wish to move some SCSI disks from another architecture to a Sparc 10
running Solaris 2.2, but are having difficulties finding the correct
parameters to give to the format utility.  Why does Solaris need to be given
this information anyway, as other OS's (eg DG/UX) don't need to be told
anything about new SCSI disks.

It looks like the following are the required parameters, according to the
"SunOS 5.1 Adding and Maintaining Devices and Drivers" manual.  Is there
any way to empirically determine the values of these parameters?
        total # cylinders
        # cylinders for bad blocks
        # sectors per logical track
        # heads
        rotational speed in rpm (why on earth is this needed?)

If I guess the #cyls, #heads and sectors/track to add up to the correct size
(assuming 512 bytes sectors) will it work anyway?

Any pointers appreciated.

--
___________________



 
 
 

3rd party SCSI disks on Solaris 2.x

Post by Hans J. May » Wed, 19 Jan 1994 18:25:49


(I've followed up because this is the easiest way to post :-)

I'm trying to install Sol-2.3 on a DSP3105. This works fine until the reboot
after installation. Then I get trapped by the infamous "tagged command dis-
connected" message and the system ties up and is unusable.

I remember some time ago someone posted a message containing the solution to
this problem but I did not save it because I never thought it would be of any
relevance to me :-( (it's a mod to /etc/system:scsi-options or something like
that).

Did you manage to install Sol-2.x on any non-Sun disk drive (especially any
kind of Digital Storage Product? I am going to try a DSP3160 this evening)?

TIA - Hans
--

German National Research Center for Computer Science (GMD)

 
 
 

3rd party SCSI disks on Solaris 2.x

Post by Hans J. May » Wed, 19 Jan 1994 18:28:33


(I've followed up because this is the easiest way to post :-)

I'm trying to install Sol-2.3 on a DSP3105. This works fine until the reboot
after installation. Then I get trapped by the infamous "tagged command dis-
connected" message and the system ties up and is unusable.

I remember some time ago someone posted a message containing the solution to
this problem but I did not save it because I never thought it would be of any
relevance to me :-( (it's a mod to /etc/system:scsi-options or something like
that).

Did you manage to install Sol-2.x on any non-Sun disk drive (especially any
kind of Digital Storage Product? I am going to try a DSP3160 this evening)?

TIA - Hans
--

German National Research Center for Computer Science (GMD)

 
 
 

3rd party SCSI disks on Solaris 2.x

Post by Casper H.S. D » Wed, 19 Jan 1994 21:50:36



Quote:>(I've followed up because this is the easiest way to post :-)
>I'm trying to install Sol-2.3 on a DSP3105. This works fine until the reboot
>after installation. Then I get trapped by the infamous "tagged command dis-
>connected" message and the system ties up and is unusable.
>I remember some time ago someone posted a message containing the solution to
>this problem but I did not save it because I never thought it would be of any
>relevance to me :-( (it's a mod to /etc/system:scsi-options or something like
>that).

The scsi_options kernel variable controls this.  A number of
options are ored, from <sys/scsi/conf/autoconf.h>:

#define SCSI_OPTIONS_DR         0x8     /* Global disconnect/reconnect  */
#define SCSI_OPTIONS_LINK       0x10    /* Global linked commands */
#define SCSI_OPTIONS_SYNC       0x20    /* Global synchronous xfer capability */
#define SCSI_OPTIONS_PARITY     0x40    /* Global parity support */
#define SCSI_OPTIONS_TAG        0x80    /*   "    tagged command support */
#define SCSI_OPTIONS_FAST       0x100   /*   "    FAST scsi support */
#define SCSI_OPTIONS_WIDE       0x200   /*   "    WIDE scsi support */

The default on most systems is 0x1f8 (everything - wide)

To switch of tagged commands put the following in /etc/system:

        set scsi_options = 0x178

Installing from CD is usually not a problem because the kernel is
booted with:

    set scsi_options=0x58 (slow & dumb SCSI)

This works for all disks worth having.
I think you can boot from CD and edit /etc/system (or perhaps you can
but single user)

Quote:>Did you manage to install Sol-2.x on any non-Sun disk drive (especially any
>kind of Digital Storage Product? I am going to try a DSP3160 this evening)?

Yes we use non-sun drives, no we don't use DSP3160 drives.

Casper

 
 
 

3rd party SCSI disks on Solaris 2.x

Post by Steve J » Wed, 19 Jan 1994 14:37:47



>If I guess the #cyls, #heads and sectors/track to add up to the correct size
>(assuming 512 bytes sectors) will it work anyway?

That's exactly what I did for a 3rd party disk on the x86 version of
Solaris 2.1.  It worked.

-Steve Jay

 
 
 

3rd party SCSI disks on Solaris 2.x

Post by Syed Zaeem Hosa » Thu, 20 Jan 1994 17:21:09



Quote:>(I've followed up because this is the easiest way to post :-)

>I'm trying to install Sol-2.3 on a DSP3105. This works fine until the reboot
>after installation. Then I get trapped by the infamous "tagged command dis-
>connected" message and the system ties up and is unusable.

>I remember some time ago someone posted a message containing the solution to
>this problem but I did not save it because I never thought it would be of any
>relevance to me :-( (it's a mod to /etc/system:scsi-options or something like
>that).

>Did you manage to install Sol-2.x on any non-Sun disk drive (especially any
>kind of Digital Storage Product? I am going to try a DSP3160 this evening)?

I have installed Solaris 2.0 through 2.2 on an IPX equipped with a DEC
DSP3105 drive without these problems. I have not tried Solaris 2.3
yet.

(FWIW, I removed Solaris 2.X each time after a couple of hours to days,
and "backed up" to Solaris 1.1 after I decided that the new OS was too
unstable for real use - nothing to do with the drive though!)
                                                                Z

--
-------------------------------------------------------------------------
| Syed Zaeem Hosain          P. O. Box 610097            (408) 441-7021 |

-------------------------------------------------------------------------

 
 
 

3rd party SCSI disks on Solaris 2.x

Post by Simon Pick » Fri, 21 Jan 1994 07:53:54



>We wish to move some SCSI disks from another architecture to a Sparc 10
>running Solaris 2.2, but are having difficulties finding the correct
>parameters to give to the format utility.
>[truncated by written permission of the author :-)]

Thanks to all those who replied, by mail and news.

Most suggested that the paramters are only used for optimisation, and it is
ok to guess values so that (#cylinders) * (#head)s * (#sectors/track) adds
up to the total number of blocks on the disk.  The rotational speed is
apparently used to work out the optimal interleave.

I have successfully got one 3rd party disk going using the UNIX command
factor to give the prime factors of the number of blocks and guessing
likely combinations.

I also tried scsiping, a public domain program to measure these parameters,
but it didn't work until I had formatted the disk anyway!

Thanks again to all.

--
___________________



 
 
 

3rd party SCSI disks on Solaris 2.x

Post by David E A Wils » Sat, 22 Jan 1994 10:40:33



>I have successfully got one 3rd party disk going using the UNIX command
>factor to give the prime factors of the number of blocks and guessing
>likely combinations.

Yes - I have used this as well.

Quote:>I also tried scsiping, a public domain program to measure these parameters,
>but it didn't work until I had formatted the disk anyway!

I have found a solution to this one (under 4.1.3 anyway). I could not work out
how format could find the drive but scsiping could not until I ran both programs

under trace. I found that format uses the _FNDELAY flag on its open call. Adding
this flag to scsiping solved the problem.

 
 
 

3rd party SCSI disks on Solaris 2.x

Post by Casper H.S. D » Mon, 24 Jan 1994 21:11:31



Quote:>I have found a solution to this one (under 4.1.3 anyway). I could not work out
>how format could find the drive but scsiping could not until I ran both programs
>under trace. I found that format uses the _FNDELAY flag on its open call. Adding
>this flag to scsiping solved the problem.

New versions of scsiping use FNDELAY (or was that scsiinfo).
After we found outthat format used FNDELAY we looked in the
kernel source to see what it was supposed to do, so we could
determine whether it was safe, the comment said:
``it is format opening us''.

Casper

 
 
 

1. 3rd party (OEM) SCSI hard disk suggestions wanted

        A request to anyone who might have the time to answer this post:

        We have found, as others may have, that IBM hard drives are too
expensive for our budget (beyond the initial purchase anyway) and now
face a need for more storage.

        As a consequence, I'd like to ask for information that people may
have on particular hardware or vendors in the third party market. Our
specific needs are for drives in the 1.0 Gb - 1.2 Gb range, preferrably
external since we don't have much more room for internal drives.

        Comments might include ease of installation, reliability, cost
(of course) and impressions of the supplier.

        If at all possible, for those people who have had good experiences,
I'd appreciate references to your sources including telephone numbers,
U.S. mailing addresses, or e-mail addresses.

        If anyone expresses an interest, I'd be willing to summarize
any information that I receive.

        Thanks.

        Andrew Orndorff
        System Administrator

        NHTSA Data Center

        UUCP:           ...!uunet!dcatlas!drewo

2. GoPenguin.com Pre Release

3. Install 3rd party SCSI DISK ARRAY to SPARC(OS 5.4), How to?

4. HELP! Install RH5.2

5. Adding a 3rd party SCSI disk to an rs6000

6. getting data from tape drive

7. Add 3rd party SCSI disk

8. Solution yet for Solaris 8 name resolution bugs?

9. 3rd party scsi disk support

10. fuji disk M2266 on AIX 3.1/RS-6000 (or other 3rd party disks)

11. PARTY PARTY PARTY PARTY PARTY

12. Booting RS6000 from 3rd party disks

13. 3rd party disk on a SUN Ultra 10