Sponsored Content
Operating Systems Linux Red Hat Udev Rule TAG for identifying a local sas disk, non-scsi, non-fiber, non-iscsi Post 302977540 by mrmurdock on Tuesday 19th of July 2016 02:13:35 PM
Old 07-19-2016
Udev Rule TAG for identifying a local sas disk, non-scsi, non-fiber, non-iscsi

I need to add a VMware virtual disk to the 99-oracle-asmdevices.rules file but the OS is not assigning a WWID to the disk. It has been fdisk'd and a single partition created.
What TAG inside the file needs to be added? the Program scsi-id does not work for some reason. latest patches has been installed from redhat.
I have to use udisks --show-info /dev/sdb (yes thats the device).
I have attached the output from the above command.
here is my 99-oracle-asmdevices file.

Code:
 KERNEL=="dm-*",ACTION=="add", ENV{DM_NAME}=="/dev/sdb",OWNER="oracle",GROUP="dba",MODE="0660"

 

10 More Discussions You Might Find Interesting

1. AIX

how to use a scsi disk??

hi, i removed a FC disk (it has a single VG on it) from a AIX 6.1 server and exported it to another AIX server. after doing cfgmgr -v .. the disk showed up in the second AIX 6.1 server. Now how can i see the data which is on the disk from the second AIX server. (5 Replies)
Discussion started by: navadeep
5 Replies

2. UNIX for Advanced & Expert Users

Identifying generic scsi disk on AIX 5.3

I was wondering if anyone knew of any tools that would identify generic scsi disks on servers running AIX 5.3? Going through diag into the hot plugs does not work. I know it used to for 4.3 on some servers I managed with generic scsi but for some reason I either dont the option to choose a disk... (2 Replies)
Discussion started by: plcj58
2 Replies

3. AIX

mkvg on iscsi disk won't work (6.1)

Hi All, Recently I'm taking my first steps in AIX, initially with no real issues. Until now, off course... I hooked up a couple of iSCSI disks to the system, with a RHEL5 machine running tgt on the other side. When running cfgmgr after initial configuration, I got an error: # cfgmgr -l... (4 Replies)
Discussion started by: mr.aart
4 Replies

4. Solaris

iSCSI disk showing incorrect size

Hi, I have a very frustrating issue! I hope you guys can assist When a disk is presented out the iSCSI target display a lower disk capacity SOLARIS VERSION is SOLARIS 10 05/09 Kernel Patch 139555-31 ISCSI Patch 119090-31, 141878-11 Unix Commands To discover Target bash-3.00# i... (0 Replies)
Discussion started by: capitalexall
0 Replies

5. UNIX for Dummies Questions & Answers

find physical disk type : SAS / SATA

Hi, Is there an easy way to find the disk-type from the command line or with another api ? sdparm works for SAS but not for SATA, hdparm works for SATA but not SAS. Thanks (1 Reply)
Discussion started by: coderd
1 Replies

6. Red Hat

set device mode permanently with udev rule

On a test server running CentOS 6, I try to permanently set the owner, group and mode of disk devices for use with a DB2 database. For this I created an udev rule file /etc/udev/rules.d/99-db2.rules: KERNEL=="sdb*", OWNER="db2usrl1", GROUP="db2adml1", MODE="0600" After a reboot, the owner and... (4 Replies)
Discussion started by: hergp
4 Replies

7. Linux

udev rule + script for setting webcam's mic as audio input

Hello, whenever I plugin my webcam, I want to use its microphone instead of the one integrated in my laptop. I therefore created a udev rule: SUBSYSTEM=="usb", ATTR{idVendor}=="046d", ATTR{idProduct}=="0807", RUN+="/usr/local/bin/webcammic"This rule works, I've tested it with a testscript (the... (0 Replies)
Discussion started by: MojoDodo
0 Replies

8. Solaris

Iscsi shared disk - same naming across server

Hi all, Is there anyway i can control the naming of the disk device ? I have added an iscsi disk on server1 using iscsiadm , devfsadm and it is now showing as /dev/dsk/c2t0d0 in node1 However, i am worried that the same disk will appear as /dev/dsk/cXtXd0 in node2 This iscsi disk(lun)... (0 Replies)
Discussion started by: javanoob
0 Replies

9. AIX

Replaced pdisk not showing up in SAS Disk Array Configuration

OSLevel: 5300-10-02-0943 System Model: IBM,8203-E4A Power 6 == Hi! I replaced a failed pdisk in the raid enclosure as follows, - rmdev -l 'pdisk18' '-d' - Replaced it. - cfgmgr (detected) - I can see the new drive, with the correct serial # lscfg -v -l pdisk18 pdisk18... (2 Replies)
Discussion started by: estrar
2 Replies

10. AIX

Power machine 720 SAS disk

Hello, I would like to check how many SAS disks and its size per disk for the whole power system. As per my understanding, if we assign the SAS controller to LPAR, then we can see the disk in lpar smitty command. How can we check from the Power machine(physical ones) as well? I think the... (5 Replies)
Discussion started by: Phat
5 Replies
fmthard(1M)															       fmthard(1M)

NAME
fmthard - populate label on hard disks SYNOPSIS
SPARC fmthard -d data | -n volume_name | -s datafile [-i] /dev/rdsk/c? [t?] d?s2 fmthard -d data | -n volume_name | -s datafile [-i] /dev/rdsk/c? [t?] d?s2 The fmthard command updates the VTOC (Volume Table of Contents) on hard disks and, on systems, adds boot information to the Solaris fdisk partition. One or more of the options -s datafile, -d data, or -n volume_name must be used to request modifications to the disk label. To print disk label contents, see prtvtoc(1M). The /dev/rdsk/c?[t?]d?s2 file must be the character special file of the device where the new label is to be installed. On systems, fdisk(1M) must be run on the drive before fmthard. If you are using an system, note that the term ``partition'' in this page refers to slices within the fdisk partition on machines. Do not confuse the partitions created by fmthard with the partitions created by fdisk. The following options are supported: -d data The data argument of this option is a string representing the information for a particular partition in the current VTOC. The string must be of the format part:tag:flag:start:size where part is the partition number, tag is the ID TAG of the partition, flag is the set of permission flags, start is the starting sector number of the partition, and size is the number of sectors in the partition. See the description of the datafile below for more information on these fields. -i This option allows the command to create the desired VTOC table, but prints the information to standard output instead of modifying the VTOC on the disk. -n volume_name This option is used to give the disk a volume_name up to 8 characters long. -s datafile This option is used to populate the VTOC according to a datafile created by the user. If the datafile is "-", fmthard reads from standard input. The datafile format is described below. This option causes all of the disk par- tition timestamp fields to be set to zero. Every VTOC generated by fmthard will also have partition 2, by convention, that corresponds to the whole disk. If the input in datafile does not specify an entry for partition 2, a default partition 2 entry will be created auto- matically in VTOC with the tag V_BACKUP and size equal to the full size of the disk. The datafile contains one specification line for each partition, starting with partition 0. Each line is delimited by a new-line character ( ). If the first character of a line is an asterisk (*), the line is treated as a com- ment. Each line is composed of entries that are position-dependent, separated by "white space" and having the fol- lowing format: partition tag flag starting_sector size_in_sectors where the entries have the following values: partition The partition number. Currently, for Solaris SPARC, a disk can have up to 8 partitions, 0-7. Even though the partition field has 4 bits, only 3 bits are currently used. For , all 4 bits are used to allow slices 0-15. Each Solaris fdisk partition can have up to 16 slices. tag The partition tag: a decimal number. The following are reserved codes: 0 (V_UNASSIGNED), 1 (V_BOOT), 2 (V_ROOT), 3 (V_SWAP), 4 (V_USR), 5 (V_BACKUP), 6 (V_STAND), 7 (V_VAR), and 8 (V_HOME). flag The flag allows a partition to be flagged as unmountable or read only, the masks being: V_UNMNT 0x01, and V_RONLY 0x10. For mountable partitions use 0x00. starting_sector The sector number (decimal) on which the partition starts. size_in_sectors The number (decimal) of sectors occupied by the partition. You can save the output of a prtvtoc command to a file, edit the file, and use it as the datafile argument to the -s option. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ uname(1), format(1M), prtvtoc(1M), attributes(5) Only fdisk(1M), installgrub(1M) Special care should be exercised when overwriting an existing VTOC, as incorrect entries could result in current data being inaccessible. As a precaution, save the old VTOC. For disks under one terabyte, fmthard cannot write a VTOC on an unlabeled disk. Use format(1M) for this purpose. 11 Apr 2005 fmthard(1M)
All times are GMT -4. The time now is 11:10 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy