Skip to main content
NetApp Knowledge Base

Node panic and cannot boot up with error "Device not found"

Views:
4,061
Visibility:
Public
Votes:
5
Category:
fas-systems
Specialty:
hw
Last Updated:

Applies to

  • AFF A200 | FAS2620 | FAS2650
  • AFF A220 | AFF C190 | FAS2720 | FAS2750
  • AFF A300 | FAS8200
  • FAS8300
  • AFF A700 | FAS9000
  • AFF A900 | FAS9500
  • mSATA boot device (P/N X3320A)
  • Fails to Boot ONTAP OS

 

Issue

  • Node does not autoboot.
  • After performing "boot_ontap" in loader, system will not boot up and report the following error.
  • Receive similar messages to the following, upon LOADER boot attempt:

LOADER-A> boot_ontap
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)
*** command status = Device not found(-6)

LOADER-A> boot_primary
Loading X86_64/freebsd/image1/kernel:Failed: Device not found
Could not load fat://boot0/X86_64/freebsd/image1/kernel: Device not found
*** command status = Device not found(-6)

LOADER-A> boot_backup
Loading X86_64/freebsd/image2/kernel:Failed: Device not found
Could not load fat://boot0/X86_64/freebsd/image2/kernel: Device not found
*** command status = Device not found(-6)

LOADER-A> boot_ontap
Could not load fat://boot0/X86_64/freebsd/image2/kernel:Unknown error
ERROR: Error booting OS on: 'boot0' file: fat://boot0/X86_64/freebsd/image2/kernel (boot0,fat)
*** command status = Unknown error(-62)

LOADER-A> boot_primary
Loading X86_64/freebsd/image2/kernel:Failed: Unknown error
Could not load fat://boot0/X86_64/freebsd/image2/kernel: Unknown error
*** command status = Unknown error(-62)

LOADER-A> boot_backup
Loading X86_64/freebsd/image1/kernel:Failed: Error
Could not load fat://boot0/X86_64/freebsd/image1/kernel: Error
*** command status = Error(-1)

LOADER-A> boot_recovery
Bootable external device not found!
Boot Recovery failed
*** command status = Error(-1)

  • Similar errors when netbooting and installing ONTAP. Example:

Please choose one of the following:
...
(7) Install new software first.
...
Selection (1-9)? 7

super-block backups (for fsck_ffs -b #) at:
192
******* Working on device /dev/ada0 *******
ada0: CAM_CMD_TIMEOUT, retrying (4 retries left)
ada0: CAM_CMD_TIMEOUT, retrying (3 retries left)
Jul 10 15:45:05 [localhost:ata.timeout.retry:notice]: ATA device timeout (ATA TIMEOUT (retrying), Device ada0:  (4 retries left)).
Partitioning of boot device complete
Install Failed.
fdisk: invalid fdisk partition table found
fdisk: WARNING: adjusting start offset of partition 1
    from 288 to 315, to fall on a head boundary
fdisk: WARNING: adjusting size of partition 1 from 33554016 to 33553989
    to end on a cylinder boundary
fdisk: Failed to write MBR. Try to use gpart(8).
fdisk: Failed to write MBR. Try to use gpart(8).
fdisk: Failed to write MBR. Try to use gpart(8).
fdisk: Failed to write MBR. Try to use gpart(8).
newfs_msdos: /dev/ada0s1: No such file or directory
ERROR: Unable to create a filesystem on the boot device.
umount: /mnt: not a file system root directory

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.
  • Was this article helpful?