Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 3 results
    • 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…
    • https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/How_to_determine_E-Series_drive_replacement_details_using_StorageGRID_log_bundle
      This procedure is intended to guide users and technical support engineers with identifying the drive model and enclosure details for a faulty E-Series drive in StorageGRID appliances by using the eos-...This procedure is intended to guide users and technical support engineers with identifying the drive model and enclosure details for a faulty E-Series drive in StorageGRID appliances by using the eos-system-status/status.json log file. The status.json file contains hardware and firmware inventory of the E-Series components in a StorageGRID appliance. In StorageGRID log bundle under: <NODE NAME>/<DATE>/base-os-logs/var/local/eos-system-status/status.json
    • https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/How_to_know_when_data_drives_are_given_up_and_start_reallocating_the_data
      Cluster Alert : blockServiceUnhealthy is right alert to see when the data is reallocated to other drives (Bin Sync) . The alert occurs when the cluster gave up on a data drive. diveFailed : This occur...Cluster Alert : blockServiceUnhealthy is right alert to see when the data is reallocated to other drives (Bin Sync) . The alert occurs when the cluster gave up on a data drive. diveFailed : This occurs when Cluster Master node fails to get drive information from master service on each nodes. nodeOffline : This occurs when Cluster Master node fail to communicate to master service running on each nodes.