Multiple disk Missing disks after renaming an aggregate

Last updated

Nov 28, 2024
Save as PDF
Share
1. Share
2. Tweet
3. Share

Views:: 39

Visibility:: Public

Votes:: 0

Category:: aff-series

Specialty:: hw

Last Updated:: 11/28/2024, 9:47:58 AM

Applies to

ONTAP 9
AFF C400

Issue

After renaming an aggregate Ems-logs reports errors of missing disks

[Node-01: config_thread: raid.config.filesystem.disk.missing:info]: File system Disk e5a.10.0.4 Shelf 10 Bay 4 [NETAPP   X4013WBORA7T6NTF NA50] S/N [XXXXXXXXXXXXX] UID [0014EE83:0EAC8680:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000] is missing.

 [Node-01: config_thread: raid.config.filesystem.disk.missing:info]: File system Disk e0d.10.3.8 Shelf 10 Bay 8 [NETAPP   X4013WBORA7T6NTF NA50] S/N [XXXXXXXXXXXXX] UID [0014EE83:0EA9D200:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000] is missing.

 [Node-01: config_thread: raid.config.filesystem.disk.missing:info]: File system Disk e0d.10.3.5 Shelf 10 Bay 5 [NETAPP   X4013WBORA7T6NTF NA50] S/N [XXXXXXXXXXXXX] UID [0014EE83:0EAC7680:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000] is missing.

 [Node-01: config_thread: raid.config.filesystem.disk.missing:info]: File system Disk e0d.10.3.7 Shelf 10 Bay 7 [NETAPP   X4013WBORA7T6NTF NA50] S/N [XXXXXXXXXXXXX] UID [0014EE83:0EACA400:00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000] is missing.

 [Node-01: config_failed_disk: callhome.disks.missing:error]: Call home for MULTIPLE DISKS MISSING

No shelf 10 connected to the system as per the sysconfig -a command
AUDIT-MLOG-TXT in autosupport shows that shelf 10 was connected to the system and the aggregates created by the disks of that shelf were deleted but not as per the best practise

[kern_audit:info:2463] 8003e800014c63fb:8003e800014c79a6 :: Node-01:console :: console :: Node-01:admin :: storage aggregate offline -aggregate aggrname :: Pending

[kern_audit:info:2463] 8003e800014c63fb:8003e800014c79a6 :: Node-01:console :: console :: Node-01:admin :: storage aggregate offline -aggregate aggrname :: Success

[kern_audit:info:2463] 8003e800014c63fb:8003e800014c7aa1 :: Node-01:console :: console :: Node-01:admin :: storage aggregate offline -aggregate aggrname :: Pending

[kern_audit:info:2463] 8003e800014c63fb:8003e800014c7aa1 :: Node-01:console :: console :: Node-01:admin :: storage aggregate offline -aggregate aggrname :: Error: Failed to check if aggrname is a foreign (unknown) aggregate. Reason: entry doesn't exist.

[kern_audit:info:2463] 8003e800014c63fb:8003e800014c7aa2 :: Node-01:console :: console :: Node-01:admin :: storage aggregate offline -aggregate aggrname :: Pending

[kern_audit:info:2463] 8003e800014c63fb:8003e800014c7aa2 :: Node-01:console :: console :: Node-01:admin :: storage aggregate offline -aggregate aggrname :: Success

[kern_audit:info:2463] 8003e800014c63fb:8003e800014c7aa7 :: Node-01:console :: console :: Node-01:admin :: storage aggregate delete -aggregate aaggrname :: Pending

[kern_audit:info:2463] 8003e800014c63fb:8003e800014c7aa7 :: Node-01:console :: console :: Node-01:admin :: storage aggregate delete -aggregate aggrname :: Success

[kern_audit:info:2463] 8003e800014c63fb:8003e800014c7b13 :: Node-01:console :: console :: Node-01:admin :: storage aggregate delete -aggregate aggrname :: Pending

[kern_audit:info:2463] 8003e800014c63fb:8003e800014c7b13 :: Node-01:console :: console :: Node-01:admin :: storage aggregate delete -aggregate aaggrname :: Success