Search

Unexpected reboot with reason REBOOT_VKI_CE_PANIC
https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/Unexpected_controller_on_NetApp_E-Series_28xx__Controller_version_11.50.2
Applies to NetApp E-Series Issue AutoSupport case gets opened with the following message: E-Series Notification from <hostname> (Core dump has been captured) INFO
core.BVScript-x.xxxxxx.gz produced during Bulk Volume operations
https://kb.netapp.com/on-prem/solidfire/hardware_Kbs/core.BVScript-x.xxxxxx.gz_produced_during_Bulk_Volume_operations
Applies to NetApp Element Software Element OS 12.x Issue core.BVScript-x.xxxxxx.gz produced during Bulk Volume operations Example: SolidFire Alert from node_name cluster_id (Other P3) Core nodeID=2, p...Applies to NetApp Element Software Element OS 12.x Issue core.BVScript-x.xxxxxx.gz produced during Bulk Volume operations Example: SolidFire Alert from node_name cluster_id (Other P3) Core nodeID=2, path=/sf/core.BVScript-13.71764.gz, modifiedTime=2023-03-03T14:54:10Z
E-Series EF600 unexpected reboot due to ancient IO with reason 0x429c002
https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/E-Series_EF600_unexpected_reboot_due_to_ancient_IO_with_reason_0x429c002
Applies to E-Series EF600 Santricity OS version is earlier than 11.81 Issue Controller experienced unexpected reboot for ancient I/O. This triggered a core dump collection. ---- Log Entry #18 (Core 1)...Applies to E-Series EF600 Santricity OS version is earlier than 11.81 Issue Controller experienced unexpected reboot for ancient I/O. This triggered a core dump collection. ---- Log Entry #18 (Core 1) Jan-08-2024 10:30:59 AM ---- Reboot due to ancient IO, scsiOp=0x1464bedc0 poolId=0 opCode=28 age=330000ms 2024-01-08 08:57:17.131785 rebootReason 0x429c002, rebootReasonExtra 0x0
E-Series controller hits panic while deleting initiator entry for the host
https://kb.netapp.com/on-prem/E-Series/Management-Apps-KBs/E-Series_Controller_hits_panic_while_deleting_initiator_entry_for_the_host
E-Series The controller resets in the MAJOR-EVENT-LOG: B:5/21/20, 8:54:20 PM (20:54:20) 886 4010 Controller reset - Shelf 99, Bay B ----> Reboot Reason : REBOOT_VKI_SIGSEGV The Core dump has been capt...E-Series The controller resets in the MAJOR-EVENT-LOG: B:5/21/20, 8:54:20 PM (20:54:20) 886 4010 Controller reset - Shelf 99, Bay B ----> Reboot Reason : REBOOT_VKI_SIGSEGV The Core dump has been captured as the controller rebooted in the excLogShow of the STATE-CAPTURE-DATA: ---- Log Entry #0 (Core 0) Apr-30-2020 02:26:31 AM ---- WARNING: Reset by alternate controller ---- Log Entry #1 (Core 0) May-21-2020 02:55:30 PM ---- 2020-05-21 20:53:30.227168 SIGSEGV Received
How to configure A700 systems with X9170A core dump device
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/How_to_configure_A700_systems_with_X9170A_core_dump_device
Starting with ONTAP 9.8, support for the X9170A core dump device module was introduced for the AFF A700 and ASA AFF A700 models when supporting NVMe storage shelves (NS224). By default, when AFF A700 ...Starting with ONTAP 9.8, support for the X9170A core dump device module was introduced for the AFF A700 and ASA AFF A700 models when supporting NVMe storage shelves (NS224). By default, when AFF A700 and ASA AFF A700 models are ordered with ONTAP 9.8 or later in NetApp's Configure, Price, Quote (CPQ) application, the X9170A core dump device module is included and installed in slot 6-1 of each controller.
E-Series controller panic with ancient IO and is stuck in AVT Pending
https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/E-Series_controller_panic_with_ancient_IO_and_is_stuck_in_AVT_Pending
Applies to NetApp E-Series SANtricity OS 11.60.1R1 or higher Issue Controller experienced unexpected reboot for ancient I/O and triggered a core dump collection.
E-Series reboot with "Panic in DriveLogicalUnit::unmapped" after performing drive replacement
https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/E_Series_reboot_with_Panic_in_DriveLogicalUnit__unmapped_after_performing_drive_replacement
Backtrace of the crashed thread: #0 0x00007f710927fff7 in raise () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x00007f7109772d0f in vkiPanic () from /raid/lib/libeos-Syste...Backtrace of the crashed thread: #0 0x00007f710927fff7 in raise () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x00007f7109772d0f in vkiPanic () from /raid/lib/libeos-System.so No symbol table info available. #2 0x00007f7109772e5a in _vkiReboot () from /raid/lib/libeos-System.so No symbol table info available. #3 0x00007f710976ecd9 in _vkiLogMsg () from /raid/lib/libeos-System.so No symbol table info available. #4 0x00007f710976f123 in _vkiCmnErr () from /raid/lib/li…
E-Series controller "Assertion failed" reset due to FC chip fault
https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/E_Series_controller_Assertion_failed_reset_due_to_FC_chip_fault
Fibre Channel (FC) Host connectivity With active I/O on a Fibre Channel host interface, in the rare event that an I/O completion coincides with a chip fault, a controller reboot generating a core dump...Fibre Channel (FC) Host connectivity With active I/O on a Fibre Channel host interface, in the rare event that an I/O completion coincides with a chip fault, a controller reboot generating a core dump may occur. The following assertion can be found in excLogShow: 10/08/20-11:09:01 (raidSched1): ASSERT: Assertion failed: state == ExchOwnedByChip, file qlfcLLogin.cc, line 349 Assertion failed: state == ExchOwnedByChip, file qlfcLLogin.cc, line 349
E-Series reboot with "Panic Reason: rebootReason 0x42e8001, rebootReasonExtra 0x0" while performing volume expansion
https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/E_Series_reboot_with_Panic_Reason__rebootReason_0x42e8001_rebootReasonExtra_0x0_while_performing_volume_expansion
Thread 53 (Thread 0x7ff5b2506c00 (LWP 3209)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x00007ff5b23f753e in futex (val3=0, uaddr2=0x0, timeout=<optimized out>, val=0, futex_...Thread 53 (Thread 0x7ff5b2506c00 (LWP 3209)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x00007ff5b23f753e in futex (val3=0, uaddr2=0x0, timeout=<optimized out>, val=0, futex_op=128, uaddr=0x24b2b2370) at vkiSync.c:150 #2 _vkiCSemTake (semId=9851052912, tickTimeout=1250) at vkiSync.c:568 #3 0x00007ff59a721d5c in ras::RemotePeerManager::sendRemoteMessage (this=0x145c05670, response=0x7ff5b2505a80, target=0x145e998b0, targetId=10, msg=<optimized out>, msgLength=<optimized…
E-Series Controller reboots due to timeouts to alternate controller
https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/E-Series_Controller_reboots_due_to_timeouts_to_alternate_controller
Applies to SANtricity OS 11.50.3R1P1 and earlier E2800 / EF280 E5700 / EF570 EF600 Issue One of the controllers reboots with a reboot reason of 0x42e8001 with an reboot reason extra of 0x1 . The contr...Applies to SANtricity OS 11.50.3R1P1 and earlier E2800 / EF280 E5700 / EF570 EF600 Issue One of the controllers reboots with a reboot reason of 0x42e8001 with an reboot reason extra of 0x1 . The controller does recover and boots back up but generates a Controller Health Image/ Core dump.
Core dump triggered WARNING: Restart by watchdog time out on EOS domain
https://kb.netapp.com/on-prem/E-Series/Management-Apps-KBs/Core_dump_triggered_WARNING__Restart_by_watchdog_time_out_on_EOS_domain
PCI SERR Exception PCI-E Root Port to Host Card (Unit 6) VID 0x8086 DID 0x6f02 ---- Log Entry #2 (Core 0) Nov-21-2019 07:08:41 PM ---- Processor Global Fatal Error: 40 PCI SERR Exception PCI-E Root Po...PCI SERR Exception PCI-E Root Port to Host Card (Unit 6) VID 0x8086 DID 0x6f02 ---- Log Entry #2 (Core 0) Nov-21-2019 07:08:41 PM ---- Processor Global Fatal Error: 40 PCI SERR Exception PCI-E Root Port to Host Card (Unit 6) VID 0x8086 DID 0x6f02 B0: ---- Log Entry #3 (Core 0) Nov-21-2019 07:59:33 PM ---- Processor Global Fatal Error: 40 PCI SERR Exception PCI-E Root Port to Host Card (Unit 6) VID 0x8086 DID 0x6f02 B0:D1:F0 PCI Status = 0 ---- Log Entry #4 (Core 0) Jun-03-2020 12:41:10 PM ----