06-05-2008
Quote:
Originally Posted by
ppass
Hi all ,
I am trying to install solaris 9 on E2900 that is connect to a 3320 SCSI storage , The issue is that i want to have the SCSI disks(3320) to start with controllers 1 and 2 ( c1t0 ....c2t0) and my 2 local disks on c3 and c4 .
Is there a way that i could accomplish that ...
Thanks in advance .
Cheers
ppass
No, there is no way to acomplish this.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hello all,
How does the Solaris identifies the controller subscript ? ( like c0txdxs0 or c1txdxsx ?? )
I have a unix box ( Ultra 30) running with 2.5.1.
When I connected an external hard disk to the on-board scsi port, it got identified as c0t1dxsx...
(... (1 Reply)
Discussion started by: shibz
1 Replies
2. Solaris
Hello, I'm trying to fix this server System Board (CPU/Memory Unit). The error indicates that its missing 3.3VDC. So far all the fuses and caps have been checked. I new at this type of machine, need help for idea on this system. Thank you in advance.
Vu (0 Replies)
Discussion started by: vhtran
0 Replies
3. Solaris
Hi men,
Have you ever meet this error ?
I install full Sun MC 4.0 packages (+ Add ons) exception of Sun Midrange Platform Administration because i don't know how to configure it
Then all other servers are ok, only E2900 servers have Config reader module error: Data Acquisition error
I... (12 Replies)
Discussion started by: tien86
12 Replies
4. Solaris
Dear Friends,
Sun Fire E2900 crashed. I collected explorer output. core dump files been generated.
There some interesting output files related to crash dumps, that I need some help from you guys to understand.
The file in the explorer output is under /sysconfig/crash it's called:... (5 Replies)
Discussion started by: Sun Fire
5 Replies
5. Shell Programming and Scripting
i have a file staff.txt with contents
tom|25|New York
sims|40|London
neyo|18|Moscow
i want to label the column at the top, my output should be
Names|age|city of birth
tom|25|New York
sims|40|London
neyo|18|Moscow (4 Replies)
Discussion started by: blackzinga80
4 Replies
6. Solaris
Hi,
I am fairly new to Solaris , i have an e2900 server which gives the following output on the console:
Fri Sep 23 08:20:57 noname.example.com lom: /N0/SB0 : F
ailed AR interconnect test. Status = 00060040
Fri Sep 23 08:21:00 noname.example.com lom: AR Intercon
nect test: System board... (7 Replies)
Discussion started by: steve_b72
7 Replies
7. Emergency UNIX and Linux Support
Hi,
I have a scheduled activity to reboot E2900 server. But suddenly I came to know that console ip is not pinging, not connecting via telnet, as it used to connect. I already checked with my onsite person and he changed cable, still no luck. Network person checked his switch, which is showing... (8 Replies)
Discussion started by: solaris_1977
8 Replies
8. Solaris
What would you think is a reasonable useful lifespan for a Sunfire e2900. I'm not referring to it's performance capabilities as much as I'm referring to the hardware's ability to perform reliably. (2 Replies)
Discussion started by: DustinT
2 Replies
9. Solaris
While trying to perform a firmware upgrade on this ilom, the system refused to allow uploading of more than ~900k or so... We tried multiple approaches using FTP and all failed. I decided to start this morning by firing up Apache on another box and trying the same process via HTTP but when I went... (8 Replies)
Discussion started by: DustinT
8 Replies
10. Solaris
several newbie questions:
> how-to find serialnumber for Sun E2900
prtdiag -v does not show chassis serial number
> LOM is not connectable .
Are there any tools to get automatically Serial numbers for HW.
Thanks ! (7 Replies)
Discussion started by: magedfawzy
7 Replies
SCSI(7) Miscellaneous Information Manual SCSI(7)
NAME
SCSI, RAID - Small Computer System Interface
SYNOPSIS
dsk#, tape#_d#, cdrom#
DESCRIPTION
The operating system interfaces to disk and tape devices through the Small Computer System Interface (SCSI). SCSI support is limited to
the Compaq-supplied storage devices and certain third-party devices. To determine which named devices are supported in the default system,
refer to the file /etc/ddr.dbase. For example, the following devices are listed therein: Winchester disks: RZ24L, RZ25, RZ25L, RZ25M,
RZ28M, RZ29B, RZ55, RZ56, RZ58, RZ73, RZ74, RX23, RX26, RX33, IOMEGA ZIP, RAID (Redundant Arrays of Independent Disks) SCSI controllers:
HSZ10, HSZ40, HSZ80 Magnetic tapes: TZ30, TZK11, TLZ06, TKZ09, TKZ60, DLT8000, SDT-10000 Media Changers: TL800, ESL9000 Optical disks:
RRD42, RRD43, RRD44
Vendors can add their own devices to ddr.dbase.
Refer to the Software Product Description (SPD) for a given release of the operating system for more information on processor-specific
device support.
Under the operating system, a SCSI device is referred to by a device identifier that is assigned by the operating system. This name has no
relationship to the descriptive name of the device, although in previous releases of the operating system disks such as the RZ74 mapped to
a system-assigned rz# logical name (where # was the instance number of that disk.
Current logical names for SCSI disks and tapes take the forms specified in the rz(8) and tz(7) reference pages, such as dsk? and tape?.
Refer to the dsfmgr(8) reference page for the naming conventions for disks, tapes and other devices, such as CD-ROM readers. Refer to the
hwmgr(8) reference page for information on determining device names and other device data.
SCSI Device Limits
The number of possible target device IDs is determined by the controller type and method of connection, such as a multibus connection using
fibre channel. Refer to the emx(7) reference page for an example of device addressing.
Device Special Files
The dsfmgr command creates device special files for all the devices that are attached to SCSI controllers. This event occurs automatically
on system startup, and no administrative intervention is required unless an event requires that a device be renamed or its I/O be reas-
signed. In such cases, you can use dsfmgr and hwmgr to manage SCSI devices and their associated device special files without the need to
calculate values from their Bus, Target ID, and LUN data.
RESTRICTIONS
The SCSI device driver is not warrantied to operate with optical disks other than the devices listed in /etc/ddr.dbase/. The SCSI driver
attempts to support, on a best-effort basis, disks and magnetic tapes supplied by other vendors.
The following notes apply to the driver's handling of disks from other vendors: These disks are identified using the following command: #
hwmgr -get attribute -a name This command will return the device name SCSI-WWID (World-Wide Identifier) for all devices on the system,
which includes the model name of the device. You can filter the output by specifying categories of devices. Disks are assigned a default
partition table. The default table can be modified by editing the ccmn_rzxx_sizes[8] entry in the /usr/sys/data/cam_data.c file. The
disklabel command can also be used to modify the partition table on an RZxx disk.
RELATED INFORMATION
atapi_ide(7), dsfmgr(8), emx(7), hwmgr(8), rz(7), tz(7), disklabel(8), ddr.dbase(4) delim off
SCSI(7)