I was working in an environment after a reboot of the server that when I tried to startup the Oracle Clusterware on all belonged nodes, I received the following error:
Disk Group DATA creation failed with the following message: ORA-15018: diskgroup cannot be created ORA-15031: disk specification 'XXXX:XXX40' matches no disks
After some investigation of the logs, I checked the support package ASMLib to verify the status of the disks as below:
[root@techdatabasket grid]# /usr/sbin/oracleasm scandisks Reloading disk partitions: done Cleaning any stale ASM disks... Scanning system for ASM disks... Instantiating disk "XXX40" Unable to instantiate disk "XXX40" [root@techdatabasket grid]#
Then I confirmed that it has not been possible to gather the status of one of the disks. Therefore, I continue to get more additional information to solve the issue as the current ASMlib is installed, and its logs are as below:
[root@techdatabasket grid]# rpm -qa | grep -i oracleasm oracleasmlib-2.0.12-1.el7.x86_64 oracleasm-support-2.1.11-2.el7.x86_64 [root@techdatabasket grid]# tail /var/log/oracleasm /var/log/oracleasm Cleaning any stale ASM disks… Scanning system for ASM disks… oracleasm-read-label: Unable to open device "/dev/fd0": No such device or address oracleasm-read-label: Unable to open device "/dev/sr0": No medium found Disk "XXX40" does not exist or is not instantiated Instantiating disk "XXX40" Tue Apr 26 09:26:47 Cleaning any stale ASM disks… Tue Apr 26 09:26:47 Scanning system for ASM disks… Tue Apr 26 09:26:47 Disk "XXX40" does not exist or is not instantiated Tue Apr 26 09:26:47 Unable to instantiate disk "XXX40"
[root@techdatabasket grid]# oracleasm scandisks Reloading disk partitions: done Cleaning any stale ASM disks... Scanning system for ASM disks... Instantiating disk "XXX40" Unable to instantiate disk "XXX40"
At this point, it was clear to me that I should verify the status of the library and in case restart it. Thus, I found out that the ASMlib was not available after the restart, and then I restarted it and scanned the disks:
root@techdatabasket grid]# oracleasm status Checking if ASM is loaded: no Checking if /dev/oracleasm is mounted: no [root@techdatabasket grid]# oracleasm init Creating /dev/oracleasm mount point: /dev/oracleasm Loading module "oracleasm": oracleasm Configuring "oracleasm" to use device physical block size Mounting ASMlib driver filesystem: /dev/oracleasm [root@techdatabasket grid]# oracleasm status Checking if ASM is loaded: yes Checking if /dev/oracleasm is mounted: yes [root@techdatabasket grid]# oracleasm scandisks Reloading disk partitions: done Cleaning any stale ASM disks... Scanning system for ASM disks... Instantiating disk "XXX40" [root@techdatabasket grid]#
Once the ASMlib was mounted and could recognize all the disks, I started the Oracle Clusterware successfully.
I hope this post helps you!
*The views expressed here are my own and do not represent those of my employer.*
Hello, I’m Bruno — a dual citizen of Brazil and Sweden. I bring a global perspective shaped by experiences in both South America and Europe, with a strong focus on collaboration and innovation across cultures. I am a Computer Scientist, PhD Candidate in Information and Communication Technologies, focusing on Data Science and Artificial Intelligence, and hold dual Master’s degrees in Data Science and Cybersecurity. With over fifteen years of international experience spanning Brazil, Hungary, and Sweden, I have collaborated with global organizations such as IBM, Playtech, and Oracle, as well as contributed remotely to projects across multiple regions. My professional interests include Databases, Cybersecurity, Cloud Computing, Data Science, Data Engineering, Big Data, Artificial Intelligence, Programming, and Software Engineering, all driven by a deep passion for transforming data into strategic business value.