One partial bad disk can cause the DCS deploy failed with wrong message (Doc ID 2452851.1)

Last updated on APRIL 17, 2023

Applies to:

Symptoms

Fresh deploy failed with error: DCS-10001:Internal error encountered: Fail to discover disk groups
In the agent log we can find:

Number of NVME drive visible are : 4
2018-09-14 18:21:25,524 DEBUG [Discovering DiskGroup] []
c.o.d.c.u.CommonsUtils: Output :
Number of NVME drive visible should be either 2, 5 or 8

[ 4.912662] nvme nvme0: pci function 0000:19:00.0 <<<<<<<<<<< during boot,
it does see all 5 drives 0,1,2,3,4
[ 4.912742] nvme nvme1: pci function 0000:20:00.0
[ 4.912810] nvme nvme2: pci function 0000:8d:00.0
[ 4.912855] nvme nvme3: pci function 0000:94:00.0
[ 4.912898] nvme nvme4: pci function 0000:9b:00.0
[ 4.917341] usb 1-8: New USB device found, idVendor=2a4b, idProduct=0400
[ 4.917344] usb 1-8: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[ 4.917346] usb 1-8: Product: Emulex Pilot4 HighSpeed HUB
[ 4.917348] usb 1-8: Manufacturer: Emulex Communications
[ 4.917350] usb 1-8: SerialNumber: 0xxxxxxxxx
[ 4.918378] hub 1-8:1.0: USB hub found
[ 4.918561] hub 1-8:1.0: 7 ports detected
[ 5.113777] nvme nvme1: Shutdown timeout set to 10 seconds
[ 5.115444] nvme nvme0: Could not set queue count (16390)
<<<<<<<<<<<<<<<<<< then fails to fully initiate nvme0, can't set shutdown
timeout, so it can only use 4
[ 5.115448] nvme nvme0: IO queues not created
[ 5.115457] nvme nvme2: Shutdown timeout set to 10 seconds
[ 5.115460] nvme nvme4: Shutdown timeout set to 10 seconds
[ 5.115469] nvme nvme3: Shutdown timeout set to 10 seconds
[ 5.129903] nvme1n1: p1 p2
[ 5.130815] nvme4n1: p1 p2
[ 5.132829] nvme2n1: p1 p2
[ 5.133424] nvme3n1: p1 p2

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.