"device_block" and "device_unblock" from disks in storage tray DE3-24C, ASM disks dropping
(Doc ID 2667269.1)
Last updated on AUGUST 02, 2022
Applies to:
Oracle Database Appliance X8-2HA Hardware - Version All Versions and laterInformation in this document applies to any platform.
Symptoms
Shared disks become unavailable for a short period of time, which can cause them to be dropped by ASM.
Tell-tale signs are device_block and device_unblock in the messages log:
Mar 19 21:30:03 kernel: sd 1:0:13:0: device_block, handle(0x0017)
Mar 19 21:30:03 kernel: sd 1:0:14:0: device_block, handle(0x0018)
Mar 19 21:30:03 kernel: sd 1:0:15:0: device_block, handle(0x0019)
Mar 19 21:30:03 kernel: sd 1:0:16:0: device_block, handle(0x001a)
Mar 19 21:30:03 kernel: sd 1:0:17:0: device_block, handle(0x001b)
Mar 19 21:30:03 kernel: mpt3sas_cm0: log_info(0x31110e05): originator(PL), code(0x11), sub_code(0x0e05)
Mar 19 21:30:03 kernel: mpt3sas_cm0: log_info(0x31110e05): originator(PL), code(0x11), sub_code(0x0e05)
Mar 19 21:30:03 kernel: mpt3sas_cm0: log_info(0x31110e05): originator(PL), code(0x11), sub_code(0x0e05)
Mar 19 21:30:04 kernel: sd 1:0:0:0: device_unblock and setting to running, handle(0x000a)
Mar 19 21:30:04 kernel: sd 1:0:1:0: device_unblock and setting to running, handle(0x000b)
Mar 19 21:30:04 kernel: sd 1:0:2:0: device_unblock and setting to running, handle(0x000c)
Mar 19 21:30:04 kernel: sd 1:0:3:0: device_unblock and setting to running, handle(0x000d)
Mar 19 21:30:04 kernel: sd 1:0:4:0: device_unblock and setting to running, handle(0x000e)
Mar 19 21:30:04 kernel: sd 1:0:5:0: device_unblock and setting to running, handle(0x000f)
Mar 19 21:30:04 kernel: sd 1:0:6:0: device_unblock and setting to running, handle(0x0010)
Mar 19 21:30:03 kernel: sd 1:0:14:0: device_block, handle(0x0018)
Mar 19 21:30:03 kernel: sd 1:0:15:0: device_block, handle(0x0019)
Mar 19 21:30:03 kernel: sd 1:0:16:0: device_block, handle(0x001a)
Mar 19 21:30:03 kernel: sd 1:0:17:0: device_block, handle(0x001b)
Mar 19 21:30:03 kernel: mpt3sas_cm0: log_info(0x31110e05): originator(PL), code(0x11), sub_code(0x0e05)
Mar 19 21:30:03 kernel: mpt3sas_cm0: log_info(0x31110e05): originator(PL), code(0x11), sub_code(0x0e05)
Mar 19 21:30:03 kernel: mpt3sas_cm0: log_info(0x31110e05): originator(PL), code(0x11), sub_code(0x0e05)
Mar 19 21:30:04 kernel: sd 1:0:0:0: device_unblock and setting to running, handle(0x000a)
Mar 19 21:30:04 kernel: sd 1:0:1:0: device_unblock and setting to running, handle(0x000b)
Mar 19 21:30:04 kernel: sd 1:0:2:0: device_unblock and setting to running, handle(0x000c)
Mar 19 21:30:04 kernel: sd 1:0:3:0: device_unblock and setting to running, handle(0x000d)
Mar 19 21:30:04 kernel: sd 1:0:4:0: device_unblock and setting to running, handle(0x000e)
Mar 19 21:30:04 kernel: sd 1:0:5:0: device_unblock and setting to running, handle(0x000f)
Mar 19 21:30:04 kernel: sd 1:0:6:0: device_unblock and setting to running, handle(0x0010)
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 |
| Cause |
| Solution |
| References |