If this isn't exactly what you wanted, please try our Search (there's a LOT of techy and non-techy stuff here about Linux, Unix, Mac OS X and just computers in general!):
From: Tony Lawrence <tony@aplawrence.com>
Subject: Re: Probing SCSI HD on SCO ODT 3
References: <f65R7.692$3r4.28357@news1.tin.it>
Date: Mon, 10 Dec 2001 16:40:28 GMT
news nwttuno wrote:
>
> I've installed a additional SCSI 9GB HD on a HP NetServer LH-II running SCO
> ODT 3.
>
> The new HD is connected to the same SCSI controller to which the SCSI tape
> is currently connected (but not the old SCSI HD, which is connected to
> another channel on the same controller, a Mylex SCSI controller with Adaptec
> 7xxx chipset on-board. The reason for this layout is a difficulty in
> connecting the new hard disk, whose connector is a 68-pin, to the 96-pin
> connector used on NetServer LH-II for the Hard Disks cages).
>
> At boot time the BIOS detects the new disk and says it has the ID configured
> by jumpers. The BIOS also says the HD is connected to the primary SCSI
> channel and lists it immediatly after the Tape Drive (also connected to the
> primary SCSI channel but with a different ID).
>
> I used 'mkdev .scsi' to see which adapter type SCO uses for the Tape, and
> the type is 'arad'.
> So I run mkdev hd to configure the new HD and used :
>
> type=arad (the same used by the Tape)
> SCSI host adapter = 0 (the same used by the Tape)
> id=5 (the ID set by jumpers)
> lun=0 (an acceptable default, I think)
>
> The O.S. relinks the kernel and requires a reboot.
>
> Next I issued 'mkdev hd' again to create partitions and filesystems on the
> disk, but SCO says that there is an 'Active UNIX partition' on it, while the
> disk I want to format is brand new. So I suppose SCO is giving me
> informations about the old disk and not about the new one. Of course at this
> stage I didn't go on with partitioning and formatting because I strongly
> suspect I would destroy data on the old disk.
Well, as long as you don't touch the partition, the next thing you get
is a divvy table- that would tell you for sure what you are looking at.
Double check /etc/conf/cf.d/mscsi to be sure the right stuff got in
there.
>
> The question is:
>
> 0) Is it acceptable to place 2 SCSI disk on different channels of the same
> controller? (this is certainly unusual but it seems OK to me).
Sure. Or on separate controllers.
>
> 1) Is there any way to probe a SCSI device on ODT 3 so that I can be sure
> SCO (and not only the BIOS) sees the new disk and is able to work on it?
> (sometihng like 'sconf -v', but I've read it's recommended not to use this
> command with SCO pre OSR5.0.5).
It doesn't even exist on ODT 3
>
> 2) Is there a method to force 'mkdev hd' to use a specific hard disk ?
Specifying the parameters as you apparently did should do it-
>
> 3) Assumed the system is a bit messed up about the new disk, is it safe to
> restart from scratch the procedure removing informations about this scsi new
> device using 'mkdev .scsi' (on SCO documentation is told not to remove scsi
> tapes using this command, but what about removing scsi hard disks?).
If there's something screwy with the config, just fix it manually in
/etc/conf/cf/d/mscsi and relink.
--
Tony Lawrence
SCO/Linux Support Tips, How-To's, Tests and more:
Enter your email address for automatic notification of new posts here
(be sure to whitelist 'feedburner.com' if you use spam filtering)
| Views for this page | ||||
|---|---|---|---|---|
| Today | This Week | This Month | This Year | Overall |
| 1 | 7 | 27 | 457 | 3,448 |
/Bofcusm/1276.html copyright 1997-2004 (various authors) All Rights Reserved
Have you tried Searching this site?
Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.

Add your comments