SUMMARY - Kernel changes for second SCSI board?

From: John E. Ryan (jryan@mikison.ma30.bull.com)
Date: Tue Jan 25 1994 - 04:35:28 CST

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

Subject: Kernel changes for second SCSI board?

Thanks for the responses, everything worked out GREAT! I got answers
to my questions PLUS additional useful information! Thanks to:

Lupe Christoph
Glenn Satchell
Wayne Tilford and
Torsten Metzner

My original questions and the responses follow.

John Ryan

== John E. Ryan Bull HN Information Systems Inc. == == (508) 294-3252 (FAX 294-3635) 300 Concord Road MA30/857 == == J.Ryan@ma30.bull.com Billerica, MA. 01821 USA ==

>I have a Sun-4 server and would like to add some SCSI disks. I >currently have an on-board SCSI port that has 4 disks attached. I also >have another SCSI board that is currently unused. I believe the >relevent kernel entries are as follows:

># Support for the SCSI-3 host adapter and the on-board SCSI controller ># on several machines (e.g. 3/50). ># >controller si0 at vme24d16 ? csr 0x200000 priority 2 vector siintr 0x40 >controller si1 at vme24d16 ? csr 0x204000 priority 2 vector siintr 0x41 >tape st0 at si0 drive 040 flags 1 >tape st1 at si0 drive 050 flags 1 >tape st2 at si0 drive 030 flags 1 >tape st3 at si0 drive 020 flags 1 >tape st4 at si1 drive 040 flags 1 >tape st5 at si1 drive 050 flags 1 >tape st6 at si1 drive 030 flags 1 >tape st7 at si1 drive 020 flags 1 >disk sr0 at si0 drive 060 flags 2 >disk sd0 at si0 drive 000 flags 0 >disk sd1 at si0 drive 001 flags 0 >disk sd2 at si0 drive 010 flags 0 >disk sd3 at si0 drive 011 flags 0 >disk sd4 at si0 drive 020 flags 0 >disk sd6 at si0 drive 030 flags 0

># ># Support for onboard SCSI-ESP host adapters ># >controller sm0 at obio ? csr 0xfa000000 priority 2 >tape st0 at sm0 drive 040 flags 1 >tape st1 at sm0 drive 050 flags 1 >tape st2 at sm0 drive 030 flags 1 >tape st3 at sm0 drive 020 flags 1 >disk sr0 at sm0 drive 060 flags 2 >disk sd0 at sm0 drive 000 flags 0 >disk sd1 at sm0 drive 001 flags 0 >disk sd2 at sm0 drive 010 flags 0 >disk sd3 at sm0 drive 011 flags 0 >disk sd4 at sm0 drive 020 flags 0 >disk sd6 at sm0 drive 030 flags 0

>The on-board SCSI is found at "sm0" and the other one is found at >"si0". I believe that I need to change the kernel before I add the >disks to "sio" to avoid having 2 "sd0", 2 "sd2" ... disks. Is this >all I need to do or am I missing something? Is changing the disk >names enough or do the "drive" fields need to change also? Does it >matter what names I use when I change the disk names? From: Lupe Christoph <lupe@alanya.isar.muc.de>

Yes, you have to renumber the disks to avoid name clashes. The current setting is for alternatives. The drive field is an octal (leading zero) number. The second digit is the SCSI target ID, the third number is the LUN (0 on today's embedded controller drives).

The letters on the name select the driver. Leave them alone. "disk" and "tape" is equivalent, it's just for us humans :-) The flags select the actual SCSI device type. -- | lupe@alanya.isar.muc.de (private, German IN) | Disclaimer: | | lupe@cic.de (company, XLink) | This is an unofficial | | suninfo!alanya!lupe (for Sun Germany) | opinion of Christoph & | | Non sunt multiplicanda entia praeter necessitatem. | Imschweiler Consulting | From: glenn@uniq.com.au (Glenn Satchell - Uniq Professional Services)

By the look of your description you have a 4/300 system. The built in scsi uses the sm0 (as you mentioned). The vme scsi board is the same as the one used in 4/490's and the old sun3 servers. It does *not* do synchronous scsi so the maximum transfer rate will be around 1.5 Mb/sec. This means don't put your fast disks on this bus as you will waste the performance! The onboard will do syncronous scsi although the kernel doesn't print a message out like it does on the sun4c systems.

As for the kernel mods, you are pretty much right. You should only need to chsnge the sd<n> to some other number (and the st<n> entries too). Note that si0 is the first vme controller and si1 would be a second one if you had it.

regards, -- Glenn Satchell glenn@uniq.com.au | "This is a unix system. Uniq Professional Services Pty Ltd ACN 056 279 335 | I can do this easy." PO Box 70, Paddington, NSW 2021, (Sydney) Australia | Phone 02 360 7434 Pager 016 287 000 Fax 02 331 2572 | - Lex, Jurassic Park "Sun Accredited System Consultants" | From: wtilford@lgc.com

John I can't see where you told us if this is a /370 or /470 and what OS rev ??

On the 4/3xx you do have an sm0 and si0. The 4/4xx has si0 and si1. So I guess you are a 4/370. All it looks like you need to do is edit the lines for si0 and match the disk names to the targets you have set. YES they need to be different, i.e. you will have two targets the same on both controllers but the disk name must be different. I have seen them more than single digits. They must be sdxx.

disk sd5 at sm0 drive 020 flags 0 disk sd6 at sm0 drive 030 flags 0 disk sd7 at sm0 drive 040 flags 0 disk sd11 at sm0 drive 050 flags 0

or something similar. I guess you understand how to set the targets for the disks? This is all a little difficult the first time or two but you will get the hang of it soon. The older arch is difficult because you can't test the scsi targets before you boot. Good luck !!!!!!!!!!!!

Wayne Tilford EMail:wtilford@lgc.com Landmark Graphics Corp New Orleans, La 504-585-7755 From: Torsten Metzner <tom@uni-paderborn.de>

Hello John, I have never tried this on a sun4 Server but I think it's OK if you change the sd? entries and only the sd? entries. If I understand the drive kernel entries correct ( who knows {;-) ) the drive entry specifies the target id's in the following way:

Target ID: 0 1 2 3 4 5 / \ / \ / \ / \ / \ / \ LUN: 0 1 0 1 0 1 0 1 0 1 0 1 | | | | | | | | | | | | drive: 000 001 010 011 020 021 030 031 040 041 050 051 (octal)

drive: 0 1 8 9 16 17 24 25 32 33 40 41 (decimal)

So in my opinion you need to change the sd? entries and in my opinion you can choose disk names like sd10 or sd11. But be sure that the devices exist.

E.G.: It should be OK, if your configuration file looks like:

Then, if your disks have an embedded controller ( the usual for external disks ) and you have the disks with target id 0 and 3 on the sm0 controller and the disks with target id 0 and 3 on the si0 controller the system should recognizes the disks as: sd0, sd6, sd7 and sd12.

Hope this is correct ( I think so ) and it helps,

Torsten. P.S.: The Emulex MD21 ( the controller we have in our sun4 server ) is an external controller and for this reason you can have two disks per target, but I think that's not very interested for you. ------------------------------------------------------------------------------- My address : Torsten Metzner E-Mail: tom@uni-paderborn.de Rechnerbetreuung Mathematik Tel.: +49 5251 603898 or Universitaet-GH Paderborn Tel.: +49 5251 602634 FB 17 - Mathematik Fax : +49 5251 603836 Warburger Str. 100 33098 Paderborn Germany -------------------------------------------------------------------------------

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:08:54 CDT