APEX

when you used iscsi for your devices, did you used oracleasm to name that devices? because if you did not oracleasm configure -i oracleasm createdisk you will not see them.. then you can use other ways how to name the devices like udev.. then you can use it in your diskstring and you will see them when you start asmca

I have used the  below steps

yum install oracleasm

yum install kmod-oracleasm

yum install oracleasm-support

rpm -ivh oracleasmlib-2.0.12-1.el7.x86_64.rpm

which oracleasm

returned  /usr/sbin/oracleasm

oracleasm configure -i

oracleasm init

/etc/init.d/oracleasm createdisk OCR /dev/sdb1

/etc/init.d/oracleasm createdisk FRA /dev/sdb2

/etc/init.d/oracleasm createdisk DATA /dev/sdb3

Paste the output of /usr/sbin/oracleasm configure

You may not choosen for ASM SCAN BOOT -- YES.

Regards

Murali

I have used once oracleasm and the /etc/init.d/oracleasm failed to create the disks with the /usr/sbin/oracleasm it worked. Somehow only with one if them it worked.

I would rather use udev (this is my udev file from yesterdays installation) and I think a lot of deployments don't use oracleasm for naming the disks..

[root@rac1 rpm]# cat /etc/udev/rules.d/99-oracle.rules

KERNEL=="sd?1", SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/$parent", RESULT=="1ATA_VBOX_HARDDISK_VB2709a858-60625687", SYMLINK+="asm-disk1", OWNER="grid", GROUP="asmadmin", MODE="0660"

KERNEL=="sd?1", SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/$parent", RESULT=="1ATA_VBOX_HARDDISK_VBf189f74c-ae118012", SYMLINK+="asm-disk2", OWNER="grid", GROUP="asmadmin", MODE="0660"

KERNEL=="sd?1", SUBSYSTEM=="block", PROGRAM=="/usr/lib/udev/scsi_id -g -u -d /dev/$parent", RESULT=="1ATA_VBOX_HARDDISK_VB8e629c0a-30334875", SYMLINK+="asm-disk3", OWNER="grid", GROUP="asmadmin", MODE="0660"

Hi Royce,

The steps look good for me assuming you have set asm scan boot to yes to scan disks every time when you boot the system.

You can verify the setting in the /etc/sysconfig/oracleasm file .

One more thing to look is to verify the ASMlib is coming after iscsi and have the devices attached to the system.

Cheers,

Gleb

No I have turned on

PFA

yes I have  set scan boot to yes

Hi Royce,

The oracleasm scans /proc/partitions and expects devices to be available in /dev. If the device doesn't exist in /dev it will fail to open the device.

RHEL/OL5 does not create dm-xx devices in /dev by default.

Comment out the following line in file /etc/udev/rules.d/50-udev.rules.

In latest versions of RHEL/OL5, the udev rule has been moved to file /etc/udev/rules.d/90-dm.rules.

#KERNEL=="dm-[0-9]*", ACTION=="add", OPTIONS+="ignore_device"

Regards,

Alok

Hi,

Have you tried using udev rules ? always ASMLib is my first option to mark asm disks but I have faced issues with it, so if you are getting errors that has no sense try udev rules to mark asm disks

Check this out:

Best regards.