Full Device Name Post: 16909

Sponsored Content

Top Forums UNIX for Dummies Questions & Answers Full Device Name Post 16909 by killerserv on Friday 8th of March 2002 07:15:22 AM

03-08-2002

Registered User

Here is the probe output on one of my Server running on a raid SCSI disk:

disk0 /pci@1f,4000/scsi@3/disk@0,0
disk1 /pci@1f,4000/scsi@3/disk@1,0
disk2 /pci@1f,4000/scsi@3/disk@2,0
disk3 /pci@1f,4000/scsi@3/disk@3,0
disk4 /pci@1f,4000/scsi@3/disk@4,0
disk5 /pci@1f,4000/scsi@3/disk@5,0
disk6 /pci@1f,4000/scsi@3/disk@6,0
tape0 /pci@1f,4000/scsi@3,1/tape@4,0
tape1 /pci@1f,4000/scsi@3,1/tape@5,0

it seems that the /scsi@3 is fixed. Its something like what they call as Parameter for your example called as" SCSI ID 3". Does this mean a primary scsi channel ? Yes, probarbaly your system detect it as a primary SCSI.

killerserv

View Public Profile for killerserv

Find all posts by killerserv

4 More Discussions You Might Find Interesting

1. AIX

How to find all device on p570 when need do device firmware upgrade?

I need upgrade firmware for the device of p570, when I go to IBM FIX download website, there are a lot of device of p570 listed. How can I know what device I have on my p570?

2. Red Hat

Unable To Activate Ethernet Network Device in RHEL 5.5 - e100 device eth0 does not seem to be presen

Hi All, Could anyone please help to resolve the below problem. I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error. I spent 2 days for the above and go through with several suggestion found by googling. But no luck. ...

3. Solaris

File system full - not removed: No space left on device

Does anyone have any advise on trying to clean up a full filesystem? I can't rm any files because of the follow: not removed: No space left on device Any help would be very much appreciated.

4. HP-UX

Failed to open tape device /dev/rmt/0mn:Device busy (errno = 16)

Hi, Unable to make tape backup, please help. /opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00 * Creating local directories for configuration files and archive. ======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery. (Mon...

LEARN ABOUT NETBSD

esiop

ESIOP(4)						   BSD Kernel Interfaces Manual 						  ESIOP(4)

NAME

     esiop -- Enhanced Symbios Logic/NCR 53c8xx SCSI driver

SYNOPSIS

     esiop* at pci? dev ? function ?
     options SIOP_SYMLED
     scsibus* at esiop?

DESCRIPTION

     The esiop driver provides improved support over siop(4) for the Symbios Logic/NCR 53x8xx series of SCSI controller chips:

	   -   53c825 and 53c825a (Fast-Wide SCSI)
	   -   53c875 and 53c875j (Ultra-Wide SCSI)
	   -   53c876 (Dual Ultra-Wide SCSI)
	   -   53c885 (Ultra-Wide SCSI and Ethernet)
	   -   53c895 (Ultra2-Wide SCSI)
	   -   53c896 (PCI 64bit, dual Ultra2-Wide SCSI)
	   -   53c1010-33 (PCI 64bit, dual Ultra160 SCSI)
	   -   53c1510d (PCI 64bit, dual Ultra2-wide SCSI)
     Older adapters are supported by the siop(4) driver.

     The SIOP_SYMLED option causes the driver to report SCSI activity on the GPIO pin 1, which is connected to the activity LED on some adapters.
     At this time only the 53c895 based Symbios and Tekram adapters are known to require this.

SEE ALSO

     cd(4), ch(4), intro(4), pci(4), scsi(4), sd(4), siop(4), st(4), uk(4)

HISTORY

     The esiop driver first appeared in NetBSD 1.6.

AUTHORS

     The esiop driver was written by Manuel Bouyer <Manuel.Bouyer@lip6.fr> for NetBSD.

BSD
								  April 23, 2002							       BSD