Disk copy failed

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 16

Visibility:: Public

Votes:: 0

Category:: fas-systems

Specialty:: hw

Last Updated:

Applies to

ONTAP 9

Issue

In the EMS log report that disk copy started after was aborted
The disk becomes offline before aborted occurs.

Tue Nov 19 10:40:30 +0900 [node1: config_thread: raid.rg.diskcopy.start:notice]: /n2_aggr_sas/plex0/rg1: starting disk copy from 0a.01.8 (S/N [WBN2HBHQ]) to 0a.01.4 (S/N [WBN1BDAQ]). Reason: Disk replace was started..

Tue Nov 19 11:07:29 +0900 [node1: config_thread: raid.disk.offline:notice]: Marking Disk /n2_aggr_sas/plex0/rg1/0a.01.8 Shelf 1 Bay 8 [NETAPP   X343_SSKBE1T8A10 NA04] S/N [WBN2HBHQ] UID [5000C500:9A54D0CF:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000] offline.

Tue Nov 19 11:07:29 +0900 [node1: config_thread: raid_rg_diskcopy_aborted_1:notice]: params: {'owner': '', 'rg': '/n2_aggr_sas/plex0/rg1', 'source': '0a.01.8', 'target': '0a.01.4', 'blockNum': '68567936', 'duration': '26:58.66', 'reason': 'Disk failed in the same RAID group while disk copy operation was in progress.', 'aggregate_uuid': '2de12b49-2074-4518-92e8-8e4f22229718'}