Issues joining F710 nodes with OneFS 9.10 installed to clusters running OneFS 9.7

From the cluster: Run: isi devices nodes list from any node in the cluster.

TESTCLUSTERF710-3# isi devices node list
Serial Number  Product                                       Version           Status
----------------------------------------------------------------------------------------
XXXXXXX        F710-1U-Dual-512GB-2x1GE-2x25GE SFP+-38TB SSD B_MR_9_10_0_0_007R available
----------------------------------------------------------------------------------------
Total: 1
TESTCLUSTERF710-3#

If you are serial attached to the node, check the join wizard banner:

Welcome to the PowerScale configuration wizard.
Copyright (c) 2001-2024 Dell Inc. All Rights Reserved.
Enter 'help' at any prompt for additional information on that step.
Enter 'back' at any prompt to return to previous step.
Enter 'quit' at any prompt to discard all changes.
Enter 'manual' at any prompt to switch to manual mode (console).
 
               Node build: Isilon OneFS 9.10.0.0 B_9_10_0_0_007(RELEASE)
               Node serial number: XXXXXXX
 
Select an option:
               [ 1] Create a new cluster
               [ 2] Join an existing cluster
               [ 3] Exit wizard and configure manually
               [ 4] Reboot into SmartLock Compliance mode
Wizard >>>

If the nodes were reimaged or joined to the cluster, run isi_psi get uint64 installation.devices.bootdisk.partition_reserve:

TESTCLUSTERF710-3# isi_psi get uint64 installation.devices.bootdisk.partition_reserve
8589934592
TESTCLUSTERF710-3#

If the node has Self-Encrypted Drives (SEDs), you see the node panic during the join attempt:

panic @ time 1740683810.247, thread 0xfffffebafbd9e5c0: ufs_dirbad: /: bad dir ino 79694 at offset 0: mangled entry
time = 1740683810
Uptime: 2m24s
cpuid = 92, TSC = 0xd1e7b2c775
Panic occurred in module kernel loaded at 0xffffffff80200000:

Stack: --------------------------------------------------
kernel:ufs_lookup_ino+0xec0
kernel:VOP_CACHEDLOOKUP_APV+0x89
kernel:vfs_cache_lookup+0xd5
kernel:VOP_LOOKUP_APV+0x89
kernel:lookup+0x755
kernel:namei+0x4bd
kernel:_vn_open_cred+0x462
kernel:_vn_open+0x1e
kernel:isi_kern_openat+0x3b3
kernel:sys_openat+0x59
kernel:amd64_syscall+0x380
--------------------------------------------------

After the panic messaging finishes, you will see:

Initializing PCIe, USB, and Video... Done
PowerScale F710
BIOS Version: 2.3.5


F2 = System Setup
F10 = Lifecycle Controller (Config
   iDRAC, Update FW, Install OS)
F11 = Boot Manager
F12 = PXE Boot
iDRAC IPV4:  172.26.248.52 [Dedicated]
                                
Initializing Firmware Interfaces...
 
Enumerating Boot options...
Enumerating Boot options... Done
Persistent Memory Restore Complete [No Errors]
Loading Lifecycle Controller Drivers...
Loading Lifecycle Controller Drivers...Done
Lifecycle Controller: Collecting System Inventory...

iDRAC IPV4:  xxx.xxx.xxx.xxx [Dedicated]

Lifecycle Controller: Done
Booting...
Booting from OS_1
Boot Failed: OS_1

Booting from OS_2
Boot Failed: OS_2

Booting from PCIe SSD in Slot 9 in Bay 1: EFI Fixed Disk Boot Device 1
Boot Failed: PCIe SSD in Slot 9 in Bay 1: EFI Fixed Disk Boot Device 1

Booting from PCIe SSD in Slot 2 in Bay 1: EFI Fixed Disk Boot Device 2
Boot Failed: PCIe SSD in Slot 2 in Bay 1: EFI Fixed Disk Boot Device 2

No boot device available or Operating System detected. 
Please ensure a compatible bootable media is available.

Available Actions: 
F1 to Continue and Retry Boot Order 
F2 for System Setup (BIOS) 
F10 for Lifecycle Controller 
- Enable/Configure iDRAC 
- Update Server Firmware 
- Help Install an Operating System 
F11 for Boot Manager

All the above are examples of nodes that must be remediated. Contact support and quote this knowledge base document.
If you have not yet attempted to join the node to the cluster, there is a cluster patch to resolve the issue. The patch is available on the support site here.