Sugon DS900 disk 亮红灯 -->解决方法

Sugon DS900 控制器 失败 (Sugon DS900 Controller Failuty)-->解决方法

Sugon DS900 前面板 惊叹号 亮红灯 -->解决方法

Sugon DS900 控制器 惊叹号 亮红灯    -->解决方法

Sugon DS900 控制器 OK状态灯 不亮灯     -->解决方法

Sugon DS900 Service Processor Unknown 惊叹号 亮红灯  -->解决方法

Sugon DS900 Service Processor Unknown OK状态灯 不亮灯   -->解决方法

Sugon DS900 控制器 B 惊叹号 亮红灯  -->解决方法

Sugon DS900 控制器 B OK状态灯 不亮灯   -->解决方法

Sugon DS900 Service Processor Unknown CACHE 亮红灯   -->解决方法

Sugon DS900 控制器 B CACHE 亮红灯   -->解决方法

Sugon DS900 前面板 惊叹号 亮红灯    -->解决方法

Sugon DS900 Service Processor SPA 亮红灯         -->解决方法
Sugon DS900 Service Processor SPA 前面 亮红灯    -->解决方法
Sugon DS900 Service Processor SPA 后面 亮红灯    -->解决方法

Sugon DS900 Service Processor SPB 亮红灯         -->解决方法
Sugon DS900 Service Processor SPB 前面 亮红灯    -->解决方法
Sugon DS900 Service Processor SPB 后面 亮红灯    -->解决方法

LOADER-A>sp status
Firmware Version 5.3
Ethernet Lin: up,full duplex,auto-neg complete
Mgmt MAC Address:
IPv4 setting 
Using DHCP: yes
IP Address: unknown
Netmask:    unknown
Gateway:    unknown
IPv6:       Disabled

        Service Processor           Status: Unknown
                                      IPMI: unknown
                                       PKT: unknown

[cluster:mcc.config.bootConfigNotRead:ALERT]: Configuration could not be read from persistent storage due 
to internal error Failed to retrieve persistent storage (MBX) due to no mailbox disks being found. 
The system will try to retrieve 
or set the configuration automatically later, during boot. 

disk:L#: rtID/plx/rgid/rgdn nplx/ngrp/ndsk/tot gen/time shtdwn vnm
[cluster:raid.assim.tree.noRootVol:error]: No usable root volume was found! 
Halting node. Ensure healing of DR root aggregates has been performed and has completed successfully
 before booting this node.

WARNING: Neither label appeared to be valid, the labels may be corrupt.
0a.00.20:  :Invalid Label!

聚合： aggro_cluster2
磁盘信息  卷 性能
状态：  offline(脱机)
节点:   cluster
RAID配置 raid_dp数据
RAID状态: mirrored,normal
根： 否
卷数：
分配磁盘：
snaplock:已禁用
聚合snapMirror： 已使用
聚合类型： 标准
Flash Pool: 不使用
文件：  0
64位聚合： 是

聚合： aggro_cluster2
磁盘信息  卷 性能
状态：  offline(脱机)
节点:   cluster
RAID配置 raid_dp数据
RAID状态: mirrored,normal
根： 否
卷数：
分配磁盘：
snaplock:已禁用
聚合snapMirror： 已使用
聚合类型： 标准
Flash Pool: 不使用
文件：  0
64位聚合： 是

Sugon DS900 控制器 失败 (Sugon DS900 Controller Unknown)-->解决方法

Sugon DS900 错误代码： 

Sugon DS900  控制器 Unknown; -->解决方法
Sugon DS900  存储池 Unknown; -->解决方法

Sugon DS900  cluster node1 offline  -->解决方法
Sugon DS900  cluster node2 offline  -->解决方法
Sugon DS900  cluster node3 offline  -->解决方法
Sugon DS900  cluster node4 offline  -->解决方法

Sugon DS900  raid_dp offline  -->解决方法

Sugon DS900  RAID5已降级;
Sugon DS900  RAID6已降级;
Sugon DS900  RAID1已降级;
Sugon DS900  驱动器SAS错误;
Sugon DS900  Disk0 亮红灯 错误;
Sugon DS900  Disk1 亮红灯 错误;
Sugon DS900  Disk2 亮红灯 错误;
Sugon DS900  Disk3 亮红灯 错误;
Sugon DS900  Disk4 亮红灯 错误;
Sugon DS900  Disk5 亮红灯 错误;
Sugon DS900  Disk6 亮红灯 错误;
Sugon DS900  Disk7 亮红灯 错误;
Sugon DS900  Disk8 亮红灯 错误;
Sugon DS900  Disk9 亮红灯 错误;
Sugon DS900  Disk10 亮红灯 错误;
Sugon DS900  Disk11 亮红灯 错误;

Sugon DS900  光纤通道端口不能正常工作;

Sugon DS900  光纤通道I/O端口未正常工作;

Sugon DS900 cluster node1 ping 不通管理地址
Sugon DS900 cluster node2 ping 不通管理地址
Sugon DS900 cluster node3 ping 不通管理地址
Sugon DS900 cluster node4 ping 不通管理地址
Sugon DS900  ping 不通管理地址
Sugon DS900  SPA ping 不通管理地址
Sugon DS900  SPB ping 不通管理地址
Sugon DS900  Mgmt ping 不通管理地址
Sugon DS900  http://ip   管理界面打不开
Sugon DS900  https://ip   管理界面打不开
Sugon DS900  login   管理界面登录不进去
Sugon DS900  串口登录不上  
Sugon DS900  串口登录无任何显示

Sugon DS900 疑难问题-->解决方法

ONTAP 9 无法启动

NetApp Data ONTAP 9.16.0P1   无法启动  -->疑难问题-->解决方法
NetApp Data ONTAP 9.15.16P3  无法启动  -->疑难问题-->解决方法
NetApp Data ONTAP 9.14.16P9  无法启动  -->疑难问题-->解决方法
NetApp Data ONTAP 9.13.1P12  无法启动  -->疑难问题-->解决方法
NetApp Data ONTAP 9.12.1P15  无法启动  -->疑难问题-->解决方法

NetApp Data ONTAP 9.11.1P17 无法启动   -->疑难问题-->解决方法
NetApp Data ONTAP 9.9.1P20  无法启动   -->疑难问题-->解决方法
NetApp Data ONTAP 9.8P21    无法启动   -->疑难问题-->解决方法


NetApp Data ONTAP 9.7P23    无法启动   -->疑难问题-->解决方法
NetApp Data ONTAP 9.6P18    无法启动   -->疑难问题-->解决方法
NetApp Data ONTAP 9.5P19    无法启动   -->疑难问题-->解决方法

NetApp Data ONTAP 9.3P21    无法启动   -->疑难问题-->解决方法
NetApp Data ONTAP 9.3P4     无法启动   -->疑难问题-->解决方法
NetApp Data ONTAP 9.1P20    无法启动   -->疑难问题-->解决方法 

node1  ERROR  mcc.config.headswapPartnerEr: Partner node1 failed to 
update configuration due to error Sanown assign request failed

node2  ERROR  mcc.config.headswapPartnerEr: Partner node2 failed to 
update configuration due to error Sanown assign request failed

acp.update.failed                ERROR  
acp.sock.error                   ERROR 
acp.shelf.power.on.failed        INFORMATIONAL
acp.shelf.power.off.failed       INFORMATIONAL
acp.shelf.power.on.failed        INFORMATIONAL
-->疑难问题-->解决方法
raid.assim.tree.noRootVol:error]: No usable root volume was found!
Disk label processing failed!

node2  ERROR  mcc.config.headswapPartnerEr: Partner node-b2 failed to
 update configuration due to error Sanown assign request failed.
 
Could not delete environment variable 'bootarg.init.boot_recovery': 
Environment variable not found
 [localhost:raid.assim.tree.noRootVol:error]: No usable root volume was found! 
 ERROR: Failed to recognize disks
 
 更换控制器后收到错误："mgmtgwd.configbr.backupfailed "
 更换控制器 失败
 -->疑难问题-->解决方法
 ERROR: Failed to recognize disks
 [cluster3:disk.releaseFailed:error]: Disk release failed on 0a.01.0 CDB 0x5f:0603 - SCSI:not ready 
 
 ERROR: Failed to recognize disks: No disks to read.
 [fmmb.instStat.change:info]: no mailbox instance on local side.    (重点错误)
[coredump.host.spare.none:info]: No sparecore disk was found for host 0.  (重点错误)
[raid.assim.tree.noRootVol:error]: No usable root volume was found!   (重点错误)

[monitor.chassisPowerSupply.degraded:notice]: Chassis power supply 2 is degraded: PSU2 is over voltage
[monitor.chassisPowerSupply.degraded:notice]: Chassis power supply 2 is degraded: PSU2 has failed
[monitor.chassisPowerSupply.degraded:notice]: Chassis power supply 2 is degraded: PSU2 DC has failed
[monitor.chassisPowerSupply.degraded:notice]: Chassis power supply 2 is degraded: 
PSU2 Fan1 Speed is Critical Low (2700 RPM)
[callhome.chassis.ps.degraded:error]: Call home for CHASSIS POWER SUPPLY DEGRADED: PS 2

ontap upgrade failed

[fci.adapter.link.online:info]: Fibre Channel adapter 0a link online.
[fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 0c.
[sas.link.error:error]: Could not recover link on SAS adapter 1c after 10 seconds.
 Offlining the adapter.
[sas.link.error:error]: Could not recover link on SAS adapter 1b after 10 seconds. 
Offlining the adapter.

Failed to recover SP
IPMI:Get controller FRU inventory:failed
IPMI:Get midplane FRU 0 inventory:failed
Configuring Devices ...
IPMI PCI Slot Control failed.

即使在更换主板后、已关闭的控制器也无法启动、并显示相同的错误

[SysFW.notice]: Failed to recover SP
[SysFW.critical]: IPMI:Get controller FRU inventory:failed
[SysFW.notice]: IPMI:Get midplane FRU 0 inventory:failed
[Trap Event.critical]: hwassist post_error (26)

 ontap-updates do-download-job  failed Error: Image update failed..
ontap-updates paused-on-error Est: 201 min 0 of 6 updated. Node "":
 Error: Image update failed..

Error: command failed: Install Failed. Cannot update or install image
 because the system management storage area is almost out of space.
To make space available, delete old Snapshot copies. For further
 assistance, contact technical support.

Process package failed.
Control writes attempted: 1; failed: 1

Power Supply installed element list: 1, 2; with error: failed

Channel: 0a failed  -->疑难问题-->解决方法
netapp SP Status   IPMI_HB_OK -->疑难问题-->解决方法

How to troubleshoot "Failed to recover SP"  
or IPMI FRU midplane and inventory errors on FAS and AFF systems

IPMI session creation failed - err(0x0001)

splog_main: splog.warnings:error]: splogd is running in 
degraded mode and having difficulty getting splogs from the SP FW.

sp.userlist.update.failed:error]: Error updating SP user information, 
communication error (op=1, action=6).

Waiting for SP ...
SP failure. Resetting SP from primary FW. This can take a few minutes
Waiting for SP ...
SP failure. Resetting SP from backup FW. This can take a few minutes
Waiting for SP ...
Failed to recover SP
IPMI PCI Slot Control failed.
IPMI:Get controller FRU inventory:failed

Node offline due to failed service processor firmware update during ONTAP update

After the failed firmware update the SP on controller B 
was rebooted and it never came up due to mismatch with ONTAP version.

Ontap Update - Failed to verify the signatures of the image

Service Processor showing Unknown Status -->疑难问题-->解决方法