netapp fas3240更换控制器后，boot_ontap启动系统自动进入维护模式？

IBM N6240,其实就是OEM netapp fas3240存储，双控配置，其中B控故障，串口连接无输出，随即购买控制器备件更换，按照原厂的更换控制器的手册《Replacing_a_controller_module_in_a_32xx_Data》走的流程。
简单过程就是 把坏了的控制器的B控上的闪存卡 拆到新控制器上，原本是该在在loader界面输入 boot_ontap引导新控制器后，在提示按CTRL-C界面进入boot menu，然后选择进入维护模式，可是在这里按ctrl C就无任何反应，然后系统就自动进入维护模式，再使用disk show -v查看了system id，然后在好的A控制器里执行命令disk reassign –s <old system ID> –d <new system ID>，重启了B控，还是依然进入了维护模式。
目前硬件诊断都通过，无任何硬件错误了，磁盘owner信息也已经和目前的system id一致，ha-config模式也是HA，日期和时间也修改好了，系统版本为8.1.2 7mode,控制器底层的微码两边都一致BIOS version: 5.2.0，Loader version: 3.4，Firmware Version: 1.3.2P1
求大神指点一下，哪里还需要关注一下？
[15:02:57]LOADER-B> printenv
[15:02:57]
[15:02:57]Variable Name Value
[15:02:57]-------------------- --------------------------------------------------
[15:02:57]CPU_NUM_CORES 4
[15:02:57]BOOT_CONSOLE sp0a
[15:02:57]BIOS_VERSION 5.2.0
[15:02:57]BIOS_DATE 03/07/2013
[15:02:57]SYS_MODEL IBM-2858-CN1
[15:02:57]SYS_REV A1
[15:02:57]SYS_SERIAL_NUM 2858C2113A021511
[15:02:57]MOBO_MODEL IBM-2858-CN1
[15:02:57]MOBO_REV A1
[15:02:57]MOBO_SERIAL_NUM 9407320053
[15:02:57]CPU_SPEED 2300
[15:02:57]CPU_TYPE Intel(R) Xeon(R) CPU L5410 @ 2.33GHz
[15:02:57]savenv saveenv
[15:02:57]ENV_VERSION 1
[15:02:57]psm-cc-config? true
[15:02:57]bootarg.mgwd.scsi_blade_uuid 40fd38bc-cead-11e2-82f8-83aa0fdc89fc
[15:02:57]fmmbx-lkg-0 886C254C11E2CEA934129EB4123456780000033200000000BA050650A842BD000000000000000000000000000000000000000000000000000000000000000000BA0506501414BD000000000000000000000000000000000000000000000000000000000000000000
[15:02:58]fmmbx-lkg-0b 886C254C11E2CEA934129EB41234567800000332000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
[15:02:58]last-OS-booted-raid-ver 11
[15:02:58]last-OS-booted-wafl-ver 22331
[15:02:58]last-OS-booted-ver 8.1.2
[15:02:58]partner-sysid 2015191690
[15:02:58]REBOOT_REASON REBOOT_HALT_CMD
[15:02:58]failoverToken N6240b_13:59:09_2017:06:01
[15:02:58]fc-port-0c 9
[15:02:58]fc-port-0d 9
[15:02:58]bootarg.init.sldiag_req true
[15:02:58]BOOT_DEVICE u0a.0
[15:02:58]BOOT_FILE X86_64/freebsd/image1/kernel
[15:02:58]BIOS_INTERFACE 9FC3
[15:02:58]BOOT_FLASH flash0a
[15:02:58]LOADER_VERSION 3.4
[15:02:58]ARCH X86_64
[15:02:58]BOARDNAME SB_XVI
[15:02:58]PRIMARY_KERNEL_URL fat://boot0/X86_64/kernel/primary.krn
[15:02:58]BACKUP_KERNEL_URL fat://boot0/backup/X86_64/kernel/primary.krn
[15:02:58]GX_PRIMARY_KERNEL_URL fat://boot0/X86_64/freebsd/image1/kernel
[15:02:58]GX_DIAG_URL fat://boot0/X86_64/freebsd/image1/kernel
[15:02:59]GX_BACKUP_KERNEL_URL fat://boot0/X86_64/freebsd/image2/kernel
[15:02:59]ntap.init.kernelname X86_64/freebsd/image1/kernel
[15:02:59]FIRMWARE_URL fat://boot0/X86_64/firmware/SB_XVI/firmware.img
[15:02:59]AUTOBOOT true
[15:02:59]AUTOBOOT_FROM PRIMARY
[15:02:59]AUTO_FW_UPDATE true
[15:02:59]BOOTED_FROM OTHER
[15:02:59]boot_ontap autoboot boot0
[15:02:59]boot_primary setenv BOOTED_FROM PRIMARY; boot -elf64 $GX_PRIMARY_KERNEL_URL $PRIMARY_KERNEL_URL
[15:02:59]boot_backup setenv BOOTED_FROM BACKUP; boot -elf64 $GX_BACKUP_KERNEL_URL $BACKUP_KERNEL_URL
[15:02:59]netboot setenv BOOTED_FROM NETWORK; boot -elf64
[15:02:59]boot_diags boot -sld -elf64 $GX_DIAG_URL $PRIMARY_KERNEL_URL
[15:02:59]ldkern load -elf64 $GX_PRIMARY_KERNEL_URL $PRIMARY_KERNEL_URL
[15:02:59]update_flash flash -backup $FIRMWARE_URL flash0a
[15:02:59]version printenv BIOS_VERSION LOADER_VERSION
[15:02:59]BT_BIOS_VERSION 5.2.0
[15:02:59]BT_LOADER_VERSION 3.4
[15:03:51]LOADER-B> version
[15:03:51]
[15:03:51]Variable Name Value
[15:03:51]-------------------- --------------------------------------------------
[15:03:51]BIOS_VERSION 5.2.0
[15:03:51]LOADER_VERSION 3.4