I want to preface that I didn't have the time to test boot option 9a/9c today but will try next chance.
Customer just got a new FAS50 system with 8 internal disks and boot option 4 lands it into loader prompt.
These are the last few lines of the boot process before landing in the loader prompt:
bootarg.bootmenu.selection is |4a|
BOOTMGR: The system has 0 disks assigned whereas it needs 3 to boot, will try to assign the required number.
Feb 03 16:47:47 [localhost:raid.autoPart.disabled:ALERT]: Disk auto-partitioning is disabled on this system: the system needs a minimum of 8 SSDs.
BOOTMGR: already_assigned=0, min_to_boot=3, num_assigned=0
Feb 03 16:47:47 [localhost:callhome.raid.adp.disabled:notice]: Disk auto-partitioning is disabled on this system: ADP DISABLED.
Feb 03 16:47:47 [localhost:diskown.split.shelf.assignStatus:notice]: Split-shelf based automatic drive assignment is "disabled".
Feb 03 16:47:47 [localhost:diskown.split.shelf.assignStatus:notice]: Split-shelf based automatic drive assignment is "disabled".
fm_run0: no local disks found & OFW channel is not up.
fm_run0: OFW read failed, retry cnt: 20
Feb 03 16:48:28 [localhost:cf.fm.noMBDisksOrIc:error]: Could not find the local mailbox disks. Could not determine the firmware state of the partner through the HA interconnect.
Terminated
.
varfs_backup_restore: No checksum generated for oldvarfs.tgz, file not found
Uptime: 2m44s
FM halt: Time 71345 ms, 403873901057 cycles
System halting...
I am unable to create a case yet due to some mixup with how the nodes are registered in mysupport I guess. Hopefully fixed soon but might be days.
I also want to note in case it matters; the nodes came with ONTAP 9.17.1 but were downgraded to 9.16.1P10 via USB to match the cluster they will join.
So I just wanted to check with you folks if there are obvious things I should put on the list of things to check and try.