Skip to main content
NetApp Knowledge Base

Multi-Disk Error Causes Node to Reboot

Views:
24
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
hw
Last Updated:

Applies to

  • All FAS and AFF models
  • ONTAP 9
  • V-Series Backend

Issue

Multi disk panic causes a node to reboot. The following error messages are seen in EMS:
 
EMS Error Message:
 
Sat Sep 04 15:56:53 EDT [cluster-01: config_thread: raid.vol.failed:notice]: Aggregate aggr1: Failed due to multi-disk error.
Sat Sep 04 15:56:53 EDT [cluster-01: config_thread: callhome.fdsk.fault:error]: Call home for FILESYSTEM DISK FAILED Shelf -, Bay -, Model [VRAID], S/N [6006016015603C0044145347182DE8110]
Sat Sep 04 15:56:53 EDT [cluster-01: raid_disk_thread: raid.disk.unload.done:info]: Unload of Disk NanoFCS01B:34.126L26 Shelf - Bay - [DGC VRAID 0533] S/N [6006016015603C0044145347182DE811] UID [60060160:15603C00:44145347:182DE811:00000000:00000000:00000000:00000000:00000000:00000000] has completed successfully
Sat Sep 04 15:56:53 EDT [cluster-01: config_thread: cf.multidisk.fatalProblem:info]: Node encountered a multidisk error or other fatal error while waiting to be taken over. aggr1: raid volfsm, fatal disk error in RAID group with no parity disk. raid type raid0 Group name plex0/rg1 state NORMAL 1 disk failed in the group. Disk NanoFCS01B:34.126L26 Shelf - Bay - [DGC VRAID 0533] S/N [6006016015603C0044145347182DE811] UID [60060160:15603C00:44145347:182DE811:00000000:00000000:00000000:00000000:00000000:00000000] error fatal disk error..
CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support

 

  • Was this article helpful?