HP3000-L Archives

June 2003, Week 2

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Stan Sieler <[log in to unmask]>
Reply To:
Stan Sieler <[log in to unmask]>
Date:
Mon, 9 Jun 2003 15:39:48 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (31 lines)
Re:
>  If device IDs are what worry you, why don't you simply apply patch MPEMX74A
> which title says:
>
>     "IODFAULT Generic Device IDs to support current and future disks"
>
> It brings 3 new device IDs: LVDDISK, HVDDISK and SEDISK which I won't
> explain ;-)

The generic disk device IDs are:

   SEDISK    DISC 4  2 0128 SCSI_DISC_DM           ...
   HVDDISK   DISC 4  2 0128 SCSI_DISK_AND_ARRAY_DM ...
   LVDDISK   DISC 4  2 0128 SCSI_DISK_AND_ARRAY_DM ...
   FCDISK    DISC 4  2 0128 SCSI_DISK_AND_ARRAY_DM ...
   HPDARRAY  DISC 4  2 0128 SCSI_DISK_AND_ARRAY_DM ...

NOTE: if you've got an LVD/LW disk that's converted to Single-Ended
SCSI, you must be sure to configure it as an SEDISK (or some other disk
device ID with a manager of SCSI_DISC_DM and *not* SCSI_DISK_AND_ARRAY_DM).
Otherwise, strange and wonderful problems can occur :)

Stan
--
Stan Sieler
[log in to unmask]
www.allegro.com/sieler/wanted/index.html

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2