zxmaus: thanks, but these commands are not what I meant. At least according to my findings.
Some of my systems have lots of LUN-s, used for various purposes:
* used as PV-s in some VG-s (mostly rootvg)
* used as GPFS NSD backing devices
* used as Oracle ASM data disks
and some more.
Your commands can show relevant info only for LUNS used as PV disks, but they are misleading on other cases.
Now I can try to run
and see if it can put the device into DEFINED state. When the device is open, I get an error and the device state is kept unchanged. But I would like to find a way to obtain the same info without modifying the system. By the way, how does rmdev find this info?
Hi i need help pls ...
Server type sun fire 3800 I need to install solaris 9 .
When i boot the system i recieve the following :
System Controller 'sunfire3800':
Type 0 for Platform Shell
Type 1 for domain A console
Type 2 for domain B console
Type 3 for... (5 Replies)
I have a real emergency. I have a Sun Fire V240 UltraSparc server and am connected via the Serial Mgmnt Port with a Laptop. I have been building an Oracle database on it for the past couple months, not getting very far along with it , when suddenly, the system had a fatal crash. I've lost the... (2 Replies)
I've a Sun V440 machine, and it's running solaris 10 .. for some reason i need to install a fresh copy of solaris 10. for that i've prepared solaris 10 dvd but surprisingly i found there is no any dvd rom on this machine, so i've took a dvd rom from a V240 machine and inserted on V440.
after... (3 Replies)
Hi guys,
I had a solaris box, with veritas controled disk.
1 disc is showing soft errors, how can I repair the soft errors?
Please help.
Cheers; (4 Replies)
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.
... (0 Replies)
Hi all,
I am not sure whether anyone of you using XIV to copy vg from one host to another. After I managed to copy all the respective vg over to destination vg, and map all vg to destination and when come to varyonvg, I got the following error
0516-510 varyonvg: Physical volume not found for... (2 Replies)
I installed a new hard drive completely blank.
sun blade 150
openboot 4.10.6
message:
Boot device: disk:a File and args:
Bad magic number in disk label
Can't open label package
Evaluating:
Can't open boot device (15 Replies)
Hello Forum,
I'm really in a fix now,
I'm getting this error message now, seems like the boot block is damaged?
When I do probe-all the system freezes...
Can any one guide me as what to do next?
System is Solaris 8 running Open Boot PROM 4
System also does not have a cd/dvd rom drive...
... (17 Replies)
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... (4 Replies)
Discussion started by: anuragr
4 Replies
LEARN ABOUT OSF1
raid
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)