login as: manage Keyboard-interactive authentication prompts from server: | Password: End of keyboard-interactive prompts from server HPE MSA Storage MSA 2050 SAN System Name: Uninitialized Name System Location: Uninitialized Location Version: VL270R001-01 # show unwritable-cache Unwritable System Cache ----------------------- Percent of unwritable cache in controller A: 0 Percent of unwritable cache in controller B: 0 Success: Command completed successfully. (2026-03-15 15:44:40) # show disk-groups Name Size Free Pool Tier % of Pool Own RAID Disks Status Current Job Job% Sec Fmt Health Reason Action ------------------------------------------------------------------------------- diskgroup1 3996.6GB 0B N/A 100 B RAID1 2 QTOF 512e Fault The disk group is quarantined. - Look for events in the event log related to quarantine (172, 485, or 590) an d follow the recommended actions for those events. ------------------------------------------------------------------------------- Success: Command completed successfully. (2026-03-15 15:44:49) # show volumes Pool Name Total Size Alloc Size Type Large Virtual Extents Health Reason Action ---------------------------------------------------------------------------- Vdisk 3993.9GB 3993.9GB base Disabled OK ---------------------------------------------------------------------------- Success: Command completed successfully. (2026-03-15 15:45:10) # show controllers Controllers ----------- Controller ID: A Serial Number: Hardware Version: CPLD Version: MAC Address: 00:00:00:00:00:00 WWNN: 208000C0FF44597D IP Address: 172.16.50.5 IP Subnet Mask: 255.255.255.0 IP Gateway: 172.16.50.253 Disks: 2 Virtual Pools: 0 Disk Groups: 1 System Cache Memory (MB): 8192 Host Ports: 4 Disk Channels: 2 Disk Bus Type: SAS Status: Down Failed Over to This Controller: No Fail Over Reason: Not applicable Multi-core: Disabled Health: Fault Health Reason: The controller is not operat ional. Health Recommendation: - Restart the Storage Controller in this controller modul e, unless it is performing an operation where it is normal for it to be shut dow n, such as firmware update. Position: Top Phy Isolation: Enabled Controller Redundancy Mode: Failed Over Controller Redundancy Status: Operational but not redundant Controllers ----------- Controller ID: B Serial Number: 7CE912M472 Hardware Version: 1.0 CPLD Version: 1.9 MAC Address: 00:C0:FF:44:57:6F WWNN: 208000C0FF44597D IP Address: 172.16.50.4 IP Subnet Mask: 255.255.255.0 IP Gateway: 172.16.50.253 Disks: 2 Virtual Pools: 0 Disk Groups: 1 System Cache Memory (MB): 8192 Host Ports: 4 Disk Channels: 2 Disk Bus Type: SAS Status: Operational Failed Over to This Controller: Yes Fail Over Reason: Non volatile device flush or restore failure Multi-core: Disabled Health: OK Health Reason: Health Recommendation: Position: Bottom Phy Isolation: Enabled Controller Redundancy Mode: Failed Over Controller Redundancy Status: Operational but not redundant Success: Command completed successfully. (2026-03-15 15:45:20) # restart sc a y While a Storage Controller is restarting, communication will temporarily be lost with the corresponding Management Controller, and also may cause a temporary loss of data availability. Do you want to continue? (y/n) y Success: Command completed successfully. (2026-03-15 15:48:22) # Disk Groups: 1 System Cache Memory (MB): 8192 Error: The command was not recognized. (2026-03-15 15:48:25) # show disk-groups detail Disk Group ---------- Name: diskgroup1 Blocksize: 512 Size: 3996.6GB Free: 0B Pool: Tier: N/A % of Pool: 100 Current Owner: B Preferred Owner: A RAID: RAID1 Disks: 2 Spares: 0 Chunk Size: N/A Status: QTOF Current Job: Current Job Completion: Serial Number: 00c0ff44588b00009a63b55d00000000 Active Drive Spin Down Enable: Disabled Active Drive Spin Down Delay: 0 Sector Format: 512e Health: Fault Health Reason: The disk group is quarantined. Health Recommendation: - Look for events in the event log related to quarantine (172, 485, or 590) and follow the recommended actions for those events. Success: Command completed successfully. (2026-03-15 15:48:39) # show disk-groups Name Size Free Pool Tier % of Pool Own RAID Disks Status Current Job Job% Sec Fmt Health Reason Action ------------------------------------------------------------------------------------------------------------------------------------ diskgroup1 3996.6GB 0B N/A 100 B RAID1 2 QTOF 512e Fault The disk group is quarantined. - Look for events in the event log related to quarantine (172, 485, or 590) and follow the recommended actions for those events. ------------------------------------------------------------------------------------------------------------------------------------ Success: Command completed successfully. (2026-03-15 15:48:55) # show events 2026-03-15 15:48:47 [310] #B921: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 15:48:46 [310] #B920: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 15:48:46 [211] #B919: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 0, device PHYs: 3) 2026-03-15 15:48:44 [084] #B918: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Non volatile device flush or restore failure) 2026-03-15 15:47:57 [310] #B917: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 15:47:57 [211] #B916: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 1, device PHYs: 3) 2026-03-15 15:47:03 [081] #B915: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Kill was released (that is, the partner controller was allowed to boot up), unknown reason. 2026-03-15 13:33:12 [314] #B914: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR There is a problem with a FRU. (FRU type: Controller module A, enclosure: 1, product ID: 876127-001, SN: 7CE913M204, version: N/A, related event serial number: B913, related event code: 313) 2026-03-15 13:33:12 [313] #B913: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR RAID controller A failed, reason Non volatile device flush or restore failure. Product ID 876127-001, S/N 7CE913M204) 2026-03-15 13:32:15 [310] #B912: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 13:32:13 [310] #B911: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a resc2026-03-15 13:32:13 [211] #B910: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 0, device PHYs: 3) 2026-03-15 13:32:12 [084] #B909: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Non volatile device flush or restore failure) 2026-03-15 13:31:24 [310] #B908: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 13:31:24 [211] #B907: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 1, device PHYs: 3) 2026-03-15 13:30:30 [081] #B906: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Kill was released (that is, the partner controller was allowed to boot up), automatic. 2026-03-15 13:28:32 [310] #B905: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 13:28:31 [310] #B904: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 13:28:31 [211] #B903: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 0, device PHYs: 3) 2026-03-15 13:28:29 [084] #B902: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Non volatile device flush or restore failure) 2026-03-15 13:27:42 [310] #B901: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 13:27:42 [211] #B900: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 1, device PHYs: 3) 2026-03-15 13:26:48 [081] #B899: MScontroller was allowed to boot up), user requested. 2026-03-15 12:19:44 [314] #B898: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR There is a problem with a FRU. (FRU type: Controller module A, enclosure: 1, product ID: 876127-001, SN: 7CE913M204, version: N/A, related event serial number: B897, related event code: 313) 2026-03-15 12:19:44 [313] #B897: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR RAID controller A failed, reason Non volatile device flush or restore failure. Product ID 876127-001, S/N 7CE913M204) 2026-03-15 12:17:46 [310] #B896: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 12:17:45 [310] #B895: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 12:17:45 [211] #B894: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 0, device PHYs: 3) 2026-03-15 12:17:43 [084] #B893: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Non volatile device flush or restore failure) 2026-03-15 12:16:56 [310] #B892: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 12:16:56 [211] #B891: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 1, device PHYs: 3) 2026-03-15 12:16:02 [081] #B890: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Kill was released (that is, the partner controller was allowed to boot up), unknown reason. 2026-03-15 12:14:08 [503] #B889: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Intelligent BackEnd Error Monitor (IBEEM) has discovered that continuous errors are being reported for the indicated PHY. (channel: 1, enclosure: 1, PHY: 36, type: Egress) 2026-03-15 12:14:08 [503] #B888: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Intelligent BackEnd Error Monitor (IBEEM) has discovered that continuous errors are being reported for the indicated PHY. (channel: 1, enclosure: 1, PHY: 35, type: Egress) 2026-03-15 12:14:08 [503] #B887: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Intelligent BackEnd Error Monitor (IBEEM) has discovered that continuous errors are being reported for the indicated PHY. (channel: 1, enclosure: 1, PHY: 30, type: Egress) 2026-03-15 12:14:08 [503] #B886: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Intelligent BackEnd Error Monitor (IBEEM) has discovered that continuous errors are being reported for the indicated PHY. (channel: 1, enclosure: 1, PHY: 29, type: Egress) 2026-03-15 12:09:55 [314] #B885: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR There is a problem with a FRU. (FRU type: Controller module A, enclosure: 1, product ID: 876127-001, SN: 7CE913M204, version: N/A, related event serial number: B884, related event code: 313) 2026-03-15 12:09:55 [313] #B884: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR RAID controller A failed, reason Non volatile device flush or restore failure. Product ID 876127-001, S/N 7CE913M204) 2026-03-15 12:08:57 [310] #B883: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 12:08:56 [310] #B882: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 12:08:56 [211] #B881: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 0, device PHYs: 3) 2026-03-15 12:08:55 [084] #B880: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Non volatile device flush or restore failure) 2026-03-15 12:08:08 [310] #B879: MSe data was completed following a rescan. 2026-03-15 12:08:08 [211] #B878: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 1, device PHYs: 3) 2026-03-15 12:07:12 [081] #B877: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Kill was released (that is, the partner controller was allowed to boot up), unknown reason. 2026-03-15 11:50:19 [310] #B876: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 11:50:19 [019] #B875: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL A rescan-bus operation was done. (number of disks that were found: 2, number of enclosures that were found: 1) (rescan reason: initiated by a user, rescan reason code: 0) 2026-03-15 11:50:18 [211] #B874: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 3, expanders: 0, native levels: 0, partner levels: 0, device PHYs: 0) 2026-03-15 11:50:15 [211] #B873: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 0, number of elements: 51, expanders: 1, native levels: 1, partner levels: 0, device PHYs: 3) 2026-03-15 11:50:12 [114] #B872: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Disk link down. (channel: 1) 2026-03-15 11:50:12 [114] #B871: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Disk link down. (channel: 0) 2026-03-15 11:47:46 [314] #B870: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR There is a problem with a FRU. (FRU type: Controller module A, enclosure: 1, product ID: 876127-001, SN: 7CE913M204, version: N/A, related event serial number: B869, related event code: 313) 2026-03-15 11:47:46 [313] #B869: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR RAID controller A failed, reason Non volatile device flush or restore failure. Product ID 876127-001, S/N 7CE913M204) 2026-03-15 11:46:49 [310] #B868: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 11:46:47 [310] #B867: MSe data was completed following a rescan. 2026-03-15 11:46:47 [211] #B866: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 0, device PHYs: 3) 2026-03-15 11:46:45 [084] #B865: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Non volatile device flush or restore failure) 2026-03-15 11:45:59 [310] #B864: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 11:45:58 [309] #B863: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The startup IP address information was obtained from flash rather than the FRU-ID SEEPROM. 2026-03-15 11:45:58 [211] #B862: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 1, device PHYs: 3) 2026-03-15 11:45:04 [081] #B861: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Kill was released (that is, the partner controller was allowed to boot up), automatic. 2026-03-15 11:44:45 [181] #B860: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-15 11:44:45 [139] #B859: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller booted up. MC firmware version: VXM270R001-01 2026-03-15 11:44:45 [363] #B858: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Firmware versions match those in the firmware bundle. (controller: B) 2026-03-15 11:44:33 [141] #B857: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller IP address changed. (new IP address: IP: 172.16.50.4/255.255.255.0/172.16.50.253) 2026-03-15 11:44:33 [181] #B856: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-15 11:44:32 [175] #B855: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is up for controller B. 2026-03-15 11:44:32 [181] #B854: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-15 11:44:06 [111] #B853: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 2, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-15 11:44:06 [111] #B852: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 1, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-15 11:44:05 [310] #B851: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 11:44:04 [181] #B850: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-15 11:44:03 [310] #B849: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 11:44:03 [509] #B848: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR The metadata volume for a virtual pool went offline. Volume mappings and persistent reservations are inaccessible or lost. (pool: A, SN: 00c0ff44588b00009c63b55d01000000) 2026-03-15 11:44:02 [191] #B847: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor good. 2026-03-15 11:44:02 [202] #B846: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through: Write-Back cache was re-enabled. 2026-03-15 11:44:00 [077] #B845: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Write-back cache was initialized for controller A. Write-back data was found. 2026-03-15 11:43:58 [077] #B844: MStroller B. Write-back data was found. 2026-03-15 11:43:57 [112] #B843: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 4) 2026-03-15 11:43:57 [112] #B842: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 3) 2026-03-15 11:43:57 [112] #B841: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 2) 2026-03-15 11:43:56 [112] #B840: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 1) 2026-03-15 11:43:56 [485] #B839: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING A disk group was quarantined to prevent writing invalid data that may exist in the controller that logged this event. (disk group: diskgroup1, SN: 00c0ff44588b00009a63b55d00000000) 2026-03-15 11:43:56 [173] #B838: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL A disk group was dequarantined. (disk group: diskgroup1, SN: 00c0ff44588b00009a63b55d00000000) (disk group status: FTOL, mode: AUTO) 2026-03-15 11:43:51 [211] #B837: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 0, number of elements: 51, expanders: 1, native levels: 1, partner levels: 0, device PHYs: 3) 2026-03-15 11:43:48 [084] #B836: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Non volatile device flush or restore failure) 2026-03-15 11:43:43 [204] #B835: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x00000030, p3: 0x00000000, p4: 0x00000000) 2026-03-15 11:43:42 [204] #B834: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x0000002F, p3: 0x00000000, p4: 0x00000000) 2026-03-15 11:43:42 [595] #B833: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Controller serial numbers have been logged. (controller A: 00c0ff44588b0000, controller B: 00c0ff44576f0000) 2026-03-15 11:43:37 [190] #B832: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor charging. 2026-03-15 11:43:01 [056] #B831: MS- kill was released or a reset occurred). SC firmware version: VLS270R01-01 2026-03-15 11:41:49 [068] #B830: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The controller that logged this event has shut down; restarting 2026-03-15 11:39:40 [314] #B829: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR There is a problem with a FRU. (FRU type: Controller module A, enclosure: 1, product ID: N/A, SN: N/A, version: N/A, related event serial number: B828, related event code: 313) 2026-03-15 11:39:40 [313] #B828: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR RAID controller A failed, reason Non volatile device flush or restore failure. Product ID N/A, S/N N/A) 2026-03-15 11:38:42 [310] #B827: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 11:38:41 [310] #B826: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 11:38:41 [211] #B825: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 0, device PHYs: 3) 2026-03-15 11:38:39 [084] #B824: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Non volatile device flush or restore failure) 2026-03-15 11:37:54 [310] #B823: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 11:37:54 [211] #B822: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 1, device PHYs: 3) 2026-03-15 11:36:58 [081] #B821: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Kill was released (that is, the partner controller was allowed to boot up), automatic. 2026-03-15 11:36:00 [310] #B820: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a resc2026-03-15 11:35:59 [310] #B819: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 11:35:59 [211] #B818: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 0, device PHYs: 3) 2026-03-15 11:35:57 [084] #B817: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Non volatile device flush or restore failure) 2026-03-15 11:35:10 [310] #B816: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 11:35:10 [211] #B815: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 1, device PHYs: 3) 2026-03-15 11:34:16 [081] #B814: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Kill was released (that is, the partner controller was allowed to boot up), unknown reason. 2026-03-15 11:30:18 [177] #B813: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Cache memory used for write data was freed for a volume. (pool: diskgroup1, volume: Vdisk, SN: 00c0ff44588b0000db63b55d01000000) 2026-03-15 10:10:21 [314] #B812: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR There is a problem with a FRU. (FRU type: Controller module A, enclosure: 1, product ID: N/A, SN: N/A, version: N/A, related event serial number: B811, related event code: 313) 2026-03-15 10:10:21 [313] #B811: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR RAID controller A failed, reason Non volatile device flush or restore failure. Product ID N/A, S/N N/A) 2026-03-15 10:09:23 [310] #B810: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 10:09:22 [310] #B809: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 10:09:22 [211] #B808: MSnents were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 0, device PHYs: 3) 2026-03-15 10:09:20 [084] #B807: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Non volatile device flush or restore failure) 2026-03-15 10:08:35 [310] #B806: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 10:08:35 [211] #B805: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 1, device PHYs: 3) 2026-03-15 10:07:39 [081] #B804: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Kill was released (that is, the partner controller was allowed to boot up), automatic. 2026-03-15 10:06:41 [310] #B803: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 10:06:40 [310] #B802: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 10:06:40 [211] #B801: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 0, device PHYs: 3) 2026-03-15 10:06:38 [084] #B800: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Non volatile device flush or restore failure) 2026-03-15 10:05:52 [310] #B799: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-15 10:05:51 [211] #B798: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 1, device PHYs: 3) 2026-03-15 10:04:57 [081] #B797: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Kill was released (that is, the partner controller was allowed to boot up), u2026-03-13 13:05:53 [314] #B796: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR There is a problem with a FRU. (FRU type: Controller module A, enclosure: 1, product ID: N/A, SN: N/A, version: N/A, related event serial number: B795, related event code: 313) 2026-03-13 13:05:53 [313] #B795: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR RAID controller A failed, reason Non volatile device flush or restore failure. Product ID N/A, S/N N/A) 2026-03-13 13:03:56 [310] #B794: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-13 13:03:55 [310] #B793: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-13 13:03:54 [211] #B792: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 0, device PHYs: 3) 2026-03-13 13:03:52 [084] #B791: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Non volatile device flush or restore failure) 2026-03-13 13:03:05 [310] #B790: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-13 13:03:05 [211] #B789: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 1, device PHYs: 3) 2026-03-13 13:02:11 [081] #B788: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Kill was released (that is, the partner controller was allowed to boot up), automatic. 2026-03-13 13:00:14 [310] #B787: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-13 13:00:12 [310] #B786: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-13 13:00:12 [211] #B785: MSnents were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 0, device PHYs: 3) 2026-03-13 13:00:10 [084] #B784: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Non volatile device flush or restore failure) 2026-03-13 12:59:40 [310] #B783: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-13 12:59:37 [309] #B782: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The startup IP address information was obtained from flash rather than the FRU-ID SEEPROM. 2026-03-13 12:59:37 [211] #B781: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 1, device PHYs: 3) 2026-03-13 12:58:59 [081] #B780: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Kill was released (that is, the partner controller was allowed to boot up), partner controller installed. 2026-03-13 05:39:21 [181] #B779: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-13 05:39:19 [181] #B778: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-13 05:39:19 [139] #B777: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller booted up. MC firmware version: VXM270R001-01 2026-03-13 05:39:19 [363] #B776: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Firmware versions match those in the firmware bundle. (controller: B) 2026-03-13 05:39:08 [141] #B775: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller IP address changed. (new IP address: IP: 172.16.50.4/255.255.255.0/172.16.50.253) 2026-03-13 05:39:08 [181] #B774: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-13 05:39:07 [175] #B773: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is up for controller B. 2026-03-13 05:39:07 [181] #B772: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-13 05:38:32 [555] #B771: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING An Enclosure Management Processor (EMP) reported an alert condition on an expander. Type: the FRU is not installed. (enclosure: 1, WWN: 500C0FF044597D3C) I/O module A, status: N/A 2026-03-13 05:38:27 [111] #B770: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 2, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-13 05:38:27 [111] #B769: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 1, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-13 05:38:25 [310] #B768: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-13 05:38:24 [044] #B767: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Unwritable write-back cache data exists for a volume. (disk group: diskgroup1, volume: Vdisk, SN: 00c0ff44588b0000db63b55d01000000) It comprises 1% of cache space. 2026-03-13 05:38:24 [310] #B766: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-13 05:38:24 [509] #B765: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR The metadata volume for a virtual pool went offline. Volume mappings and persistent reservations are inaccessible or lost. (pool: A, SN: 00c0ff44588b00009c63b55d01000000) 2026-03-13 05:38:23 [191] #B764: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor good. 2026-03-13 05:38:21 [077] #B763: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Write-back cache was initialized for controller A. Write-back data was found. 2026-03-13 05:38:19 [077] #B762: MStroller B. Write-back data was found. 2026-03-13 05:38:18 [112] #B761: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 4) 2026-03-13 05:38:18 [112] #B760: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 3) 2026-03-13 05:38:18 [112] #B759: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 2) 2026-03-13 05:38:18 [112] #B758: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 1) 2026-03-13 05:38:17 [485] #B757: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING A disk group was quarantined to prevent writing invalid data that may exist in the controller that logged this event. (disk group: diskgroup1, SN: 00c0ff44588b00009a63b55d00000000) 2026-03-13 05:38:17 [173] #B756: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL A disk group was dequarantined. (disk group: diskgroup1, SN: 00c0ff44588b00009a63b55d00000000) (disk group status: FTOL, mode: AUTO) 2026-03-13 05:38:15 [190] #B755: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor charging. 2026-03-13 05:38:13 [191] #B754: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor good. 2026-03-13 05:38:13 [211] #B753: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 0, number of elements: 51, expanders: 1, native levels: 1, partner levels: 0, device PHYs: 3) 2026-03-13 05:38:10 [204] #B752: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x00000030, p3: 0x00000000, p4: 0x00000000) 2026-03-13 05:38:03 [190] #B751: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor charging. 2026-03-13 05:37:47 [204] #B750: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x0000002F, p3: 0x00000000, p4: 0x00000000) 2026-03-13 05:37:47 [595] #B749: MSAed. (controller A: 0000000000000000, controller B: 00c0ff44576f0000) 2026-03-13 05:37:46 [084] #B748: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Other not present) 2026-03-13 05:37:16 [056] #B747: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Storage Controller booted up (cold boot - power up). SC firmware version: VLS270R01-01 2026-03-13 04:25:09 [557] #B746: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 5V Loc: left-PSU, sensor status: N/A, current: 1.67 A 2026-03-13 04:25:09 [557] #B745: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 12V Loc: left-PSU, sensor status: N/A 2026-03-13 04:25:09 [554] #B744: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 3.3V Loc: left-PSU, sensor status: N/A, voltage: 3.37 V 2026-03-13 04:25:09 [554] #B743: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 5V Loc: left-PSU, sensor status: N/A, voltage: 3.78 V 2026-03-13 04:25:09 [554] #B742: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Capacitor Cell 4 Voltage-Ctlr A, sensor status: N/A, voltage: 9.01 V 2026-03-13 04:25:09 [198] #B741: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: power supply failed. 2026-03-13 04:25:09 [314] #B740: MSU, Left, enclosure: 1, product ID: 814665-001, SN: 7CE914T347, version: C1, related event serial number: B739, related event code: 551) 2026-03-13 04:25:09 [551] #B739: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a power supply. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) power supply LEFT, power supply status: DC failure, AC failure 2026-03-13 04:20:19 [181] #B738: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-13 04:20:16 [181] #B737: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-13 04:20:16 [139] #B736: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller booted up. MC firmware version: VXM270R001-01 2026-03-13 04:20:16 [363] #B735: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Firmware versions match those in the firmware bundle. (controller: B) 2026-03-13 04:20:04 [141] #B734: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller IP address changed. (new IP address: IP: 172.16.50.4/255.255.255.0/172.16.50.253) 2026-03-13 04:20:04 [181] #B733: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-13 04:20:03 [175] #B732: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is up for controller B. 2026-03-13 04:20:03 [181] #B731: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-13 04:19:36 [555] #B730: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING An Enclosure Management Processor (EMP) reported an alert condition on an expander. 2026-03-13 04:19:31 [111] #B729: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 1, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-13 04:19:31 [111] #B728: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 2, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-13 04:19:30 [310] #B727: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-13 04:19:28 [044] #B726: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Unwritable write-back cache data exists for a volume. (disk group: diskgroup1, volume: Vdisk, SN: 00c0ff44588b0000db63b55d01000000) It comprises 1% of cache space. 2026-03-13 04:19:28 [310] #B725: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-13 04:19:28 [509] #B724: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR The metadata volume for a virtual pool went offline. Volume mappings and persistent reservations are inaccessible or lost. (pool: A, SN: 00c0ff44588b00009c63b55d01000000) 2026-03-13 04:19:27 [191] #B723: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor good. 2026-03-13 04:19:25 [077] #B722: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Write-back cache was initialized for controller A. Write-back data was found. 2026-03-13 04:19:24 [077] #B721: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Write-back cache was initialized for controller B. Write-back data was found. 2026-03-13 04:19:23 [112] #B720: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 4) 2026-03-13 04:19:22 [190] #B719: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor charging. 2026-03-13 04:19:22 [112] #B718: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 3) 2026-03-13 04:19:22 [112] #B717: MSA2026-03-13 04:19:22 [112] #B716: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 1) 2026-03-13 04:19:21 [485] #B715: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING A disk group was quarantined to prevent writing invalid data that may exist in the controller that logged this event. (disk group: diskgroup1, SN: 00c0ff44588b00009a63b55d00000000) 2026-03-13 04:19:21 [173] #B714: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL A disk group was dequarantined. (disk group: diskgroup1, SN: 00c0ff44588b00009a63b55d00000000) (disk group status: FTOL, mode: AUTO) 2026-03-13 04:19:16 [211] #B713: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 0, number of elements: 51, expanders: 1, native levels: 1, partner levels: 0, device PHYs: 3) 2026-03-13 04:19:13 [204] #B712: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x00000030, p3: 0x00000000, p4: 0x00000000) 2026-03-13 04:18:50 [204] #B711: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x0000002F, p3: 0x00000000, p4: 0x00000000) 2026-03-13 04:18:50 [595] #B710: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Controller serial numbers have been logged. (controller A: 0000000000000000, controller B: 00c0ff44576f0000) 2026-03-13 04:18:49 [084] #B709: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Other not present) 2026-03-13 04:18:19 [056] #B708: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Storage Controller booted up (cold boot - power up). SC firmware version: VLS270R01-01 2026-03-12 12:47:42 [181] #B707: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 12:47:42 [139] #B706: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller booted up. MC firmware version: VXM270R001-01 2026-03-12 12:47:42 [363] #B705: MSAmware bundle. (controller: B) 2026-03-12 12:47:40 [181] #B704: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 12:47:30 [141] #B703: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller IP address changed. (new IP address: IP: 172.16.50.4/255.255.255.0/172.16.50.253) 2026-03-12 12:47:30 [181] #B702: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 12:47:28 [175] #B701: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is up for controller B. 2026-03-12 12:47:28 [181] #B700: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 12:46:56 [555] #B699: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING An Enclosure Management Processor (EMP) reported an alert condition on an expander. Type: the FRU is not installed. (enclosure: 1, WWN: 500C0FF044597D3C) I/O module A, status: N/A 2026-03-12 12:46:51 [111] #B698: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 2, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-12 12:46:51 [111] #B697: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 1, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-12 12:46:49 [310] #B696: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 12:46:48 [044] #B695: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Unwritable write-back cache data exists for a volume. (disk group: diskgroup1, volume: Vdisk, SN: 00c0ff44588b0000db63b55d01000000) It comprises 1% of cache space. 2026-03-12 12:46:48 [310] #B694: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a resc2026-03-12 12:46:48 [509] #B693: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR The metadata volume for a virtual pool went offline. Volume mappings and persistent reservations are inaccessible or lost. (pool: A, SN: 00c0ff44588b00009c63b55d01000000) 2026-03-12 12:46:47 [191] #B692: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor good. 2026-03-12 12:46:45 [077] #B691: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Write-back cache was initialized for controller A. Write-back data was found. 2026-03-12 12:46:43 [077] #B690: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Write-back cache was initialized for controller B. Write-back data was found. 2026-03-12 12:46:42 [112] #B689: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 4) 2026-03-12 12:46:42 [112] #B688: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 3) 2026-03-12 12:46:42 [112] #B687: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 2) 2026-03-12 12:46:42 [112] #B686: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 1) 2026-03-12 12:46:41 [485] #B685: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING A disk group was quarantined to prevent writing invalid data that may exist in the controller that logged this event. (disk group: diskgroup1, SN: 00c0ff44588b00009a63b55d00000000) 2026-03-12 12:46:41 [173] #B684: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL A disk group was dequarantined. (disk group: diskgroup1, SN: 00c0ff44588b00009a63b55d00000000) (disk group status: FTOL, mode: AUTO) 2026-03-12 12:46:37 [211] #B683: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 0, number of elements: 51, expanders: 1, native levels: 1, partner levels: 0, device PHYs: 3) 2026-03-12 12:46:34 [204] #B682: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x00000030, p3: 0x00000000, p4: 0x00000000) 2026-03-12 12:46:16 [190] #B681: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor charging. 2026-03-12 12:46:11 [204] #B680: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x0000002F, p3: 0x00000000, p4: 0x00000000) 2026-03-12 12:46:11 [595] #B679: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Controller serial numbers have been logged. (controller A: 0000000000000000, controller B: 00c0ff44576f0000) 2026-03-12 12:46:10 [084] #B678: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Other not present) 2026-03-12 12:45:39 [056] #B677: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Storage Controller booted up (cold boot - power up). SC firmware version: VLS270R01-01 2026-03-12 12:09:20 [068] #B676: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The controller that logged this event has shut down; no restart 2026-03-12 11:32:57 [314] #B675: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR There is a problem with a FRU. (FRU type: Controller module A, enclosure: 1, product ID: N/A, SN: N/A, version: N/A, related event serial number: B674, related event code: 313) 2026-03-12 11:32:57 [313] #B674: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR RAID controller A failed, reason Non volatile device flush or restore failure. Product ID N/A, S/N N/A) 2026-03-12 11:32:00 [310] #B673: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 11:31:58 [310] #B672: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 11:31:58 [211] #B671: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 0, device PHYs: 3) 2026-03-12 11:31:56 [084] #B670: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Non volatile device flush or restore failure) 2026-03-12 11:31:09 [310] #B669: MSe data was completed following a rescan. 2026-03-12 11:31:09 [211] #B668: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 1, device PHYs: 3) 2026-03-12 11:30:15 [081] #B667: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Kill was released (that is, the partner controller was allowed to boot up), automatic. 2026-03-12 11:28:17 [310] #B666: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 11:28:16 [310] #B665: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 11:28:16 [211] #B664: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 0, device PHYs: 3) 2026-03-12 11:28:14 [084] #B663: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Non volatile device flush or restore failure) 2026-03-12 11:27:44 [019] #B662: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL A rescan-bus operation was done. (number of disks that were found: 2, number of enclosures that were found: 1) (rescan reason: initiated by internal logic, rescan reason code: 24) 2026-03-12 11:27:43 [310] #B661: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 11:27:42 [211] #B660: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 1, device PHYs: 3) 2026-03-12 11:27:03 [081] #B659: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Kill was released (that is, the partner controller was allowed to boot up), partner controller installed. 2026-03-12 11:15:21 [111] #B658: MSoint-to-point, external device(s)) 2026-03-12 11:15:05 [111] #B657: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 1, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-12 11:08:44 [112] #B656: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Host link down. (port: 2) 2026-03-12 11:08:41 [112] #B655: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Host link down. (port: 1) 2026-03-12 10:55:33 [503] #B654: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Intelligent BackEnd Error Monitor (IBEEM) has discovered that continuous errors are being reported for the indicated PHY. (channel: 1, enclosure: 1, PHY: 36, type: Egress) 2026-03-12 10:55:33 [503] #B653: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Intelligent BackEnd Error Monitor (IBEEM) has discovered that continuous errors are being reported for the indicated PHY. (channel: 1, enclosure: 1, PHY: 35, type: Egress) 2026-03-12 10:55:33 [503] #B652: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Intelligent BackEnd Error Monitor (IBEEM) has discovered that continuous errors are being reported for the indicated PHY. (channel: 1, enclosure: 1, PHY: 30, type: Egress) 2026-03-12 10:55:33 [503] #B651: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Intelligent BackEnd Error Monitor (IBEEM) has discovered that continuous errors are being reported for the indicated PHY. (channel: 1, enclosure: 1, PHY: 29, type: Egress) 2026-03-12 10:55:33 [503] #B650: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Intelligent BackEnd Error Monitor (IBEEM) has discovered that continuous errors are being reported for the indicated PHY. (channel: 1, enclosure: 1, PHY: 28, type: Egress) 2026-03-12 10:41:18 [310] #B649: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 10:41:18 [044] #B648: MSvolume. (disk group: diskgroup1, volume: Vdisk, SN: 00c0ff44588b0000db63b55d01000000) It comprises 1% of cache space. 2026-03-12 10:41:18 [019] #B647: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL A rescan-bus operation was done. (number of disks that were found: 2, number of enclosures that were found: 1) (rescan reason: initiated by a user, rescan reason code: 0) 2026-03-12 10:41:14 [309] #B646: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The startup IP address information was obtained from flash rather than the FRU-ID SEEPROM. 2026-03-12 10:41:14 [211] #B645: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 0, number of elements: 51, expanders: 1, native levels: 1, partner levels: 0, device PHYs: 3) 2026-03-12 10:41:11 [114] #B644: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Disk link down. (channel: 1) 2026-03-12 10:41:11 [114] #B643: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Disk link down. (channel: 0) 2026-03-12 10:26:22 [181] #B642: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 10:26:20 [181] #B641: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 10:26:20 [139] #B640: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller booted up. MC firmware version: VXM270R001-01 2026-03-12 10:26:20 [363] #B639: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Firmware versions match those in the firmware bundle. (controller: B) 2026-03-12 10:26:07 [141] #B638: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller IP address changed. (new IP address: IP: 172.16.50.4/255.255.255.0/172.16.50.253) 2026-03-12 10:26:07 [181] #B637: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 10:26:07 [175] #B636: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is up for controller B. 2026-03-12 10:26:07 [181] #B635: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 10:25:38 [555] #B634: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING An Enclosure Management Processor (EMP) reported an alert condition on an expander. Type: the FRU is not installed. (enclosure: 1, WWN: 500C0FF044597D3C) I/O module A, status: N/A 2026-03-12 10:25:33 [111] #B633: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 2, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-12 10:25:33 [111] #B632: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 1, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-12 10:25:31 [310] #B631: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 10:25:30 [044] #B630: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Unwritable write-back cache data exists for a volume. (disk group: diskgroup1, volume: Vdisk, SN: 00c0ff44588b0000db63b55d01000000) It comprises 1% of cache space. 2026-03-12 10:25:30 [310] #B629: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 10:25:30 [509] #B628: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR The metadata volume for a virtual pool went offline. Volume mappings and persistent reservations are inaccessible or lost. (pool: A, SN: 00c0ff44588b00009c63b55d01000000) 2026-03-12 10:25:29 [191] #B627: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor good. 2026-03-12 10:25:27 [077] #B626: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Write-back cache was initialized for controller A. Write-back data was found. 2026-03-12 10:25:25 [077] #B625: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Write-back cache was initialized for controller B. Write-back data was found. 2026-03-12 10:25:24 [112] #B624: MS2026-03-12 10:25:24 [112] #B623: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 3) 2026-03-12 10:25:24 [112] #B622: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 2) 2026-03-12 10:25:24 [112] #B621: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 1) 2026-03-12 10:25:23 [485] #B620: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING A disk group was quarantined to prevent writing invalid data that may exist in the controller that logged this event. (disk group: diskgroup1, SN: 00c0ff44588b00009a63b55d00000000) 2026-03-12 10:25:23 [173] #B619: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL A disk group was dequarantined. (disk group: diskgroup1, SN: 00c0ff44588b00009a63b55d00000000) (disk group status: FTOL, mode: AUTO) 2026-03-12 10:25:19 [211] #B618: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 0, number of elements: 51, expanders: 1, native levels: 1, partner levels: 0, device PHYs: 3) 2026-03-12 10:25:16 [204] #B617: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x00000030, p3: 0x00000000, p4: 0x00000000) 2026-03-12 10:25:01 [190] #B616: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor charging. 2026-03-12 10:24:53 [204] #B615: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x0000002F, p3: 0x00000000, p4: 0x00000000) 2026-03-12 10:24:53 [595] #B614: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Controller serial numbers have been logged. (controller A: 0000000000000000, controller B: 00c0ff44576f0000) 2026-03-12 10:24:52 [084] #B613: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Other not present) 2026-03-12 10:24:22 [056] #B612: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Storage Controller booted up (cold boot - power up). SC firmware version: VLS270R01-01 2026-03-12 09:42:53 [557] #B611: MS an alert condition on a current sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 5V Loc: right-PSU, sensor status: N/A, current: 1.67 A 2026-03-12 09:42:53 [557] #B610: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 12V Loc: right-PSU, sensor status: N/A 2026-03-12 09:42:53 [554] #B609: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 3.3V Loc: right-PSU, sensor status: N/A, voltage: 3.36 V 2026-03-12 09:42:53 [554] #B608: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 5V Loc: right-PSU, sensor status: N/A, voltage: 2.13 V 2026-03-12 09:42:53 [554] #B607: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 12V Loc: right-PSU, sensor status: N/A, voltage: 5.73 V 2026-03-12 09:42:53 [198] #B606: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: power supply failed. 2026-03-12 09:42:53 [314] #B605: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR There is a problem with a FRU. (FRU type: A/C PSU, Right, enclosure: 1, product ID: 814665-001, SN: 7CE914T348, version: C1, related event serial number: B604, related event code: 551) 2026-03-12 09:42:53 [551] #B604: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a power supply. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) power supply RIGHT, power supply status: DC failure, AC failure 2026-03-12 09:37:13 [181] #B603: MSmeters were set. 2026-03-12 09:37:13 [139] #B602: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller booted up. MC firmware version: VXM270R001-01 2026-03-12 09:37:13 [363] #B601: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Firmware versions match those in the firmware bundle. (controller: B) 2026-03-12 09:36:59 [141] #B600: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller IP address changed. (new IP address: IP: 172.16.50.4/255.255.255.0/172.16.50.253) 2026-03-12 09:36:59 [181] #B599: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 09:36:59 [175] #B598: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is up for controller B. 2026-03-12 09:36:59 [181] #B597: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 09:36:45 [181] #B596: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 09:36:33 [555] #B595: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING An Enclosure Management Processor (EMP) reported an alert condition on an expander. Type: the FRU is not installed. (enclosure: 1, WWN: 500C0FF044597D3C) I/O module A, status: N/A 2026-03-12 09:36:28 [111] #B594: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 2, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-12 09:36:27 [111] #B593: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 1, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-12 09:36:26 [310] #B592: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a resc2026-03-12 09:36:25 [044] #B591: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Unwritable write-back cache data exists for a volume. (disk group: diskgroup1, volume: Vdisk, SN: 00c0ff44588b0000db63b55d01000000) It comprises 1% of cache space. 2026-03-12 09:36:25 [310] #B590: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 09:36:25 [509] #B589: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR The metadata volume for a virtual pool went offline. Volume mappings and persistent reservations are inaccessible or lost. (pool: A, SN: 00c0ff44588b00009c63b55d01000000) 2026-03-12 09:36:24 [191] #B588: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor good. 2026-03-12 09:36:22 [077] #B587: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Write-back cache was initialized for controller A. Write-back data was found. 2026-03-12 09:36:20 [077] #B586: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Write-back cache was initialized for controller B. Write-back data was found. 2026-03-12 09:36:19 [112] #B585: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 4) 2026-03-12 09:36:19 [112] #B584: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 3) 2026-03-12 09:36:19 [112] #B583: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 2) 2026-03-12 09:36:18 [112] #B582: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 1) 2026-03-12 09:36:18 [485] #B581: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING A disk group was quarantined to prevent writing invalid data that may exist in the controller that logged this event. (disk group: diskgroup1, SN: 00c0ff44588b00009a63b55d00000000) 2026-03-12 09:36:18 [173] #B580: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL A disk group was dequarantined. (disk group: diskgroup1, SN: 00c0ff44588b00009a63b55d00000000) (disk group status: FTOL, mode: AUTO) 2026-03-12 09:36:13 [211] #B579: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channe2026-03-12 09:36:10 [204] #B578: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x00000030, p3: 0x00000000, p4: 0x00000000) 2026-03-12 09:35:51 [190] #B577: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor charging. 2026-03-12 09:35:46 [204] #B576: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x0000002F, p3: 0x00000000, p4: 0x00000000) 2026-03-12 09:35:46 [595] #B575: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Controller serial numbers have been logged. (controller A: 0000000000000000, controller B: 00c0ff44576f0000) 2026-03-12 09:35:46 [084] #B574: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Other not present) 2026-03-12 09:35:16 [056] #B573: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Storage Controller booted up (warm boot - kill was released or a reset occurred). SC firmware version: VLS270R01-01 2026-03-12 09:34:08 [068] #B572: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The controller that logged this event has shut down; restarting 2026-03-12 09:21:07 [314] #B571: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR There is a problem with a FRU. (FRU type: Controller module A, enclosure: 1, product ID: 876127-001, SN: 7CE913M204, version: N/A, related event serial number: B570, related event code: 313) 2026-03-12 09:21:07 [313] #B570: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR RAID controller A failed, reason Non volatile device flush or restore failure. Product ID 876127-001, S/N 7CE913M204) 2026-03-12 09:20:09 [310] #B569: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 09:20:08 [310] #B568: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a resc2026-03-12 09:20:08 [211] #B567: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 0, device PHYs: 3) 2026-03-12 09:20:07 [084] #B566: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Non volatile device flush or restore failure) 2026-03-12 09:19:19 [310] #B565: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 09:19:19 [309] #B564: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The startup IP address information was obtained from flash rather than the FRU-ID SEEPROM. 2026-03-12 09:19:19 [211] #B563: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 1, device PHYs: 3) 2026-03-12 09:18:24 [081] #B562: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Kill was released (that is, the partner controller was allowed to boot up), automatic. 2026-03-12 09:17:12 [181] #B561: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 09:17:12 [139] #B560: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller booted up. MC firmware version: VXM270R001-01 2026-03-12 09:17:12 [363] #B559: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Firmware versions match those in the firmware bundle. (controller: B) 2026-03-12 09:16:58 [141] #B558: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller IP address changed. (new IP address: IP: 172.16.50.4/255.255.255.0/172.16.50.253) 2026-03-12 09:16:58 [181] #B557: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 09:16:57 [175] #B556: MS controller B. 2026-03-12 09:16:57 [181] #B555: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 09:16:45 [181] #B554: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 09:16:26 [111] #B553: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 1, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-12 09:16:26 [111] #B552: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 2, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-12 09:16:25 [310] #B551: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 09:16:24 [044] #B550: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Unwritable write-back cache data exists for a volume. (disk group: diskgroup1, volume: Vdisk, SN: 00c0ff44588b0000db63b55d01000000) It comprises 1% of cache space. 2026-03-12 09:16:24 [310] #B549: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 09:16:23 [509] #B548: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR The metadata volume for a virtual pool went offline. Volume mappings and persistent reservations are inaccessible or lost. (pool: A, SN: 00c0ff44588b00009c63b55d01000000) 2026-03-12 09:16:23 [191] #B547: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor good. 2026-03-12 09:16:21 [077] #B546: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Write-back cache was initialized for controller A. Write-back data was found. 2026-03-12 09:16:19 [077] #B545: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Write-back cache was initialized for controller B. Write-back data was found.2026-03-12 09:16:18 [112] #B544: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 4) 2026-03-12 09:16:18 [112] #B543: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 3) 2026-03-12 09:16:17 [112] #B542: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 2) 2026-03-12 09:16:17 [112] #B541: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 1) 2026-03-12 09:16:17 [485] #B540: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING A disk group was quarantined to prevent writing invalid data that may exist in the controller that logged this event. (disk group: diskgroup1, SN: 00c0ff44588b00009a63b55d00000000) 2026-03-12 09:16:17 [173] #B539: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL A disk group was dequarantined. (disk group: diskgroup1, SN: 00c0ff44588b00009a63b55d00000000) (disk group status: FTOL, mode: AUTO) 2026-03-12 09:16:12 [211] #B538: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 0, number of elements: 51, expanders: 1, native levels: 1, partner levels: 0, device PHYs: 3) 2026-03-12 09:16:09 [204] #B537: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x00000030, p3: 0x00000000, p4: 0x00000000) 2026-03-12 09:15:53 [084] #B536: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Non volatile device flush or restore failure) 2026-03-12 09:15:51 [190] #B535: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor charging. 2026-03-12 09:15:46 [204] #B534: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x0000002F, p3: 0x00000000, p4: 0x00000000) 2026-03-12 09:15:46 [595] #B533: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Controller serial numbers have been logged. (controller A: 00c0ff44588b0000, controller B: 00c0ff44576f0000) 2026-03-12 09:15:15 [056] #B532: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Storage Controller booted up (warm boot - kill was released or a reset occurr2026-03-12 09:13:52 [068] #B531: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The controller that logged this event has shut down; restarting 2026-03-12 09:12:09 [314] #B530: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR There is a problem with a FRU. (FRU type: Controller module A, enclosure: 1, product ID: 876127-001, SN: 7CE913M204, version: N/A, related event serial number: B529, related event code: 313) 2026-03-12 09:12:09 [313] #B529: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR RAID controller A failed, reason Non volatile device flush or restore failure. Product ID 876127-001, S/N 7CE913M204) 2026-03-12 09:11:11 [310] #B528: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 09:11:10 [310] #B527: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 09:11:10 [211] #B526: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 0, device PHYs: 3) 2026-03-12 09:11:09 [084] #B525: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Non volatile device flush or restore failure) 2026-03-12 09:10:22 [310] #B524: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 09:10:22 [211] #B523: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 1, device PHYs: 3) 2026-03-12 09:09:26 [081] #B522: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Kill was released (that is, the partner controller was allowed to boot up), unknown reason. 2026-03-12 08:56:02 [314] #B521: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR There is a problem with a FRU. (FRU type: Controller module A, enclosure: 1, product 313) 2026-03-12 08:56:02 [313] #B520: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR RAID controller A failed, reason Non volatile device flush or restore failure. Product ID 876127-001, S/N 7CE913M204) 2026-03-12 08:55:05 [310] #B519: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 08:55:03 [310] #B518: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 08:55:03 [211] #B517: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 0, device PHYs: 3) 2026-03-12 08:55:01 [084] #B516: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Non volatile device flush or restore failure) 2026-03-12 08:54:14 [310] #B515: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 08:54:14 [211] #B514: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 1, device PHYs: 3) 2026-03-12 08:53:20 [081] #B513: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Kill was released (that is, the partner controller was allowed to boot up), automatic. 2026-03-12 08:51:23 [310] #B512: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 08:51:21 [310] #B511: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 08:51:21 [211] #B510: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channe2026-03-12 08:51:20 [084] #B509: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Non volatile device flush or restore failure) 2026-03-12 08:50:48 [310] #B508: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 08:50:46 [309] #B507: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The startup IP address information was obtained from flash rather than the FRU-ID SEEPROM. 2026-03-12 08:50:46 [211] #B506: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 1, device PHYs: 3) 2026-03-12 08:50:05 [081] #B505: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Kill was released (that is, the partner controller was allowed to boot up), partner controller installed. 2026-03-12 08:02:49 [175] #B504: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is up for controller B. 2026-03-12 08:02:49 [181] #B503: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 08:02:39 [175] #B502: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is down for controller B. 2026-03-12 08:02:39 [181] #B501: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 08:02:31 [141] #B500: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller IP address changed. (new IP address: IP: 172.16.50.4/255.255.255.0/172.16.50.253) 2026-03-12 08:02:31 [181] #B499: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 07:49:19 [175] #B498: MS controller B. 2026-03-12 07:49:19 [181] #B497: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 07:49:18 [181] #B496: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 07:49:18 [139] #B495: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller booted up. MC firmware version: VXM270R001-01 2026-03-12 07:49:18 [363] #B494: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Firmware versions match those in the firmware bundle. (controller: B) 2026-03-12 07:49:05 [141] #B493: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller IP address changed. (new IP address: IP: 10.0.0.3/255.255.255.0/10.0.0.1) 2026-03-12 07:49:05 [181] #B492: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 07:48:40 [555] #B491: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING An Enclosure Management Processor (EMP) reported an alert condition on an expander. Type: the FRU is not installed. (enclosure: 1, WWN: 500C0FF044597D3C) I/O module A, status: N/A 2026-03-12 07:48:35 [111] #B490: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 2, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-12 07:48:35 [111] #B489: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 1, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-12 07:48:34 [310] #B488: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 07:48:34 [181] #B487: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 07:48:33 [044] #B486: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Unwritable write-back cache data exists for a volume. (disk group: diskgroup1, volume: Vdisk, SN: 00c0ff44588b0000db63b55d01000000) It comprises 1% of cache space. 2026-03-12 07:48:33 [310] #B485: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 07:48:32 [509] #B484: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR The metadata volume for a virtual pool went offline. Volume mappings and persistent reservations are inaccessible or lost. (pool: A, SN: 00c0ff44588b00009c63b55d01000000) 2026-03-12 07:48:32 [191] #B483: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor good. 2026-03-12 07:48:30 [077] #B482: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Write-back cache was initialized for controller A. Write-back data was found. 2026-03-12 07:48:28 [077] #B481: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Write-back cache was initialized for controller B. Write-back data was found. 2026-03-12 07:48:27 [112] #B480: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 4) 2026-03-12 07:48:27 [112] #B479: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 3) 2026-03-12 07:48:26 [112] #B478: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 2) 2026-03-12 07:48:26 [112] #B477: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 1) 2026-03-12 07:48:26 [485] #B476: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING A disk group was quarantined to prevent writing invalid data that may exist in the controller that logged this event. (disk group: diskgroup1, SN: 00c0ff44588b00009a63b55d00000000) 2026-03-12 07:48:26 [173] #B475: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL A disk group was dequarantined. (disk group: diskgroup1, SN: 00c0ff44588b00009a63b55d00000000) (disk group status: FTOL, mode: AUTO) 2026-03-12 07:48:21 [211] #B474: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channe2026-03-12 07:48:18 [204] #B473: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x00000030, p3: 0x00000000, p4: 0x00000000) 2026-03-12 07:48:02 [084] #B472: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Non volatile device flush or restore failure) 2026-03-12 07:48:00 [190] #B471: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor charging. 2026-03-12 07:47:55 [204] #B470: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x0000002F, p3: 0x00000000, p4: 0x00000000) 2026-03-12 07:47:55 [595] #B469: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Controller serial numbers have been logged. (controller A: 00c0ff44588b0000, controller B: 00c0ff44576f0000) 2026-03-12 07:47:24 [056] #B468: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Storage Controller booted up (warm boot - kill was released or a reset occurred). SC firmware version: VLS270R01-01 2026-03-12 07:45:32 [111] #B467: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 1, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-12 07:45:29 [112] #B466: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Host link down. (port: 1) 2026-03-12 07:45:11 [111] #B465: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 1, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-12 07:45:02 [111] #B464: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 2, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-12 07:43:51 [112] #B463: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Host link down. (port: 2) 2026-03-12 07:43:17 [112] #B462: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Host link down. (port: 1) 2026-03-12 07:23:55 [111] #B461: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 2, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-12 07:23:49 [112] #B460: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Host link down. (port: 2) 2026-03-12 07:22:07 [175] #B459: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is up for controller B. 2026-03-12 07:22:07 [181] #B458: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 07:10:17 [175] #B457: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is down for controller B. 2026-03-12 07:10:17 [181] #B456: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 06:59:22 [314] #B455: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR There is a problem with a FRU. (FRU type: Controller module A, enclosure: 1, product ID: 876127-001, SN: 7CE913M204, version: N/A, related event serial number: B454, related event code: 313) 2026-03-12 06:59:22 [313] #B454: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR RAID controller A failed, reason Non volatile device flush or restore failure. Product ID 876127-001, S/N 7CE913M204) 2026-03-12 06:58:27 [175] #B453: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is up for controller B. 2026-03-12 06:58:27 [181] #B452: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 06:58:24 [310] #B451: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 06:58:23 [310] #B450: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 06:58:23 [211] #B449: MSnents were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 0, device PHYs: 3) 2026-03-12 06:58:21 [084] #B448: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Non volatile device flush or restore failure) 2026-03-12 06:58:17 [175] #B447: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is down for controller B. 2026-03-12 06:58:17 [181] #B446: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 06:57:34 [310] #B445: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 06:57:34 [211] #B444: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 1, device PHYs: 3) 2026-03-12 06:56:40 [081] #B443: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Kill was released (that is, the partner controller was allowed to boot up), automatic. 2026-03-12 06:55:25 [181] #B442: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 06:55:25 [139] #B441: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller booted up. MC firmware version: VXM270R001-01 2026-03-12 06:55:25 [363] #B440: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Firmware versions match those in the firmware bundle. (controller: B) 2026-03-12 06:55:13 [141] #B439: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller IP address changed. (new IP address: IP: 10.0.0.3/255.255.255.0/10.0.0.1) 2026-03-12 06:55:13 [181] #B438: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 06:55:11 [175] #B437: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is up for controller B. 2026-03-12 06:55:11 [181] #B436: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 06:54:42 [111] #B435: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 1, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-12 06:54:42 [111] #B434: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 2, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-12 06:54:40 [310] #B433: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 06:54:40 [181] #B432: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 06:54:39 [044] #B431: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Unwritable write-back cache data exists for a volume. (disk group: diskgroup1, volume: Vdisk, SN: 00c0ff44588b0000db63b55d01000000) It comprises 1% of cache space. 2026-03-12 06:54:39 [310] #B430: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 06:54:39 [509] #B429: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR The metadata volume for a virtual pool went offline. Volume mappings and persistent reservations are inaccessible or lost. (pool: A, SN: 00c0ff44588b00009c63b55d01000000) 2026-03-12 06:54:38 [191] #B428: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor good. 2026-03-12 06:54:36 [077] #B427: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Write-back cache was initialized for controller A. Write-back data was found. 2026-03-12 06:54:34 [077] #B426: MStroller B. Write-back data was found. 2026-03-12 06:54:33 [112] #B425: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 4) 2026-03-12 06:54:33 [112] #B424: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 3) 2026-03-12 06:54:33 [112] #B423: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 2) 2026-03-12 06:54:33 [112] #B422: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 1) 2026-03-12 06:54:32 [485] #B421: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING A disk group was quarantined to prevent writing invalid data that may exist in the controller that logged this event. (disk group: diskgroup1, SN: 00c0ff44588b00009a63b55d00000000) 2026-03-12 06:54:32 [173] #B420: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL A disk group was dequarantined. (disk group: diskgroup1, SN: 00c0ff44588b00009a63b55d00000000) (disk group status: FTOL, mode: AUTO) 2026-03-12 06:54:30 [211] #B419: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 0, number of elements: 51, expanders: 1, native levels: 1, partner levels: 0, device PHYs: 3) 2026-03-12 06:54:27 [204] #B418: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x00000030, p3: 0x00000000, p4: 0x00000000) 2026-03-12 06:54:10 [084] #B417: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Non volatile device flush or restore failure) 2026-03-12 06:54:08 [190] #B416: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor charging. 2026-03-12 06:54:03 [204] #B415: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x0000002F, p3: 0x00000000, p4: 0x00000000) 2026-03-12 06:54:03 [595] #B414: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Controller serial numbers have been logged. (controller A: 00c0ff44588b0000, controller B: 00c0ff44576f0000) 2026-03-12 06:53:31 [056] #B413: MS- power up). SC firmware version: VLS270R01-01 2026-03-12 06:45:03 [175] #B412: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is up for controller B. 2026-03-12 06:45:03 [181] #B411: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 06:44:23 [175] #B410: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is down for controller B. 2026-03-12 06:44:23 [181] #B409: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 06:44:06 [314] #B408: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR There is a problem with a FRU. (FRU type: Controller module A, enclosure: 1, product ID: 876127-001, SN: 7CE913M204, version: N/A, related event serial number: B407, related event code: 313) 2026-03-12 06:44:06 [313] #B407: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR RAID controller A failed, reason Non volatile device flush or restore failure. Product ID 876127-001, S/N 7CE913M204) 2026-03-12 06:43:08 [310] #B406: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 06:43:07 [310] #B405: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 06:43:07 [211] #B404: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 0, device PHYs: 3) 2026-03-12 06:43:05 [084] #B403: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Non volatile device flush or restore failure) 2026-03-12 06:42:18 [310] #B402: MSe data was completed following a rescan. 2026-03-12 06:42:18 [211] #B401: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 1, device PHYs: 3) 2026-03-12 06:41:24 [081] #B400: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Kill was released (that is, the partner controller was allowed to boot up), automatic. 2026-03-12 06:40:11 [181] #B399: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 06:40:11 [139] #B398: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller booted up. MC firmware version: VXM270R001-01 2026-03-12 06:40:11 [363] #B397: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Firmware versions match those in the firmware bundle. (controller: B) 2026-03-12 06:39:58 [141] #B396: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller IP address changed. (new IP address: IP: 10.0.0.3/255.255.255.0/10.0.0.1) 2026-03-12 06:39:58 [181] #B395: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 06:39:57 [175] #B394: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is up for controller B. 2026-03-12 06:39:57 [181] #B393: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 06:39:26 [181] #B392: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 06:39:26 [111] #B391: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 2, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-12 06:39:26 [111] #B390: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 1, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-12 06:39:24 [310] #B389: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 06:39:23 [044] #B388: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Unwritable write-back cache data exists for a volume. (disk group: diskgroup1, volume: Vdisk, SN: 00c0ff44588b0000db63b55d01000000) It comprises 1% of cache space. 2026-03-12 06:39:23 [310] #B387: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 06:39:23 [509] #B386: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR The metadata volume for a virtual pool went offline. Volume mappings and persistent reservations are inaccessible or lost. (pool: A, SN: 00c0ff44588b00009c63b55d01000000) 2026-03-12 06:39:22 [191] #B385: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor good. 2026-03-12 06:39:20 [077] #B384: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Write-back cache was initialized for controller A. Write-back data was found. 2026-03-12 06:39:18 [077] #B383: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Write-back cache was initialized for controller B. Write-back data was found. 2026-03-12 06:39:17 [112] #B382: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 4) 2026-03-12 06:39:17 [112] #B381: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 3) 2026-03-12 06:39:17 [112] #B380: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 2) 2026-03-12 06:39:17 [112] #B379: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 1) 2026-03-12 06:39:16 [485] #B378: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING A disk group was quarantined to prevent writing invalid data that may exist in the 2026-03-12 06:39:16 [173] #B377: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL A disk group was dequarantined. (disk group: diskgroup1, SN: 00c0ff44588b00009a63b55d00000000) (disk group status: FTOL, mode: AUTO) 2026-03-12 06:39:14 [211] #B376: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 0, number of elements: 51, expanders: 1, native levels: 1, partner levels: 0, device PHYs: 3) 2026-03-12 06:39:11 [204] #B375: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x00000030, p3: 0x00000000, p4: 0x00000000) 2026-03-12 06:38:54 [084] #B374: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Non volatile device flush or restore failure) 2026-03-12 06:38:52 [190] #B373: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor charging. 2026-03-12 06:38:47 [204] #B372: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x0000002F, p3: 0x00000000, p4: 0x00000000) 2026-03-12 06:38:47 [595] #B371: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Controller serial numbers have been logged. (controller A: 00c0ff44588b0000, controller B: 00c0ff44576f0000) 2026-03-12 06:38:16 [056] #B370: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Storage Controller booted up (cold boot - power up). SC firmware version: VLS270R01-01 2026-03-12 06:36:33 [554] #B369: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 5V Loc: right-PSU, sensor status: OK, voltage: 5.08 V 2026-03-12 06:36:33 [554] #B368: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 12V Loc: right-PSU, sensor status: OK, voltage: 11.95 V 2026-03-12 06:36:33 [199] #B367: MSsupply recovered. 2026-03-12 06:36:33 [551] #B366: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a power supply. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) power supply RIGHT, power supply status: Good 2026-03-12 06:36:27 [175] #B365: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is down for controller B. 2026-03-12 06:36:27 [181] #B364: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 06:36:23 [557] #B363: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 5V Loc: right-PSU, sensor status: N/A, current: 1.67 A 2026-03-12 06:36:23 [557] #B362: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 12V Loc: right-PSU, sensor status: N/A, current: 4.61 A 2026-03-12 06:36:23 [554] #B361: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 3.3V Loc: right-PSU, sensor status: OK, voltage: 3.35 V 2026-03-12 06:36:18 [557] #B360: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 5V Loc: right-PSU, sensor status: N/A, current: 1.67 A 2026-03-12 06:36:18 [557] #B359: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 12V Loc: right-PSU, sensor status: N/A, current: 1.56 A2026-03-12 06:36:18 [554] #B358: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 3.3V Loc: right-PSU, sensor status: N/A, voltage: 3.36 V 2026-03-12 06:36:18 [554] #B357: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 5V Loc: right-PSU, sensor status: N/A, voltage: 3.7 V 2026-03-12 06:36:18 [554] #B356: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 12V Loc: right-PSU, sensor status: N/A, voltage: 8.8 V 2026-03-12 06:36:18 [198] #B355: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: power supply failed. 2026-03-12 06:36:18 [314] #B354: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR There is a problem with a FRU. (FRU type: A/C PSU, Right, enclosure: 1, product ID: 814665-001, SN: 7CE914T348, version: C1, related event serial number: B353, related event code: 551) 2026-03-12 06:36:18 [551] #B353: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a power supply. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) power supply RIGHT, power supply status: DC failure, AC failure 2026-03-12 06:35:07 [175] #B352: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is up for controller B. 2026-03-12 06:35:07 [181] #B351: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 06:34:56 [175] #B350: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is down for controller B. 2026-03-12 06:34:56 [181] #B349: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 06:04:15 [314] #B348: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR There is a problem with a FRU. (FRU type: Controller module A, enclosure: 1, product ID: 876127-001, SN: 7CE913M204, version: N/A, related event serial number: B347, related event code: 313) 2026-03-12 06:04:15 [313] #B347: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR RAID controller A failed, reason Non volatile device flush or restore failure. Product ID 876127-001, S/N 7CE913M204) 2026-03-12 06:02:18 [310] #B346: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 06:02:16 [310] #B345: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 06:02:15 [211] #B344: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 0, device PHYs: 3) 2026-03-12 06:02:14 [084] #B343: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Non volatile device flush or restore failure) 2026-03-12 06:01:27 [310] #B342: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 06:01:27 [211] #B341: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 47, expanders: 1, native levels: 0, partner levels: 1, device PHYs: 3) 2026-03-12 06:00:33 [081] #B340: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Kill was released (that is, the partner controller was allowed to boot up), automatic. 2026-03-12 06:00:16 [181] #B339: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 06:00:16 [139] #B338: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller booted up. MC firmware version: VXM270R001-01 2026-03-12 06:00:16 [363] #B337: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Firmware versions match those in the firmware bundle. (controller: B) 2026-03-12 06:00:03 [141] #B336: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller IP address changed. (new IP address: IP: 10.0.0.3/255.255.255.0/10.0.0.1) 2026-03-12 06:00:03 [181] #B335: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 06:00:02 [175] #B334: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is up for controller B. 2026-03-12 06:00:02 [181] #B333: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 05:59:35 [111] #B332: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 2, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-12 05:59:34 [111] #B331: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 1, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-12 05:59:34 [181] #B330: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 05:59:33 [310] #B329: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 05:59:32 [044] #B328: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Unwritable write-back cache data exists for a volume. (disk group: diskgroup1, volume: Vdisk, SN: 00c0ff44588b0000db63b55d01000000) It comprises 1% of cache space. 2026-03-12 05:59:32 [310] #B327: MSe data was completed following a rescan. 2026-03-12 05:59:32 [509] #B326: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR The metadata volume for a virtual pool went offline. Volume mappings and persistent reservations are inaccessible or lost. (pool: A, SN: 00c0ff44588b00009c63b55d01000000) 2026-03-12 05:59:31 [191] #B325: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor good. 2026-03-12 05:59:29 [077] #B324: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Write-back cache was initialized for controller A. Write-back data was found. 2026-03-12 05:59:27 [077] #B323: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Write-back cache was initialized for controller B. Write-back data was found. 2026-03-12 05:59:26 [112] #B322: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 4) 2026-03-12 05:59:26 [112] #B321: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 3) 2026-03-12 05:59:25 [112] #B320: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 2) 2026-03-12 05:59:25 [112] #B319: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 1) 2026-03-12 05:59:25 [485] #B318: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING A disk group was quarantined to prevent writing invalid data that may exist in the controller that logged this event. (disk group: diskgroup1, SN: 00c0ff44588b00009a63b55d00000000) 2026-03-12 05:59:25 [173] #B317: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL A disk group was dequarantined. (disk group: diskgroup1, SN: 00c0ff44588b00009a63b55d00000000) (disk group status: FTOL, mode: AUTO) 2026-03-12 05:59:20 [211] #B316: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 0, number of elements: 51, expanders: 1, native levels: 1, partner levels: 0, device PHYs: 3) 2026-03-12 05:59:17 [204] #B315: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x00000030, p3: 0x00000000, p4: 0x00000000) 2026-03-12 05:59:01 [084] #B314: MSle device flush or restore failure) 2026-03-12 05:58:58 [190] #B313: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor charging. 2026-03-12 05:58:53 [204] #B312: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x0000002F, p3: 0x00000000, p4: 0x00000000) 2026-03-12 05:58:53 [595] #B311: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Controller serial numbers have been logged. (controller A: 00c0ff44588b0000, controller B: 00c0ff44576f0000) 2026-03-12 05:58:22 [056] #B310: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Storage Controller booted up (cold boot - power up). SC firmware version: VLS270R01-01 2026-03-12 05:57:10 [557] #B309: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 5V Loc: left-PSU, sensor status: N/A, current: 1.67 A 2026-03-12 05:57:10 [557] #B308: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 12V Loc: left-PSU, sensor status: N/A 2026-03-12 05:57:10 [554] #B307: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 3.3V Loc: left-PSU, sensor status: N/A, voltage: 3.37 V 2026-03-12 05:57:10 [554] #B306: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 5V Loc: left-PSU, sensor status: N/A, voltage: 0.4 V 2026-03-12 05:57:10 [554] #B305: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a voltage senstlr A, sensor status: N/A, voltage: 3.2 V 2026-03-12 05:57:10 [198] #B304: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: power supply failed. 2026-03-12 05:57:10 [314] #B303: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR There is a problem with a FRU. (FRU type: A/C PSU, Left, enclosure: 1, product ID: 814665-001, SN: 7CE914T347, version: C1, related event serial number: B302, related event code: 551) 2026-03-12 05:57:10 [551] #B302: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a power supply. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) power supply LEFT, power supply status: DC failure, AC failure 2026-03-12 05:54:38 [111] #B301: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 1, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-12 05:49:10 [112] #B300: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Host link down. (port: 1) 2026-03-12 05:20:39 [111] #B299: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 2, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-12 05:20:14 [111] #B298: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 1, speed: 8 Gbps, point-to-point, external device(s)) 2026-03-12 05:20:10 [175] #B297: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is up for controller B. 2026-03-12 05:20:10 [181] #B296: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 05:18:08 [181] #B295: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 05:18:07 [314] #B294: MSller module A, enclosure: 1, product ID: 876127-001, SN: 7CE913M204, version: N/A, related event serial number: B293, related event code: 313) 2026-03-12 05:18:07 [313] #B293: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR RAID controller A failed, reason Non volatile device flush or restore failure. Product ID 876127-001, S/N 7CE913M204) 2026-03-12 05:17:50 [181] #B292: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 05:17:50 [139] #B291: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller booted up. MC firmware version: VXM270R001-01 2026-03-12 05:17:50 [363] #B290: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Firmware versions match those in the firmware bundle. (controller: B) 2026-03-12 05:17:35 [141] #B289: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller IP address changed. (new IP address: IP: 10.0.0.3/255.255.255.0/10.0.0.1) 2026-03-12 05:17:35 [181] #B288: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2026-03-12 05:17:06 [310] #B287: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 05:17:06 [071] #B286: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Failover completed. (failed or shutdown controller: A) 2026-03-12 05:17:06 [044] #B285: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Unwritable write-back cache data exists for a volume. (disk group: unknown name, volume: unknown name, SN: 00c0ff44588b0000db63b55d01000000) It comprises 1% of cache space. 2026-03-12 05:17:05 [509] #B284: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR The metadata volume for a virtual pool went offline. Volume mappings and persistent reservations are inaccessible or lost. (pool: A, SN: 00c0ff44588b00009c63b55d01000000) 2026-03-12 05:17:05 [191] #B283: MSapacitor good. 2026-03-12 05:17:05 [202] #B282: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through: Write-Back cache was re-enabled. 2026-03-12 05:17:05 [310] #B281: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2026-03-12 05:17:04 [044] #B280: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Unwritable write-back cache data exists for a volume. (disk group: diskgroup1, volume: Vdisk, SN: 00c0ff44588b0000db63b55d01000000) It comprises 74% of cache space. 2026-03-12 05:17:04 [044] #B279: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Unwritable write-back cache data exists for a volume. (disk group: diskgroup1, volume: A, SN: 00c0ff44588b00009c63b55d01000000) It comprises 1% of cache space. 2026-03-12 05:17:03 [077] #B278: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Write-back cache was initialized for controller A. Write-back data was found. 2026-03-12 05:17:03 [019] #B277: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL A rescan-bus operation was done. (number of disks that were found: 2, number of enclosures that were found: 1) (rescan reason: initiated by internal logic, rescan reason code: 2) 2026-03-12 05:17:03 [485] #B276: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING A disk group was quarantined to prevent writing invalid data that may exist in the controller that logged this event. (disk group: diskgroup1, SN: 00c0ff44588b00009a63b55d00000000) 2026-03-12 05:17:03 [071] #B275: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Failover was initiated. (failed or shutdown controller: A) 2026-03-12 05:17:03 [188] #B274: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Write-back cache was disabled. 2026-03-12 05:17:01 [077] #B273: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Write-back cache was initialized for controller B. Write-back data was found. 2026-03-12 05:17:00 [112] #B272: MS2026-03-12 05:16:59 [112] #B271: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 3) 2026-03-12 05:16:59 [112] #B270: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 2) 2026-03-12 05:16:59 [112] #B269: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 1) 2026-03-12 05:16:54 [211] #B268: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 0, number of elements: 51, expanders: 1, native levels: 1, partner levels: 0, device PHYs: 3) 2026-03-12 05:16:53 [190] #B267: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor charging. 2026-03-12 05:16:51 [204] #B266: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x00000030, p3: 0x00000000, p4: 0x00000000) 2026-03-12 05:16:34 [084] #B265: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Killed partner controller. (reason: Non volatile device flush or restore failure) 2026-03-12 05:16:28 [204] #B264: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x0000002F, p3: 0x00000000, p4: 0x00000000) 2026-03-12 05:16:28 [595] #B263: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Controller serial numbers have been logged. (controller A: 00c0ff44588b0000, controller B: 00c0ff44576f0000) 2026-03-12 05:15:57 [056] #B262: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Storage Controller booted up (cold boot - power up). SC firmware version: VLS270R01-01 2025-01-27 09:15:16 [033] #B261: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Date/time was changed to 2025-01-27 09:14:30. 2023-09-16 14:59:22 [033] #B260: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Date/time was changed to 2023-09-16 15:02:49. 2023-09-16 00:36:10 [111] #B259: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 1, speed: 8 Gbps, point-to-point, external device(s)) 2023-09-16 00:29:32 [112] #B258: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Host link down. (port: 1) 2023-09-15 21:49:02 [175] #B257: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is up for controller B. 2023-09-15 21:49:02 [181] #B256: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2023-09-15 21:44:01 [175] #B255: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is down for controller B. 2023-09-15 21:44:01 [181] #B254: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2022-10-03 10:51:12 [175] #B253: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is up for controller B. 2022-10-03 10:51:12 [181] #B252: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2022-10-03 10:48:32 [175] #B251: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is down for controller B. 2022-10-03 10:48:32 [181] #B250: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2022-07-18 13:07:11 [033] #B249: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Date/time was changed to 2022-07-18 13:11:54. 2021-11-11 10:14:02 [141] #B248: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller IP address changed. (new IP address: IP: 172.16.50.4/255.255.255.0/172.16.50.253) 2021-11-11 10:14:02 [181] #B247: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2021-11-11 10:14:01 [141] #B246: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller IP address changed. (new IP address: IP: 10.0.0.3/255.255.255.0/10.0.0.1) 2021-11-11 10:14:01 [181] #B245: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2021-11-11 10:12:10 [141] #B244: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller IP address changed. (new IP address: IP: 172.16.50.4/255.255.255.0/172.16.50.253) 2021-11-11 10:12:10 [181] #B243: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2021-11-11 10:12:10 [141] #B242: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller IP address changed. (new IP address: IP: 10.0.0.3/255.255.255.0/10.0.0.1) 2021-11-11 10:12:10 [181] #B241: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2021-09-01 13:58:48 [175] #B240: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is up for controller B. 2021-09-01 13:58:48 [181] #B239: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2021-09-01 13:54:48 [175] #B238: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is down for controller B. 2021-09-01 13:54:48 [181] #B237: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2021-05-27 14:46:54 [141] #B236: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller IP address changed. (new IP address: IP: 172.16.50.4/255.255.255.0/172.16.50.253) 2021-05-27 14:46:54 [181] #B235: MSmeters were set. 2021-05-27 14:46:54 [141] #B234: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller IP address changed. (new IP address: IP: 10.0.0.3/255.255.255.0/10.0.0.1) 2021-05-27 14:46:54 [181] #B233: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2021-05-27 14:45:03 [141] #B232: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller IP address changed. (new IP address: IP: 172.16.50.4/255.255.255.0/172.16.50.253) 2021-05-27 14:45:03 [181] #B231: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2021-05-27 14:45:02 [141] #B230: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller IP address changed. (new IP address: IP: 10.0.0.3/255.255.255.0/10.0.0.1) 2021-05-27 14:45:02 [181] #B229: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2021-05-27 14:39:37 [141] #B228: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller IP address changed. (new IP address: IP: 172.16.50.4/255.255.255.0/172.16.50.253) 2021-05-27 14:39:37 [181] #B227: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2021-05-27 14:08:29 [111] #B226: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 2, speed: 8 Gbps, point-to-point, external device(s)) 2021-05-27 13:59:57 [111] #B225: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 1, speed: 8 Gbps, point-to-point, external device(s)) 2021-05-27 13:30:06 [175] #B224: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is up for controller B. 2021-05-27 13:30:06 [181] #B223: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2021-05-27 13:27:58 [181] #B222: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2021-05-27 13:27:58 [139] #B221: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller booted up. MC firmware version: VXM270R001-01 2021-05-27 13:27:58 [363] #B220: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Firmware versions match those in the firmware bundle. (controller: B) 2021-05-27 13:27:43 [141] #B219: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller IP address changed. (new IP address: IP: 10.0.0.3/255.255.255.0/10.0.0.1) 2021-05-27 13:27:43 [181] #B218: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2021-05-27 13:27:29 [181] #B217: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2021-05-27 13:27:16 [310] #B216: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2021-05-27 13:27:15 [191] #B215: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor good. 2021-05-27 13:27:15 [202] #B214: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through: Write-Back cache was re-enabled. 2021-05-27 13:27:15 [310] #B213: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2021-05-27 13:27:15 [073] #B212: MSAcontroller. This indicates that the partner controller is operational. 2021-05-27 13:27:12 [077] #B211: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Write-back cache was initialized for controller B. Write-back data was found. 2021-05-27 13:27:11 [195] #B210: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: partner processor recovered. 2021-05-27 13:27:09 [112] #B209: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 4) 2021-05-27 13:27:09 [112] #B208: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 3) 2021-05-27 13:27:09 [112] #B207: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 2) 2021-05-27 13:27:09 [112] #B206: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 1) 2021-05-27 13:26:49 [211] #B205: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 54, expanders: 1, native levels: 0, partner levels: 1, device PHYs: 3) 2021-05-27 13:26:49 [211] #B204: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 0, number of elements: 54, expanders: 1, native levels: 1, partner levels: 0, device PHYs: 3) 2021-05-27 13:26:48 [190] #B203: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor charging. 2021-05-27 13:26:41 [204] #B202: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x00000030, p3: 0x00000000, p4: 0x00000000) 2021-05-27 13:26:40 [204] #B201: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x0000002F, p3: 0x00000000, p4: 0x00000000) 2021-05-27 13:26:40 [595] #B200: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Controller serial numbers have been logged. (controller A: 00c0ff44588b0000, controller B: 00c0ff44576f0000) 2021-05-27 13:26:10 [056] #B199: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Storage Controller booted up (cold boot - power up). SC firmware version: VLS22021-05-27 13:06:56 [068] #B198: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Both controllers have shut down; no restart 2021-05-27 13:06:56 [083] #B197: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Partner controller changed state. (new state: Shutdown) 2021-05-27 12:59:51 [112] #B196: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Host link down. (port: 2) 2020-11-28 10:06:40 [181] #B195: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2020-11-28 10:06:40 [139] #B194: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller booted up. MC firmware version: VXM270R001-01 2020-11-28 10:06:40 [363] #B193: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Firmware versions match those in the firmware bundle. (controller: B) 2020-11-28 10:06:25 [141] #B192: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller IP address changed. (new IP address: IP: 172.16.50.4/255.255.255.0/172.16.50.253) 2020-11-28 10:06:25 [181] #B191: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2020-11-28 10:06:24 [175] #B190: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is up for controller B. 2020-11-28 10:06:24 [181] #B189: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2020-11-28 10:06:10 [181] #B188: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2020-11-28 10:06:01 [111] #B187: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 1, speed: 8 Gbps, point-to-point, external device(s)) 2020-11-28 10:06:01 [111] #B186: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 2, speed: 8 Gbps, point-to-point, external device(s)) 2020-11-28 10:05:58 [072] #B185: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Recovery completed for controller B. 2020-11-28 10:05:55 [077] #B184: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Write-back cache was initialized for controller B. Write-back data was found. 2020-11-28 10:05:55 [072] #B183: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Recovery was initiated for controller B. 2020-11-28 10:05:51 [310] #B182: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2020-11-28 10:05:51 [191] #B181: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor good. 2020-11-28 10:05:51 [202] #B180: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through: Write-Back cache was re-enabled. 2020-11-28 10:05:49 [310] #B179: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2020-11-28 10:05:49 [073] #B178: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Heartbeat was detected from the partner controller. This indicates that the partner controller is operational. 2020-11-28 10:05:48 [195] #B177: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: partner processor recovered. 2020-11-28 10:05:48 [188] #B176: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Write-back cache was disabled. 2020-11-28 10:05:46 [112] #B175: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 4) 2020-11-28 10:05:46 [112] #B174: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 3) 2020-11-28 10:05:46 [112] #B173: MS2020-11-28 10:05:45 [112] #B172: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 1) 2020-11-28 10:05:37 [211] #B171: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 54, expanders: 1, native levels: 0, partner levels: 1, device PHYs: 3) 2020-11-28 10:05:35 [211] #B170: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 0, number of elements: 54, expanders: 1, native levels: 1, partner levels: 0, device PHYs: 3) 2020-11-28 10:05:32 [204] #B169: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x00000030, p3: 0x00000000, p4: 0x00000000) 2020-11-28 10:05:13 [190] #B168: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor charging. 2020-11-28 10:05:09 [204] #B167: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x0000002F, p3: 0x00000000, p4: 0x00000000) 2020-11-28 10:05:09 [595] #B166: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Controller serial numbers have been logged. (controller A: 00c0ff44588b0000, controller B: 00c0ff44576f0000) 2020-11-28 10:04:39 [056] #B165: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Storage Controller booted up (warm boot - kill was released or a reset occurred). SC firmware version: VLS270R01-01 2020-11-28 10:02:29 [107] #B164: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR Critical Error: OSMEnterDebugger p1: 0x03A6F33, p2: 0x04C9074, p3: 0x02C2349, p4: 0x02C23F8 CThr: Null, DbgRegNum=255 2019-12-29 10:55:34 [554] #B163: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 5V Loc: left-PSU, sensor status: OK, voltage: 5.01 V 2019-12-29 10:55:34 [554] #B162: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Capacitor Cell 4 Voltage-Ctlr A, sensor status: OK, voltag2019-12-29 10:55:34 [199] #B161: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: power supply recovered. 2019-12-29 10:55:34 [551] #B160: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a power supply. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) power supply LEFT, power supply status: Good 2019-12-29 10:55:29 [557] #B159: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 5V Loc: left-PSU, sensor status: N/A, current: 1.67 A 2019-12-29 10:55:29 [557] #B158: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 12V Loc: left-PSU, sensor status: N/A, current: 1.2 A 2019-12-29 10:55:29 [554] #B157: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 3.3V Loc: left-PSU, sensor status: OK, voltage: 3.36 V 2019-12-29 10:38:39 [557] #B156: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 5V Loc: left-PSU, sensor status: N/A, current: 1.67 A 2019-12-29 10:38:39 [557] #B155: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 12V Loc: left-PSU, sensor status: N/A 2019-12-29 10:38:39 [554] #B154: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 3.3V Loc: left-PSU, sensor status: N/A, voltage: 3.38 V2019-12-29 10:38:39 [554] #B153: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 5V Loc: left-PSU, sensor status: N/A, voltage: 0.36 V 2019-12-29 10:38:39 [554] #B152: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Capacitor Cell 4 Voltage-Ctlr A, sensor status: N/A, voltage: 3.16 V 2019-12-29 10:38:39 [198] #B151: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: power supply failed. 2019-12-29 10:38:39 [314] #B150: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR There is a problem with a FRU. (FRU type: A/C PSU, Left, enclosure: 1, product ID: 814665-001, SN: 7CE914T347, version: C1, related event serial number: B149, related event code: 551) 2019-12-29 10:38:39 [551] #B149: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a power supply. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) power supply LEFT, power supply status: DC failure, AC failure 2019-12-29 10:37:09 [557] #B148: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 5V Loc: right-PSU, sensor status: N/A, current: 1.67 A 2019-12-29 10:37:09 [557] #B147: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 12V Loc: right-PSU, sensor status: N/A, current: 6.81 A 2019-12-29 10:37:09 [554] #B146: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 3.3V Loc: right-PSU, sensor status: OK, voltage: 2019-12-29 10:37:09 [554] #B145: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 5V Loc: right-PSU, sensor status: OK, voltage: 4.87 V 2019-12-29 10:37:09 [554] #B144: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 12V Loc: right-PSU, sensor status: OK, voltage: 11.62 V 2019-12-29 10:37:09 [199] #B143: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: power supply recovered. 2019-12-29 10:37:09 [551] #B142: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a power supply. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) power supply RIGHT, power supply status: Good 2019-12-29 10:25:09 [557] #B141: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 5V Loc: right-PSU, sensor status: N/A, current: 1.67 A 2019-12-29 10:25:09 [557] #B140: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 12V Loc: right-PSU, sensor status: N/A, current: 2.3 A 2019-12-29 10:25:09 [554] #B139: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 3.3V Loc: right-PSU, sensor status: N/A, voltage: 3.37 V 2019-12-29 10:25:09 [554] #B138: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 5V Loc: right-PSU, sensor status: N/A, voltage: 3.42 V 2019-12-29 10:25:09 [554] #B137: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 12V Loc: right-PSU, sensor status: N/A, voltage: 8.24 V 2019-12-29 10:25:09 [198] #B136: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: power supply failed. 2019-12-29 10:25:09 [314] #B135: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR There is a problem with a FRU. (FRU type: A/C PSU, Right, enclosure: 1, product ID: 814665-001, SN: 7CE914T348, version: C1, related event serial number: B134, related event code: 551) 2019-12-29 10:25:09 [551] #B134: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a power supply. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) power supply RIGHT, power supply status: DC failure, AC failure 2019-10-28 09:41:28 [111] #B133: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 1, speed: 8 Gbps, point-to-point, external device(s)) 2019-10-28 09:41:13 [112] #B132: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Host link down. (port: 1) 2019-10-27 14:16:04 [111] #B131: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 2, speed: 8 Gbps, point-to-point, external device(s)) 2019-10-27 14:07:15 [112] #B130: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Host link down. (port: 2) 2019-10-27 14:06:57 [111] #B129: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 1, speed: 8 Gbps, point-to-point, external device(s)) 2019-10-27 14:05:51 [112] #B128: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Host link down. (port: 1) 2019-10-27 14:03:05 [111] #B127: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 1, speed: 8 Gbps, point-to-point, external device(s)) 2019-10-27 14:02:40 [111] #B126: MSoint-to-point, external device(s)) 2019-10-27 14:01:54 [112] #B125: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Host link down. (port: 1) 2019-10-27 13:58:24 [112] #B124: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Host link down. (port: 2) 2019-10-27 13:52:12 [111] #B123: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 2, speed: 8 Gbps, point-to-point, external device(s)) 2019-10-27 13:52:07 [112] #B122: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING Host link down. (port: 2) 2019-10-27 13:52:01 [111] #B121: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 2, speed: 8 Gbps, point-to-point, external device(s)) 2019-10-27 13:18:59 [111] #B120: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link up. (port: 1, speed: 8 Gbps, point-to-point, external device(s)) 2019-10-27 13:17:51 [141] #B119: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller IP address changed. (new IP address: IP: 172.16.50.4/255.255.255.0/172.16.50.253) 2019-10-27 13:17:51 [181] #B118: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2019-10-27 13:17:31 [175] #B117: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is up for controller B. 2019-10-27 13:17:31 [181] #B116: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2019-10-27 13:17:21 [175] #B115: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is down for controller B. 2019-10-27 13:17:21 [181] #B114: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2019-10-27 13:15:01 [175] #B113: MS controller B. 2019-10-27 13:15:01 [181] #B112: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2019-10-27 13:13:49 [554] #B111: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 5V Loc: left-PSU, sensor status: OK, voltage: 5.06 V 2019-10-27 13:13:49 [554] #B110: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Capacitor Cell 4 Voltage-Ctlr A, sensor status: OK, voltage: 11.93 V 2019-10-27 13:13:49 [199] #B109: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: power supply recovered. 2019-10-27 13:13:49 [551] #B108: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a power supply. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) power supply LEFT, power supply status: Good 2019-10-27 13:13:44 [557] #B107: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 5V Loc: left-PSU, sensor status: N/A, current: 1.67 A 2019-10-27 13:13:44 [557] #B106: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 12V Loc: left-PSU, sensor status: N/A, current: 2.91 A 2019-10-27 13:13:44 [554] #B105: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 3.3V Loc: left-PSU, sensor status: OK, voltage: 32019-10-27 13:13:24 [181] #B104: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2019-10-27 13:12:48 [181] #B103: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2019-10-27 13:12:48 [139] #B102: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller booted up. MC firmware version: VXM270R001-01 2019-10-27 13:12:48 [363] #B101: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Firmware versions match those in the firmware bundle. (controller: B) 2019-10-27 13:12:36 [141] #B100: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller IP address changed. (new IP address: IP: 10.0.0.3/255.255.255.0/10.0.0.1) 2019-10-27 13:12:36 [181] #B99: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2019-10-27 13:12:03 [557] #B98: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 5V Loc: left-PSU, sensor status: N/A, current: 1.67 A 2019-10-27 13:12:03 [557] #B97: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 12V Loc: left-PSU, sensor status: N/A 2019-10-27 13:12:03 [554] #B96: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 3.3V Loc: left-PSU, sensor status: N/A, voltage: 3.34 V 2019-10-27 13:12:03 [554] #B95: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensoensor status: N/A, voltage: 0.22 V 2019-10-27 13:12:03 [554] #B94: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Capacitor Cell 4 Voltage-Ctlr A, sensor status: N/A, voltage: 3.2 V 2019-10-27 13:12:03 [198] #B93: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: power supply failed. 2019-10-27 13:12:03 [314] #B92: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR There is a problem with a FRU. (FRU type: A/C PSU, Left, enclosure: 1, product ID: 814665-001, SN: 7CE914T347, version: C1, related event serial number: B91, related event code: 551) 2019-10-27 13:12:03 [551] #B91: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a power supply. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) power supply LEFT, power supply status: DC failure, AC failure 2019-10-27 13:11:58 [310] #B90: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2019-10-27 13:11:58 [191] #B89: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor good. 2019-10-27 13:11:58 [202] #B88: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through: Write-Back cache was re-enabled. 2019-10-27 13:11:57 [310] #B87: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2019-10-27 13:11:56 [073] #B86: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Heartbeat was detected from the partner controller. This indicates that the partner controller is operational. 2019-10-27 13:11:52 [077] #B85: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Write-back cache was initialized for controller B. Write-back data was found. 2019-10-27 13:11:51 [195] #B84: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: partner processor recovered. 2019-10-27 13:11:49 [112] #B83: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 4) 2019-10-27 13:11:48 [112] #B82: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 3) 2019-10-27 13:11:48 [112] #B81: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 2) 2019-10-27 13:11:48 [112] #B80: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 1) 2019-10-27 13:11:29 [211] #B79: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 54, expanders: 1, native levels: 0, partner levels: 1, device PHYs: 3) 2019-10-27 13:11:29 [211] #B78: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 0, number of elements: 54, expanders: 1, native levels: 1, partner levels: 0, device PHYs: 3) 2019-10-27 13:11:29 [190] #B77: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: supercapacitor charging. 2019-10-27 13:11:21 [204] #B76: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x00000030, p3: 0x00000000, p4: 0x00000000) 2019-10-27 13:11:20 [204] #B75: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x0000002F, p3: 0x00000000, p4: 0x00000000) 2019-10-27 13:11:20 [595] #B74: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Controller serial numbers have been logged. (controller A: 00c0ff44588b0000, controller B: 00c0ff44576f0000) 2019-10-27 13:10:49 [056] #B73: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Storage Controller booted up (cold boot - power up). SC firmware version: VLS270R01-01 2019-10-27 12:57:19 [068] #B72: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Both controllers have shut down; no restart 2019-10-27 12:56:33 [175] #B71: MSAr controller B. 2019-10-27 12:56:33 [181] #B70: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2019-10-27 10:45:48 [554] #B69: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 5V Loc: right-PSU, sensor status: OK, voltage: 5.06 V 2019-10-27 10:45:48 [554] #B68: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 12V Loc: right-PSU, sensor status: OK, voltage: 11.94 V 2019-10-27 10:45:48 [199] #B67: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: power supply recovered. 2019-10-27 10:45:48 [551] #B66: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a power supply. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) power supply RIGHT, power supply status: Good 2019-10-27 10:45:43 [557] #B65: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 5V Loc: right-PSU, sensor status: N/A, current: 1.67 A 2019-10-27 10:45:43 [557] #B64: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 12V Loc: right-PSU, sensor status: N/A, current: 4.25 A 2019-10-27 10:45:43 [554] #B63: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 3.3V Loc: right-PSU, sensor status: OK, voltage: 32019-10-27 10:44:48 [557] #B62: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 5V Loc: right-PSU, sensor status: N/A, current: 1.67 A 2019-10-27 10:44:48 [557] #B61: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 12V Loc: right-PSU, sensor status: N/A, current: 0.47 A 2019-10-27 10:44:48 [554] #B60: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 3.3V Loc: right-PSU, sensor status: N/A, voltage: 3.36 V 2019-10-27 10:44:48 [554] #B59: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 5V Loc: right-PSU, sensor status: N/A, voltage: 2.22 V 2019-10-27 10:44:48 [554] #B58: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 12V Loc: right-PSU, sensor status: N/A, voltage: 5.92 V 2019-10-27 10:44:48 [198] #B57: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: power supply failed. 2019-10-27 10:44:48 [314] #B56: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR There is a problem with a FRU. (FRU type: A/C PSU, Right, enclosure: 1, product ID: 814665-001, SN: 7CE914T348, version: C1, related event serial number: B55, related event code: 551) 2019-10-27 10:44:48 [551] #B55: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a power supply. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) power supply RIGHT, power supply status: DC failure, AC failure 2019-10-27 09:36:23 [465] #B54: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL An unsupported cable or SFP was removed from a Fibre Channel port. (host port: 1) 2019-10-27 09:30:02 [019] #B53: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL A rescan-bus operation was done. (number of disks that were found: 2, number of enclosures that were found: 1) (rescan reason: initiated by internal logic, rescan reason code: 4) 2019-10-27 09:28:33 [310] #B52: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2019-10-27 09:28:18 [211] #B51: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 54, expanders: 1, native levels: 0, partner levels: 1, device PHYs: 3) 2019-10-27 09:28:18 [211] #B50: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 0, number of elements: 54, expanders: 1, native levels: 1, partner levels: 0, device PHYs: 3) 2019-10-27 09:28:13 [310] #B49: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2019-10-27 09:28:13 [211] #B48: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 52, expanders: 1, native levels: 0, partner levels: 1, device PHYs: 2) 2019-10-27 09:28:13 [211] #B47: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 0, number of elements: 52, expanders: 1, native levels: 1, partner levels: 0, device PHYs: 2) 2019-10-27 09:24:49 [554] #B46: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 5V Loc: right-PSU, sensor status: OK, voltage: 5.06 V 2019-10-27 09:24:49 [199] #B45: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: power supply recovered. 2019-10-27 09:24:49 [551] #B44: MSAed an alert condition on a power supply. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) power supply RIGHT, power supply status: Good 2019-10-27 09:24:44 [557] #B43: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 5V Loc: right-PSU, sensor status: N/A, current: 1.67 A 2019-10-27 09:24:44 [557] #B42: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 12V Loc: right-PSU, sensor status: N/A, current: 6.57 A 2019-10-27 09:24:44 [554] #B41: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 3.3V Loc: right-PSU, sensor status: OK, voltage: 3.36 V 2019-10-27 09:24:44 [554] #B40: MSA 2050 SAN Array SN#00C0FF44576F Controller B RESOLVED An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: resolved. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 12V Loc: right-PSU, sensor status: OK, voltage: 11.54 V 2019-10-27 09:18:29 [141] #B39: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller IP address changed. (new IP address: IP: 172.16.9.15/255.255.255.0/172.16.9.253) 2019-10-27 09:18:29 [181] #B38: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2019-10-27 09:18:19 [175] #B37: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The network-port Ethernet link is up for controller B. 2019-10-27 09:18:19 [181] #B36: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2019-10-27 09:11:35 [181] #B35: MSAeters were set. 2019-10-27 09:10:57 [181] #B34: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2019-10-27 09:10:56 [139] #B33: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller booted up. MC firmware version: VXM270R001-01 2019-10-27 09:10:56 [363] #B32: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Firmware versions match those in the firmware bundle. (controller: B) 2019-10-27 09:10:43 [141] #B31: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The Management Controller IP address changed. (new IP address: IP: 10.0.0.3/255.255.255.0/10.0.0.1) 2019-10-27 09:10:43 [181] #B30: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Management Controller configuration parameters were set. 2019-10-27 09:10:19 [557] #B29: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 5V Loc: right-PSU, sensor status: N/A, current: 1.67 A 2019-10-27 09:10:19 [557] #B28: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a current sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) current sensor for Current 12V Loc: right-PSU, sensor status: N/A 2019-10-27 09:10:19 [554] #B27: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 3.3V Loc: right-PSU, sensor status: N/A, voltage: 3.34 V 2019-10-27 09:10:19 [554] #B26: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 5V Loc: right-PSU, sensor status: N/A, voltage: 0.22 V 2019-10-27 09:10:19 [554] #B25: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a voltage sensor. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) voltage sensor for Voltage 12V Loc: right-PSU, sensor status: N/A, voltage: 3.19 V 2019-10-27 09:10:19 [198] #B24: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: power supply failed. 2019-10-27 09:10:19 [314] #B23: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR There is a problem with a FRU. (FRU type: A/C PSU, Right, enclosure: 1, product ID: 814665-001, SN: 7CE914T348, version: C1, related event serial number: B22, related event code: 551) 2019-10-27 09:10:19 [551] #B22: MSA 2050 SAN Array SN#00C0FF44576F Controller B ERROR An Enclosure Management Processor (EMP) reported an alert condition on a power supply. Type: fault. (enclosure: 1, WWN: 500C0FF044597D3C) power supply RIGHT, power supply status: DC failure, AC failure 2019-10-27 09:10:15 [310] #B21: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2019-10-27 09:10:14 [464] #B20: MSA 2050 SAN Array SN#00C0FF44576F Controller B WARNING An unsupported SFP was detected. The SFP is not compatible with this system. You must use an SFP that is qualified for use in this system. (host port: 1) 2019-10-27 09:10:13 [310] #B19: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Discovery and initialization of enclosure data was completed following a rescan. 2019-10-27 09:10:10 [073] #B18: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Heartbeat was detected from the partner controller. This indicates that the partner controller is operational. 2019-10-27 09:10:06 [077] #B17: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Write-back cache was initialized for controller B. Write-back data was found. 2019-10-27 09:10:05 [195] #B16: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through trigger event: partner processor recovered. 2019-10-27 09:10:05 [202] #B15: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Auto-write-through: Write-Back cache was re-enabled. 2019-10-27 09:10:04 [112] #B14: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 4) 2019-10-27 09:10:03 [112] #B13: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 3) 2019-10-27 09:10:03 [112] #B12: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 2) 2019-10-27 09:10:03 [112] #B11: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Host link down. (port: 1) 2019-10-27 09:10:02 [080] #B10: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The configuration of one or more disks was changed. (changed parameter: Initiator response timeout, new setting: enabled, number of disks changed: 1, total number of disks: 2) 2019-10-27 09:10:02 [080] #B9: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The configuration of one or more disks was changed. (changed parameter: SMART support, new setting: enabled, number of disks changed: 1, total number of disks: 2) 2019-10-27 09:10:02 [080] #B8: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The configuration of one or more disks was changed. (changed parameter: Write-back cache, new setting: disabled, number of disks changed: 1, total number of disks: 2) 2019-10-27 09:09:42 [211] #B7: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 1, number of elements: 54, expanders: 1, native levels: 0, partner levels: 1, device PHYs: 3) 2019-10-27 09:09:42 [211] #B6: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The SAS topology changed (hardware components were added or removed). (Channel: 0, number of elements: 54, expanders: 1, native levels: 1, partner levels: 0, device PHYs: 3) 2019-10-27 09:09:34 [204] #B5: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x00000030, p3: 0x00000000, p4: 0x00000000) 2019-10-27 09:09:33 [204] #B4: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL The system has come up normally and the NV device is in a normal expected state. (p1: 0x00000000, p2: 0x0000002F, p3: 0x00000000, p4: 0x00000000) 2019-10-27 09:09:33 [595] #B3: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Controller serial numbers have been logged. (controller A: 00c0ff44588b0000, co2019-10-27 09:09:11 [056] #B2: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Storage Controller booted up (cold boot - power up). SC firmware version: VLS270R01-01 2019-05-08 06:58:21 [068] #B1: MSA 2050 SAN Array SN#00C0FF44576F Controller B INFORMATIONAL Both controllers have shut down; no restart Success: Command completed successfully. (2026-03-15 15:49:11) #