My Oracle Support Banner

CELL-04582: An error was encountered while populating the disk. (Doc ID 2486273.1)

Last updated on JULY 30, 2019

Applies to:

Zero Data Loss Recovery Appliance X7 Hardware - Version All Versions to All Versions [Release All Releases]
Exadata X7-2 Hardware - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.

Symptoms

The following can be observed in ms traces:

MS detected error: CELL-04582: An error was encountered while populating the disk. -- while executing command:  list griddisk attributes name, status, asmModeStatus, asmdeactivationoutcome

Alert history shows the same error:

1_1  2018-12-16T09:37:25+01:00  critical  "DiskController check has detected the following issue(s):     Attribute Name : DiskControllerModel     Required       : Avago MegaRAID SAS 9361-16i     Found          : Unknown     Attribute Name : DiskControllerFirmwareRevision     Required       : 24.19.0-0063     Found          : Unknown"
2_1  2018-12-17T08:40:32+01:00  warning   "An error was encountered while populating the disk. "

In messages files we can find:

Dec 17 03:07:37 <hostname> kernel: [10052912.377615] sd 8:2:5:0: [sdf] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Dec 17 03:07:37 <hostname> kernel: [10052912.377620] sd 8:2:5:0: [sdf] tag#0 CDB: Read(16) 88 00 00 00 00 04 60 69 80 04 00 00 00 01 00 00
Dec 17 03:07:37 <hostname> kernel: [10052912.377623] blk_update_request: I/O error, dev sdf, sector 18797395972
Dec 17 03:07:38 <hostname> kernel: [10052913.262002] sd 8:2:5:0: [sdf] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Dec 17 03:07:38 <hostname> kernel: [10052913.262006] sd 8:2:5:0: [sdf] tag#0 CDB: Read(16) 88 00 00 00 00 04 60 69 80 04 00 00 00 01 00 00
Dec 17 03:07:38 <hostname> kernel: [10052913.262009] blk_update_request: I/O error, dev sdf, sector 18797395972
Dec 17 03:07:38 <hostname> kernel: [10052913.657451] EXT4-fs (md25p1): mounted filesystem with ordered data mode. Opts: (null)
Dec 17 03:07:40 <hostname> kernel: [10052915.597433] sd 8:2:11:0: [sdl] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Dec 17 03:07:40 <hostname> kernel: [10052915.597444] sd 8:2:11:0: [sdl] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 01 00 00 00 00 00 08 00 00
Dec 17 03:07:40 <hostname> kernel: [10052915.597447] blk_update_request: I/O error, dev sdl, sector 65536
Dec 17 03:07:40 <hostname> kernel: [10052915.607789] sd 8:2:10:0: [sdk] tag#0 FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Dec 17 03:07:40 <hostname> kernel: [10052915.607792] sd 8:2:10:0: [sdk] tag#0 CDB: Read(16) 88 00 00 00 00 00 00 01 00 00 00 00 00 08 00 00
Dec 17 03:07:40 <hostname> kernel: [10052915.607794] blk_update_request: I/O error, dev sdk, sector 65536
...
Dec 17 03:08:03 <hostname> kernel: [10052938.461351] megaraid_sas 0000:5e:00.0: Controller in crit error
Dec 17 03:08:03 <hostname> kernel: [10052938.470434] megaraid_sas 0000:5e:00.0: Controller in crit error
Dec 17 03:08:03 <hostname> kernel: [10052938.500488] megaraid_sas 0000:5e:00.0: Controller in crit error
Dec 17 03:08:03 <hostname> kernel: [10052938.510277] megaraid_sas 0000:5e:00.0: Controller in crit error
Dec 17 03:08:05 <hostname> kernel: [10052940.580048] megaraid_sas 0000:5e:00.0: Controller in crit error
Dec 17 03:08:05 <hostname> kernel: [10052940.589061] megaraid_sas 0000:5e:00.0: Controller in crit error
Dec 17 03:08:05 <hostname> kernel: [10052940.619148] megaraid_sas 0000:5e:00.0: Controller in crit error
Dec 17 03:08:05 <hostname> kernel: [10052940.628035] megaraid_sas 0000:5e:00.0: Controller in crit error

In host console:

[   12.001658] megaraid_sas 0000:5e:00.0: Waiting for FW to come to ready state
[   12.002697] megaraid_sas 0000:5e:00.0: FW in FAULT state!!
[   57.723850] megaraid_sas 0000:5e:00.0: FW restarted successfully from megasas_init_fw!
[   87.676052] megaraid_sas 0000:5e:00.0: Waiting for FW to come to ready state
[   87.689723] megaraid_sas 0000:5e:00.0: FW in FAULT state!!

...

2018-12-17 15:23:45 +0100 [ERROR] LSI controller SubOEMId is incorrect. SubOEMId: 
^[[40;31m[ERROR    ]^[[0m Unable to run /opt/MegaRAID/MegaCli/MegaCli64 -LDSetProp DisDskCache -Lall -a0 -nolog
^[[40;31m[ERROR    ]^[[0m Unable to run /opt/MegaRAID/MegaCli/MegaCli64 -LDSetProp WB -Lall -a0 -nolog
^[[40;31m[ERROR    ]^[[0m Unable to run /opt/MegaRAID/MegaCli/MegaCli64 -LDSetProp NoCachedBadBBU -Lall -a0 -nolog
^[[40;31m[ERROR    ]^[[0m Unable to run /opt/MegaRAID/MegaCli/MegaCli64 -LDSetProp NORA -Lall -a0 -nolog
^[[40;31m[ERROR    ]^[[0m Unable to run /opt/MegaRAID/MegaCli/MegaCli64 -LDSetProp Direct -Lall -a0 -nolog
^[[40;31m[ERROR    ]^[[0m Unable to run /opt/MegaRAID/MegaCli/MegaCli64 -AdpBIOS -Enbl -a0 -nolog
^[[40;31m[ERROR    ]^[[0m Unable to run /opt/MegaRAID/MegaCli/MegaCli64 -AdpBIOS -BE -a0 -nolog
^[[40;31m[ERROR    ]^[[0m Unable to run /opt/MegaRAID/MegaCli/MegaCli64 -AdpBIOS -EnblAutoSelectBootLd -a0 -nolog
^[[40;31m[ERROR    ]^[[0m Unable to run /opt/MegaRAID/MegaCli/MegaCli64 -AdpSetProp BgiRate 30 -a0 -nolog
^[[40;31m[ERROR    ]^[[0m Unable to run /opt/MegaRAID/MegaCli/MegaCli64 -AdpSetProp AbortCCOnError 0 -a0 -nolog
^[[40;31m[ERROR    ]^[[0m Failed to initialize LSI SAS MegaRAID disk controller properties. Please contact Oracle support.

...

Server_Model=ORACLE_SERVER_X7-2L
paste: /var/log/exadatatmp/_exa_hwfw_wfwh_axe_14477/_GetSunDiskMakeModelEtc_ctEledoMekaMksiDnuSteG_make: No such file or directory
Initializing firmware update.

[WARNING] Firmware updates were already tried once and likely failed.
[WARNING] To retry the firmware update reboot or try to update the firmware manually.

...

Starting mrdiagd: [  OK  ] [  OK  ]
Logging started to /var/log/cellos/validations.log
Command line is /opt/oracle.cellos/validations/bin/vldrun.pl -quiet -all
Run validation ipmisettings - ^[[1;32mPASSED
^[[0mRun validation misceachboot - ^[[1;32mPASSED
^[[0mRun validation celldstatus - ^[[1;32mPASSED
^[[0mRun validation biosbootorder - ^[[1;32mPASSED
^[[0mRun validation oswatcher - ^[[1;32mPASSED
^[[0mRun validation checkconfigs - ^[[1;31mFAILED
^[[0mCheck log in /var/log/cellos/validations/checkconfigs.log
Run validation saveconfig - ^[[1;36mBACKGROUND RUN
^[[0m2018-12-17 15:26:41 +0100 The each boot completed with FAILURE.

The status of the disks cannot be checked when issuing commands like CellCLI> LIST CELLDISK detail, CellCLI> LIST PHYSICALDISK or MegaCLI commands

The HBA card is detected properly by ILOM:

/System/PCI_Devices/Add-on/Device_11
   Properties:
       part_number = 7332895
       description = Oracle Storage 12 Gb SAS PCIe HBA, 16 port, RAID, internal
       location = PCIE11 (PCIe Slot 11)
       pci_vendor_id = 0x1000
       pci_device_id = 0x00ce
       pci_subvendor_id = 0x1000
       pci_subdevice_id = 0x9371

Also there are no traces of any PCI bus errors visible in ILOM or any FMA faults that could point to PCI problems.

Changes

 n/a

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


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