System disruption occurs after temporarily unable to read or write to boot device on A400/FAS8300/FAS8700

EMS Logs

Following are example EMS log entries that might be seen during this condition.

• PANIC: g_vfs_done(): rootfs.uzip read error - suspect boot device in process g_up on release 9.7P4 (C) on Tue Aug 11 02:55:33 EDT 2020
• PANIC: Process mgwd unresponsive for 158 seconds (mgwd startup: "(2139)") in process nodewatchdog
• PANIC: Process vifmgr unresponsive for 658 seconds in process nodewatchdog on release 9.7P18

Console Startup Messages During Failure to Boot

Following are console message that could be seen during an attempted ONTAP boot.

Could not load fat://boot0/X86_64/freebsd/image1/kernel:Device not found

ERROR: Error booting OS on: 'boot0' file: fat://boot0/X86_64/freebsd/image1 /kernel (boot0,fat)

g_vfs_done(): rootfs.uzip read error - suspect boot device in process g_up on release

PANIC: thread (swi4: clock (0)) on cpu 0 hung for 4001 milliseconds in process swi4: clock (0) on release xxx (C) on ...
ERROR: ATA device failure
Version 2.20.1276. Copyright (C) 2021 American Megatrends, Inc.
BIOS Date: 01/19/2021 15:40:12 Ver: 16.3
Press <DEL> or <ESC> to enter setup.
Press <F7> to enter Boot Menu.
Ready to boot. ERROR:
[D9] Boot option loading failed

coredump: processing segment 5, at relative offset 340377600
..........(ada0:ahcich2:0:0:0): WRITE_DMA48. ACB: 35 00 98 05 6c 40 04 00 00 00 00 01
(ada0:ahcich2:0:0:0): CAM status: Command timeout
(ada0:ahcich2:0:0:0): Error 5, Retries exhausted
Aborting dump due to I/O error.
coredump: error: dump compressed: i/o error 'coredump failure' on disk boot device
Failed to dump segments matching 0xf3