Solved: Re: Nexus N9K-C9372TX no free pages availableLoading intird failed: 27

ecomengineer · ‎02-08-2023

Hi all,

I have a Cisco nexus N9K-C9372TX stuck in the loader prompt. I have the nxos copied in the bootflash. I have tried 2 options.

First option -

I tried to boot directly from tftp and received the following error:

#########################################################################

loader > boot tftp://172.22.115.243/nxos.7.0.3.I7.9.bin
Booting tftp://172.22.115.243/nxos.7.0.3.I7.9.bin
Trying netboot
Filename: /nxos.7.0.3.I7.9.bin
Address: 172.22.115.245
Netmask: 255.255.0.0
Server: 172.22.115.243
Gateway: 172.22.115.99
Filesystem type is tftp, using whole disk
......no free pages availableLoading intird failed: 27
Boot failed

Error 9: Unknown boot failure

loader >

#########################################################################

Second option -

I tried to boot from the bootflash and received the following error:

#########################################################################

loader > boot bootflash://nxos.7.0.3.I7.9.bin
Booting bootflash://nxos.7.0.3.I7.9.bin
Trying diskboot
Filesystem type is ext2fs, partition type 0x83
Image valid

Image Signature Verification Failed.

Boot failed

Error 9: Unknown boot failure

loader >

After the above error, when I hit the Esc key on my keyboard, it shows the following output:

loader > Trying to read config file /boot/grub/menu.lst.local from (hd0,5)
Filesystem type is ext2fs, partition type 0x83

Booting bootflash:/nxos.7.0.3.I7.9.bin ...
Booting bootflash:/nxos.7.0.3.I7.9.bin
Trying diskboot
Filesystem type is ext2fs, partition type 0x83
no free pages availableLoading intird failed: 27
Boot failed
No autoboot or failed autoboot. falling to loader

Loader Version 7.17

#########################################################################

I have never seen this error "no free pages availableLoading intird failed: 27" before and have no clue what is going on and how to recover the switch from the loader prompt.

Any help will be much appreciated. Thanks!

sp2720401 · ‎02-22-2023

Backup the licenses and configuration to USB or to SCP server.

Boot an older NX-OS from USB. Use the latest 6.X NX-OS (and kickstart if required) then format the bootflash. Then boot from USB to the first available 7.X NX-OS and format the bootflash again.

All IOS updates should inlcude the EPLD and BIOS as parts of the upgrade.

View solution in original post

M02@rt37 · ‎02-10-2023

Hello @ecomengineer

The error message "Loading intird failed: 27" is related to the loading of the IOS image on a Cisco device. This error message typically indicates that there is not enough memory available on the device to load the IOS image.

You could try:

- Check the memory requirements for the IOS image you are trying to load and verify that the device has enough memory to support it.

- Delete unnecessary files and processes on the device to free up memory. You can use the "show memory" command to see the amount of memory available on the device

- Try to use a different IOS image with lower memory requirements.

Best regards
.ı|ı.ı|ı. If This Helps, Please Rate .ı|ı.ı|ı.

ecomengineer · ‎02-13-2023

Hi M02@rt37,

Thanks for your reply. I agree with you that most likely there is not enough memory available on the device.

However, the problem is that it is a Cisco Nexus switch which is stuck in loader> prompt, therefore I'm not able to run any show commands on it.

Is there any way to see the available memory and delete files from Cisco Nexus device which is stuck at loader> prompt?

M02@rt37 · ‎02-13-2023

Hi @ecomengineer

you can see the available memory and delete files from a Cisco Nexus device that is stuck at the loader> prompt by using the built-in loader functions.

Use the "dir" command to see the available files and their sizes. Then, use the "delete" command followed by the file name to delete the desired file. To check the available memory, use the "meminfo" command.

Best regards
.ı|ı.ı|ı. If This Helps, Please Rate .ı|ı.ı|ı.

ecomengineer · ‎03-01-2023

Hi M02@rt37, the commands "delete" and "meminfo" didn't work/aren't available. See the below output for all the things that were tried -

loader > dir

bootflash::

lost+found

.patch

n9000-dk9.7.0.3.I1.3.bin

n9000-epld.7.0.3.I1.3.img

home

license_SAL1951VEP6_12.lic

.patch-issu

virtual-instance

scripts

20160104_152921_poap_6587_init.log

20160301_103151_poap_6315_init.log

nxos.7.0.3.I2.2c.bin

20160407_143730_poap_6318_init.log

nxos.7.0.3.I7.9.bin

.rpmstore

nxos.9.3.6.bin

evt_log_snapshot

.swtam

eem_snapshots

loader > meminfo

Error 27: Unrecognized command

loader > delete

Error 27: Unrecognized command

loader > cmdline meminfo

loader > cmdline delete

loader > cmdline delete 20160104_152921_poap_6587_init.log

loader > dir

bootflash::

lost+found

.patch

n9000-dk9.7.0.3.I1.3.bin

n9000-epld.7.0.3.I1.3.img

home

license_SAL1951VEP6_12.lic

.patch-issu

virtual-instance

scripts

20160104_152921_poap_6587_init.log

20160301_103151_poap_6315_init.log

nxos.7.0.3.I2.2c.bin

20160407_143730_poap_6318_init.log

nxos.7.0.3.I7.9.bin

.rpmstore

nxos.9.3.6.bin

evt_log_snapshot

.swtam

eem_snapshots

loader > cmdline delete "20160104_152921_poap_6587_init.log"

loader > dir

bootflash::

lost+found

.patch

n9000-dk9.7.0.3.I1.3.bin

n9000-epld.7.0.3.I1.3.img

home

license_SAL1951VEP6_12.lic

.patch-issu

virtual-instance

scripts

20160104_152921_poap_6587_init.log

20160301_103151_poap_6315_init.log

nxos.7.0.3.I2.2c.bin

20160407_143730_poap_6318_init.log

nxos.7.0.3.I7.9.bin

.rpmstore

nxos.9.3.6.bin

evt_log_snapshot

.swtam

eem_snapshots

loader > cmdline init_system

loader > dir

bootflash::

lost+found

.patch

n9000-dk9.7.0.3.I1.3.bin

n9000-epld.7.0.3.I1.3.img

home

license_SAL1951VEP6_12.lic

.patch-issu

virtual-instance

scripts

20160104_152921_poap_6587_init.log

20160301_103151_poap_6315_init.log

nxos.7.0.3.I2.2c.bin

20160407_143730_poap_6318_init.log

nxos.7.0.3.I7.9.bin

.rpmstore

nxos.9.3.6.bin

evt_log_snapshot

.swtam

eem_snapshots

loader > cmdline recoverymode=1

loader > boot nxos.7.0.3.I7.9.bin

Booting nxos.7.0.3.I7.9.bin

Trying diskboot

Filesystem type is ext2fs, partition type 0x83

Image valid

Image Signature Verification Failed.

Boot failed

Error 9: Unknown boot failure

usb2::

System Volume Information

nxos.7.0.3.I7.9.bin

bootflash::

lost+found

.patch

n9000-dk9.7.0.3.I1.3.bin

n9000-epld.7.0.3.I1.3.img

home

license_SAL1951VEP6_12.lic

.patch-issu

virtual-instance

scripts

20160104_152921_poap_6587_init.log

20160301_103151_poap_6315_init.log

nxos.7.0.3.I2.2c.bin

20160407_143730_poap_6318_init.log

nxos.7.0.3.I7.9.bin

.rpmstore

nxos.9.3.6.bin

evt_log_snapshot

.swtam

eem_snapshots

loader > boot usb2:/nxos.7.0.3.I7.9.bin

Booting usb2:/nxos.7.0.3.I7.9.bin

Trying diskboot

Filesystem type is fat, partition type 0xb

no free pages availableLoading intird failed: 27

Boot failed

Error 9: Unknown boot failure

loader >

sp2720401 · ‎02-22-2023

Backup the licenses and configuration to USB or to SCP server.

Boot an older NX-OS from USB. Use the latest 6.X NX-OS (and kickstart if required) then format the bootflash. Then boot from USB to the first available 7.X NX-OS and format the bootflash again.

All IOS updates should inlcude the EPLD and BIOS as parts of the upgrade.

ecomengineer · ‎03-01-2023

Hi @sp2720401 thanks for your response. We will try these and update here with the results.

ecomengineer · ‎03-14-2023

Hi @sp2720401 using the process of bootable USB helped in resolving the issue. We were able to boot an older NXOS 6.X from the USB and format the bootflash. Then we upgraded to NXOS 7.X and now the switch is back in normal mode and working fine.