Skip to main content
NetApp Knowledgebase

Node panics and fails to boot with errors referencing CPU hung, mgwd unresponsive or boot device not found

Views:
992
Visibility:
Public
Votes:
0
Category:
aff-series
Specialty:
hw
Last Updated:

Applies to

  • AFF-A200 | FAS2650
  • AFF-A220 | FAS2750
  • AFF-A300 | FAS8200
  • AFF-A700 | FAS9000
  • x3320A mSATA boot device

Issue

  • The boot device may become suddenly disconnected and the CPU may become hung.
  • The node with the boot device experiencing the issue will panic or fail to reboot and we see one of the following messages:

Panic String:

  • PANIC: thread (xxx) on cpu hung for 4001 milliseconds in process xxx
example
PANIC: thread (swi4: clock) on cpu 0 hung for 4001 milliseconds in process swi4: clock on release 9.5P1 (C) on Thu Jun 11 03:41:13 EDT 2020
 
  • Panic string: Process mgwd unresponsive for 620 seconds in process
  • 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

     

Failure to reboot:
  • 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)

 

 

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